On 22 December 2011 06:48, tim-t <[email protected]> wrote: > > The same code works well on a different domain with a different gAPI. > > Any ideas? I don't think I violate TOS, but who knows...
Who knows indeed. It's all being done server-side, so you need to see the result of whatever requests your server code is making. I get a result with this http://lakelocate.com/advanced-search.php?park=&zipstate=Michigan&zipcode=&distance=100&parksize=&submit=Search With this though http://lakelocate.com/advanced-search.php?park=&zipstate=&zipcode=49862&distance=100&parksize=&submit=Search I get no content **at all** so it's not possible to investigate anything. Presumably your server-side code simply stops when it gets an unexpected response to something. However, we can't tell whether you're geocoding "Michigan" as well as "49862". You might want to consider doing the geocoding client-side and firing off a request to your database from the client so you can use JSON or AJAX and refresh the map without reloading the entire page with a new querystring. That distributes the geocoding across your user base rather than concentrating it on your server, and would make violating rate/quantity limits less likely. -- You received this message because you are subscribed to the Google Groups "Google Maps API V2" 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.
