Make sure you're using the "enableHighAccuracy" option. See http://dev.w3.org/geo/api/spec-source.html#position_options_interface
Chad Killingsworth On Jun 9, 5:48 am, Tobe <[email protected]> wrote: > getCurrentPosition returns me something like (xx.xxxxxxxx, > yy.yyyyyyyy) (or with 6 more digits). When I get 14 digits it is much > more precise (reverse-geocoding often returns the street and not just > the quarter). I set the maximumAge to 1000 so that it should be re- > geolocated every 10 seconds. Also don't know why it is so alternating. > > On 9 Jun., 11:44, Miguel Angel Vilela <[email protected]> wrote: > > > > > That sounds like a question about the W3C Geolocation API, I'm not aware of > > the influence of maximumAge or the time it takes to obtain the location in > > the decimal precision for the returned location (assuming that's what you > > mean with 8 vs. 14 floating point numbers). > > > W3C Geolocation API Specificationhttp://dev.w3.org/geo/api/spec-source.html > > > Considering that coordinates with 8 digits after the decimal dot represent a > > precision of 1.11 mm (and with 14 digits a precision of 1.11 nm) I wouldn't > > worry about anything beyond 6 digits (1.11 m) or maybe 7 (1.11 cm). > > > On Tue, Jun 8, 2010 at 23:05, Tobe <[email protected]> wrote: > > > ohhh sure, sounds simple :) Now, it works a lot better, but there is > > > one thing I discovered. When I open the web-application or waited a > > > "long" time since the last localization it just returns a latitude and > > > longitude with 8 floating point numbers. The next times, it always > > > returns 14 floating point numbers. I set the maximumAge to 1000. Is > > > there a logical reason for it or is it just because of the accuracy of > > > the localization? > > > > On Jun 8, 12:31 pm, Miguel Angel Vilela <[email protected]> wrote: > > > > Rather than call the geolocation synchronously, you can calculate > > > distances > > > > in the callback function, so that it's done only when the geolocation > > > result > > > > arrives. > > > > > On Tue, Jun 8, 2010 at 12:12, Tobe <[email protected]> > > > wrote: > > > > > Hi, > > > > > i want to use geolocation and calculate distances from this position > > > > > to a list of places. Can I call the geolocation synchronously to first > > > > > get the position and after that calculate the distances? > > > > > > -- > > > > > 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]<google-maps-js-api-v3%2B > > > > > [email protected]><google-maps-js-api-v3%2B > > > [email protected]> > > > > > . > > > > > For more options, visit this group at > > > > >http://groups.google.com/group/google-maps-js-api-v3?hl=en. > > > > -- > > > 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]<google-maps-js-api-v3%2B > > > [email protected]> > > > . > > > For more options, visit this group at > > >http://groups.google.com/group/google-maps-js-api-v3?hl=en. -- 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.
