Skip to content

laidig/geocoder-comparison

 
 

Folders and files

NameName
Last commit message
Last commit date

Latest commit

 

History

23 Commits
 
 
 
 
 
 
 
 

Repository files navigation

Comparing Geocoders

If you're thinking about moving off of Google Maps, by far the most difficult piece of the stack to replicate is its geocoder. Google probably has the most comprehensive database and by far the best address parsing. It also has this problematic line in its terms of service:

Note: the Geocoding API may only be used in conjunction with a Google map; geocoding results without displaying them on a map is prohibited. For complete details on allowed usage, consult the Maps API Terms of Service License Restrictions.

So, no Google map, no Google geocoder.

We do have other options, of course:

##Usage: This depents on setting environment variables for geocoder keys. source setup_env.sh script, when appropriately configured with your keys, will set them.

Once that is set, all that is necessary is to run python bin/geocode.py [INFILE]. This will write out a file called out.csv

About

A test of various geocoders available on the web

Resources

Stars

Watchers

Forks

Releases

No releases published

Packages

No packages published

Languages

  • Python 97.7%
  • Shell 2.3%