Reference · built on requestCommons signalPlaces & geographic reference

geoBoundaries

Open global administrative boundary polygons from ADM0 to ADM5 maintained by William & Mary geoLab.

About

geoBoundaries is an open database of political administrative boundaries maintained by the William & Mary geoLab. The project aggregates, standardizes, and tracks legal territorial boundaries across sovereign states down to sub-national units from ADM0 through ADM5. Every boundary entry provides standardized metadata including ISO codes, boundary type definitions, and direct links to GeoJSON, TopoJSON, and shapefile downloads.

Through Fibric, an operator references geoBoundaries geometry to determine jurisdictional coverage, map regional service areas, and align territory assignments across municipal, provincial, and national frontiers without proprietary boundary licensing.

This is a reference listing. It documents what Fibric would read from geoBoundaries 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

  • Country-level ADM0 sovereign administrative boundary polygons and multi-polygons in GeoJSON format
  • Sub-national ADM1 through ADM5 administrative division boundaries including states, provinces, and municipalities
  • Standardized ISO 3166-1 alpha-3 country identifiers and geographic metadata tables
  • Direct download endpoints for GeoJSON, TopoJSON, and shapefile boundary geometries
  • Boundary release metadata and source provenance tracking via the geoBoundaries REST API

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

  • Assign field accounts to sub-national territories

    Evaluate facility coordinates against geoBoundaries ADM1 and ADM2 polygons to associate accounts with provincial sales territories.

    With Territory Balance

  • Validate jurisdictional compliance for delivery regions

    Query ADM2 municipal boundaries to determine whether customer dispatch locations fall within authorized regional operating envelopes.

    With Field Dispatch, Route Resequence

Requirements

  • Geospatial processing libraries capable of parsing GeoJSON and TopoJSON polygons
  • Caching mechanism to store boundary geometries locally for high-frequency point-in-polygon queries
  • Attribution to the William & Mary geoLab in accordance with CC BY 4.0 licensing
Authentication
None. The geoBoundaries API provides open access to boundary datasets without requiring an API key or registration.

Limits

  • Boundary precision varies across jurisdictions depending on underlying government source publications
  • High-resolution geometries can require substantial bandwidth and client memory during transfer
  • Disputed territorial borders follow United Nations cartographic guidelines rather than competing national claims

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 geoBoundaries ↗

Questions and answers

What administrative levels does geoBoundaries provide?
geoBoundaries tracks ADM0 (national borders), ADM1 (states or provinces), ADM2 (counties or districts), and down to ADM5 for select countries where local units are published.
Does geoBoundaries require an API key?
No. The geoBoundaries REST API is freely accessible without an API key or authentication tokens.
What license governs geoBoundaries data?
geoBoundaries is distributed under the Creative Commons Attribution 4.0 International (CC BY 4.0) license.
Ask about geoBoundaries

Ask about the capabilities and requirements in this listing.

For project-specific requirements, contact Fibric.