Rasterarray Tiles API
The Mapbox Rasterarray Tiles API serves MRT (Mapbox Raster Tiles) format tiles generated from raster data processed by the Mapbox Tiling Service. This API enables access to advanced raster data formats with support for temporal sequences and job-based processing workflows.
Retrieve rasterarray tiles
get
https://api.mapbox.com/rasterarrays/v1/{tileset_id}/{zoom}/{x}/{y}.mrt
| Required parameters | Type | Description |
|---|---|---|
tileset_id | string | Unique identifier for the raster tileset in the format username.id. |
zoom | integer | Specifies the tile's zoom level, as described in the Slippy Map Tilenames specification. |
{x}/{y} | integer | Specifies the tile's column {x} and row {y}, as described in the Slippy Map Tilenames specification. |
| Required query parameters | Type | Description |
|---|---|---|
access_token | string | Your Mapbox API access token. This token must have the appropriate scopes to access raster array tiles. |
jobid | string | A unique job identifier that references the specific processing job for the raster data. This is typically returned from the Raster Tiling Service when a tileset is processed. Example: clzbftvx6001908mc5z9hddb9 |
Example request: Retrieve rasterarray tiles
# Retrieve an MRT tile with job ID
$curl "https://api.mapbox.com/rasterarrays/v1/mapbox.gfs-temperature/4/28/1989.mrt?access_token=YOUR_MAPBOX_ACCESS_TOKEN&jobid=clzbftvx6001908mc5z9hddb9"
Response: Retrieve rasterarray tiles
The response is an MRT (Mapbox Raster Tile) format file containing the processed raster data. MRT is a binary format optimized for efficient transmission and rendering of raster array data. The response content type is application/octet-stream.
For performance, tiles are delivered with appropriate cache headers to optimize client-side and CDN caching.
Rasterarray Tiles API errors
Response body message | HTTP status code | Description |
|---|---|---|
Bad Request | 400 | The request is malformed or missing required parameters. Check that all required parameters are provided and properly formatted. |
Not Authorized - No Token | 401 | No access token was provided in the query. |
Not Authorized - Invalid Token | 401 | The provided access token is invalid or expired. Check the access token you used in the query. |
Forbidden | 403 | Access to this resource is not allowed. This may occur if: • Your account doesn't have access to this tileset • There's an issue with your account (check your Account page) • You're using an access token with URL restrictions that don't match this request |
Not Found | 404 | The requested tile does not exist. This may occur if: • The tileset ID doesn't exist • The tile coordinates (z/x/y) are invalid or outside the tileset bounds |
Zoom level must be between 0-30. | 422 | The zoom level specified in the query is larger than 30 or contains non-numeric characters. |
Rasterarray Tiles API restrictions and limits
- The default rate limit for the Mapbox Rasterarray Tiles API endpoint is 100,000 requests per minute. もし、レート制限をの数を高くしたい場合は、お問い合わせください。.
- If you exceed the rate limit, you will receive an
HTTP 429 Too Many Requestsresponse. For information on rate limit headers, see the Rate limit headers section. - MRT tiles are binary format files that require using Mapbox libraries or SDKs for decoding and rendering.
- The maximum supported zoom level is 30, though actual available zoom levels depend on the specific tileset and processing parameters.
- For general information on caching, see the Maps APIs caching troubleshooting guide.
このpageは役に立ちましたか？