Hi Marcelo, Google has several automated systems to detect and prevent scraping - I suspect your regular requests have run afoul of these. The maximum request rate is not a promise that you can query at that rate indefinitely, rather to help diagnose why you've been blocked.
For your particular case, consider the following alternatives: 1 - use the tiles that we've already generated from the same elevation data. 2 - request more than one point per query. 3 - subsample your region. Our elevation data may have a lower resolution than your target, in which case you would be making redundant requests. Cheers Ben On 27 Mar 2010 19:50, "Marcelo" <[email protected]> wrote: Dann, Thor, I've been trying to use this great new service, but I think I got blocked too soon. I want to create an elevation tileset that fills the screen on my Nexus One, at 800x480 pixels, so that would be a total of 380,000 points, divided by 25,000 a day, about 15.36 days to complete. I started with a batch of 8000 points, sending one query of one point every 2 seconds, and I got blocked after about 250 points. Do I need to go even slower? -- Marcelo - http://maps.forum.nu -- -- You received this message because you are subscribed to the Google Groups "Google Maps JavaScript AP... -- 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.
