That sounds like the issue. There weren't so many proxies around when we came up with the IP-based solution for limiting geocodes. Please email me offline with details on the Rackspace IPs; we may be able to do something.
- pamela On Fri, Jul 17, 2009 at 5:12 AM, Barry Hunter <[email protected]>wrote: > > One option is to get Google to up the quote for the proxy. Google have > been amenable to raising quotes for well known proxies. First point of > contact is probably Pamala Fox - and just mentioning her name should > be enough get the thread noticed. > > On 16/07/2009, BigJoeTX <[email protected]> wrote: > > > > Just wanted to leave one final update after spending the majority of > > the day tracking this problem down. We talked to our hosting company > > (Mosso / Rackspace Cloud - http://www.rackspacecloud.com/) and every > > single site hosted by these guys goes out of the same two IP > > addresses. I'm 99.9% sure now that this is problem, especially since > > we tested our code on a different server and it worked. > > > > If you're Geocoding on your sites using php, you might think twice > > about using Rackspace Cloud. > > > > Thanks again for all the help, > > Joe > > > > > > On Jul 16, 11:30 am, BigJoeTX <[email protected]> wrote: > > > > If that's your actual live PHP code, then I strongly recommend not > > > > re-geocoding your address every time someone opens your page. Delete > all > > > > that geocoding and use > > > > > > > $latitude=30.627425; > > > > $longitude=-96.304859; > > > > > > That code was just test code I set up that I tried to make as simple > > > as possible to avoid anything else that might be messed up. In > > > practice, that code would write the longitude and latitude to a > > > database when our sales team submits an new entry. Those are then > > > called into our main site from the database. > > > > > > Like I said, we have a limited number of entries per day, 500 at the > > > most across all of our sites were we use the geocoding service. > > > > > > Also, I think this: > > > > > > > From the server, the calls are counted against the quota associated > with > > > > your Google API key. So if you've got 2,000 users and they all use > your > > > > page to perform 10 geocodes each, then your daily 15,000 quota gets > > > > exceeded, and you get error 620 for 24 hours. > > > > > > Might conflict with what Google says here (I found that not too long > > > ago): > http://code.google.com/support/bin/answer.py?answer=93464&topic=12266 > > > > > > Or I'm totally misunderstanding what Google is trying to say. > > > > > > - Joe > > > > > > > > > > > > > -- > > > > Mike Williamshttp://econym.org.uk/gmap > > > > > > > > -- > Barry > > - www.nearby.org.uk - www.geograph.org.uk - > > > > --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
