Why does v2 return differet (and better) directions than v3 for the same addresses?

[brandon nauroth]

Given the same start and end address, the v2 maps API returns a better result than v3 in cases where a user includes a placename

 

For example, given the following start and end addresses:

start:

110 se 1st street, gainesville, fl

end:

1601sw 51st ter cabana bch, gainesville, fl

 

If you plug the above two addresses into the examples of the v2 and v3 directions in the pages below, you can see the v2 is able to determine the address for cabana beach apartments.  The v3 just goes to the city center.

 

http://gmaps-samples.googlecode.com/svn/trunk/gdirections/directions.html

http://gmaps-samples-v3.googlecode.com/svn/trunk/drivingdirections/directions-demo.html

 

How can I get the v3 to return a "smart" result like v2?

[api guy]

Does Google or anyone else have an answer for this?  I am also getting different results for the same address from v2 and v3, and v2 is almost always the correct result.

[pi5701]

the examples you posted have NOT the same start and end addresses

[api guy]

what do you mean? obviously when you go to the the example v2 and v3 links brandon gave you need to erase the default From: and To: address (ie erase the san francisco and mountain view stuff)  and paste in the gainesville start/end address that brandon gave for each.  In doing so it is guaranteed the start/end addresses are the same for each.  I just did it and he is right, the result from v2 is correct and the v3 result is completely different.

[Landon Garry]

I doubt this has changed since your post, but navigation using the same start/end addresses give me the exact same result, turn by turn, for both v2 and v3.

[api guy]

did you use the exact same start/end addresses the original poster provided?  because for me they are different. 

 

It does not happen with all addresses -- in fact, most of the time the results will be the same.  But too often the V3 is not handling addresses the same way V2 does. 

 

Here is another post I found supporting this claim:

 

https://groups.google.com/d/topic/google-maps-js-api-v3/uFpuy3lzms8/discussion

 

[Dave]

It's all a matter of what I call a "well formed address". The address you are specifying as the destination is:  1601sw 51st ter cabana bch, gainesville, fl

OK, now play a little artificial intelligence with this and try to figure out *exactly* what you are asking. I mean, just look at the abbreviations being used: "sw", "ter", "bch". How would you expect even a really good AI engine to figure out what you are looking for? And exactly what part of the address is "cabana bch"?

Try this address instead: 1601 SW 51 Terrace, Gainesville, FL 32607 

And also notice that even using V2 and using your end address, you never actually get to SW 51st Terrace. It gets you into the ballpark, but it omits the last two turns. Using the address I specified above gives the exact same results in V2 and V3. 

Dave

[api guy]

but this just proves the point -- end users dont always enter the perfect address, but the interpretation of such addresses should be just as good in v3 as it is in v2.  even if its ballpark by a couple turns, that is wayyyy preferable to miles off target the v3 gives.  the results should be identical, and for some reason v3 isnt able to cope the same way given the same malformed address.  there has to be some sort of fix or way around this?