Re: [QGIS-Developer] Feature freeze / exemptions

[Nyall Dawson]

On Wed, 5 Sep 2018 at 15:13, Matthias Kuhn  wrote:
>
> Feature freeze is coming end of next week with a freeze window of 6 weeks. In 
> the past, we have regularly granted freeze exemptions to some features upon 
> request.
>
> I think it would be good to know, what we can expect this time to decide on 
> what is granted and then send them over to Loomio for review.
>
> Myself, I would like to include Geometry Validation 
> (https://github.com/qgis/QGIS-Enhancement-Proposals/issues/131). I estimate 
> will require about 1 to maximum 2 more week to get it into a mergeable state, 
> which will still leave us with 4-5 weeks of bugfixing time for this code. One 
> part of it is, it will revisit some of the geometry checker code which is 
> corrected for threading and other issues, so that can already be seen as 
> "bugfixing of existing code" that will land as part of it.

I would also like to pre-emptively apply for a freeze exemption for
the work detailed in
https://github.com/qgis/QGIS-Enhancement-Proposals/issues/114 and
currently the target of the crowd funding campaign at
https://north-road.com/edit-features-in-place-using-qgis-spatial-operations-campaign/

The fund raising is proceeding nicely and I believe this work will be
successfully funded, and I'd love to get it in for 3.4. I'd estimate
1-2 weeks post freeze for merge.

Nyall
___
QGIS-Developer mailing list
QGIS-Developer@lists.osgeo.org
List info: https://lists.osgeo.org/mailman/listinfo/qgis-developer
Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-developer

Re: [QGIS-Developer] Feature freeze / exemptions

[Paolo Cavallini]

Hi Matthias,

Il 09/05/2018 07:13 AM, Matthias Kuhn ha scritto:
>
> Feature freeze is coming end of next week with a freeze window of 6
> weeks. In the past, we have regularly granted freeze exemptions to
> some features upon request.
>
> I think it would be good to know, what we can expect this time to
> decide on what is granted and then send them over to Loomio for review.
>
> Myself, I would like to include Geometry Validation
> (https://github.com/qgis/QGIS-Enhancement-Proposals/issues/131). I
> estimate will require about 1 to maximum 2 more week to get it into a
> mergeable state, which will still leave us with 4-5 weeks of bugfixing
> time for this code. One part of it is, it will revisit some of the
> geometry checker code which is corrected for threading and other
> issues, so that can already be seen as "bugfixing of existing code"
> that will land as part of it.
>
thanks for this request - this is indeed a gray area that has caused
some discomfort in the past, so it will be good to have more clear
guidelines. I think it will be difficult to carve them in stone however;
some ad hoc evaluation will be necessary.
Maybe we can ask three questions:
* should we set a hard limit for freeze (e.g. no exemption in the last X
weeks), or we can decide anytime based on the merit of the code submitted?
* whom should decide on this? I personally think core developers should
have a much heavier weight in this decision than PSC
* based on which (more or less objective) criteria? This could include
isolation of code,  i.e. likelihood that it will break other parts,
importance of the new feature for the majority of users, quality of the
code, commitment to promptly fix bugs.
All the best.

-- 
Paolo Cavallini - www.faunalia.eu
QGIS & PostGIS courses: http://www.faunalia.eu/training.html
https://www.google.com/trends/explore?date=all=IT=qgis,arcgis


___
QGIS-Developer mailing list
QGIS-Developer@lists.osgeo.org
List info: https://lists.osgeo.org/mailman/listinfo/qgis-developer
Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-developer

[QGIS-Developer] Feature freeze / exemptions

[Matthias Kuhn]

Feature freeze is coming end of next week with a freeze window of 6
weeks. In the past, we have regularly granted freeze exemptions to some
features upon request.

I think it would be good to know, what we can expect this time to decide
on what is granted and then send them over to Loomio for review.

Myself, I would like to include Geometry Validation
(https://github.com/qgis/QGIS-Enhancement-Proposals/issues/131). I
estimate will require about 1 to maximum 2 more week to get it into a
mergeable state, which will still leave us with 4-5 weeks of bugfixing
time for this code. One part of it is, it will revisit some of the
geometry checker code which is corrected for threading and other issues,
so that can already be seen as "bugfixing of existing code" that will
land as part of it.

Thanks a lot and best regards

-- 
Matthias Kuhn
matth...@opengis.ch 
+41 (0)76 435 67 63 
OPENGIS.ch Logo 
___
QGIS-Developer mailing list
QGIS-Developer@lists.osgeo.org
List info: https://lists.osgeo.org/mailman/listinfo/qgis-developer
Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-developer

Re: [QGIS-Developer] MAC QGIS 3.x build

[William Kyngesburye]

> On Sep 4, 2018, at 4:24 AM, Nyall Dawson  wrote:
> 
> On Tue, 4 Sep 2018 at 19:19, David Marteau  > wrote:
>> 
>> Hi Peter,
>> 
>> Warning, if you are using macport: qt5.11 is installed by default and you 
>> may (or may not)  experience some display problems, instead you may choose 
>> to stick to qt5.9 by installing
>> 
>> the 'qt59' port
> 
> Is that the infamous "small canvas" issue?
> 
I don't know about that, I use Qt 5.9 in my official build, and it has the 
small canvas problem.

-
William Kyngesburye 
http://www.kyngchaos.com/

"We are at war with them. Neither in hatred nor revenge and with no particular 
pleasure I shall kill every ___ I can until the war is over. That is my duty."

"Don't you even hate 'em?"

"What good would it do if I did? If all the many millions of people of the 
allied nations devoted an entire year exclusively to hating the  it 
wouldn't kill one ___ nor shorten the war one day."

 "And it might give 'em all stomach ulcers."

- Tarzan, on war

___
QGIS-Developer mailing list
QGIS-Developer@lists.osgeo.org
List info: https://lists.osgeo.org/mailman/listinfo/qgis-developer
Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-developer

Re: [QGIS-Developer] MAC QGIS 3.x build

[William Kyngesburye]

Yeah, I haven't updated the build instructions for QGIS 3.  It took me a while 
to get going on figuring out all the new stuff (I've had a lot of distraction 
the past year or so).

I don't have any published scripts for the official build.  Mostly it's just 
following the build instructions (what they would be when I update them), plus 
a bundling script for the extras bundled in the app (not necessary for anyone 
installing from source).

Thanks for the reminder that the instructions need updating.

Last I heard, homebrew wasn't quite ready with a 3.x build.

> On Sep 4, 2018, at 4:04 AM, Peter Petrik  
> wrote:
> 
> Hi,
> 
> As a (happy) Linux user, I switched to Mac (High Sierra 10.13.6) for some 
> QGIS development and I see that 
> https://github.com/qgis/QGIS/blob/master/INSTALL 
>  still suggests qt4 and 
> python 2.6 for Mac. Does anyone has a suggestion what to use/read to 
> facilitate the building of current master and get quickly up-to-speed? 
> 
> Also, can you please point me to the scripts/repositories that are used for 
> official Mac releases?
> 
> I have found https://github.com/OSGeo/homebrew-osgeo4mac 
> , but I am not sure if that can 
> be used for development?
> 
> Thanks a lot for any ideas! 
> Peter
> ___
> QGIS-Developer mailing list
> QGIS-Developer@lists.osgeo.org
> List info: https://lists.osgeo.org/mailman/listinfo/qgis-developer
> Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-developer

-
William Kyngesburye 
http://www.kyngchaos.com/

"Oh, look, I seem to have fallen down a deep, dark hole.  Now what does that 
remind me of?  Ah, yes - life."

- Marvin


___
QGIS-Developer mailing list
QGIS-Developer@lists.osgeo.org
List info: https://lists.osgeo.org/mailman/listinfo/qgis-developer
Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-developer

Re: [QGIS-Developer] Some initial OpenCL feedback

[Alessandro Pasotti]

On Tue, Sep 4, 2018 at 4:57 PM Andreas Neumann  wrote:

> Hi Alessandro,
>
> Thanks for the clarification that only the change of the OpenCL-device
> needs a restart.
>
> I tried both - acceleration in CPU and in GPU. I had the impression that
> the acceleration in the CPU was slightly faster than in the CPU - but not a
> lot faster. Maybe the GPU (Intel HD Graphics 4600) is not too powerful. It
> is a ThinkPad notebook, not a desktop.
>

Thanks for the info!

Yes, maybe that the lower I/O (there is no need to transfer data to/from
the graphic card) compensates the slower processing on the CPU

Cheers

Greetings,
>
> Andreas
>
> On 2018-09-04 15:56, Alessandro Pasotti wrote:
>
>
> On Tue, Sep 4, 2018 at 2:21 PM Andreas Neumann 
> wrote:
>
>> Hi Alessandro,
>>
>> I just tested if the hardware acceleration (OpenCL) helps in the live
>> hillshade renderer.
>>
>
>
> Hi Andreas,
>
> thanks a lot for your feedback, I honestly am a little worried about the
> possible problems on different platforms, graphic cards and driver
> versions, I choose to stay on the safe side and there is a safeguard that
> disables the OpenCL support at the first issue in the renderer.
>
> The processing algs looks generally more stable (never got a single crash
> myself).
>
>
>
>> The good news is that it works stable so far and substantially improves
>> rendering time of the live hillshade renderer. My notebook on my workplace
>> is rather slow. Without hardware acceleration it renders the hillshade in
>> approx 8 seconds (large window on two screens). With OpenCL acceleration
>> set to on, it renders in about 1 second or even less. I assume quite some
>> time is also spent on reading the file. This with resampling on (average
>> for zooming out and bilinear for zooming in beyond native resolution).
>>
>
> Yes some time is spent on reading the file and some time is spend on I/O
> tranferring data to/from the graphic card, this means that the performance
> gain is usually higher on larger images than on smaller images.
>
>
>> Hardware is an Intel HD Graphics 4600. The CPU is also listed as
>> supported.
>>
>
> Can you also try the CPU? I'm curious about the performances.
>
>
>> Visually, with or without HW accelation on, there still are some
>> rectangular artefacts in both versions.
>>
>
> Yes: that does not change, the algorithm is pretty much the same in both
> implementations.
>
>
>
>> Tested on Windows.
>>
>> --
>>
>> One more thing: on my machine there is no restart of QGIS necessary for
>> the changes (HW acceleration on of off) to be applied. This is contrary to
>> the statement in the settings dialogue, which says, that a restart of QGIS
>> is necessary.
>>
>
> The text can probably be improved: what needs a restart is if you change
> the device, enabling and disabling OpenCL support does not require a
> restart.
>
>
>> ---
>>
>> Thanks a lot for your work!
>>
>
>
> Thank you for the feedback!
>
>
>
>
> --
> Alessandro Pasotti
> w3:   www.itopen.it
>
>
>

-- 
Alessandro Pasotti
w3:   www.itopen.it
___
QGIS-Developer mailing list
QGIS-Developer@lists.osgeo.org
List info: https://lists.osgeo.org/mailman/listinfo/qgis-developer
Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-developer

Re: [QGIS-Developer] Some initial OpenCL feedback

[Andreas Neumann]

Hi Alessandro, 

Thanks for the clarification that only the change of the OpenCL-device
needs a restart. 

I tried both - acceleration in CPU and in GPU. I had the impression that
the acceleration in the CPU was slightly faster than in the CPU - but
not a lot faster. Maybe the GPU (Intel HD Graphics 4600) is not too
powerful. It is a ThinkPad notebook, not a desktop. 

Greetings, 

Andreas 

On 2018-09-04 15:56, Alessandro Pasotti wrote:

> On Tue, Sep 4, 2018 at 2:21 PM Andreas Neumann  wrote: 
> 
>> Hi Alessandro, 
>> 
>> I just tested if the hardware acceleration (OpenCL) helps in the live 
>> hillshade renderer.
> 
> Hi Andreas,  
> 
> thanks a lot for your feedback, I honestly am a little worried about the 
> possible problems on different platforms, graphic cards and driver versions, 
> I choose to stay on the safe side and there is a safeguard that disables the 
> OpenCL support at the first issue in the renderer. 
> 
> The processing algs looks generally more stable (never got a single crash 
> myself). 
> 
>> The good news is that it works stable so far and substantially improves 
>> rendering time of the live hillshade renderer. My notebook on my workplace 
>> is rather slow. Without hardware acceleration it renders the hillshade in 
>> approx 8 seconds (large window on two screens). With OpenCL acceleration set 
>> to on, it renders in about 1 second or even less. I assume quite some time 
>> is also spent on reading the file. This with resampling on (average for 
>> zooming out and bilinear for zooming in beyond native resolution).
> 
> Yes some time is spent on reading the file and some time is spend on I/O 
> tranferring data to/from the graphic card, this means that the performance 
> gain is usually higher on larger images than on smaller images. 
> 
>> Hardware is an Intel HD Graphics 4600. The CPU is also listed as supported.
> 
> Can you also try the CPU? I'm curious about the performances. 
> 
>> Visually, with or without HW accelation on, there still are some rectangular 
>> artefacts in both versions.
> 
> Yes: that does not change, the algorithm is pretty much the same in both 
> implementations. 
> 
>> Tested on Windows. 
>> 
>> -- 
>> 
>> One more thing: on my machine there is no restart of QGIS necessary for the 
>> changes (HW acceleration on of off) to be applied. This is contrary to the 
>> statement in the settings dialogue, which says, that a restart of QGIS is 
>> necessary.
> 
> The text can probably be improved: what needs a restart is if you change the 
> device, enabling and disabling OpenCL support does not require a restart. 
> 
>> --- 
>> 
>> Thanks a lot for your work!
> 
> Thank you for the feedback! 
> 
> -- 
> Alessandro Pasotti
> w3:   www.itopen.it [1]

 

Links:
--
[1] http://www.itopen.it___
QGIS-Developer mailing list
QGIS-Developer@lists.osgeo.org
List info: https://lists.osgeo.org/mailman/listinfo/qgis-developer
Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-developer

Re: [QGIS-Developer] Some initial OpenCL feedback

[Alessandro Pasotti]

On Tue, Sep 4, 2018 at 2:21 PM Andreas Neumann  wrote:

> Hi Alessandro,
>
> I just tested if the hardware acceleration (OpenCL) helps in the live
> hillshade renderer.
>


Hi Andreas,

thanks a lot for your feedback, I honestly am a little worried about the
possible problems on different platforms, graphic cards and driver
versions, I choose to stay on the safe side and there is a safeguard that
disables the OpenCL support at the first issue in the renderer.

The processing algs looks generally more stable (never got a single crash
myself).


The good news is that it works stable so far and substantially improves
> rendering time of the live hillshade renderer. My notebook on my workplace
> is rather slow. Without hardware acceleration it renders the hillshade in
> approx 8 seconds (large window on two screens). With OpenCL acceleration
> set to on, it renders in about 1 second or even less. I assume quite some
> time is also spent on reading the file. This with resampling on (average
> for zooming out and bilinear for zooming in beyond native resolution).
>

Yes some time is spent on reading the file and some time is spend on I/O
tranferring data to/from the graphic card, this means that the performance
gain is usually higher on larger images than on smaller images.

Hardware is an Intel HD Graphics 4600. The CPU is also listed as supported.
>

Can you also try the CPU? I'm curious about the performances.


> Visually, with or without HW accelation on, there still are some
> rectangular artefacts in both versions.
>

Yes: that does not change, the algorithm is pretty much the same in both
implementations.



> Tested on Windows.
>
> --
>
> One more thing: on my machine there is no restart of QGIS necessary for
> the changes (HW acceleration on of off) to be applied. This is contrary to
> the statement in the settings dialogue, which says, that a restart of QGIS
> is necessary.
>

The text can probably be improved: what needs a restart is if you change
the device, enabling and disabling OpenCL support does not require a
restart.


> ---
>
> Thanks a lot for your work!
>


Thank you for the feedback!




-- 
Alessandro Pasotti
w3:   www.itopen.it
___
QGIS-Developer mailing list
QGIS-Developer@lists.osgeo.org
List info: https://lists.osgeo.org/mailman/listinfo/qgis-developer
Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-developer

Re: [QGIS-Developer] The gitter bridge doesn't support private messaging, or inviting to rooms.

[DelazJ]

Hi,

Thanks to the person who fixed this issue.

Regards,
Harrissou

Le lun. 3 sept. 2018 à 14:58, Tom Chadwin  a
écrit :

> I was literally about to post this same message - I've left the QGIS Gitter
> room because of the issue.
>
> Thanks, Harrissou
>
> Tom
>
>
>
> -
> Buy Pie Spy: Adventures in British pastry 2010-11 on Amazon
> --
> Sent from:
> http://osgeo-org.1560.x6.nabble.com/QGIS-Developer-f4099106.html
> ___
> QGIS-Developer mailing list
> QGIS-Developer@lists.osgeo.org
> List info: https://lists.osgeo.org/mailman/listinfo/qgis-developer
> Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-developer
___
QGIS-Developer mailing list
QGIS-Developer@lists.osgeo.org
List info: https://lists.osgeo.org/mailman/listinfo/qgis-developer
Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-developer

Re: [QGIS-Developer] MAC QGIS 3.x build

[David Marteau]

> Le 4 sept. 2018 à 15:12, William Kyngesburye  a écrit :
> 
> 
>> On Sep 4, 2018, at 4:24 AM, Nyall Dawson > > wrote:
>> 
>> On Tue, 4 Sep 2018 at 19:19, David Marteau > > wrote:
>>> 
>>> Hi Peter,
>>> 
>>> Warning, if you are using macport: qt5.11 is installed by default and you 
>>> may (or may not)  experience some display problems, instead you may choose 
>>> to stick to qt5.9 by installing
>>> 
>>> the 'qt59' port
>> 
>> Is that the infamous "small canvas" issue?
>> 
> I don't know about that, I use Qt 5.9 in my official build, and it has the 
> small canvas problem.

It is more about the "slowness" problem on Mac: 
https://trac.macports.org/ticket/56915  
 , https://issues.qgis.org/issues/19546

> 
> -
> William Kyngesburye 
> http://www.kyngchaos.com/ 
> 
> "We are at war with them. Neither in hatred nor revenge and with no 
> particular pleasure I shall kill every ___ I can until the war is over. That 
> is my duty."
> 
> "Don't you even hate 'em?"
> 
> "What good would it do if I did? If all the many millions of people of the 
> allied nations devoted an entire year exclusively to hating the  it 
> wouldn't kill one ___ nor shorten the war one day."
> 
>  "And it might give 'em all stomach ulcers."
> 
> - Tarzan, on war
> 

___
QGIS-Developer mailing list
QGIS-Developer@lists.osgeo.org
List info: https://lists.osgeo.org/mailman/listinfo/qgis-developer
Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-developer

Re: [QGIS-Developer] MAC QGIS 3.x build

[Peter Petrik]

Hi, 

Thanks for all info. That qt bug looks scary :O

Qgis 3.4 for other platforms (linux, windows) will be released with which 
version of Qt ? 

Cheers
Peter

> On 4 Sep 2018, at 15:09, William Kyngesburye  wrote:
> 
> Yeah, I haven't updated the build instructions for QGIS 3.  It took me a 
> while to get going on figuring out all the new stuff (I've had a lot of 
> distraction the past year or so).
> 
> I don't have any published scripts for the official build.  Mostly it's just 
> following the build instructions (what they would be when I update them), 
> plus a bundling script for the extras bundled in the app (not necessary for 
> anyone installing from source).
> 
> Thanks for the reminder that the instructions need updating.
> 
> Last I heard, homebrew wasn't quite ready with a 3.x build.
> 
>> On Sep 4, 2018, at 4:04 AM, Peter Petrik > > wrote:
>> 
>> Hi,
>> 
>> As a (happy) Linux user, I switched to Mac (High Sierra 10.13.6) for some 
>> QGIS development and I see that 
>> https://github.com/qgis/QGIS/blob/master/INSTALL 
>>  still suggests qt4 and 
>> python 2.6 for Mac. Does anyone has a suggestion what to use/read to 
>> facilitate the building of current master and get quickly up-to-speed? 
>> 
>> Also, can you please point me to the scripts/repositories that are used for 
>> official Mac releases?
>> 
>> I have found https://github.com/OSGeo/homebrew-osgeo4mac 
>> , but I am not sure if that can 
>> be used for development?
>> 
>> Thanks a lot for any ideas! 
>> Peter
>> ___
>> QGIS-Developer mailing list
>> QGIS-Developer@lists.osgeo.org 
>> List info: https://lists.osgeo.org/mailman/listinfo/qgis-developer
>> Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-developer
> 
> -
> William Kyngesburye 
> http://www.kyngchaos.com/ 
> 
> "Oh, look, I seem to have fallen down a deep, dark hole.  Now what does that 
> remind me of?  Ah, yes - life."
> 
> - Marvin
> 
> 

___
QGIS-Developer mailing list
QGIS-Developer@lists.osgeo.org
List info: https://lists.osgeo.org/mailman/listinfo/qgis-developer
Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-developer

[QGIS-Developer] Some initial OpenCL feedback

[Andreas Neumann]

Hi Alessandro, 

I just tested if the hardware acceleration (OpenCL) helps in the live
hillshade renderer. 

The good news is that it works stable so far and substantially improves
rendering time of the live hillshade renderer. My notebook on my
workplace is rather slow. Without hardware acceleration it renders the
hillshade in approx 8 seconds (large window on two screens). With OpenCL
acceleration set to on, it renders in about 1 second or even less. I
assume quite some time is also spent on reading the file. This with
resampling on (average for zooming out and bilinear for zooming in
beyond native resolution). 

Hardware is an Intel HD Graphics 4600. The CPU is also listed as
supported. 

Visually, with or without HW accelation on, there still are some
rectangular artefacts in both versions. 

Tested on Windows. 

-- 

One more thing: on my machine there is no restart of QGIS necessary for
the changes (HW acceleration on of off) to be applied. This is contrary
to the statement in the settings dialogue, which says, that a restart of
QGIS is necessary. 

--- 

Thanks a lot for your work! 

Andreas___
QGIS-Developer mailing list
QGIS-Developer@lists.osgeo.org
List info: https://lists.osgeo.org/mailman/listinfo/qgis-developer
Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-developer

Re: [QGIS-Developer] Python ResourceWarning: unclosed file in Processing Plugin

[Martin Isenburg]

Hello.

thanks for the suggestion. I tried this instead:

output = subprocess.Popen(commandline, shell=True,
stdout=subprocess.PIPE, stdin=open(os.devnull), stderr=subprocess.STDOUT,
universal_newlines=False)
output.wait()
feedback.pushConsoleInfo(output.communicate()[0].decode("utf-8"))

but as soon as the subprocess is started (long before it completes) this
WARNING is output to the console.

2018-09-04T13:05:31 WARNING
warning:C:/Users/isenburg/AppData/Roaming/QGIS/QGIS3\profiles\default/python/plugins\LAStools\LAStoolsUtils.py:60:
ResourceWarning:

 unclosed file

 traceback: File
"C:/Users/isenburg/AppData/Roaming/QGIS/QGIS3\profiles\default/python/plugins\LAStools\LAStools\lasview.py",
line 67, in processAlgorithm
  LAStoolsUtils.runLAStools(commands, feedback)
  File
"C:/Users/isenburg/AppData/Roaming/QGIS/QGIS3\profiles\default/python/plugins\LAStools\LAStoolsUtils.py",
line 60, in runLAStools
  output = subprocess.Popen(commandline, shell=True,
stdout=subprocess.PIPE, stdin=open(os.devnull), stderr=subprocess.STDOUT,
universal_newlines=False)


how do others grab the stderr output off their subprocesses for display in
the console?


Martin

On Tue, Sep 4, 2018 at 1:03 AM Nyall Dawson  wrote:

> On Tue, 4 Sep 2018 at 02:56, Martin Isenburg 
> wrote:
> >
> > Hello,
> >
> > as soon as I run any of my LAStools plugin scripts I get the WARNING
> "ResourceWarning" about an "unclosed file" shown below in the Python
> warning window. I use the call "output = subprocess.Popen()" to get the
> stderr output from the process so I can push it to the console once the
> subprocess is complete with the
> feedback.pushConsoleInfo(output.decode("utf-8")). Is it bad? Can I fix it?
> Should I ignore it?
> >
> > Complete code:
> >
> >
> https://github.com/rapidlasso/LAStoolsPluginQGIS3/blob/master/LAStools/LAStoolsUtils.py
> >
> > Regards.
> >
> > Martin
> >
> > 2018-09-03T18:34:08 WARNING
> warning:C:/Users/isenburg/AppData/Roaming/QGIS/QGIS3\profiles\default/python/plugins\LAStools\LAStoolsUtils.py:60:
> ResourceWarning:
> >
> >  unclosed file
> >
> >  traceback: File
> "C:/Users/isenburg/AppData/Roaming/QGIS/QGIS3\profiles\default/python/plugins\LAStools\LAStoolsPipelines\flightlinesToDTMandSpikeFreeDSM.py",
> line 82, in processAlgorithm
> >   LAStoolsUtils.runLAStools(commands, feedback)
> >   File
> "C:/Users/isenburg/AppData/Roaming/QGIS/QGIS3\profiles\default/python/plugins\LAStools\LAStoolsUtils.py",
> line 60, in runLAStools
> >   output = subprocess.Popen(commandline, shell=True,
> stdout=subprocess.PIPE, stdin=open(os.devnull), stderr=subprocess.STDOUT,
> universal_newlines=False).communicate()[0]
>
> I think you need a:
>
> output.wait()
>
> after this line. See
>
> https://stackoverflow.com/questions/23279941/closing-stdin-in-subprocess-popen
>
> Nyall
>
>
> >
> > ___
> > QGIS-Developer mailing list
> > QGIS-Developer@lists.osgeo.org
> > List info: https://lists.osgeo.org/mailman/listinfo/qgis-developer
> > Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-developer
>
___
QGIS-Developer mailing list
QGIS-Developer@lists.osgeo.org
List info: https://lists.osgeo.org/mailman/listinfo/qgis-developer
Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-developer

Re: [QGIS-Developer] MAC QGIS 3.x build

[Nyall Dawson]

On Tue, 4 Sep 2018 at 19:19, David Marteau  wrote:
>
> Hi Peter,
>
> Warning, if you are using macport: qt5.11 is installed by default and you may 
> (or may not)  experience some display problems, instead you may choose to 
> stick to qt5.9 by installing
>
> the 'qt59' port

Is that the infamous "small canvas" issue?

Nyall

>
> David
>
> Le 4 sept. 2018 à 11:14, Denis Rouzaud  a écrit :
>
> Hi Peter,
>
> You can look at current Homebrew formula:
> https://github.com/OSGeo/homebrew-osgeo4mac/blob/master/Formula/qgis3.rb
>
> You'll find a very good doc from Larry (althugh might be a bit outdated)
> https://github.com/qgis/homebrew-qgisdev/tree/master/development
>
> Otherwise, there is blog post from David on how to build using Mac ports
> https://www.3liz.com/blog/rldhont/index.php?post/2017/06/01/How-to-build-qgis-on-OSX-with-MacPort
>
> If while using one or the other, you feel like updating the readme, do not 
> hesitate to do so ;)
>
> Cheers,
> Denis
>
>
> Le mar. 4 sept. 2018 à 11:04, Peter Petrik 
>  a écrit :
>>
>> Hi,
>>
>> As a (happy) Linux user, I switched to Mac (High Sierra 10.13.6) for some 
>> QGIS development and I see that 
>> https://github.com/qgis/QGIS/blob/master/INSTALL still suggests qt4 and 
>> python 2.6 for Mac. Does anyone has a suggestion what to use/read to 
>> facilitate the building of current master and get quickly up-to-speed?
>>
>> Also, can you please point me to the scripts/repositories that are used for 
>> official Mac releases?
>>
>> I have found https://github.com/OSGeo/homebrew-osgeo4mac, but I am not sure 
>> if that can be used for development?
>>
>> Thanks a lot for any ideas!
>> Peter
>> ___
>> QGIS-Developer mailing list
>> QGIS-Developer@lists.osgeo.org
>> List info: https://lists.osgeo.org/mailman/listinfo/qgis-developer
>> Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-developer
>
> --
>
> Denis Rouzaud
> de...@opengis.ch
> +41 76 370 21 22
>
>
> ___
> QGIS-Developer mailing list
> QGIS-Developer@lists.osgeo.org
> List info: https://lists.osgeo.org/mailman/listinfo/qgis-developer
> Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-developer
>
>
> ___
> QGIS-Developer mailing list
> QGIS-Developer@lists.osgeo.org
> List info: https://lists.osgeo.org/mailman/listinfo/qgis-developer
> Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-developer
___
QGIS-Developer mailing list
QGIS-Developer@lists.osgeo.org
List info: https://lists.osgeo.org/mailman/listinfo/qgis-developer
Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-developer

Re: [QGIS-Developer] MAC QGIS 3.x build

[David Marteau]

Hi Peter,

Warning, if you are using macport: qt5.11 is installed by default and you may 
(or may not)  experience some display problems, instead you may choose to stick 
to qt5.9 by installing

the 'qt59' port

David

> Le 4 sept. 2018 à 11:14, Denis Rouzaud  a écrit :
> 
> Hi Peter,
> 
> You can look at current Homebrew formula:
> https://github.com/OSGeo/homebrew-osgeo4mac/blob/master/Formula/qgis3.rb 
> 
> 
> You'll find a very good doc from Larry (althugh might be a bit outdated)
> https://github.com/qgis/homebrew-qgisdev/tree/master/development 
> 
> 
> Otherwise, there is blog post from David on how to build using Mac ports
> https://www.3liz.com/blog/rldhont/index.php?post/2017/06/01/How-to-build-qgis-on-OSX-with-MacPort
>  
> 
> 
> If while using one or the other, you feel like updating the readme, do not 
> hesitate to do so ;)
> 
> Cheers,
> Denis
> 
> 
> Le mar. 4 sept. 2018 à 11:04, Peter Petrik 
>  > a écrit :
> Hi,
> 
> As a (happy) Linux user, I switched to Mac (High Sierra 10.13.6) for some 
> QGIS development and I see that 
> https://github.com/qgis/QGIS/blob/master/INSTALL 
>  still suggests qt4 and 
> python 2.6 for Mac. Does anyone has a suggestion what to use/read to 
> facilitate the building of current master and get quickly up-to-speed? 
> 
> Also, can you please point me to the scripts/repositories that are used for 
> official Mac releases?
> 
> I have found https://github.com/OSGeo/homebrew-osgeo4mac 
> , but I am not sure if that can 
> be used for development?
> 
> Thanks a lot for any ideas! 
> Peter
> ___
> QGIS-Developer mailing list
> QGIS-Developer@lists.osgeo.org 
> List info: https://lists.osgeo.org/mailman/listinfo/qgis-developer 
> 
> Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-developer 
> -- 
> Denis Rouzaud
> de...@opengis.ch  
> +41 76 370 21 22 <>
> 
>  <>___
> QGIS-Developer mailing list
> QGIS-Developer@lists.osgeo.org
> List info: https://lists.osgeo.org/mailman/listinfo/qgis-developer
> Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-developer

___
QGIS-Developer mailing list
QGIS-Developer@lists.osgeo.org
List info: https://lists.osgeo.org/mailman/listinfo/qgis-developer
Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-developer

Re: [QGIS-Developer] MAC QGIS 3.x build

[Denis Rouzaud]

Hi Peter,

You can look at current Homebrew formula:
https://github.com/OSGeo/homebrew-osgeo4mac/blob/master/Formula/qgis3.rb

You'll find a very good doc from Larry (althugh might be a bit outdated)
https://github.com/qgis/homebrew-qgisdev/tree/master/development

Otherwise, there is blog post from David on how to build using Mac ports
https://www.3liz.com/blog/rldhont/index.php?post/2017/06/01/How-to-build-qgis-on-OSX-with-MacPort

If while using one or the other, you feel like updating the readme, do not
hesitate to do so ;)

Cheers,
Denis


Le mar. 4 sept. 2018 à 11:04, Peter Petrik <
peter.pet...@lutraconsulting.co.uk> a écrit :

> Hi,
>
> As a (happy) Linux user, I switched to Mac (High Sierra 10.13.6) for some
> QGIS development and I see that
> https://github.com/qgis/QGIS/blob/master/INSTALL still suggests qt4 and
> python 2.6 for Mac. Does anyone has a suggestion what to use/read to
> facilitate the building of current master and get quickly up-to-speed?
>
> Also, can you please point me to the scripts/repositories that are used
> for official Mac releases?
>
> I have found https://github.com/OSGeo/homebrew-osgeo4mac, but I am not
> sure if that can be used for development?
>
> Thanks a lot for any ideas!
> Peter
> ___
> QGIS-Developer mailing list
> QGIS-Developer@lists.osgeo.org
> List info: https://lists.osgeo.org/mailman/listinfo/qgis-developer
> Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-developer

-- 

Denis Rouzaud
de...@opengis.ch  
+41 76 370 21 22
___
QGIS-Developer mailing list
QGIS-Developer@lists.osgeo.org
List info: https://lists.osgeo.org/mailman/listinfo/qgis-developer
Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-developer

[QGIS-Developer] MAC QGIS 3.x build

[Peter Petrik]

Hi,

As a (happy) Linux user, I switched to Mac (High Sierra 10.13.6) for some
QGIS development and I see that
https://github.com/qgis/QGIS/blob/master/INSTALL still suggests qt4 and
python 2.6 for Mac. Does anyone has a suggestion what to use/read to
facilitate the building of current master and get quickly up-to-speed?

Also, can you please point me to the scripts/repositories that are used for
official Mac releases?

I have found https://github.com/OSGeo/homebrew-osgeo4mac, but I am not sure
if that can be used for development?

Thanks a lot for any ideas!
Peter
___
QGIS-Developer mailing list
QGIS-Developer@lists.osgeo.org
List info: https://lists.osgeo.org/mailman/listinfo/qgis-developer
Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-developer

[QGIS-Developer] Plugin [1531] Label to Attribute approval notification.

[noreply]

Plugin Label to Attribute approval by pcav.
The plugin version "[1531] Label to Attribute 0.1" is now approved
Link: http://plugins.qgis.org/plugins/Label2Attr/
___
QGIS-Developer mailing list
QGIS-Developer@lists.osgeo.org
List info: https://lists.osgeo.org/mailman/listinfo/qgis-developer
Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-developer

Re: [QGIS-Developer] What to do about WFS test failures?

[Tim Sutton]

Hi



> On 03 Sep 2018, at 22:54, Jonathan Moules  
> wrote:
> 
> I'd suggest based on Tom's post that the work should include some sort of 
> reliable way of testing the WFS client (and of course full test coverage) - I 
> don't know if GeoServer is Docker-happy these days
> 

Kartoza publishes geoserver images here:

https://hub.docker.com/r/kartoza/geoserver/tags/ 


https://github.com/kartoza/docker-geoserver 


Regards

Tim


> , but the default install in a VM should be sufficient for the task (it comes 
> with test layers) - although GeoServer doesn't support WFS-T for writing.
> Cheers,
> Jonathan
> 
> On 03/09/2018 12:04, Régis Haubourg wrote:
>> Hi all,
>> I very much think that the WFS client is an really bad state, and is not 
>> really reliable, especially in WFS-T context.
>> The good news is that we just have been funded to refactor it !
>> The work should start in september and land in 3.6. I will let our dev's 
>> come here with more technical details about the goals. I hope we will also 
>> be able to take benefit of this to this the OGC compliancy of the client 
>> here.
>> Best regards,
>> Régis
>> 
>> Le lun. 3 sept. 2018 à 11:36, Tom Chadwin > > a écrit :
>> I can't offer any helpful suggestions, but just to let you know I finally had
>> to disable all my plugin WFS tests. I used to cope, by rerunning failed
>> Travis runs, but by about three months ago, it seemed no longer usable -
>> failure after failure.
>> 
>> I was using a third-party WFS, and perhaps I could have got round this by
>> adding a WFS provider to the test docker image, but in this plugin's case, I
>> didn't think it worth the significant effort to do so. The WM(T)S tests also
>> use third-party sources and seem stable, so perhaps this wasn't the
>> underlying issue anyway.
>> 
>> If an improvement or solution could be found, it would be great to reinstate
>> these tests.
>> 
>> Thanks
>> 
>> Tom
>> 
>> 
>> 
>> -
>> Buy Pie Spy: Adventures in British pastry 2010-11 on Amazon
>> --
>> Sent from: http://osgeo-org.1560.x6.nabble.com/QGIS-Developer-f4099106.html 
>> 
>> ___
>> QGIS-Developer mailing list
>> QGIS-Developer@lists.osgeo.org 
>> List info: https://lists.osgeo.org/mailman/listinfo/qgis-developer 
>> 
>> Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-developer 
>> 
>> 
>> ___
>> QGIS-Developer mailing list
>> QGIS-Developer@lists.osgeo.org 
>> List info: https://lists.osgeo.org/mailman/listinfo/qgis-developer 
>> 
>> Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-developer 
>> 
> ___
> QGIS-Developer mailing list
> QGIS-Developer@lists.osgeo.org
> List info: https://lists.osgeo.org/mailman/listinfo/qgis-developer
> Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-developer

—








Tim Sutton

Co-founder: Kartoza
Ex Project chair: QGIS.org

Visit http://kartoza.com  to find out about open source:

Desktop GIS programming services
Geospatial web development
GIS Training
Consulting Services

Skype: timlinux
IRC: timlinux on #qgis at freenode.net



signature.asc
Description: Message signed with OpenPGP
___
QGIS-Developer mailing list
QGIS-Developer@lists.osgeo.org
List info: https://lists.osgeo.org/mailman/listinfo/qgis-developer
Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-developer

Re: [QGIS-Developer] Processing Script addLayerToLoadOnCompletion

[matteo]

Hi Ginetto,

well actually this is a simple script and not Processing plugin, so I
think no reloading is needed

Cheers

Matteo
___
QGIS-Developer mailing list
QGIS-Developer@lists.osgeo.org
List info: https://lists.osgeo.org/mailman/listinfo/qgis-developer
Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-developer

Re: [QGIS-Developer] Processing Script addLayerToLoadOnCompletion

[Luigi Pirelli]

are you reloading processing plugin? the temporary path of processing are
statically set once (c++ static var in QgsProcessingUtils) for qgis session
=> if you reload the processing plugin without exitig processing (e.g. to
update the list of scripts), the oldtemp folder is no more available but
still referenced => generating strange errors at the end of any process.
Just rerun qgis to check if this is the problem.

There is no easy fix other that avoid static variable end method (e.g.
refactoring) of QgsProcessignUtils, bts is not a common use case errors,
but only happens to script developers => no fix is necessary.

Luigi Pirelli

**
* LinkedIn: https://www.linkedin.com/in/luigipirelli
* Stackexchange: http://gis.stackexchange.com/users/19667/luigi-pirelli
* GitHub: https://github.com/luipir
* Mastering QGIS 2nd Edition:
*
https://www.packtpub.com/big-data-and-business-intelligence/mastering-qgis-second-edition
* Hire me: http://goo.gl/BYRQKg
**


On Mon, 3 Sep 2018 at 16:52, matteo  wrote:

> Hi all,
>
> I was thinking to add a small example of addLayerToLoadOnCompletion
> function to the ScriptTemplate of Processing. The code is the following:
>
> buffered_layer = processing.run("native:buffer", parameters={
> 'INPUT': dest_id,
> 'DISTANCE': 1,
> 'SEGMENTS': 5,
> 'END_CAP_STYLE': 0,
> 'JOIN_STYLE': 0,
> 'MITER_LIMIT': 2,
> 'DISSOLVE': False,
> 'OUTPUT': 'memory:'
> }, context=context, feedback=feedback)['OUTPUT']
>
> feedback.pushDebugInfo(str(dest_id))
>
> context.addLayerToLoadOnCompletion(buffered_layer.source(),
> context.LayerDetails(
> name='new_layer',
> project=context.project()
> ))
>
> but Processing always throws this error:
>
> The following layers were not correctly
>
> generated.Polygon?crs=EPSG:3003=ID:long(10)=fk:string(254)=ROTAZ:long(10)=DIMENS:long(10)=ETICHETTA:string(254)=VALORE:long(10)=T_MIN:double(20,5)=T_MAX:double(20,5)=PIOGGIA:double(20,5)=LARGH:double(20,5)=LUNG:double(20,5)=assex:string(254)=assey:string(254)=colore:string(38)=xlab:double(10,2)=ylab:double(10,2)=raster:double(23,15)=raster_1:double(23,15)=raster_2:double(23,15)={685540af-711d-462b-a9d0-9b00af4c2f6a}You
> can check the 'Log Messages Panel' in QGIS main window to find more
> information about the execution of the algorithm.
>
>
> Am I missing something?
>
> Thanks for any suggestion
>
> Matteo
>
>
>
> ___
> QGIS-Developer mailing list
> QGIS-Developer@lists.osgeo.org
> List info: https://lists.osgeo.org/mailman/listinfo/qgis-developer
> Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-developer
___
QGIS-Developer mailing list
QGIS-Developer@lists.osgeo.org
List info: https://lists.osgeo.org/mailman/listinfo/qgis-developer
Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-developer

[QGIS-Developer] Plugin [1145] ClusterPoints approval notification.

[noreply]

Plugin ClusterPoints approval by pcav.
The plugin version "[1145] ClusterPoints 3.3" is now approved
Link: http://plugins.qgis.org/plugins/ClusterPoints/
___
QGIS-Developer mailing list
QGIS-Developer@lists.osgeo.org
List info: https://lists.osgeo.org/mailman/listinfo/qgis-developer
Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-developer

Re: [QGIS-Developer] What to do about WFS test failures?

[Régis Haubourg]

Hi,
I just checked the goals of the work on the WFS provider. It is not a
refactor in fat, sorry for having used that word. The work consists in
having a closer look to the WFS and snapping cache interactions because
they cause lots of problems when the distant database has triggers that
would require WFS cache reloading and then snapping cache reloading.
Maybe Vincent can tell more about that, but it's not a major change then. I
should'nt have raised the hand here, sorry for the noise.
Regards,
Régis

Le mar. 4 sept. 2018 à 08:51, Jonathan Moules 
a écrit :

> I'd suggest based on Tom's post that the work should include some sort of
> reliable way of testing the WFS client (and of course full test coverage) -
> I don't know if GeoServer is Docker-happy these days, but the default
> install in a VM should be sufficient for the task (it comes with test
> layers) - although GeoServer doesn't support WFS-T for writing.
> Cheers,
> Jonathan
>
> On 03/09/2018 12:04, Régis Haubourg wrote:
>
> Hi all,
> I very much think that the WFS client is an really bad state, and is not
> really reliable, especially in WFS-T context.
> The good news is that we just have been funded to refactor it !
> The work should start in september and land in 3.6. I will let our dev's
> come here with more technical details about the goals. I hope we will also
> be able to take benefit of this to this the OGC compliancy of the client
> here.
> Best regards,
> Régis
>
> Le lun. 3 sept. 2018 à 11:36, Tom Chadwin  a
> écrit :
>
>> I can't offer any helpful suggestions, but just to let you know I finally
>> had
>> to disable all my plugin WFS tests. I used to cope, by rerunning failed
>> Travis runs, but by about three months ago, it seemed no longer usable -
>> failure after failure.
>>
>> I was using a third-party WFS, and perhaps I could have got round this by
>> adding a WFS provider to the test docker image, but in this plugin's
>> case, I
>> didn't think it worth the significant effort to do so. The WM(T)S tests
>> also
>> use third-party sources and seem stable, so perhaps this wasn't the
>> underlying issue anyway.
>>
>> If an improvement or solution could be found, it would be great to
>> reinstate
>> these tests.
>>
>> Thanks
>>
>> Tom
>>
>>
>>
>> -
>> Buy Pie Spy: Adventures in British pastry 2010-11 on Amazon
>> --
>> Sent from:
>> http://osgeo-org.1560.x6.nabble.com/QGIS-Developer-f4099106.html
>> ___
>> QGIS-Developer mailing list
>> QGIS-Developer@lists.osgeo.org
>> List info: https://lists.osgeo.org/mailman/listinfo/qgis-developer
>> Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-developer
>
>
>
> ___
> QGIS-Developer mailing listqgis-develo...@lists.osgeo.org
> List info: https://lists.osgeo.org/mailman/listinfo/qgis-developer
> Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-developer
>
>
> ___
> QGIS-Developer mailing list
> QGIS-Developer@lists.osgeo.org
> List info: https://lists.osgeo.org/mailman/listinfo/qgis-developer
> Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-developer
___
QGIS-Developer mailing list
QGIS-Developer@lists.osgeo.org
List info: https://lists.osgeo.org/mailman/listinfo/qgis-developer
Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-developer

Re: [QGIS-Developer] What to do about WFS test failures?

[Andrea Aime]

On Tue, Sep 4, 2018 at 8:51 AM Jonathan Moules 
wrote:

> I'd suggest based on Tom's post that the work should include some sort of
> reliable way of testing the WFS client (and of course full test coverage) -
> I don't know if GeoServer is Docker-happy these days, but the default
> install in a VM should be sufficient for the task (it comes with test
> layers) - although GeoServer doesn't support WFS-T for writing.
>
"GeoServer doesn't support WFS-T for writing" ... what??? :-)

The default data directory disables writes for any user but the
administrator, you can change it, or just authenticate
as the admin to run WFS-T

Cheers
Andrea

==

GeoServer Professional Services from the experts! Visit http://goo.gl/it488V
for more information. == Ing. Andrea Aime @geowolf Technical Lead
GeoSolutions S.A.S. Via di Montramito 3/A 55054 Massarosa (LU) phone: +39
0584 962313 fax: +39 0584 1660272 mob: +39 339 8844549
http://www.geo-solutions.it http://twitter.com/geosolutions_it
--- *Con riferimento
alla normativa sul trattamento dei dati personali (Reg. UE 2016/679 -
Regolamento generale sulla protezione dei dati “GDPR”), si precisa che ogni
circostanza inerente alla presente email (il suo contenuto, gli eventuali
allegati, etc.) è un dato la cui conoscenza è riservata al/i solo/i
destinatario/i indicati dallo scrivente. Se il messaggio Le è giunto per
errore, è tenuta/o a cancellarlo, ogni altra operazione è illecita. Le
sarei comunque grato se potesse darmene notizia. This email is intended
only for the person or entity to which it is addressed and may contain
information that is privileged, confidential or otherwise protected from
disclosure. We remind that - as provided by European Regulation 2016/679
“GDPR” - copying, dissemination or use of this e-mail or the information
herein by anyone other than the intended recipient is prohibited. If you
have received this email by mistake, please notify us immediately by
telephone or e-mail.*
___
QGIS-Developer mailing list
QGIS-Developer@lists.osgeo.org
List info: https://lists.osgeo.org/mailman/listinfo/qgis-developer
Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-developer

Re: [QGIS-Developer] What to do about WFS test failures?

[Jonathan Moules]

I'd suggest based on Tom's post that the work should include some sort 
of reliable way of testing the WFS client (and of course full test 
coverage) - I don't know if GeoServer is Docker-happy these days, but 
the default install in a VM should be sufficient for the task (it comes 
with test layers) - although GeoServer doesn't support WFS-T for writing.


Cheers,
Jonathan

On 03/09/2018 12:04, Régis Haubourg wrote:

Hi all,
I very much think that the WFS client is an really bad state, and is 
not really reliable, especially in WFS-T context.

The good news is that we just have been funded to refactor it !
The work should start in september and land in 3.6. I will let our 
dev's come here with more technical details about the goals. I hope we 
will also be able to take benefit of this to this the OGC compliancy 
of the client here.

Best regards,
Régis

Le lun. 3 sept. 2018 à 11:36, Tom Chadwin > a écrit :


I can't offer any helpful suggestions, but just to let you know I
finally had
to disable all my plugin WFS tests. I used to cope, by rerunning
failed
Travis runs, but by about three months ago, it seemed no longer
usable -
failure after failure.

I was using a third-party WFS, and perhaps I could have got round
this by
adding a WFS provider to the test docker image, but in this
plugin's case, I
didn't think it worth the significant effort to do so. The WM(T)S
tests also
use third-party sources and seem stable, so perhaps this wasn't the
underlying issue anyway.

If an improvement or solution could be found, it would be great to
reinstate
these tests.

Thanks

Tom



-
Buy Pie Spy: Adventures in British pastry 2010-11 on Amazon
--
Sent from:
http://osgeo-org.1560.x6.nabble.com/QGIS-Developer-f4099106.html
___
QGIS-Developer mailing list
QGIS-Developer@lists.osgeo.org 
List info: https://lists.osgeo.org/mailman/listinfo/qgis-developer
Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-developer



___
QGIS-Developer mailing list
QGIS-Developer@lists.osgeo.org
List info: https://lists.osgeo.org/mailman/listinfo/qgis-developer
Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-developer


___
QGIS-Developer mailing list
QGIS-Developer@lists.osgeo.org
List info: https://lists.osgeo.org/mailman/listinfo/qgis-developer
Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-developer