Different direction results v2->v3 (v3 WRONG)

60 views
Skip to first unread message

FSS Labs

unread,
Feb 11, 2011, 8:38:06 AM2/11/11
to google-map...@googlegroups.com
I have a critical condition effecting a website that I am building. Increasingly the application base is shifting from v2 to v3, and even Google has deprecated v2 completely.

I do not know who to direct this support issue to, but on the internal demo code, version 2 returns the CORRECT directions to my destination (as does maps.google.com), but version 3 returns directions to a destination nearby (on a different road).

Given that this is being used for direction to a client's office, it is not good to be sending clients to the wrong street using the new API's. (I have tried this with each of the 3.x releases using the "v=3.x" value on the script load.

The API demos that I used to verify this, modified locally only to change the destination:




SPECIFIC LOCATION THAT I AM REFERRING TO:

    (any origin) to destination (33.95062845457156,-84.415002509787)

maps.google.com gets this correct:


and tests with JS API v2 gets it correct, but version 2 sends the driver down an adjacent road to a different reverse-geocoded address.

one difference seems to be from the reverse geo-coding that is done somewhere in the API's.
    v2 returns a destination for 33.95062845457156,-84.415002509787 of "UNKNOWN ROAD"
while
    v3 returns the address "161 Village Pkwy NE, Marietta, GA 30067, USA" (which is absolutely incorrect and is on a different road) 

Anyone know how I need to go about getting attention to this problem?

THANKS!
Jay 

Dave Medlicott

unread,
Jan 26, 2012, 7:39:35 PM1/26/12
to google-map...@googlegroups.com
Did you ever figure this out? The location you are looking to get directions to is a private driveway in an apartment complex. Look at it on Google maps and go to streetview.

davie

unread,
Jan 27, 2012, 9:59:11 AM1/27/12
to Google Maps JavaScript API v3
Hi
obviously the coordinates 33.95062845457156,-84.415002509787 are not
on the road and the different decoders are attempting to find the
nearest road
Ge the correct coordinates

Regards Davie
Reply all
Reply to author
Forward
0 new messages