Reference · built on requestCommons signalPlaces & geographic reference

OpenAddresses

Aggregated open address point files and coordinates collected from municipal and national governments worldwide.

Request accessPricing ↗

About

OpenAddresses is a global open data initiative that aggregates, standardizes, and publishes authoritative civic address points from municipal, regional, and national government data sources worldwide. Its collection pipeline harvests address data from hundreds of government open data portals, normalizes the records into a unified schema, and provides downloadable country, state, and city datasets in CSV and GeoJSON formats.

Through Fibric, an operator references open address coordinates and street numbers across international markets, proposing address verification fixes or delivery point coordinates for logistics operations.

This is a reference listing. It documents what Fibric would read from OpenAddresses and what it could propose, based on the publisher's published interfaces. Fibric builds it under a managed deployment when you request it; selecting it here installs nothing.

Inputs

  • Standardized address point records containing latitude, longitude, house number, street name, and city
  • Country, regional, and municipal address dataset archives from batch.openaddresses.io/data
  • Postal codes, district names, and region identifiers from local government cadastral sources
  • Source jurisdiction metadata and collection run timestamps accompanying each dataset
  • Unified schema format conforming to OpenAddresses standard CSV and GeoJSON structures

Proposed actions

Read-only. This feed informs operators; it changes nothing.

Proposed actions are target capabilities. Every action runs propose-first and needs a validated deployment and the appropriate permissions.

What you can build

  • Validate international physical delivery coordinates

    Match international shipping addresses against OpenAddresses civic point datasets, proposing precise delivery coordinates for carrier route planning.

    With Address Repair, Customs Declaration

  • Confirm delivery location drop-offs

    Cross-reference GPS scan points from freight carriers against OpenAddresses building coordinates, proposing delivery dispute resolutions when drop-off points differ.

    With Delivery Dispute, Missed Delivery

  • Build territory coverage baselines across new markets

    Count confirmed physical address density across international regions to propose operational territory boundaries for field service expansions.

    With Territory Balance

Requirements

  • Local storage or database indexing capable of processing large point coordinate collections
  • Parsing logic handling per-jurisdiction CSV or GeoJSON archive downloads
  • Compliance with individual source government license terms cited in metadata summaries
Authentication
None. OpenAddresses datasets are distributed as direct public HTTPS downloads from batch.openaddresses.io requiring no authentication or API keys.

Limits

  • Address coverage varies across countries depending on local government open data availability
  • Datasets are distributed as bulk archive files rather than a hosted real-time search API
  • Update schedules depend on municipal release cycles and OpenAddresses automated harvesting runs

Access and pricing

Reference listing. Public feed access is separate from Fibric integration. If you request this feed, your quote covers the build, usage, and support.

Request OpenAddresses ↗

Questions and answers

Where does OpenAddresses obtain address data?
OpenAddresses harvests data directly from national, state, and local government geographic authorities, cadastre offices, and municipal open data portals.
What data formats are provided by OpenAddresses?
Datasets are distributed as compressed CSV files and GeoJSON archives organized by country, sub-region, and city under batch.openaddresses.io/data.
Are there licensing restrictions on OpenAddresses data?
Data in OpenAddresses is primarily licensed under open government licenses such as CC0, CC BY, and public domain. Each source folder includes license metadata specifying exact attribution requirements.
Ask about OpenAddresses

Ask about the capabilities and requirements in this listing.

For project-specific requirements, contact Fibric.

This Commons signal listing is developed, published, and supported by Fibric. It reads public data published by OpenAddresses (batch.openaddresses.io). Upstream agencies and projects are the property of their respective owners, who are not affiliated with Fibric and do not sponsor or endorse this listing. Trademark policy