[Bug]: external WFS - some problems

3liz / lizmap-web-client

Transfer a QGIS project on a server, Lizmap is providing the web interface to browse it

https://www.lizmap.com

Mozilla Public License 2.0

249 stars 141 forks source link

[Bug]: external WFS - some problems #3886

Open josemvm opened 9 months ago

josemvm commented 9 months ago

What is the bug?

for wfs layer:

the atribbute table shows the columns but not the values
the atribbute table shows nothing if the user set "limitDataToBbox"
the popup shows nothing

Steps to reproduce the issue

please try it

Versions

Versions :

Lizmap Web Client : 3.6.5
Lizmap plugin : 3.17.0
QGIS Desktop : 3.22.16
QGIS Server : 3.22.16
Py-QGIS-Server : not used
QGIS Server plugin atlasprint : 3.3.2
QGIS Server plugin lizmap_server : 2.8.0
QGIS Server plugin wfsOutputExtension : 1.8.0

Check Lizmap plugin

[X] I have done the step just before in the Lizmap QGIS desktop plugin before opening this ticket. Otherwise, my ticket is not considered valid and might get closed.

QGIS server version, only if the section above doesn't mention the QGIS Server version

3.22.16

Operating system

Ubuntu 20.04

Browsers

Firefox

Browsers version

Firefox 117.0.1

Relevant log output

No response

josemvm commented 9 months ago

often the layer map does not appear...

gioman commented 9 months ago

@josemvm any public URL we can test?

josemvm commented 9 months ago

hi @gioman unfortunately not i'm using DGT/wfs with authentication service

Gustry commented 9 months ago

often the layer map does not appear...

If it appears sometimes and sometimes not, it seems QGIS server is sometimes fetching the data and wait enough time and sometimes the request to the external server is timing out and QGIS server returns incomplete data to LWC.

Is the external server fast enough compare to what QGIS server is waiting ?

josemvm commented 9 months ago

everything works fine and speedly in qgis desktop

gioman commented 9 months ago

everything works fine and speedly in qgis desktop

@josemvm I think you should test/try the WMS/WFS service generated by QGIS server that is cascading that services (not the one generated by LMWC, just QGIS server) and see if it works as expected.

Is this ticket different than https://github.com/3liz/lizmap-web-client/issues/3884 ?

Gustry commented 9 months ago

everything works fine and speedly in qgis desktop

I guess you are talking about the external WFS straight in QGIS desktop. Indeed, if you can try in QGIS desktop :

the WFS from QGIS server (not recommended at all in a normal production environment)
the WFS from LWC

josemvm commented 9 months ago

Is this ticket different than https://github.com/3liz/lizmap-web-client/issues/3884 ?

yes, this ticket https://github.com/3liz/lizmap-web-client/issues/3884 ? is only about authentication for the same wfs service

josemvm commented 9 months ago

@josemvm I think you should test/try the WMS/WFS service generated by QGIS server that is cascading that services (not the one generated by LMWC, just QGIS server) and see if it works as expected.

how can i test it?...

josemvm commented 9 months ago

now i'm using WFS service generated by QGIS Server, cascading the layer from original source/wfs service

on QGIS Desktop i' ve create a wfs connectiona to WFS service generated by QGIS Server and once again everything works fine on QGIS Desktop

when i publish the project on LWC it doesn't really work, so it's a LWC problem and not QGIS Server one

josemvm commented 9 months ago

however the map works fine on QGIS Desktop but de QGIS Server doesn´t cascade the table values only the table columns with NULL values

Gustry commented 9 months ago

I took the the WFS from

https://demo.snap.lizmap.com/lizmap_3_6/index.php/view/map?repository=features&project=fire_hydrant_actions

and publish into

https://demo.snap.lizmap.com/lizmap_3_7/index.php/view/map?repository=debug&project=external_wfs

by changing the color of the buildings (to check it's WFS)

it works, and attribute table as well. The attribute table looks slow to open, but it works with this layer.

Versions of snap 3.7 server

* Lizmap Web Client : 3.7.0-alpha.3 * Lizmap plugin : master * QGIS Desktop : 3.28.11 * Lizmap.com : Yes * QGIS Server : 3.28.11 * Py-QGIS-Server : 1.8.8 * QGIS Server plugin atlasprint : 3.3.3-alpha * QGIS Server plugin cadastre : 1.17.4-alpha * QGIS Server plugin lizmap_server : 2.8.1-alpha * QGIS Server plugin wfsOutputExtension : 1.8.1-alpha

josemvm commented 9 months ago

we are working in different contexts:

your Buildings layer from https://demo.snap.lizmap.com/lizmap_3_6/index.php/view/map?repository=features&project=fire_hydrant_actions is is provided by postgresql or something like that
my primitive layer is provided by an external wfs service, a geoserver somewhere

however there are some similar problems with cascaded layer on LWC: here https://demo.snap.lizmap.com/lizmap_3_7/index.php/view/map?repository=debug&project=external_wfs

sometimes (often) the map doesn't appear at its initial extent, nor with zoom out and zoom in

Gustry commented 9 months ago

we are working in different contexts:

I'm not sure to understand what you mean. At some point, the WFS relies on a datasource. The project external_wfs.qgs project is indeed using an external WFS, same as your question.

sometimes (often) the map doesn't appear at its initial extent, nor with zoom out and zoom in

Indeed, strange now.