# Using longer coordinates from Earth in Open Street Map - How?

 0 There is no need to move the pin manually if you already have the exact coordinates. Just use the following URL by replacing LAT and LON: ``````http://www.openstreetmap.org/?mlat=LAT&mlon=LON `````` E.g. for the coordinates you mentioned: ``````http://www.openstreetmap.org/?mlat=51.9623976&mlon=-0.495209547 `````` answered 09 Jul '14, 11:57 scai ♦ 33.3k●21●308●459 accept rate: 23%
 0 May have solved the mystery... In the data that Google Earth spits out, there is a Longitude column and a Latitude column. These you would assume, would contain the correct Longitude and Latitude and this is what I had been looking at and getting the problems with. It appears these are incorrect though. There is another column towards the end of the row that has the LON, LAT and ALT combined in one cell. If I actually break these numbers up manually into three, and then use the LON and LAT from there, I finally get the results I want in OSM. And these numbers that are combined in this one cell are slightly different to the original ones I was looking at. At first I thought Excel might be trying to round up or down the numbers in the individual columns containing the LON and LAT separately. But looking at the raw data, it appears not. So I have no idea why Earth is spitting out a second set of near correct coordinates for a point, there seems no reason. Anyone heard of anything like this before? Cheers, Matt answered 10 Jul '14, 16:50 Matthew 11●1●1●2 accept rate: 0% 1 That'd be a question for Google rather than OSM - as I said above: ``````If you search for a feature using Google tools, you won't necessarily get the actual location of that feature back - just something fairly near it. `````` (10 Jul '14, 17:20) SomeoneElse ♦ I don't know the details of your process, but kml files may include lat and long as attributes, as well as the actual lat/long coordinates. While you'd think they're the same, maybe they're not? (10 Jul '14, 17:24) neuhausr
 1 You also need to keep in mind that precision may not be the only problem here. There's also the matter of accuracy. The Google Earth imagery is almost always misaligned to some degree. In some places it can be within a few feet, but I've seen examples where the imagery is out by hundreds of feet. If you want a marker in a particular spot in OSM, you'll want to get the coordinates from OSM to avoid this error. Also, the rounding error between the first two sets of coordinates in your question comes out to a difference of about 3 inches. When you take into consideration that the imagery can be misaligned by many times that, the rounding error becomes negligible. answered 11 Jul '14, 16:53 alester 6.6k●2●66●100 accept rate: 28%
 toggle preview community wiki:

By Email:

Markdown Basics

• *italic* or _italic_
• **bold** or __bold__
• image?![alt text](/path/img.jpg "title")
• numbered list: 1. Foo 2. Bar
• to add a line break simply add two spaces to where you would like the new line to be.
• basic HTML tags are also supported

Question tags:

×235
×144
×11
×9
×4

question asked: 09 Jul '14, 11:47

question was seen: 8,797 times

last updated: 11 Jul '14, 16:53