Once GDirections has failed with error 602, you can try using GClientGeocoder on the vague address and doing the following if you get multiple possibilities (or just choose the first one and let the user sort it out if it's the wrong one):
http://econym.org.uk/gmap/didyoumean.htm The GDirections geocoder appears to be different from the GClientGeocoder, and in some cases you might get just one possibility returned, in which case you can use that directly without asking "Did you mean...?". For example, in the case of Kapiolani Park, GClientGeocoder only finds one match "Kapiolani Park, Honolulu, HI 96815, USA" Once you've fond the match, don't use the returned address field for the GDirections call because that may still fail. E.g. "Kapiolani Park, Honolulu, HI 96815, USA" still fails in GDirections. Instead use the vague address + @ + latitude,longitude, like this Kapiolani p...@21.266871,-157.818706 The web interface may well think that is an email address and munge it, if so consider it to look like this with [at-sign] replaced by @ Kapiolani Park[at-sign]21.266871,-157.818706 -- http://econym.org.uk/gmap The Blackpool Community Church Javascript Team --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Google Maps API" group. To post to this group, send email to Google-Maps-API@googlegroups.com To unsubscribe from this group, send email to google-maps-api+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/Google-Maps-API?hl=en -~----------~----~----~----~------~----~------~--~---
