Enterprise Boundaries v2

Access to Enterprise Boundaries

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


The Enterprise Boundaries vector tiles do not directly contain detailed feature properties such as names or parent boundary information. Such detailed data is delivered separately as offline lookup tables, allowing the vector tiles to stay small and fast. For more details on how to make use of Enterprise Boundaries for data visualizations, see our getting started tutorial.


Enterprise Boundaries are composed of 15 separate tilesets each with their own map ID. There are two types of tilesets: tilesets containing line features and tilesets containing polygon features. For area tilesets, the hierarchy is designed such that levels with lowest numbers generally contain the polygons with the largest areas and levels with the highest numbers contain the polygons with the smallest areas.

Some other notes about tileset hierarchy:

  • Administrative levels are anchored to the a0 layer which contains the top-level polygon of each area which contains an ISO 3166-1 code.
  • Postal levels are anchored on the p4 level which is defined as "Full-detail" or "The minimum required number of digits to send mail".
Tileset IDDescription
mapbox.enterprise-boundaries-a0-v2States or territories that have ISO 3166-1 codes, plus Kosovo
mapbox.enterprise-boundaries-a1-v2First-level administrative areas
mapbox.enterprise-boundaries-a2-v2Second-level administrative areas
mapbox.enterprise-boundaries-a3-v2Third-level administrative areas
mapbox.enterprise-boundaries-a4-v2Fourth-level administrative areas
mapbox.enterprise-boundaries-a5-v2Fifth-level administrative areas
mapbox.enterprise-boundaries-aL-v2Administrative division lines for all levels
mapbox.enterprise-boundaries-p1-v2Postal code grouping areas
mapbox.enterprise-boundaries-p2-v2Postal code grouping areas
mapbox.enterprise-boundaries-p3-v2Postal code grouping areas
mapbox.enterprise-boundaries-p4-v2Full-detail postal code areas
mapbox.enterprise-boundaries-s1-v2First-level statistical areas
mapbox.enterprise-boundaries-s2-v2Second-level statistical areas
mapbox.enterprise-boundaries-s3-v2Third-level statistical areas
mapbox.enterprise-boundaries-s4-v2Fourth-level statistical areas

Geometry types

Each layer in Enterprise Boundary tilesets will contain one of 3 geometry types:

Linestring / multilinestring
Polygon / multipolygon

Area Layer Reference


Each area tileset has a layer named boundaries_{type}_{level}, where {type} is one of admin, postal, or stats, and {level} is a number 0 through 5. The {type} and {level} values correspond to the given tileset.

id text

The id field provides an identifier string for each feature. These IDs are globally unique within a given “worldview”; some are duplicated but only where they represent different versions of the same feature for different worldviews.

worldview text

The vector tiles contain multiple versions of some boundaries, each with a worldview value indicating the intended audience. It is important to apply a worldview filter to all your admin style layers, otherwise your map will show conflicting and overlapping boundary lines. The filter should always include both all and one of the region-specific values.

allAppropriate for all worldviews (most boundaries).
CNBoundaries for a mainland Chinese audience/worldview, but not officially approved for use in the PRC.
INBoundaries conforming to cartographic requirements for use in India.
USBoundaries for an American audience, & which are generally appropriate outside of China & India. (Lines do not necessarily reflect official US foreign policy.)


Each area tileset has a layer named points_{type}_{level}, where {type} is one of admin, postal, or stats, and {level} is a number 0 through 5. The {type} and {level} values correspond to the given tileset.

The points_* layers contain approximate center points corresponding to the polygons in the boundaries_* layers. They can be used for labeling or for visualizations using symbols. Points are generally available one zoom level lower than the polygons they correspond to.

The point layers have the same two id and worldview fields as the area layers with the same meaning.

Administrative Line Layer Reference


The administrative lines tileset contains a single layer containing boundary lines for all administrative levels (a0 through a5).

id text

Boundary line IDs are usually composed by combining the IDs of the polygons from either side of the line (sorted alphanumerically & separated by a hyphen).

admin_level text

The admin_level is a number from 0 through 5 representing the lowest-numbered administrative level the boundary is a part of.

disputed text

Boundary lines with a disputed value of true should have a dashed or otherwise distinct style applied in styles. No single map of the world will reflect all global perspectives, but acknowledging disputes where they exist is an important aspect of good cartography. The value will always be either true or false (never null).

coastal text

The coastal field contains the text true or false indicating whether the boundary is along a coast or not. Most coastal boundaries are omitted from the line layer, so the values are nearly always false.

parent_0 text

For boundaries with an admin_level of 1 through 5, the parent_0 value contains the id of the level 0 area that contains the boundary. For boundaries with an admin_level of 0, the parent_0 is the same as the line id.

worldview text

Same as areas and points; see documentation above.