As far as I know, the geocoder class in API V3 is not giving location as accurate as GLocalSearch in API V2. That might be the reason the distance is different. I came across the similar location problem and you can view my question here.
http://stackoverflow.com/questions/2935401/google-map-api-v3-geocoder-not-showing-the-correct-place On May 31, 9:28 am, Peter <codehunte...@gmail.com> wrote: > I was currently updating my system from api v2 to api v3. When doing > so I noticed that the two systems gave two different distances from > two points. The two points were as followed: > > (50.749,-2.453) to (52.461783,-1.154466) which are two uk post codes. > The api v2 gave a distance of 179 miles, which is the same as the > google maps website if you type them in, in the directions panel. e.g. > > http://maps.google.com/maps?saddr=50.749,-2.453&daddr=52.461783,-1.15... > > Where as on google maps api v3 the distance was 177 miles. Can anyone > tell me why the results vary becasue it occurs on others aswell. My > google maps setup is just the standard code no fancy business. > > Thanks -- 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 google-maps-js-api...@googlegroups.com. To unsubscribe from this group, send email to google-maps-js-api-v3+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/google-maps-js-api-v3?hl=en.
