Skip to content
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

WMS native KML output produces invalid coordinates #4938

Open
tomkralidis opened this issue Jun 6, 2014 · 3 comments
Open

WMS native KML output produces invalid coordinates #4938

tomkralidis opened this issue Jun 6, 2014 · 3 comments

Comments

@tomkralidis
Copy link
Member

Using 6.4.0, WMS GetMap requests with KML output using MapServer's native KML driver return erroneous coordinates. See testcase at http://kralidis.ca/tmp/ms_native_kml.tgz

@tomkralidis
Copy link
Member Author

cc @msmitherdc

I should have added in the testcase Makefile a CGI test: if you run
mapserv QUERY_STRING=map=./rt2.map&mode=map&MAP_IMAGETYPE=KML&layers=stations, the geometry output is correct.

So this bug is in the context of KML via WMS. CGI works fine.

From discussion with @rouault it seems that image coordinates are being output, not geospatial coordinates. If the image width/height ratio is identical to the bbox, then coordinates are output correctly.

Other comments (thanks @rouault)

  • The KML output is not compatible with the "fake extent" hack in MS that is triggered with non-squared pixels
  • the tests in msautotest do use square pixels, and avoid the bug

This is definitely a limitation for anyone wishing to provide KML via WMS.

@mapserver-bot
Copy link

This is an automated comment

This issue has been closed due to lack of activity. This doesn't mean the issue is invalid, it simply got no attention within the last year. Please reopen with missing/relevant information if still valid.

Typically, issues fall in this state for one of the following reasons:

  • Hard, impossible or not enough information to reproduce
  • Missing test case
  • Lack of a champion with interest and/or funding to address the issue

@jratike80
Copy link

This is still a bug and found again by a Mapserver user. See this mailing list thread https://lists.osgeo.org/pipermail/mapserver-users/2017-December/080397.html. Considering the discussion as recent activity and re-opening.

@jratike80 jratike80 reopened this Dec 18, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants