Andrew, Thank you so much! I figured that it might be that is re-geocoding complete entries. I also changed to the 1sec.
My hosting company is very small so I am pretty sure that there is no one else geocoding. On Dec 7, 11:22 am, Andrew Leach <[email protected]> wrote: > On Dec 7, 4:09 pm, Ryan Wood <[email protected]> wrote: > > > My apologies everyone. I linked the wrong tutorial. > > 1. If you do this > $query = "SELECT * FROM markers WHERE 1"; > then you will geocode all the rows, whether they need it or not. > > A better query might be > $query = "SELECT * FROM markers WHERE lat=0 OR lng=0"; > so that you only select rows which don't have both lat and lng > present. That makes it more efficient when it's re-run. > > 2. You can place a 1 second delay between each query by setting the > initial delay to 1s. > // Initialize delay in geocode speed > $delay = 1000000; > It's a million because usleep uses microseconds. > > 3. Server-side geocoding uses the IP address of the server to do the > tracking. If your server provides shared hosting then you are probably > sharing the IP address and its quota. Rackspace and Salesforce have > been cited here numerous times on this score; but there are others > too, of course. -- 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.
