-
-
Notifications
You must be signed in to change notification settings - Fork 2.9k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
QGIS Server WFS 1.1: issue with axis order #36584
Comments
It's definitely NOT an issue in the new client side temporal code -- it's either an issue in the wfs provider or qgis server |
no, that's correct. With WFS >= 1.1, EPSG:4326 is in latitude, longitude order. However using "EPSG:4326" isn't recommended, and "urn:ogc:def:crs:EPSG::4326" should rather be used to avoid any ambiguity on axis order. Might be a QGIS server issue. You could probably force to WFS 1.0 to avoid that issue |
Hi @rouault @nyalldawson |
Looking closer, it has code to support 1.0 and 1.1. But 1.1 support seems to be currently non-compliant regarding EPSG axis order. |
The QGIS project highly values your report and would love to see it addressed. However, this issue has been left in feedback mode for the last 14 days and is being automatically marked as "stale". |
I think the comment from @rouault (#36584 (comment)) has enough information for the issue. |
Follows GeoServer convention, fixes qgis#36584
@ismailsunni would you please have a look to my PR if that fixes your issues? |
Hi @elpaso how can I test QGIS Server from my own build? I usually use a docker image for QGIS Server. Thanks |
|
@ismailsunni gentle ping |
hi @elpaso I tried several URLs for the WFS (and WMS) like localhost:8000 but it doesn't work. I tried to check with the URL on the landing page, like
I can get the capabilities (using postman), but I can't add the URL on QGIS (it says |
forget the landing page and pass MAP=...&SERVICE=WMS... |
Ah, thanks @elpaso I tried with the same project as in my first comment, but it still gives me the same result.
I got:
|
Are you testing #41242 ? We are now following GeoServer conventions and EPSG:4326 is supposed to be interpreted as LON-LAT order. I don't know what you are testing but it seems to me |
hi @elpaso Yes, I use your branch. And yes, it was my mistake. I have checked again the URL, it is fixed now. I also have tested on QGIS, I can see my features now (I can't see it previously, like I mentioned in my first comment above). Thanks for the fix! |
Follows GeoServer convention, fixes qgis#36584 Cherry-picked from master e967fd9
Fixes qgis#36584 Cherry-picked from master 84f61ff.
Follows GeoServer convention, fixes qgis#36584 Cherry-picked from master e967fd9
Fixes qgis#36584 Cherry-picked from master 84f61ff.
Describe the bug
I am trying to use QGIS Server to serve a WFS with a time dimension and view it using the new QGIS temporal handler.
Unfortunately, the features are not shown on QGIS. I checked the requested URL with QGIS Network Logger plugin, and this is the request:
and this is the returns
The BBOX seems wrong (longitude and latitude in the wrong place).
I tried to "fix" the BBOX, like this:
and I got the expected result:
So, there is a problem either in the QGIS Server or the temporal handling of QGIS. The WMS from the same QGIS Server itself is working fine.
I tested with a WFS from a GeoServer. It does not have a time field as Datetime, but a string, so I created one from it. It's working fine on QGIS temporal handling. So, probably the problem is on the QGIS Server one. Or perhaps there is a different way to handle WFS server?
How to Reproduce
QGIS and OS versions
Additional context
The text was updated successfully, but these errors were encountered: