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]

Re: st: geocode command and google query limit


From   "Dimitriy V. Masterov" <dvmaster@gmail.com>
To   statalist@hsphsun2.harvard.edu
Subject   Re: st: geocode command and google query limit
Date   Mon, 6 Feb 2012 15:06:42 -0500

Lance,

I think you are hitting a limit on how many queries you can send. Once
you exceed the anonymous user limit (~2000-2500 addresses per day),
the geocode variable will be set to 620 for such observations and you
won't get any additional data. If you keep asking repeatedly, it will
continue to produce this result.

You should probably modify your loop to take into account the error
code and the accuracy codes:

GEOCODE ERROR DEFINITIONS:
    200 = no errors
    400 = incorrectly specified address
    500 = unknown failure reason
    601 = no address specified
    602 = unknown address
    603 = address cannot be geocoded due to legal or contractual reasons
    620 = Google Maps query limit reached

GEOSCORE ACCURACY LEVELS:
    0 = unknown accuracy
    1 = country-level accuracy
    2 = region-level (state, province, prefecture, etc.) accuracy
    3 = subregion-level (county, municipality, etc.) accuracy
    4 = town-level (city, village, etc.) accuracy
    5 = postal code-level (zip code) accuracy
    6 = street-level accuracy
    7 = intersection-level accuracy
    8 = address-level accuracy
    9 = premise-level (building name, property name, shopping center,
etc.) accuracy

DVM
*
*   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