GeoJSON output does not seem to work for WFS service

[3liz]

GeoJSON output does not seem to work for WFS service

[Gustry]

We are having an issue with export of vector layers in 3.6.2, not only geojson.

[cybernar]

I tried the same query for the geojson output, but directly to OWS port :

http://localhost:8091/ows/?map=demodocker/montpellier_uu.qgs&service=WFS&version=1.0.0&request=GetFeature&geometryname=extent&TYPENAME=commune_uu&OUTPUTFORMAT=GeoJSON

It works ! maybe some problem with domain name ?

Cyril

[cybernar]

New test with docker version of Lizmap Web Client 3.6.2 : I have made a QGIS project with both shapefile layer & PostGIS layer.
I have published these layers in WFS. I try to use "Locate by layer" and "Attribute table" with these layers
Result :

• on shapefile layer, everything's ok
• on PostGIS layer, "Locate by layer" and "Attribute table" don't work (but WMS display is OK)
  I cannot see what is wrong with PostGIS layers.

[cybernar]

Hello,

finally I resolved my problem on WFS with PostGIS layers.

To be short : I was using 2 differents PGSERVICEFILE pg_service.conf :

• the 1st, automatically generated, for the authentication (lizmap users db) with lizmap container
• the 2nd, that I created, for another GIS db, with map container

That was a bad idea.

The problem is that the connection parameters for data were accessible only for the map container. So the WMS was working, but, examining the lizmap logs, I understood that the lizmap container also need to connect to the data, even for tools such as "Locate by layer" and "Attribute table"

That said, I think a little improvement in docker-compose.yml would be to have a mounted volume for /srv/etc/pgpass.conf in the map container : that is not the case today.

And, by the way, vector download seem to work for me.

Have a nice evening, Cyril

[Gustry]

Ok, thanks for the feedback.
I though it was this issue related to empty export of vector layers