First off, the overall aim of this project is to take customer locations and string them together to get estimated drive time and directions (as well as perform calculations on those returned values to provide approximate costs). I have been using the GDirections and the load from waypoints method. All of this is working fine, except in instances where a faulty address is included in the list of waypoints.
Since I have seen no method of figuring out which item in the waypoints list was the one to cause the API to send back the error, I have been trying to figure out other ways to verify addresses before I ever bother sending out the request for directions. The newest method I tried to do was to use the Geocoding service's getLatLng method, but that was until I realized that it is sending it's best guess if no exact match is found. This isn't exactly the functionality I was hoping for or needing at this time. I did, however, like the way I could specify the callback function on this method so that I could immediately give an alert back stating the validity of the address. Is there some other method I should look into to verify that an address is going to work in the directions object or am I just going to have to use the directions object to send this new verification request (with only one waypoint) and see if it sends me back the error code again? It seems like verification of an address should be something fairly straightforward, but perhaps I am mistaken. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Google Maps API" 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-API?hl=en -~----------~----~----~----~------~----~------~--~---
