Pelias/geocode.earth API
Dec 29,2025

GISBox is a one-stop 3D GIS data editing, conversion and publishing platform that supports editing in multiple GIS formats such as OSGB/GEOTIFF/RVT, converting to 3DTiles/Terrain and publishing.

Introduction

Pelias/geocode.earth API is an open-source geocoding service that provides bidirectional conversion between addresses and coordinates. It supports forward geocoding (finding location coordinates from an address) and reverse geocoding (retrieving specific location information from coordinates), and includes structured geocoding capabilities to handle segmented data (such as house numbers, streets, etc.). The API also offers autocomplete functionality, providing real-time suggestions for location names and returning detailed information including names, addresses, and coordinates. Its typical application scenarios include providing precise address search for mapping services, enabling real-time location navigation for mobile applications, and converting address data into geographic coordinates for spatial analysis.

File Structure

The file structure of the Pelias/geocode.earth API primarily involves the following aspects:

  1. Configuration Directory (config): Contains environment variables, service parameters, and module configurations used to define data sources, API behavior, and third-party integration settings.
  2. Data Import Scripts (imports): Provides import modules for various data sources (e.g., OpenStreetMap, OpenAddresses), supporting data cleaning, format conversion, and spatial index construction.
  3. API Server (api): Implements the core logic of the geocoding service, including query parsing, scoring algorithms, and result formatting, offering search and autocomplete functionality via HTTP interfaces.
  4. Frontend Interface (web): Includes built-in demo pages with interactive maps, search boxes, and result display panels, making it easy for developers to quickly test API functionality.
  5. Test Suite (test): Covers unit and integration tests to verify geocoding accuracy, boundary condition handling, and performance metrics, ensuring service stability.
  6. Documentation Resources (documentation): Integrates API references, deployment guides, and contribution guidelines, with some versions offering multilingual translations and code example libraries.
  7. Dependency Management Files: Defines runtime environments, third-party libraries, and containerized deployment configurations via package.json (Node.js) or Dockerfile.

Pros

  1. Open Data-Driven: Pelias uses entirely open data sources, ensuring data transparency and reliability, and avoiding the data opacity issues of commercial APIs.
  2. Global Coverage: Supports geocoding services worldwide, capable of handling geographic data from different countries and regions.
  3. Local Priority Optimization: When providing search results, it can prioritize local results based on user location, enhancing the user experience.
  4. Multi-Language Support: Supports multiple languages, enabling global users to use the service for geocoding queries.
  5. Flexible Deployment Options: Users can choose between local deployment or cloud services to meet the needs of development projects of varying scales.
  6. Open-Source Community Support: As an open-source project, it has an active developer community that continuously improves and expands its features.

Cons

  1. High Deployment Complexity: Compared to commercial APIs, open-source deployment requires certain technical skills for configuration and maintenance, which may not be as accessible for small teams.
  2. Data Update Frequency Limitations: As an open-source project, data updates may not be as timely as commercial APIs, especially in terms of coverage for emerging regions.
  3. Service Stability Challenges: When self-deploying, users must ensure service stability and high availability on their own, increasing operational costs.
  4. Feature Completeness Differences: Compared to mature commercial geocoding APIs, certain advanced features (such as 3D geocoding, real-time traffic data, etc.) may be lacking.
  5. Limited Commercial Support: Despite an active community, there is a lack of professional commercial support teams, which may require enterprise users to build their own maintenance teams.

Application Scenario

The Pelias/geocode.earth API has a wide range of applications, primarily serving various applications that require geocoding and location data conversion. It can provide precise address search functionality for mapping services, enabling users to quickly locate specific coordinates by entering an address. In mobile application development, this API can enable real-time location navigation, helping users obtain route guidance and information about surrounding points of interest. For data analysis scenarios, it can convert structured address data into geographic coordinates, facilitating spatial analysis and visualization. Additionally, the API is suitable for address parsing in logistics and delivery systems, location search optimization for real estate platforms, and international applications requiring multi-language geocoding services. Its open-source nature also makes it an ideal choice for research institutions and developer communities building customized geocoding tools.

Example

1. Reverse geocoding works in the opposite way: it returns a list of locations near a given latitude/longitude point.


2. The GeoCoder visualization workspace in the earthquake hazard module.

File Opening Mode

1. Multiple interpretations of the input "Ontario, CA" by the Pelias parser.

Related GIS Services

Web Coverage Service (WCS)

Web Feature Service(WFS)

Web Map Tile Service (WMTS)

Tile Map Service (TMS)

References

  1. https://geocode.earth/opensource
  2. https://pelias.io/
  3. https://www.earthscope.org/news/nsf-funded-geocode-project-demonstrates-educational-impact-of-coding-and-using-large-real-world-datasets/
  4. https://geocode.earth/blog/2019/improved-autocomplete-parsing-is-here