The following URL (with 7 digits in the fraction): https://www.openstreetmap.org/?mlat=41.0404437&mlon=-73.9146759 Ends up being transformed to the following (with the fraction rounded to 5 digits): https://www.openstreetmap.org/?mlat=41.0404437&mlon=-73.9146759#map=19/41.04044/-73.91468 This, of course, puts the marker in the wrong place. Clearly, objects in the OSM database are stored with more precision. Why can't the URL use all of the provided precision? (Google maps has the same issue. It seems you can work around that using "plus codes".) asked 14 Sep '22, 16:51 dpawlyk |
Hi. The marker coordinates in your second URL are not rounded, the Also sixth and seventh digits represent roughly decimeters and centimeters respectively. See http://wiki.gis.com/wiki/index.php/Decimal_degrees Not much in OSM has that kind of precision, except probably survey points and such. The data is stored with huge precision, but objects are mapped from satellite imagery and GPS tracks, where the precision is usually is the meter range. So if the marker is not where you expected it, I suppose the coordinates are wrong, or the mapping around it is shifted. Regards. answered 14 Sep '22, 17:40 H_mlet |
The marker is in the correct position. What gets rounded is the centre point of the map display, meaning that the marker will not be 100% at the centre of the screen, but given that the marker only makes up a fraction of the screen space, you will not even notice it being off centre by a few pixels. answered 14 Sep '22, 17:32 Frederik Ramm ♦ |
Err. It looks like the issue is with the source.
Thanks.