Bookmark and Share

Notice: On March 31, it was announced that Statalist is moving from an email list to a forum. The old list will shut down on April 23, and its replacement, statalist.org is already up and running.


[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

st: geocode command and google query limit


From   Rüdiger Vollmeier <ruediger.vollmeier@googlemail.com>
To   statalist@hsphsun2.harvard.edu
Subject   st: geocode command and google query limit
Date   Sun, 5 Feb 2012 13:14:08 +0100

Dear Stata users,

I ve used the -geocode- command/.ado to locate institutions using the
fulladdress option (using number, street, city, country information).
However, for a high percentage of requests I made I got the error code
620 (Google query limit reached). I am wondering what the best
procedure is to deal with this issue.

So far I did loops over requests until a sufficiently high share of
observations were geolocated and then I discretionally geocoded the
unlocated observations using the Google web interface. However, I feel
that this procedure is highly frustrating and there might be better
procedures. Hence, the following questions popped into my mind:

1. Does anybody have a better idea how to deal with this issue (or, in
other words, how to game Google's query limit)?
2. Does anybody know how this query limit is set by Google? The number
of successful requests is decreasing in the requests requested so far
- but which which requests in the past does Google take into
consideration? What is the critical number of requests when the limit
is applied strictly?
3. Is it helpful to pause in between the requests (e.g. using the
-sleep- command)? How long should I pause it?

Thankful for any suggestions.
*
*   For searches and help try:
*   http://www.stata.com/help.cgi?search
*   http://www.stata.com/support/statalist/faq
*   http://www.ats.ucla.edu/stat/stata/


© Copyright 1996–2014 StataCorp LP   |   Terms of use   |   Privacy   |   Contact us   |   Site index