Timeline for MapServer - map rendered at the wrong angle
Current License: CC BY-SA 2.5
7 events
when toggle format | what | by | license | comment | |
---|---|---|---|---|---|
Apr 13, 2017 at 12:34 | history | edited | CommunityBot |
replaced http://gis.stackexchange.com/ with https://gis.stackexchange.com/
|
|
Mar 10, 2011 at 10:21 | comment | added | RichW | The conversion from OS to WGS84 was fine as I checked the coordinates after the conversion and they were spot on. It was the conversion to postgis' geometry format that did it as the coordinates were the wrong way round! Not sure what you mean about not using a projection though as I've specified 4326 throughout the map file - although the data looks correct I still have to skew it to make it line up with the google maps data.. | |
Mar 9, 2011 at 17:20 | comment | added | whuber | Yes, I suspected the same, because that would explain why the difference isn't exactly a reflection and a rotation: the different apparent latitudes would cause differential distortion in the projection. That also would account for a mismatch with GM (unless the OP choose an appropriate transverse Mercator :-)). | |
Mar 9, 2011 at 16:59 | comment | added | geographika | @whuber - on 2) I'd assumed the op was using OpenLayers or similar to overlay the data, in which case it should be automatically reprojected to Web Mercator from EPSG:4326 by MapServer. However how he is overlaying data is unknown. | |
Mar 8, 2011 at 23:18 | comment | added | whuber | Good thoughts. These comments might help: (1) rotation won't fix the problem, because a coordinate reversal is a form of reflection. (2) I suspect difficulties in overlaying the maps occur because Google Maps is using a projection and the OP's map is not. | |
Mar 8, 2011 at 18:48 | history | edited | geographika | CC BY-SA 2.5 |
added 114 characters in body
|
Mar 8, 2011 at 18:19 | history | answered | geographika | CC BY-SA 2.5 |