MBTiles — Raster Tile Pyramid, Zoom 4 to 8
A small raster tile pyramid covering the invented territory, one flat colour per zoom level so a wrongly addressed tile is obvious on sight. The row axis follows the TMS convention, which is flipped relative to the XYZ scheme web maps use — the single most common reason an MBTiles layer renders upside down.
| zoom_level | tile_column | tile_row (TMS) | colour |
|---|---|---|---|
| 4 | 7 | 10 | #26466c |
| 5 | 14 | 20 | #2e5c84 |
| 6 | 29 | 41 | #3a7696 |
| 7 | 59 | 83 | #4a8ea0 |
| 7 | 59 | 82 | #4a8ea0 |
| 8 | 119 | 166 | #60a4ac |
| 8 | 119 | 165 | #60a4ac |
Specifications
- Format
- MBTiles 1.3 (SQLite)
- Tiles
- 7
- Min Zoom
- 4
- Max Zoom
- 8
- Tile Format
- PNG 256x256, one flat colour per zoom
- Row Scheme
- TMS — tile_row is flipped relative to XYZ/Google
- Metadata Keys
- name, format, type, version, description, bounds, center, minzoom, maxzoom, attribution
- Bounds
- -12.64,46.95,-12.36,47.14
Testing contract
Expected to pass- Scenario
- Serve the tileset to a web map that requests tiles in XYZ order.
- Expected result
- Tiles appear right way up only after converting the requested XYZ row to TMS with row = 2^zoom - 1 - y; without the flip the pyramid renders mirrored vertically.
What is a .mbtiles file?
MBTiles is a specification for storing map tiles in a SQLite database. A metadata table records the tile set's name, format, bounds, and zoom range, and a tiles table holds one row per tile keyed by zoom_level, tile_column, and tile_row with the tile image or vector payload as a blob. Crucially, tile_row uses the TMS convention, which is flipped vertically relative to the XYZ scheme most web maps use.
How to use this file
Use an example .mbtiles file to test tile servers, offline map readers, and tile-set converters, verifying the TMS-versus-XYZ row flip, that the metadata bounds agree with the tiles actually present, and that a request outside the zoom range fails cleanly.
How to use this file for testing
“MBTiles — Raster Tile Pyramid, Zoom 4 to 8” is a deterministic Novus Examples fixture for Geospatial, Data import, Performance testing. GeoJSON, GPX, and KML files with points, lines, polygons, and tracks — for testing map tools, route parsers, and geo importers.
Documented properties for this file: MBTiles 1.3 (SQLite). Compare results against paired or grouped companions on this page when present (clean↔damaged, searchable↔scanned, or format twins) so scores stay reproducible across runs.
Download the file once, keep the path stable in CI or local scripts, and treat the spec table as the contract: dimensions, seeds, field lists, and roles are intentional. Corrupt or invalid samples are labelled as such — expect parsers to fail loudly rather than silently accept them.
Geospatial fixtures publish one invented territory across formats, with the coordinate reference system and feature counts documented in specs. Convert or reproject and diff against the twin in the same group; edge-case geometries state exactly which assumption they are built to break.
Related files
- gpkgGeoPackage — Aspatial Attributes Table (no geometry column)A GeoPackage holding an `attributes` table with no geometry at all — the standard's own answer to a lookup table you want to ship alongside your layers. Its gpkg_contents row has null bounds and a null SRS, which is what readers that assume every row is spatial trip over.
- gpkgGeoPackage — Three Feature Layers in One SQLite ContainerThe territory as an OGC GeoPackage: an ordinary SQLite database with the three required metadata tables and three feature layers whose geometry columns hold GeoPackage binary blobs. Unlike a shapefile it carries several geometry types, long column names and real typed columns in one file.
- gpxGPX — Route (rte) Rather Than a TrackA `rte` element: an ordered list of waypoints describing a planned route, with no timestamps because it has not been travelled yet. Many importers only look for `trk` and report this perfectly valid file as empty.
- gpxGPX — Standalone Waypoints OnlyFive `wpt` elements for the towns of the territory, with names, symbols and descriptions but no track or route. It is the GPX equivalent of a point layer, and the third of the three top-level GPX content types.
- osmKestrel Bay Territory — OpenStreetMap XML TwinThe towns and roads in OSM XML: tagged nodes, three highway ways sharing the junction node at Kestrel Bay, and a route relation over them. All object IDs are negative — the convention for objects that have never been uploaded — so nothing here can be mistaken for real OSM data.
- kmlKML — LineString Placemarks With tessellateThe three roads as LineString Placemarks with `tessellate` set, which tells a globe renderer to drape the line over terrain rather than drawing it as a straight chord. Converters that drop the flag produce lines that tunnel through hills.
Generated by generation/geospatial.py. Free for any use, no attribution required — license.