CLI for interacting with and preparing data for the Mapbox Tiling Service.
📚 If you have a question that isn't answered here, please refer to the complete Mapbox Tiling Service documentation.
CONTRIBUTING.md includes information about release processes & running tests. 🙌
- Python >= 3.6 (can be installed via virtualenv)
- Recommended: virtualenv / virtualenvwrapper
pip install mapbox-tilesets will install everything but estimate-area.
If you are using an x86 Mac or Linux machine, run:
pip install 'mapbox-tilesets[estimate-area]'
Otherwise, you will need to install some dependencies.
If you're on an arm64 Mac (e.g., with an M1 chip), you'll need to install GDAL first. On Mac, a simple way is to use Homebrew:
$ brew install gdal
...
$ pip install 'mapbox-tilesets[estimate-area]'Note, Windows is not officially supported at this time.
Windows users need to install GDAL and rasterio.
Then pip install 'mapbox-tilesets[estimate-area]'
If you are using an x86 Mac or Linux machine, run:
pip install 'mapbox-tilesets[estimate-cu]'
Otherwise, you will need to install some dependencies.
If you're on an arm64 Mac (e.g., with an M1 chip), you'll need to install GDAL first. On Mac, a simple way is to use Homebrew:
$ brew install gdal
...
$ pip install 'mapbox-tilesets[estimate-cu]'Note, Windows is not officially supported at this time.
Windows users need to install GDAL and rasterio.
Then pip install 'mapbox-tilesets[estimate-cu]'
In order to use the tilesets endpoints, you need a Mapbox Access Token with tilesets:write, tilesets:read, and tilesets:list scopes. This is a secret token, so do not share it publicly!
You can either pass the Mapbox access token to each command with the --token flag or export it as an environment variable. Acceptable values are:
MAPBOX_ACCESS_TOKENMapboxAccessToken
Set the environment variable with export
export MAPBOX_ACCESS_TOKEN=my.token
- Tileset Sources
- Recipes
- Tilesets
- Activity
tilesets upload-source <username> <source_id> <file>Uploads GeoJSON files to a source for tiling. Accepts line-delimited GeoJSON or GeoJSON feature collections as files or via stdin. The CLI automatically converts data to line-delimited GeoJSON prior to uploading. Can be used to add data to a source or to replace all of the data in a source with the --replace flag.
Please note that if your source data is a FeatureCollection, tilesets must read it all into memory to split it up into separate features before uploading it to the Tilesets API. You are strongly encouraged to provide your data in line-delimited GeoJSON format instead, especially if it is large.
Note: for large file uploads that are taking a very long time, try using the --no-validation flag.
Flags:
--no-validation[optional]: do not validate source data locally before uploading, can be helpful for large file uploads--replace[optional]: delete all existing source data and replace with data from the file--quiet[optional]: do not display an upload progress bar
Usage
# single file
tilesets upload-source <username> <source_id> ./file.geojson
# multiple files
tilesets upload-source <username> <source_id> file-1.geojson file-4.geojson
# directory of files
# Reading from a directory will not distinguish between GeoJSON files and non GeoJSON files. All source files will be run through our validator unless you pass the `--no-validation` flag.
tilesets upload-source <username> <source_id> ./path/to/multiple/files/tilesets upload-raster-source <username> <source_id> <file>Uploads Raster files to a source for tiling. Accepts GeoTIFF, NetCDF and GRIB formats right now. Can be used to add data to a source or to replace all of the data in a source with the --replace flag.
Learn more about the supported formats and using Raster source here.
Flags:
--replace[optional]: delete all existing source data and replace with data from the file--quiet[optional]: do not display an upload progress bar
Usage
# single file
tilesets upload-raster-source <username> <source_id> ./file.tif
# multiple files
tilesets upload-raster-source <username> <source_id> file-1.tif file-4.tifWARNING: add-source is maintained for legacy purposes. Please use the upload-source command instead.
tilesets add-source <username> <source_id> <file>Adds GeoJSON files to a source for tiling. Accepts line-delimited GeoJSON or GeoJSON feature collections as files or via stdin. The CLI automatically converts data to line-delimited GeoJSON prior to uploading.
Please note that if your source data is a FeatureCollection, tilesets must read it all into memory to split it up into separate features before uploading it to the Tilesets API. You are strongly encouraged to provide your data in line-delimited GeoJSON format instead, especially if it is large.
Flags:
--no-validation[optional]: do not validate source data locally before uploading--quiet[optional]: do not display an upload progress bar
Usage
# single file
tilesets add-source <username> <source_id> ./file.geojson
# multiple files
tilesets add-source <username> <source_id> file-1.geojson file-4.geojson
# directory of files
# Reading from a directory will not distinguish between GeoJSON files and non GeoJSON files. All source files will be run through our validator unless you pass the `--no-validation` flag.
tilesets add-source <username> <source_id> ./path/to/multiple/files/tilesets validate-source <path>Validates a line delimited GeoJSON source file locally. Example error output:
Invalid line delimited geojson.tilesets view-source <username> <source_id>
Get information for a tileset source, such as number of files, the size in bytes, and the ID in mapbox:// protocol format.
tilesets list-sources <username>
List all tileset sources from a particular account. Response is an array of sources.
tilesets delete-source <username> <source_id>
Permanently delete a tileset source and all of its files. This is not a recoverable action!
Flags:
-for--force: Do not ask for confirmation before deleting
Usage
# to delete mapbox://tileset-source/user/source_id
tilesets delete-source user source_idtilesets estimate-cu <tileset> -s/--sources <sources> -b/--num-bands <number> --rawEstimates the CU value of a tileset before publishing it. This is useful to understand the estimated cost a given tileset before you start processing the data. Note: This is currently only available to tileset recipes with type raster or rasterarray.
See https://docs.mapbox.com/help/glossary/compute-unit/ for more information.
Flags:
-sor--sources[optional]: Local path to the sources that your recipe points at. This is highly recommeneded.-bor--num-bands[optional]: The number of bands you expect your recipe to select across all layers. This is recommended.--minzoom[optional]: Use this flag if your recipe does not contain a minzoom value.--maxzoom[optional]: Use this flag if your recipe does not contain a maxzoom value.--raw[optional]: This will toggle the pretty print output.
Usage
# Estimate the CUs for 'account.tileset' with sources located in 'path/to/sources/' and a band count of 20.
tilesets estimate-cu account.tileset -s 'path/to/sources/*.grib2' -b 20
# Estimate the CUs for 'account.tileset' for a single source and a band count of 10 (pretty print the results)
tilesets estimate-cu account.tileset -s 'path/to/sources/helloworld.grib2' -b 10 --rawtilesets estimate-area <features> -p/--precision <precision>Estimates tiled area (km2) of features with a specified precision. Accepts line-delimited GeoJSON or GeoJSON feature collections as files or via stdin or a list of string-encoded coordinate pairs of the form "[lng, lat]", or "lng, lat", or "lng lat". Precision must be 10m, 1m, 30cm or 1cm.
Flags:
-por--precision[required]: precision level--no-validation[optional]: do not validate source data locally before area calculation--force-1cm[optional]: the --force-1cm flag must be present to enable 1cm precision area calculation and may take longer for large feature inputs or data with global extents. 1cm precision for tileset processing is only available upon request after contacting Mapbox support
Usage
# GeoJSON feature files
tilesets estimate-area ./file1.geojson ./file2.geojson -p <precision>
# GeoJSON features in stdin redirection 1
tilesets estimate-area -p <precision> < ./file.geojson
# GeoJSON features in stdin redirection 2
cat ./file.geojson | tilesets estimate-area -p <precision>
# GeoJSON features in stdin stream
tilesets estimate-area --precision <precision>
<features>
# coordinate pairs (must be in quotes)
tilesets estimate-area "[lng,lat]" "[lng,lat]" --precision <precision>Prints the Recipe JSON to stdout.
tilesets view-recipe <tileset_id>Validates a Recipe JSON document.
tilesets validate-recipe /path/to/recipe.jsonExample recipe.json:
{
"version": 1,
"layers": {
"trees": {
"source": "mapbox://tileset-source/{username}/trees-data",
"minzoom": 4,
"maxzoom": 8
}
}
}
See more details about the recipe spec here. See recipe examples here.
Example error output:
{
"errors": [
"Unknown top-level key \"potato\"."
],
"valid": false
}Update the Recipe JSON for a tileset. Performs a server-side validation of the new document.
This command only supports tilesets created with the Mapbox Tiling Service.
tilesets update-recipe <tileset_id> /path/to/recipe.jsonCreates a brand new, empty tileset with a recipe passed in from your local filesystem.
tilesets create <tileset_id> --recipe /path/to/recipe.json --name "My neat tileset"The tileset_id is in the form of username.handle - for example "mapbox.neat-tileset". The handle may only include "-" or "_" special characters and must be 32 characters or fewer.
Flags:
--recipeor-r[required]: path to your Recipe JSON document--nameor-n[required]: human-readable name of your tileset. (If your tileset_id is user.my_amazing_tileset, you might want yournamefield to be "My Amazing Tileset".)--descriptionor-d: description of your tileset--privacyor-p: Set the privacy of the tileset. Allowed values areprivateandpublic. By default, new tilesets are private.--attributionor-a[optional]: set tileset attribution. Must be a JSON string, specifically an array of attribution objects, each withtextandlinkkeys. Limited to three attribution objects, 80 characters maximum combined across all text values, and 1000 characters maximum combined across all link values.
Queues a tiling job using the recipe provided. Use to publish a new tileset or update an existing one. Returns a job ID for progress tracking.
This command only supports tilesets created with the Mapbox Tiling Service.
tilesets publish <tileset_id>
Update a tileset's information.
tilesets update <tileset_id>
--name "Hello World"
--description "Say hi to the world"
--privacy=private
--attribution='[{"text":"© Hola Mundo","link":"http://example.com"}]'
Flags:
--nameor-n[optional]: update tileset name--descriptionor-d[optional]: update tileset description--privacyor-p[optional]: set your tileset topublicorprivate--attributionor-a[optional]: set tileset attribution. Must be a JSON string, specifically an array of attribution objects, each withtextandlinkkeys. Limited to three attribution objects, 80 characters maximum combined across all text values, and 1000 characters maximum combined across all link values.
Delete a tileset. By default will prompt you for confirmation before deleting.
tilesets delete <tileset_id>
Flags:
--forceor-fto bypass confirmation prompt.
View the status of the most recent job for a tileset. To get more detailed information about a tileset's jobs, including the timestamps of failed and successful jobs, use the tilesets jobs <tileset_id> command.
tilesets status <tileset_id>
Retrieve a single job for a tileset.
This command only supports tilesets created with the Mapbox Tiling Service.
tilesets job <tileset_id> <job_id>What is a job? Each time you generate or regenerate your output tileset via the publish command (whether that's a new recipe or new source data), a single job is created that processes your data. A tileset can have many jobs, each with a unique identifier. When you publish a tileset, the HTTP response includes the unique job identifier that corresponds to the most recent job. To read more about HTTP design, see this documentation.
Check all jobs associated with a tileset. You can filter jobs by a particular stage - processing, queued, success, or failed.
This command only supports tilesets created with the Mapbox Tiling Service.
tilesets jobs <tileset_id> --stage=processingFlags:
--stage[optional]: filter by the stage of jobs--limit [1-500][optional]: the maximum number of results to return, from 1 to 500. The default is 100.
List all tilesets for an account. Just lists tileset IDs by default. Use the --verbose option for more information.
tilesets list <username>Flags:
--type [vector|raster|rasterarray][optional]: filter results by tileset type--visibility [public|private][optional]: filter results by visibility--sortby [created|modified][optional]: sort results by theircreatedormodifiedtimestamps--limit [1-500][optional]: the maximum number of results to return, from 1 to 500. The default is 100.--verbose[optional]: will list out the entire response object from the API
View the TileJSON for a tileset. tileset_id can be a comma-separated list of up to 15 tilesets for composited requests.
A TileJSON document, according to the specification, attempts to create a standard for representing metadata about multiple types of web-based layers, to aid clients in configuration and browsing.
tilesets tilejson <tileset_id>
Flags:
--secure: By default, resource URLs in the retrieved TileJSON (such as in the "tiles" array) will use the HTTP scheme. Include this query parameter in your request to receive HTTPS resource URLs instead.
Lists total request counts for a user's tilesets in the past 30 days. Returns a pagination key next if there are more results than the return limit that can be passed into another command as the start argument.
tilesets list-activity <account>Flags:
--sortby [requests|modified][optional]: Sorting key (default: requests)--orderby [asc|desc][optional]: Ordering key (default: desc)--limit [1-500][optional]: The maximum number of results to return (default: 100)--indent[optional]: Indent size for JSON output.--start[optional]: Pagination key from thenextvalue in a response that has more results than the limit.