Try NIMBO with sandbox data

Use the NIMBO sandbox to answer one technical question first:

Can your application request and display NIMBO raster tiles with the correct tile-grid configuration?

The sandbox contains one fixed, watermarked RGB basemap for July 2023. It uses a public demo token, so you can validate a MapLibre or OpenLayers integration before creating credentials or consuming GeoCredits from your own account.

This page is for web developers

To inspect NIMBO imagery without writing code, use NIMBO Earth Online. To work in QGIS, use the NIMBO QGIS plugin. Continue below only when you are integrating NIMBO into a custom web application or mapping product.

Start with MapLibre

Start with OpenLayers

What the sandbox includes

Item	Sandbox value
Product	NIMBO monthly RGB satellite basemap
Date	July 2023
Layer name	demo_2023_7_1@kermap
Access	Public demo token included in the URL
Delivery	TMS raster tiles
Projection	Web Mercator — EPSG:3857
Tile size	256 × 256 pixels
Purpose	Browser integration and tile-coordinate testing

The demo token is intentionally public

The token on this page can access only the sandbox layer. It is not your personal NIMBO token and does not use your account’s GeoCredit balance.

Sandbox TMS URL

https://prod-data.nimbo.earth/mapcache/tms/1.0.0/demo_2023_7_1@kermap/{z}/{x}/{y}.png?kermap_token=750bf73bb0f6cb9639286ea471b05e335dd4595ce1

The URL contains three tile-coordinate placeholders:

• {z} — zoom level;
• {x} — horizontal tile coordinate;
• {y} — vertical TMS tile coordinate, whose origin is at the bottom-left.

Use the correct Y-axis convention

MapLibre and OpenLayers do not express the TMS Y-axis in the same way.

Client	URL placeholder	Additional configuration
MapLibre GL JS	{y}	Set scheme: 'tms' on the raster source.
OpenLayers	{-y}	Use {-y} in the XYZ source URL.
A native TMS client	{y}	Confirm that the client expects a bottom-left TMS origin.

Do not combine both inversion methods

In MapLibre, use {y} together with scheme: 'tms'. Do not also change the URL to {-y}. In OpenLayers, use {-y} and do not add a second manual inversion.

Test the sandbox in four steps

1. Choose your web-mapping library

   Follow the complete MapLibre tutorial or OpenLayers tutorial. Both examples include the required imports, map container, styles and local development server.

2. Load the public sandbox layer

   Copy the example exactly before modifying the date, layer or authentication settings.

3. Pan and zoom the map

   Confirm that new raster tiles appear continuously and that the imagery is not vertically inverted.

4. Inspect the browser network panel

   Successful requests should target the demo_2023_7_1@kermap layer and return image responses rather than authentication or configuration errors.

A successful first test looks like this

• the map displays watermarked NIMBO imagery for July 2023;
• zoom and pan interactions request additional tiles;
• there are no north–south inversions, repeated tile bands or blank quadrants;
• the browser console does not report failed NIMBO tile requests.

What the sandbox does not validate

The sandbox proves that your client can render one NIMBO TMS layer. It does not validate:

• access to the current NIMBO catalog;
• switching between months, products or resolutions;
• your personal authentication token;
• GeoCredit consumption under real usage;
• production traffic, service levels or caching requirements;
• public, client-facing, OEM or redistribution rights.

It should not be used as the data source of a deployed application.

WMS and WMTS are not TMS URL variants

Do not create a WMS or WMTS URL by replacing /tms/ with /wms/ or /wmts/ in the sandbox template.

• TMS requests individual tiles through {z}/{x}/{y} path parameters.
• WMS uses OGC service requests such as GetCapabilities and GetMap.
• WMTS uses a capabilities document and defined tile-matrix parameters.

For a GIS or OGC-service test, create a NIMBO account and follow the dedicated WMS or WMTS documentation.

Use NIMBO in QGIS Install the NIMBO QGIS plugin, authenticate and browse the monthly layers available to your account.

Connect another GIS Choose WMTS, WMS or TMS according to the capabilities of your GIS software.

Move from the sandbox to your NIMBO account

Once the sandbox works, replace the fixed demo layer with a layer available to your account.

1. Create or open your NIMBO account

   Sign in to NIMBO Earth Online and open your dashboard.

2. Copy your personal API token

   Follow Get your NIMBO API token.

3. Choose a date and product

   Production monthly layer names follow this structure:

   <YEAR>_<MONTH>_<LAYER_CODE>@kermap

4. Replace the demo layer and demo token

   Use the production TMS template below, then retain the client-specific Y-axis convention described above.

https://prod-data.nimbo.earth/mapcache/tms/1.0.0/<YEAR>_<MONTH>_<LAYER_CODE>@kermap/{z}/{x}/{y}.png?kermap_token=<YOUR_TOKEN>

For OpenLayers, replace the final {y} placeholder with {-y}.

Common layer codes

Code	NIMBO layer	Typical purpose
1	RGB — 10 m	Recent satellite basemap and visual monitoring
2	NIR — 10 m	Vegetation and land-surface interpretation
3	NDVI — 10 m	Vegetation-condition visualization
4	Radar	Cloud-independent structural information
5	NIMBO HD — 2.5 m	Finer visual inspection of sites and assets
6	Traceability	Pixel-level acquisition-date information

Available products, dates and resolutions depend on your account and subscription.

Never deploy a personal token in public browser code

A token sent by client-side JavaScript is visible in the source code and browser network requests. Use a personal token only for a private local test that you control. For a public or client-facing application, use an approved backend or production-access architecture and contact NIMBO before deployment.

Choose the right production access

A local prototype and a production application are not the same commercial or technical use.

• Private evaluation: validate the integration locally with the sandbox, then with your own account.
• Internal professional workflow: select the plan and GeoCredit allowance that match the user, layers and expected navigation volume.
• Public or client-facing application: define Enterprise access, token protection, permitted users, traffic, caching and usage rights before deployment.

Read Pricing and usage rights and Tiles and GeoCredits before sizing a production integration.

Continue your integration

Build the MapLibre example Create a complete standalone web page, display the sandbox and switch to an authenticated monthly layer.

Build the OpenLayers example Create an OpenLayers project, configure the TMS Y-axis and update the source for another month.

Understand GeoCredit usage Estimate how zoom, viewport size, dates, layers, users and caching affect tile consumption.

Review attribution requirements Display the correct NIMBO and Copernicus credit in maps, applications and deliverables.

Create or open your NIMBO account

Discuss a production integration