Right, but I'm confused by the fact that it can geocode to the proper point on the map but not find a route to anywhere else. Here is one example of an address it can't reach, even though it's right up the street:
1703 Orrington Avenue, Evanston, IL Why can't it find a route for these two locations? These are majors streets. On Jan 28, 1:47 pm, Andrew Leach <[email protected]> wrote: > On 28 January 2011 19:34, kghastie <[email protected]> wrote: > > > Here is the offending address: 633 Clark St, Evanston, IL 60208 > > > This maps correctly on maps.google.com, but when I try it in a > > directions request, the whole request fails (ZERO_RESULTS). Any ideas > > on why or what I can do short of validating each address in a route in > > a separate map call ahead of time? > > ZERO_RESULTS means no route could be found between your two points. If > an address cannot be geocoded, you get NOT_FOUND. > > In fact that address geocodes fine. Try > here:http://code.google.com/apis/maps/documentation/javascript/examples/ge... > > Bear in mind, too, that the geocoders in the API and maps.google.com > are different. There's no guarantee that what works in one will work > in the other, and in particular maps.google.com should not be used to > confirm results from the API. -- You received this message because you are subscribed to the Google Groups "Google Maps JavaScript API v3" 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-js-api-v3?hl=en.
