Integrations

In your GIS.
Not a download.

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

Isolated software dies on the desktop.

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

Enable. Copy. Paste.

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.

  1. 01

    Enable the tile server

    Your organisation gets one host and one API key. The key is yours to generate, rotate or delete.

  2. 02

    Copy the layer

    Each place has a URL by name and year — not by an internal analysis id. Latest year is the default.

  3. 03

    Paste into the GIS

    QGIS, Netigma, ArcGIS or any client that speaks XYZ or WMTS. The map fills the tiles from the view.

The protocols GIS already speaks

One host for every product. The client you already have is enough.

XYZ

Slippy map tiles

The URL every web map and most desktop GIS already know. Zoom, x, y. Paste it. The map fills the rest.

WMTS

OGC Web Map Tile Service

The standard municipal and enterprise GIS ask for. GetCapabilities, then the layer. Same pictures as XYZ.

Zeus

The inbox and the GIS stay in step.

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.

Zeus

Put the layer where the work already happens.

Talk to us. We enable the tile server for your organisation and send the URL the GIS desk pastes.

Talk to us