Integrations
The analysis is not a file you fetch and lose. It is a live layer in the stack you already run — QGIS, Netigma, ArcGIS, the municipal desk. One host, one key, the protocols GIS already speaks.

Why it is not a file
A GeoTIFF in the inbox is a one-off. It sits on a laptop. The next team cannot find it. The municipal GIS never sees it.
We publish the same work as tiles. Your map client asks for the square it is looking at. The layer updates when the analysis does. Nothing to import, nothing to version by hand.
How it lands
A manager turns the tile server on, copies the URL and the key, and pastes them into the GIS the organisation already uses. No new desktop. No new login for the map desk.
01
Your organisation gets one host and one API key. The key is yours to generate, rotate or delete.
02
Each place has a URL by name and year — not by an internal analysis id. Latest year is the default.
03
QGIS, Netigma, ArcGIS or any client that speaks XYZ or WMTS. The map fills the tiles from the view.
One host for every product. The client you already have is enough.
XYZ
The URL every web map and most desktop GIS already know. Zoom, x, y. Paste it. The map fills the rest.
WMTS
The standard municipal and enterprise GIS ask for. GetCapabilities, then the layer. Same pictures as XYZ.
Surface temperature by place and year. The layer a city desk already wants on the heat map.
Smart CitiesAir Mapper writes the mosaic. Mission Control is where you read it. The same centimetre layer sits in the GIS.
NDVI and the plant-health layers, next to the rest of the holding.
Agriculture & LivestockZeus
Monday, Zeus runs the city's heat again. The PDF lands in the inspector's inbox. The GIS already has that layer — they pasted the URL once. The new week is the new tiles.
ZeusTalk to us. We enable the tile server for your organisation and send the URL the GIS desk pastes.
Talk to us