On Dec 29, 6:15 pm, "Neil.Young" <[email protected]> wrote: > Hmm. I'm not sure, whether this explains what happens here. I have > double checked a couple of coordinates from the database (just a few, so > the conclusion might be vague). But for all checked coordinates (used a > GPS device) was the given point from the database exactly as measured by > GPS and correctly displayed on the map, where it should be. > > But if you have some sort of alignment algorithm, which corrects a 4326 > source to match Google's Mercator projection (strange wording, indeed. I > always thought, Mercator is universal...), I could apply that to every > point coordinate and see, what's happening with the polygons.
Google uses a perfect sphere which cartographers hate but which simplifies the math. A real Mercator projection is based on an ellipsoid with different Latitudinal & Longitudinal radii. EPSG:4326 is something else. Exactly what, I am not sure. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Google Maps API" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/Google-Maps-API?hl=en -~----------~----~----~----~------~----~------~--~---
