WMTS integration for your geodata

WMTS integration: your data as a map layer in any GIS package

Data that exists only inside one viewer is rarely put to real use. Web Map Tile Service is the OGC standard for delivering pre-generated map tiles, and it is supported by practically every GIS package, from QGIS and ArcGIS to the web viewers many organisations maintain themselves. GEORIZON publishes your processed data as a WMTS service, so you add it as a layer alongside your own files and alongside national sources, without duplicating or exporting the data.

A standard WMTS service, usable in QGIS, ArcGIS and your own web viewers
Available in the national grid your organisation works in and in Web Mercator
Pre-generated tiles, so performance holds up across large areas
Access per user or per project, secured with tokens rather than open URLs

Why tiles, and when WMTS suits better than WMS

The difference between WMS and WMTS lies in when rendering happens. A WMS builds a new image for exactly the requested extent on every request, which is flexible but becomes heavy as soon as many users pan through a large dataset at once. WMTS works with a fixed tile layout and fixed zoom levels, with tiles prepared in advance. That makes the service predictably fast and easy to cache, which is precisely what you want for aerial imagery, orthophotos and layers derived from a point cloud. GEORIZON serves the tiles in a tile matrix set matching the frame you work in, so your layer coincides with the rest of your mapping without reprojection.

In practice: adding, filtering and combining

Connecting starts with the capabilities document of the service, the URL describing which layers, zoom levels and reference systems are available. In QGIS you add that URL under the WMTS connections and pick the layer; in ArcGIS the process is comparable. From that moment your data is simply a layer in your project, which you place beneath your own features, make transparent and query alongside other sources. Because the layer comes straight from your tenant, you always see the current version: process a new survey round and it appears in your GIS without anyone having to circulate a file. For layers you would rather not make public, the service works with tokens and with permissions per project.

Beyond WMTS: viewer, API and download

The WMTS integration is one way to reach your data, and rarely the only one you need. For assessing a situation the viewer works better, with panorama, point cloud and measuring tools in one environment. For integrations with an asset management system or an application of your own the open API is more suitable, because it lets you request objects, measurements and detections individually. And anyone wanting to process the source data in house downloads a selection in common formats such as LAZ or E57. The choice is yours, and every route points at the same dataset in the same tenant. Organisations including ProRail (SpoorInBeeld), the municipality of Nijmegen and Kempkes Landmeten work this way.