My application is sometimes provided with geocodes that are a little "rougher" than I would like. This means that sometimes a location might be a few hundred yards off due to rounding errors. When I try to create driving directions using these geocodes, it sometimes will return as unresolvable because a location falls into a lake or in the middle of a field.
Is there a way to instruct the driving directions to use the nearest drivable location to the geocode I provide? How can I deal with this issue given that I don't control the source data? To illustrate the problem without getting into the api code, I've created the following link to show the problem: http://maps.google.com/maps?output=html&f=d&source=s_d&saddr=tampa&daddr=25.7666666,-80.166666&btnG=Get+Directions If you look at the geocode, you'll see that the destination is in the water, but pretty close to some roads. -- 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.
