I haven't done the math or tried out the locations (can't be bothered as its not causing me the problem) but I do have more thoughts...
The Mercator distortion will be smaller near the equator and get less and less significant as you zoom in (i.e. the map bounds get closer to the centre) I wouldn't be that suprised if the API does take a few short-cuts, for example simplifying the getCenter maths, sacrificing a few metres accuracy for execution speed. It was never intended as a surveyor's tool, after all. Rounding errors will occur in the get/set centre process, inevitable as we translate for lat/long to pixels and back, do some floating point maths etc. I'd agree these should not be significant. What's 'significant'? lats like -26.578515640327577 are supposedly expressing location to within the width of a human hair. Clearly the map tiles aren't as accurate as that! So although the API accepts and generates numbers like that, we must bear in mind its all pretty meaningless after say the sixth decimal place. How does the error you see work out in terms of metres across a given km of map span, what sort of percentage is it? cheers, Ross K --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
