Frequently Asked Questions
warnings are arrays in the response data from the GET /jobs/<job_id> and GET /jobs endpoints. A tileset job will only have an
errors array if it has failed, describing why it failed. A successful job will have a
warnings array if one or more features were dropped from the resulting tileset.
If you notice that your MTS tileset is missing points, lines, or polygons, it’s likely that MTS dropped some features because the layer size was approaching the maximum allowed size of 500 KB. If you use the GET /jobs/<job_id> endpoint for this tileset job, you will see warnings about how many tiles dropped features and a list of example tiles so you can diagnose the problem.
To avoid hitting the 500 KB limit, you should reduce the number and size of features in each layer. You can do this by:
- Increasing the recipe simplification level.
- Only allowing certain attributes to exist in the final tileset.
- Unioning adjoining features, such as
LineStrings, which reduces the number of features in the tiles.
MTS tries to generate tiles for every requested zoom level. If the zoom levels in a tileset do not match the zoom levels in the corresponding recipe, this is due to features being filtered out based on the rules you have provided, which led to empty tiles at these zooms.
For example, if you specify a minzoom level of
6 but your filtering syntax only starts accepting features at zoom
8, once processing is complete MTS will dynamically set the tileset's
8 since there are no tiles to be requested at zoom
LineStrings happen when high zoom tiles do not have buffers that are large enough. To avoid possible buffer-edge artifacts, set your
buffer_size to something larger than the default of
0.5. The recommended value is
Vector tiles only support integer-based identifiers. If you provide an ID in the tileset source in any format other than integers, MTS will generate an integer hash of this value to use as the feature ID.
If you need to keep the original source IDs, you can do either of the following:
- Use integer IDs in the source data.
- Save the original ID of the feature as an attribute in the vector tiles using the
setoption in your recipe.
If a feature that you expected to see is not in the new tileset, it might have been dropped for one of the following reasons:
- The tileset source data was not valid GeoJSON. You can diagnose the problem by using the Tilesets CLI's
validate-sourcecommand to validate your source data.
- The feature was filtered out by your recipe. For more information on how and why a recipe might filter out a feature, see the Mapbox Tiling Service recipe reference.
- The feature has been simplified away at certain zoom levels. For more information on feature simplification, see the Mapbox Tiling Service recipe reference.
Tileset sources do not support GeoJSON
GeometryCollection features. If you have
GeometryCollection features in your source data, you should split each of its sub-features into a unique, individual feature.
Depending on how your data is distributed or the zoom range you choose, knowing where your data is can be a challenge. Mapbox Studio tries to help you visualize your data at the right location, but due to how it makes this calculation, you may not see any features if there are not any at the mathematical center of the tileset source used to create the tileset. If this occurs, you will need to manually click and drag the map to your feature locations, rather than being able to click "zoom to data".