A modular, open-source geocoder built on top of Elasticsearch for fast and accurate global search.
Announcement: See our update regarding the Mapzen shutdown
What's a geocoder do anyway?
Geocoding is the process of taking input text, such as an address or the name of a place, and returning a latitude/longitude location on the Earth's surface for that place.
... and a reverse geocoder, what's that?
Reverse geocoding is the opposite: returning a list of places near a given latitude/longitude point.
What are the most interesting features of Pelias?
- Completely open-source and MIT licensed
- A powerful data import architecture: Pelias supports many open-data projects out of the box but also works great with private data
- Support for searching and displaying results in many languages
- Fast and accurate autocomplete for user-facing geocoding
- Support for many result types: addresses, venues, cities, countries, and more
- Modular design, so you don't need to be an expert in everything to make changes
- Easy installation with minimal external dependencies
What are the main goals of the Pelias project?
- Provide accurate search results
- Work equally well for a small city and the entire planet
- Be highly configurable, so different use cases can be handled easily and efficiently
- Provide a friendly, welcoming, helpful community that takes input from people all over the world
How does it work?
Magic! (Just kidding) Like any geocoder, Pelias combines full text search techniques with knowledge of geography to quickly search over many millions of records, each representing some sort of location on Earth.
The Pelias architecture has three main components and several smaller pieces.
The importers filter, normalize, and ingest geographic datasets into the Pelias database. Currently there are five officially supported importers:
- OpenStreetMap: supports importing nodes and ways from OpenStreetMap
- OpenAddresses: supports importing the hundreds of millions of global addresses collected from various authoritative government sources by OpenAddresses
- Who's on First: supports importing admin areas and venues from Who's on First
- Geonames: supports importing admin records and venues from Geonames
- Polylines: supports any data in the Google Polyline format. It's mainly used to import roads from OpenStreetMap
We are always discussing supporting additional datasets. Pelias users can also write their own importers, for example to import proprietary data into your own instance of Pelias.
We've built a tool called pelias-schema that sets up Elasticsearch indices properly for Pelias.
This is where the actual geocoding process happens, and includes the components that users interact with when performing geocoding queries. The services are:
- API: The API service defines the Pelias API, and talks to Elasticsearch or other services as needed to perform queries.
- Placeholder: A service built specifically to capture the relationship between administrative areas (a catch-all term meaning anything like a city, state, country, etc). Elasticsearch does not handle relational data very well, so we built Placeholder specifically to manage this piece. It uses SQLite as a backing store, since the amount of administrative data is fairly small.
- PIP: For reverse geocoding, it's important to be able to perform point-in-polygon(PIP) calculations quickly. The PIP service is the only component of Pelias that actually understands polygon geometries, and it is very good at quickly determining which admin area polygons a given point lies in.
- Libpostal: Pelias uses the libpostal project for parsing addresses using the power of machine learning. Originally we loaded the 2GB of libpostal data directly in the API service, but this makes scaling harder and causes the API to take about 30 seconds to start, instead of a few milliseconds. We use a Go service built by the Who's on First team to make this happen quickly and efficiently.
- Interpolation: This service knows all about addresses and streets. With that knowledge, it is able to supplement the known addresses that are stored directly in Elasticsearch and return fairly accurate estimated address results for many more queries than would otherwise be possible.
These are software projects that are not used directly but are used by other components of Pelias.
There are lots of these, but here are some important ones:
- model: provide a single library for creating documents that fit the Pelias Elasticsearch schema. This is a core component of our flexible importer architecture
- wof-admin-lookup: A library for performing administrative lookup using point-in-polygon math. Previously included in each of the importers but now only used by the PIP service.
- query: This is where most of our actual Elasticsearch query generation happens.
- config: Pelias is very configurable, and all of it is driven from a single JSON file which we call
pelias.json. This package provides a library for reading, validating, and working with this configuration. It is used by almost every other Pelias component
- dbclient: A Node.js stream library for quickly and efficiently importing records into Elasticsearch
Finally, while not part of Pelias proper, we have built several useful tools for working with and testing Pelias
Notable examples include:
- acceptance-tests: A Node.js command line tool for testing a full planet build of Pelias and ensuring everything works. Familiarity with this tool is very important for ensuring Pelias is working. It supports all Pelias features and has special facilities for testing autocomplete queries.
- compare: A web-based tool for comparing different instances of Pelias (for example a production and staging environment). We have a reference instance at pelias.github.io/compare/
- dashboard: Another web-based tool for providing statistics about the contents of a Pelias Elasticsearch index such as import speed, number of total records, and a breakdown of records of various types.
Here's an old diagram of how the Pelias components interact:
Note it doesn't include most of the frontend services. We would love help making a new diagram.
The main documentation lives in the pelias/documentation repository.
Additionally, the README file in each of the component repositories listed above provides more detail on that piece.
How can I install my own instance of Pelias?
To try out Pelias quickly, use our Dockerfiles setup. It uses Docker and docker-compose to allow you to quickly set up a Pelias instance for a small area (by default Portland, Oregon) in under 30 minutes.
To do a real installation of Pelias for production use or serious development, read our full installation docs.
What's it built with?
Pelias itself (the import pipelines and API) is written in Node.js, which makes it highly accessible for other developers and performant under heavy I/O. It aims to be modular and is distributed across a number of Node packages, each with its own repository under the Pelias GitHub organization.
For a select few components that have performance requirements that Node.js cannot meet, we prefer to write things in Go. A good example of this is the pbf2json tool that quickly converts OSM PBF files to JSON for our OSM importer.
Elasticsearch is our datastore of choice because of its unparalleled full text search functionality, scalability, and sufficiently robust geospatial support.
We built Pelias as an open source project not just because we believe that users should be able to view and play with the source code of tools they use, but to get the community involved in the project itself.
Especially with a geocoder with global coverage, it's just not possible for a small team to do it alone. We need you.
Anything that we can do to make contributing easier, we want to know about. Feel free to reach out to us via Github, Gitter, email, or Twitter We'd love to help people get started working on Pelias, especially if you're new to open source or programming in general.
Both this meta-repo and the API service repo are good places to get started looking for tasks to tackle. You can also look across all of our issues on our meta-issue tracker, Waffle. We also welcome reporting issues or suggesting improvements to our documentation.
Members emeritus include: