On Apr 5, 1:58 pm, Tim <[email protected]> wrote: > Hey everyone, > I am having a strange issue with my implementation of the maps api on > our company website. I have a search function which geocodes user > input and queries it against cached lat lon in an sql database of > franchise locations. you can see it in action > atwww.lavidamassage.com/locations.php. > after it returns the lat lon pair of the query address it figures out > if any centers are within the distance filter and returns the results. > it maps the first result and provides directions from the query > address via the api. the issue is that the address for our Austin, TX > center does not get mapped properly as a destination. if you enter the > centers address as the starting address it can find it just fine, and > even geocodes it properly via the api. any guesses as to why this is > happening to this one address? it works fine in v2 of the api and on > maps.google.com, just not in v3 of the api.
This part of the address seems to be confusing it: (LaVida Massage of Austin, TX) -- Larry -- 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.
