TMS
Scheme TMS
Section titled “Scheme TMS”https://prod-data.nimbo.earth/mapcache/tms/1.0.0/{LAYER}@kermap/{z}/{x}/{y}.png?kermap_token=<YOUR_TOKEN>The layer identifier is listed by the service. For monthly imagery it uses
{year}_{month}_{component}, with an unpadded month, such as 2026_8_1.
Parameters
Section titled “Parameters”| Parameter | Meaning |
|---|---|
LAYER | Complete identifier from the service inventory |
z | Zoom level; the map-service grid advertises 0–18 |
x | Column, counted from the west |
y | TMS row, counted from the south |
kermap_token | Your API token |
TMS and XYZ use opposite row directions:
yTMS = 2^z - 1 - yXYZFor MapLibre raster sources use scheme: "tms"; for Leaflet use tms: true.
A client that supports the {-y} placeholder can invert the XYZ row for you.
Apply the inversion once.
The separate Terrain, Terrarium
and Hillshade URLs under /tiles/ use XYZ rows.
Discover layers
Section titled “Discover layers”https://prod-data.nimbo.earth/mapcache/tms/1.0.0/?kermap_token=<YOUR_TOKEN>This XML inventory lists layer-specific metadata URLs. Checked component codes:
| Code | Layer |
|---|---|
1 | RGB |
2 | NIR |
3 | Color-mapped NDVI |
5 | NIMBO HD RGB |
6 | Traceability |
Use the Data Catalog for dated release observations. Layer and month availability differs; constructing a plausible identifier does not establish that the layer exists.
Response checks
Section titled “Response checks”The 2026-09-30 audit confirmed 256 × 256 PNG responses for sampled layers. An HTTP 200 response can also contain a fully transparent no-data image. Invalid layer names returned HTTP 400, and some advertised older layers returned HTTP 502. Check the image and the requested area as well as the status code.
Where to find your kermap token ?
Section titled “Where to find your kermap token ?”Retrieve it from your NIMBO Dashboard. Follow the authentication guide.
Client reference: MapLibre source configuration.