-
Notifications
You must be signed in to change notification settings - Fork 60
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
WFS: do not send a MAP= parameter when a <file> is not given in the mapsource (for type="mapserver-wfs") #772
Comments
An [better?] alternative would be to implement a tag in the mapsource and have GeoMoose reproject the request parameters and response values. |
Test with #787 |
My current suggested solution:
I've updated this to review me since #787 has been opened. |
You suggestion doesn't work. I've setup a map-source:
GeoMoose sends
Which in general looks OK, except the bbox is in EPSG:3857 (proj is given at the end of the bbox). The getCapabilities of the site specifies only EPSG:4326. The server responds with
So no features returned. I'm guessing this is because the bbox is in EPSG:3857. |
There is more going on than just he projection issue. I got all the projections working correctly in the #787 branch and it was still refusing to return anything when the
Which will disable the use of the bounding-box loading strategy. |
It looks like lots of MapServers are specified to use EPSG:4326, especially when set up as WFS server. Due to a MapServer bug(?) they will respond to query requests in EPSG:3857.
GeoMoose currently (v3.11) has a type="mapserver-wfs" to do requests in EPSG:3857, and reproject response data in EPSG:4326. BUT using "mapserver-wfs" means that it will send a MAP= parameter, which the foreign server will complain about.
A good solution would be not to send a MAP parameter if the GeoMoose admin has not included a tag in the mapsource.
The text was updated successfully, but these errors were encountered: