Skip to main content

Custom tilesets

Atlas includes default Mapbox tilesets for Streets, Satellite, and Terrain. A full list of Atlas tilesets and sizes is in data and disk size in system requirements.

Atlas also supports adding custom tilesets in PMTiles format with your own data. You can use your custom tilesets with Mapbox GL JS and custom map styles in Atlas.

Create a custom tileset​

We recommend Tippecanoe for creating vector PMTiles tilesets for Atlas. It streams features from GeoJSON, FlatGeobuf, or CSV into a PMTiles file. For raster tilesets, use the PMTiles CLI.

# Build a PMTiles tileset from a GeoJSON source
$tippecanoe \
    -o ./atlas-server-files/data/my-layer.pmtiles \
    --layer=my_layer \
    --minimum-zoom=0 \
    --maximum-zoom=14 \
    --drop-densest-as-needed \
    my-features.geojson

Converting existing MBTiles tilesets to PMTiles​

PMTiles support only
Atlas v3 only supports custom tilesets in PMTiles format. You will need to convert MBTiles tilesets to PMTiles format first before using them with Atlas.

To convert existing MBTiles tilesets to PMTiles tilesets, use Tippecanoe's tile-join command:

$tile-join -o my-layer.pmtiles my-layer.mbtiles

Deploy to Atlas​

To add your custom tileset to Atlas, upload it to the /data/tilesets directory of your Atlas deployment. For example, for AWS S3 deployments:

$aws s3 cp my-layer.pmtiles s3://<your-bucket>/data/tilesets/my-layer.pmtiles

Cache invalidation follows the same rules as Mapbox tilesets. CDNs can cache PMTiles aggressively because the content of a given path is immutable for a given version. When you regenerate a tileset, change the filename (recommended) or invalidate the CDN cache.

Was this page helpful?