> For the complete documentation index, see [llms.txt](https://docs.mapbox.com/ja/data/boundaries/llms.txt)

# Reference

This reference documentation covers the product specification for all versions of Mapbox Boundaries. Data updates are limited to the latest version of the product.

## Overview

The boundaries data product includes over 3,000,000 boundary features and is organized into various [layer types and levels](https://docs.mapbox.com/ja/data/boundaries/reference/mapbox-boundaries-v4#layer-types-and-levels).

### Geometry

The geometries for each boundary feature are available as polygon, centroid point, and line geometries within a family of **[vector tilesets](https://docs.mapbox.com/ja/data/boundaries/reference/mapbox-boundaries-v4#tilesets)** that can be rendered using [Mapbox GL JS](https://docs.mapbox.com/mapbox-gl-js/api/) or the Maps SDKs for [iOS](https://docs.mapbox.com/ios/maps/guides/) and [Android](https://docs.mapbox.com/android/maps/guides/). Do point in polygon querying on the tilesets using the [Mapbox Tilequery API](https://docs.mapbox.com/api/maps/tilequery/).

### Metadata

Extensive metadata for each feature is provided as **[lookup tables](https://docs.mapbox.com/ja/data/boundaries/reference/mapbox-boundaries-v4#lookup-tables)** (or as **[GeoJSON Files](https://docs.mapbox.com/ja/data/boundaries/reference/mapbox-boundaries-v4#geojson-files)** with a flat file license) which can be used to create data joins to the vector tilesets using Mapbox GL. Basic metadata for some `admin` and `postal` layers can also be fetched via the [Mapbox Geocoding API](https://docs.mapbox.com/api/search/geocoding/#reverse-geocoding).

#### Key fields

A globally unique [`mapbox_id`](https://docs.mapbox.com/ja/data/boundaries/reference/mapbox-boundaries-v4#mapbox_id-text) is used as a primary key to identify every boundary in the boundaries tilesets and the corresponding metadata in the boundaries lookup tables.

If more than one boundary feature share the same `mapbox_id`, they will each have a unique [`worldview`](https://docs.mapbox.com/ja/data/boundaries/reference/mapbox-boundaries-v4#worldview-text) to distinguish between alternate representations of the boundary for local context. Features without any alternate representations are shared by all worldviews and will have `worldview="all"`. A combination of `mapbox_id` and `worldview` will always uniquely identify a single feature.

Every feature is tagged with its [`iso_3166_1`](https://docs.mapbox.com/ja/data/boundaries/reference/mapbox-boundaries-v4#iso_3166_1-text) code to identify the parent territory it belongs to. This is useful for additional data filtering and organization of features.