Google and Yahoo each provide a geocoding "API" -- a way for other programs to quickly and easily access their services. But they only allow a certain number of queries per day, based on your IP address. This form uses JavaScript-On-Demand (JSON) code that causes your Web browser to be the one making the request (rather than gpsvisualizer.com), which means your queries don't count against my server's limit. (And thanks are due to the developers of the batch geocoder at BatchGeocode.com for the Yahoo JSON info.)
Sometimes the geocoder returns coordinates that don't seem right. Unfortunately, there's no way to get Yahoo's precision information using this form -- but you can see Yahoo's precision estimate for individual addresses if you run them through the Quick Geocoder.
One common source of errors (aside from missing, misspelled, or poorly-aligned header rows) is non-street addresses that look like addresses, like P.O. Boxes or named buildings. For example, "200 Jackson Building, 333 2nd Street" might be interpreted as "200 Jackson Street" by Yahoo. There's really no way to get around this, other than ensuring that your "address" column contains actual street addresses.
©2003-2012 Adam Schneider, . E-mail: adam gpsvisualizer com.
|