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
data loss on getmap requests when vector data is reprojected EPSG:2056 to EPSG:4326 #7019
Comments
@ltclm - thanks for providing a fully working test case. I can confirm the issue still exists in the MapServer main branch. This can be seen in the image below. The orange area is the original request extent, and the pink is the extent used to select the underlying features. As you can see in the image only the lower two features intersect, and so are the only features drawn. It is harder to pin down which of the various modifications to the extent is the cause of the shift, and why this may be necessary. |
thank you @geographika for your response, the insights and the link to the related issues 👍
to
as proposed here #6478 (comment) is fixing the projection issue for the reprojected getmap requests. But with the new projection settings at layer level some getmap requests in the native data projection are not working anymore and an empty map is returned:
|
Hi @ltclm , I was using Had been looking everywhere what is causing the upgrade failure but couldn't find any answer, since I saw you using the same image and able to at least get something, I hope you can provide some insight for me. |
Expected behavior and actual behavior.
When zooming into a reprojected polygon layer we expect that all the features are displayed in all scales. The original data and the mapfile configuration is in EPSG:2056. The strange behaviour and the data loss has been observed when requesting the map in EPSG:4326.
Steps to reproduce the problem.
Using the mapfile config [1] and the data index.shp from the attachment [2], start zooming into the center of the 4 polygons in EPSG:4326. After a certain zoom/scale some data gets lost. The same effect occurs with tiled wms queries (256x256), but much earlier.
Attach simple test case (drag/drop it here)
here are some screenshots and getmap requests of the observed data loss with EPSG:4326 GetMap Requests:
http://localhost:9178/local/?SERVICE=WMS&VERSION=1.3.0&REQUEST=GetMap&BBOX=47.70122100713624036,8.631010777621343166,47.73459661396240961,8.673423389810198003&CRS=EPSG:4326&WIDTH=1591&HEIGHT=1252&LAYERS=test&STYLES=&FORMAT=image/jpeg&DPI=96&MAP_RESOLUTION=96&FORMAT_OPTIONS=dpi:96
http://localhost:9178/local/?SERVICE=WMS&VERSION=1.3.0&REQUEST=GetMap&BBOX=47.70991146067085253,8.640854182430102171,47.72659926408394426,8.662060488524529589&CRS=EPSG:4326&WIDTH=1591&HEIGHT=1253&LAYERS=test&STYLES=&FORMAT=image/jpeg&DPI=96&MAP_RESOLUTION=96&FORMAT_OPTIONS=dpi:96
http://localhost:9178/local/?SERVICE=WMS&VERSION=1.3.0&REQUEST=GetMap&BBOX=47.7172290358096447,8.65006363064953554,47.71931501123628294,8.652714418911338967&CRS=EPSG:4326&WIDTH=1591&HEIGHT=1253&LAYERS=test&STYLES=&FORMAT=image/jpeg&DPI=96&MAP_RESOLUTION=96&FORMAT_OPTIONS=dpi:96
Operating system
We are operating mapserver on aws/kubernetes using this docker image from dockerhub:
camptocamp/mapserver:7.6-gdal3.3
. The docker image is based onUbuntu 20.04.6 LTS
MapServer version and installation method
the same behaviour has been observed with
mapserver 8.0 / gdal 3.6
andmapserver 8.0 / gdal 3.8
[1] mapfile
[2]
data.zip
The text was updated successfully, but these errors were encountered: