Hi all,
This is a public callout to QGIS developers/support organisations to
see whether there's currently any work underway, or planned to
commence shortly, regarding any aspect of datum transformation within
QGIS.
Specifically,
- is anyone planning on continuing the work begun in 3.0 for
On Sat, 3 Nov 2018 at 07:27, C Hamilton wrote:
>
> In my KML Tools processing plugin algorithm I create a feature sink as
> follows:
>
> (self.sinkPt, self.dest_id_pt) = self.parameterAsSink(self.parameters,
> self.PrmPointOutputLayer, self.context, fields,
>
On Sat, 3 Nov 2018 at 19:32, Jürgen E. Fischer wrote:
>
> Hi Marco,
>
> On Wed, 24. Oct 2018 at 22:52:06 +0200, Marco Bernasocchi wrote:
> > To me would be a +1 but probably, would be nice to get Jef opinion?
>
> I don't have anything to add - dropping xenial support after 3.4 is fine with
> me.
On Sat, 3 Nov 2018 at 22:32, Anita Graser wrote:
>
> Hi,
>
> There's something weird going on in the Processing script editor. It mangles
> the code it displays, as reported in https://issues.qgis.org/issues/20349
>
> It happens on Windows and Mac. Can you reproduce it on Linux?
Yes -- PR
Hi,
ne 4. 11. 2018 v 20:53 odesílatel Martin Landa napsal:
> -D PYTHON_LIBRARY=/usr/lib/x86_64-linux-gnu/libpython3.6.so \
hm, seems to be problem here. libpython3.6 comes with
/usr/lib/x86_64-linux-gnu/libpython3.6m.so.1.
Thanks for pointers, Ma
--
Martin Landa
Hi,
ne 4. 11. 2018 v 13:41 odesílatel Jorge Gustavo Rocha
napsal:
> Do you have libpython3.6 installed? (Which is your OS, by the way?)
yes,
$ sudo apt policy libpython3.6
libpython3.6:
Installed: 3.6.7-1
Running Debian testing.
QGIS configured by
cmake -D WITH_BINDINGS=ON \
Hi Martin,
Do you have libpython3.6 installed? (Which is your OS, by the way?)
I have libpython3.6.so installed from libpython3.6 package.
On my Ubuntu 18.04, it is at:
jgr@zoe:~$ dpkg -L libpython3.6 | grep libpython3.6.so$
/usr/lib/python3.6/config-3.6m-x86_64-linux-gnu/libpython3.6.so
On Thu, 1 Nov 2018 at 08:18, Pedro Venâncio wrote:
>
> Hi Nyall,
>
>>
>> > (tools not
>> > working when windows regional settings are not set to English and also
>>
>> Someone else will need to fix this one, it's not something I can
>> reproduce. Any volunteers? If there's none, we shouldn't hold
