Geocoding APIs compared: Pricing, free tiers and terms of use

1

Pelias

Are you committed to running the process locally due to privacy or legal reasons? If not, we securely run geocoding batches of that size at Geocode Earth all the time at pretty competitive rates. We are flexible on data transfer, usually we have customers set up an SFTP server or an S3 bucket and send us the credentials. We spin up a ton of hardware in EC2 to geocode it real fast (<24 hours even for a few hundred million addresses), will work with any data format you need, and then send it back. If you _do_ need to run it locally, we're also the creators of the Pelias geocoder(https://pelias.io), which is open source like Nominatim but supports more than just OSM data (which is not a comprehensive address source globally), so often can return better results. We can help you set it up if you need.

#Maps #Mapping And GIS #Web Mapping 3 social mentions

2

OpenCage Geocoder

#Geolocation API #Geocoding #Geolocation 15 social mentions

3

OpenRouteService.org

No mention of OpenRouteService, which you can spin up locally yourself and which offers a variety of similar services: https://openrouteservice.org/.

#Operating Systems #Network & Admin #Linux 16 social mentions

4

Geocode Earth

Geocoding is a really fun (and sometimes frustrating) problem I've been lucky enough to have been working to solve for over 10 years now. I joined Mapzen in 2015 which ostensibly was part of a Samsung startup accelerator, but looking back, it's more descriptive to say it was an open-source mapping software R&D lab. We built what is now foundational open-source geospatial tools like the Pelias geocoder (my team) and the Valhalla routing engine. A lot more projects like the Tangram map renderer are still really useful post-Mapzen. A reasonable, but very wrong, first assumption about geocoding is that with a database of places you're almost there. Inputs are often structured, like some addresses, but the structure has so many edge cases you also have to effectively consider it unstructured. The data is the same, sometimes worse as a lot of data sources are quite bad. Over the last 10 years we've explored most strategies for full text search, and no ONE solution knocks it out of the park. We started with really simple "bag of words" search, just looking at token matches. That, fairly predictably was mostly a mess. With billions of places in the world recorded in open datasets, there's going to be something irrelevant somewhere that matches, and probably drowns out whatever you're looking for. Parsing inputs for structure is an enticing option too, but for any pattern you can come up with, there's either a search query or some data that will defeat that structure (try me). The previous generation of ML and a lot of sweat by Al Barrentine produced libpostal(https://github.com/openvenues/libpostal). We think we have a really compelling combination of functionality, quality, liberal usage license (hi simonw!), and open-source commitment. We always love hearing from people interested in anything geocoding so say hello :).

#Geocoding #Maps #Address Verification API 6 social mentions