Mapbox Boundaries

Current version: v3

  • Fast rendering of millions of boundaries
  • Connect data to any polygon
  • See data from localized worldviews

Mapbox Boundaries is a collection of global boundary polygons, expertly curated across every country, that supports data visualization and geospatial analysis needs. With Boundaries, you can connect your own tabular data with a managed set of geographical features representing various types of boundaries, such as administrative divisions or postal code areas. Polygons in Mapbox Boundaries are precisely matched to adjacent boundaries, so you can create exact data visualizations and accurate analysis.

You can use Mapbox Boundaries data to support use cases from business intelligence analysis and data journalism to customized territory planning and logistics management. For example, you can:

  • Visualize county-level data like unemployment in the United States
  • Create interactive maps that showcase data like top streaming songs per country
  • Allow users to search for business locations by state or zip code
  • Merge multiple polygons to form custom areas likes sales territories

To see how other Mapbox customers are using Boundaries, take a look at our product page.

Boundaries access

Access to the Mapbox Boundaries tilesets is controlled by your Mapbox account access token. If you do not have access on your account, contact Mapbox sales to request access to Boundaries tilesets.

For more information on access and licensing, refer to our Boundaries FAQ.

If you want to try working with our Boundaries data for free, you can use Mapbox Countries, the high-resolution country polygons tileset available in Mapbox Studio. You can find technical details about this tileset in our vector data reference.

Product format

There are two product components to Mapbox Boundaries: the boundary tilesets themselves, and the supporting metadata for each feature.

  • Boundary tilesets: Mapbox Boundaries is a family of vector tilesets. Each vector tile only contains a minimal set of feature properties, which keeps them small and performant. For more details on the types of tilesets and what is contained in each, refer to the Boundaries Reference section. We do not expose the raw geometries of the boundary shapes in our vector tiles.
  • Metadata: Additional data not stored in the vector tiles such as names, hierarchy information, and official reference codes are provided in offline lookup tables that can be joined and referenced as needed. For some of the boundaries that align with our Geocoding data types (for example, admin and postal), some of the metadata can be retrieved from the Geocoding API.

Boundary types and data levels

There are a few key concepts to get familiar with as you start working with Mapbox Boundaries:

  • Boundary types: Mapbox Boundaries data is categorized into five broad types based on the functions the boundaries serve, such as administrative or postal:
    • admin (adm): Divisions within a country or territory delineated for the purpose of general administration. These usually have a capital and some type of government of their own, with the power to set laws and collect taxes throughout the division.
    • legislative (leg): Constituency areas for various types of legislative assemblies or regional councils. Typically voters elect a single representative to a larger body from each of these areas.
    • locality (loc): These are types of places that do not necessarily represent any official boundaries, but are nonetheless commonly used as definitions of "place".
    • postal (pos): These are approximate areas of mail delivery based on national postal code systems.
    • stats (sta): These are non-administrative boundaries that are most commonly used for statistical purposes. These might be officially defined by a governmental statistical bureau, or they may be historical administrative boundaries that are still relevant for statistical uses.
  • Data levels: Within each boundary type, features are organized into a hierarchy of different numbered levels. Typically, larger-numbered levels will nest under smaller-numbered levels. For example in the United States, counties (admin level 2) are subdivisions of states (admin level 1), which are subdivisions of the country (admin level 0). The number of levels available will differ by country and data type.