> Also don't know why it is so alternating. It's still a question about geolocation, and not a maps API issue.
I understand it, geolocation may use a variety of methods to get a fix - triangulation, GPS, IP, inertial derived from previous fix, etc etc. As most of those take time to work out, they may or may be not available at 10 second intervals. I would imagine that querying at that rate could be returning values from one method or another by turns. I'd expect any of those to return varying numbers of decimal places, but 14 places is all just fantasy, you won't be geolocated to within a few mm, you'll be lucky if it is within a few metres. Reverse geocoding has nothing to do with any of that, and isn't affected by the number of decimal places you feed it. -- You received this message because you are subscribed to the Google Groups "Google Maps JavaScript API v3" 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-js-api-v3?hl=en.
