subject:"Re\: \[QGIS\-Developer\] issues in QGIS Server 2,18"

Re: [QGIS-Developer] issues in QGIS Server 2,18

2018-04-17 Thread Lorenzo Moretti

Hi

In addition to the problem described in GetPrint I have a problem related to 
the legend in QGIS 2.18.
If the "Show Feature Count" function is enabled my QGIS Server crashes and part 
of the qgs file is also compromised. The legend is no longer displayed. Even if 
disabled "Show Feature Count" the qgs file is damaged. I've seen that this code 
in the qgs file crashes it:
  

  
This is also the case in GetPrint with dynamic texts in the legend (object 
counting). I have to remove all references in the qgs file but not always 
enough to avoid the crash. Sometimes I have to recreate the file from the 
beginning without this option and without the same option in the print.
QGIS server is installed on an OS Desktop (Mac OS X). X11 is not enabled and 
therefore I cannot use the fake-server.
The other options in QGIS Server work well.
All this in version 2.14 did not happen.

Thanks

cheers

Lorenzo

> 
> 
> *) Crashes on GetPrint: adding some type of elements in print
> composers (like html text boxes) caused QGIS Server to crash when
> doing a GetPrint *if* the *headless* server didn't had a fake xserver
> installed. Now in 2.18 this happens even if QGIS Server is installed
> on a Desktop OS, unless installing the fake x server. Not sure is
> related but this now affects also Windows machines where a GetPrint
> requests (of a layout with one of this problematic elements) make
> always QGIS Server crash. This was not the case for 2.14.
> 


___
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] issues in QGIS Server 2,18

2018-03-29 Thread René-Luc Dhont


Hi giovanni,

I'd like to try the WFS QGIS Server service ?

Regards,

René-Luc

Le 28/03/2018 à 12:38, Giovanni Manghi a écrit :

Hi all,



I have found the reason why QGIS Server 2.18 and probably 3 are slower
than 2.14 in generating GeoJSON.
I'll fix it.


I discovered two more WFS related issues, one in QGIS Desktop the
other in the Server.

I setup a WFS service, with both QGIS Server 2.18 and Mapserver, with
a layer than contains 5.6million points.
The QGIS WFS client pulls this layer without issues, but there is a
big problem when identifying features with the option "auto open form"
enabled:
on the second identify operation QGIS freezes and it start to leak
memory until it eats it all. It does not happen if the "auto open
form" option is not enabled. This happens also on QGIS 3.

The second issue is about the same dataset published as WFS with QGIS
Server, when saving the layer using QGIS using "save as" (for example
to a geopackage) the result is missing several features/points.
I tried then to save the layer using ogr from th CLI, and at some
point the message "ERROR 1: XML parsing of GML file failed : unclosed
token at line 109413441, column 21" is shown. This is not happening
(and the result is complete) if server used is Mapserver.

I can provide the services URLs is someone wants to give it a try.


cheers!

-- G --
___
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] issues in QGIS Server 2,18

2018-03-28 Thread Giovanni Manghi

Hi all,


>> I have found the reason why QGIS Server 2.18 and probably 3 are slower
>> than 2.14 in generating GeoJSON.
>> I'll fix it.


I discovered two more WFS related issues, one in QGIS Desktop the
other in the Server.

I setup a WFS service, with both QGIS Server 2.18 and Mapserver, with
a layer than contains 5.6million points.
The QGIS WFS client pulls this layer without issues, but there is a
big problem when identifying features with the option "auto open form"
enabled:
on the second identify operation QGIS freezes and it start to leak
memory until it eats it all. It does not happen if the "auto open
form" option is not enabled. This happens also on QGIS 3.

The second issue is about the same dataset published as WFS with QGIS
Server, when saving the layer using QGIS using "save as" (for example
to a geopackage) the result is missing several features/points.
I tried then to save the layer using ogr from th CLI, and at some
point the message "ERROR 1: XML parsing of GML file failed : unclosed
token at line 109413441, column 21" is shown. This is not happening
(and the result is complete) if server used is Mapserver.

I can provide the services URLs is someone wants to give it a try.


cheers!

-- G --
___
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] issues in QGIS Server 2,18

2018-03-22 Thread Giovanni Manghi

> Hi Giovanni,
>
> I have found the reason why QGIS Server 2.18 and probably 3 are slower
> than 2.14 in generating GeoJSON.
> I'll fix it.


much appreciated René-Luc,

thanks!

-- G --
___
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] issues in QGIS Server 2,18

2018-03-16 Thread René-Luc Dhont


Hi Giovanni,

I have found the reason why QGIS Server 2.18 and probably 3 are slower 
than 2.14 in generating GeoJSON.

I'll fix it.

Regards,
René-Luc

Le 09/03/2018 à 17:43, Régis Haubourg a écrit :

Hi Giovanni,
 GetFeatures  can output GML with a different format.
What is sure is that GeoJSON spec doesn't leave any choice, unless we 
go for a proprietary output format allowing another SRS.
I'll keep that in mind when testing OGC compliancy for WFS. We are 
working on that currently to evaluate how much work is needed to reach 
a certification for WFS.

Regards
Régis

2018-03-09 14:34 GMT+01:00 Giovanni Manghi >:


Hi René-Luc,



> Le 01/03/2018 à 12:52, Giovanni Manghi a écrit :
>> Hi all,
>> now that 2.18 is LTR I guess that many have also updated their QGIS
>> Server installation to this release. Problem is that I see a few
>> issues in 2.18 and would like to have gsome feedback from others.
>>
>> *) slower: it seems this version is slower compared to 2.14, at
least
>> for some specific request like WFS GetFeatures. See for example:
>>
>> https://issues.qgis.org/issues/18249#note-1

>>
>> where in the same condition (same server, same postgis
datasource of
>> around ~25000 polygons) 2.18 is about 30 seconds slower than 2.14.
>
> This issue is simply due to the transformation of the geometry
from the
> layer CRS to the GeoJSON CRS standard: EPSG:4326

ok thanks, but one doubt: I guess that this change (compared to 2.14)
was to make qgis server more compliant and this also means that we
need to accept that for such requests will be always slower than it
was before? sorry for the dumb question as I'm not much into the ogc
internals.


cheers

-- G --
___
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] issues in QGIS Server 2,18

2018-03-09 Thread Régis Haubourg

Hi Giovanni,
 GetFeatures  can output GML with a different format.
What is sure is that GeoJSON spec doesn't leave any choice, unless we go
for a proprietary output format allowing another SRS.
I'll keep that in mind when testing OGC compliancy for WFS. We are working
on that currently to evaluate how much work is needed to reach a
certification for WFS.
Regards
Régis

2018-03-09 14:34 GMT+01:00 Giovanni Manghi :

> Hi René-Luc,
>
>
>
> > Le 01/03/2018 à 12:52, Giovanni Manghi a écrit :
> >> Hi all,
> >> now that 2.18 is LTR I guess that many have also updated their QGIS
> >> Server installation to this release. Problem is that I see a few
> >> issues in 2.18 and would like to have gsome feedback from others.
> >>
> >> *) slower: it seems this version is slower compared to 2.14, at least
> >> for some specific request like WFS GetFeatures. See for example:
> >>
> >> https://issues.qgis.org/issues/18249#note-1
> >>
> >> where in the same condition (same server, same postgis datasource of
> >> around ~25000 polygons) 2.18 is about 30 seconds slower than 2.14.
> >
> > This issue is simply due to the transformation of the geometry from the
> > layer CRS to the GeoJSON CRS standard: EPSG:4326
>
> ok thanks, but one doubt: I guess that this change (compared to 2.14)
> was to make qgis server more compliant and this also means that we
> need to accept that for such requests will be always slower than it
> was before? sorry for the dumb question as I'm not much into the ogc
> internals.
>
>
> cheers
>
> -- G --
> ___
> 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] issues in QGIS Server 2,18

2018-03-09 Thread Giovanni Manghi

Hi all,

>> It will be great to have the possibility to allow nullptr in the map
>> combobox.
>> Nyall, do you have an idea how to enhance QgsComposerItemComboBox
>> introdiuced by
>> https://github.com/qgis/QGIS/commit/1b4bd47076103e931e642c9c2b6a363f14b20a45
>> ?
>> Issue already exists: https://issues.qgis.org/issues/16899
>
> I wouldn't do it this way -- it was the hidden nature of the original
> support for setting no linked map which led to it being broken (also,
> no unit tests -- the combination of a non-obvious reuse of an existing
> widget + no unit tests is basically asking for something to break).
>
> I'd suggest instead adding an explicit checkbox here for "always show
> all layers for server requests" (but better wording!), under a new
> "server settings" group.

seems reasonable to me, and if I can ask... would it be backportable
to 2.18? This change has broken a few web published projects and the
workaround is ugly (manually change the .qgs files or add in the
layout a legend as a png/jpg image).

thanks!

-- g --
___
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] issues in QGIS Server 2,18

2018-03-04 Thread Nyall Dawson

On 1 March 2018 at 23:26, René-Luc Dhont  wrote:

> *) At some point in 2.18 development -in the print composer,
> properties of a legend- the "none" value for the "map" option was
> removed. This option (together with "auto update" unchecked) allowed
> to do GetPrint requests where a legend always shown the same fixed
> entries regardless of the layers being requested. Moreover now the
> layers legend (from a GetPrint) frequently shows "?" instead of the
> correct legend. Not sure if the two things are related.
>
>
> It will be great to have the possibility to allow nullptr in the map
> combobox.
> Nyall, do you have an idea how to enhance QgsComposerItemComboBox
> introdiuced by
> https://github.com/qgis/QGIS/commit/1b4bd47076103e931e642c9c2b6a363f14b20a45
> ?
> Issue already exists: https://issues.qgis.org/issues/16899

I wouldn't do it this way -- it was the hidden nature of the original
support for setting no linked map which led to it being broken (also,
no unit tests -- the combination of a non-obvious reuse of an existing
widget + no unit tests is basically asking for something to break).

I'd suggest instead adding an explicit checkbox here for "always show
all layers for server requests" (but better wording!), under a new
"server settings" group. And a unit test ;)

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] issues in QGIS Server 2,18

2018-03-02 Thread Paolo Cavallini

Il 02/03/2018 10:45, René-Luc Dhont ha scritto:
> Hi devs,
> 
> An other Huge issue in QGIS Server 2.18.17:
> 
> https://issues.qgis.org/issues/18247

too bad we break stuff in minor releases, but such is life. aren't our
test enough to spot these regressions? anything we can do to improve
them? maybe better to downgrade this version from the repo, while
waiting for a fix?
all the best, and thanks for pointing this out.

-- 
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

Re: [QGIS-Developer] issues in QGIS Server 2,18

2018-03-02 Thread René-Luc Dhont

Hi devs,

An other Huge issue in QGIS Server 2.18.17:

https://issues.qgis.org/issues/18247

Regards,

René-Luc

Le 01/03/2018 à 14:26, René-Luc Dhont a écrit :

Hi Giovanni,

Le 01/03/2018 à 12:52, Giovanni Manghi a écrit :

Hi all,
now that 2.18 is LTR I guess that many have also updated their QGIS
Server installation to this release. Problem is that I see a few
issues in 2.18 and would like to have gsome feedback from others.

*) slower: it seems this version is slower compared to 2.14, at least
for some specific request like WFS GetFeatures. See for example:

https://issues.qgis.org/issues/18249#note-1

where in the same condition (same server, same postgis datasource of
around ~25000 polygons) 2.18 is about 30 seconds slower than 2.14.

This issue is simply due to the transformation of the geometry from
the layer CRS to the GeoJSON CRS standard: EPSG:4326

*) At some point in 2.18 development -in the print composer,
properties of a legend- the "none" value for the "map" option was
removed. This option (together with "auto update" unchecked) allowed
to do GetPrint requests where a legend always shown the same fixed
entries regardless of the layers being requested. Moreover now the
layers legend (from a GetPrint) frequently shows "?" instead of the
correct legend. Not sure if the two things are related.

It will be great to have the possibility to allow nullptr in the map
combobox.
Nyall, do you have an idea how to enhance QgsComposerItemComboBox
introdiuced by
https://github.com/qgis/QGIS/commit/1b4bd47076103e931e642c9c2b6a363f14b20a45?

Issue already exists: https://issues.qgis.org/issues/16899

*) Crashes on GetPrint: adding some type of elements in print
composers (like html text boxes) caused QGIS Server to crash when
doing a GetPrint *if* the *headless* server didn't had a fake xserver
installed. Now in 2.18 this happens even if QGIS Server is installed
on a Desktop OS, unless installing the fake x server. Not sure is
related but this now affects also Windows machines where a GetPrint
requests (of a layout with one of this problematic elements) make
always QGIS Server crash. This was not the case for 2.14.

The solution is probably to update the environment variable
QT_GRAPHICSSYSTEM to 'raster' has explain
https://issues.qgis.org/issues/15440 and in a lot of other project:

https://stackoverflow.com/questions/6168570/qgraphicsview-slow-scale-performance-under-linux
https://forum.kde.org/viewtopic.php?t=90821

I'll test this solution.

Regards,
René-Luc

___
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] issues in QGIS Server 2,18

2018-03-01 Thread René-Luc Dhont

Hi Giovanni,

Le 01/03/2018 à 12:52, Giovanni Manghi a écrit :

*) slower: it seems this version is slower compared to 2.14, at least
for some specific request like WFS GetFeatures. See for example:

https://issues.qgis.org/issues/18249#note-1

where in the same condition (same server, same postgis datasource of
around ~25000 polygons) 2.18 is about 30 seconds slower than 2.14.

This issue is simply due to the transformation of the geometry from the
layer CRS to the GeoJSON CRS standard: EPSG:4326

Issue already exists: https://issues.qgis.org/issues/16899

The solution is probably to update the environment variable
QT_GRAPHICSSYSTEM to 'raster' has explain
https://issues.qgis.org/issues/15440 and in a lot of other project:

https://stackoverflow.com/questions/6168570/qgraphicsview-slow-scale-performance-under-linux
https://forum.kde.org/viewtopic.php?t=90821

I'll test this solution.

Regards,
René-Luc
___
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] issues in QGIS Server 2,18

Re: [QGIS-Developer] issues in QGIS Server 2,18

Re: [QGIS-Developer] issues in QGIS Server 2,18

Re: [QGIS-Developer] issues in QGIS Server 2,18

Re: [QGIS-Developer] issues in QGIS Server 2,18

Re: [QGIS-Developer] issues in QGIS Server 2,18

Re: [QGIS-Developer] issues in QGIS Server 2,18

Re: [QGIS-Developer] issues in QGIS Server 2,18

Re: [QGIS-Developer] issues in QGIS Server 2,18

Re: [QGIS-Developer] issues in QGIS Server 2,18

Re: [QGIS-Developer] issues in QGIS Server 2,18

11 matches

Site Navigation

Mail list logo

Footer information