Swiss LiDAR catalog

Publishing your lidar data

The catalog reads your STAC catalog every night and gives access to your files where they are, without copying them. This page explains how to describe your data so that it benefits from all its functions.

  1. Publish your files as COPC (point clouds) or COG (raster models), openly accessible.
  2. Describe them in a STAC catalog, static or API, with the metadata of this page.
  3. Send us the address of your catalog.

What your data gains

FunctionWhereWhat it needs
Search by area and dateSTAC API, QGIS, Pythonbbox, geometry and datetime on each item
Filters: density, resolution, rendering…API, STAC BrowserThe properties of the items table
Tile map: selection, download, total sizeSTAC Browserbbox; file:size for the sizes
Point cloud in 3D3D viewerPublic COPC file, with a CORS header
Raster model on the map3D viewer, QGISPublic COG file, with a CORS header; product:type and lidar:render
Collection figures: files, years, points, volumeEverywherepc:count and file:size on all items
License, producer, keywordsEverywhereThe metadata of your collections

1. Your files

Point cloudsRaster models
FormatCOPC (.copc.laz)Cloud Optimized GeoTIFF (COG)
ContentLidar point cloudDigital terrain model (DTM), surface model (DSM) or canopy model (DCM), as elevations or as a rendering (hillshade, slopes…)
RequirementReason
HTTPS without authentication, at a public addressThe tools read your files directly. A private or local address (http://10.0.0.1/…) is not picked up.
Range requests (Range header, 206 response)The tools read only the useful part of the file.
Coordinate reference system in the file (WKT of the COPC header, georeferencing of the GeoTIFF)Without it, the tools can neither clip nor reproject your data.
CORS header Access-Control-Allow-Origin: * RecommendedWeb viewers, including the 3D viewer, can read your files.

2. Your catalog

Catalogcatalog.json or API CollectionLiDAR 2024 – point cloud CollectionLiDAR 2024 – DTM Itembbox, datetime, pc:density… Itembbox, datetime, product:type… 2546-1212.copc.lazon your server dtm-2024.tifon your server itemasset one item per file, one collection per product and per acquisition
FormAddress to send usLinks to provide
Static catalog…/catalog.jsonchild to sub-catalogs and collections, item to items.
STAC APILanding page of the APIchild or data to /collections; items on each collection, next for the following pages; search recommended.

File names

Each published item is named after its file: SITN_2022_2546-1212.copc.laz → sitn-2022-2546-1212. Unique and stable names keep the links valid from one update to the next.

3. Metadata

Declaring your files

Each file is an asset of its item, with its media type (type):

ProductAsset typeItem product:type
Point cloudapplication/vnd.laszip+copc–
Terrain modelimage/tiff; application=geotiff; profile=cloud-optimizedmnt (or dtm) Required
Surface modelmns (or dsm) Required
Canopy modelmnc (or dcm) Required

Without a type, a file name ending with .copc.laz or .cog.tif is enough. Without product:type, a COG is not picked up: it could be an orthophoto. On a collection of raster models, also declare its types in summaries["product:type"].

Items

FieldLevelUse
geometry and bbox, in WGS84 (longitude, latitude)RequiredSearch by area, tile map
datetime, or start_datetime and end_datetimeRequiredAcquisition date, filter by year
Absolute self linkRequiredLink to your item
titleRecommendedDisplayed name
Absolute href for the assetsRecommended
file:size (on the asset)RecommendedSize of the files and downloads
proj:code, for example EPSG:2056RecommendedSystème de coordonnées filter
missionRecommendedMission filter
Point clouds: pc:count, pc:density, pc:typeRecommendedNombre de points, Densité (points/m²), Type de nuage de points filters
Point clouds: pc:schemas, classification:classes (on the asset)RecommendedDescription of the attributes and classes
Raster models: gsd (resolution in meters)RecommendedRésolution (m) filter
Raster models: lidar:renderRecommendedType de rendu filter, display on the map (below)
stac_extensionsRecommendedEach extension used is declared there

Extensions: Projection, Pointcloud, Classification, Product, File. List of filters: /queryables.

Raster models: render type

Set in lidar:render what the file contains. The viewer stretches the elevations (raw) and shows the renderings as they are.

ValueRendering
rawRaw data: elevations
hillshadeHillshade
multidirectional-hillshadeMultidirectional hillshade
ambient-occlusionAmbient occlusion / Sky view factor
slopeSlopes
slope-aspectAspect and slopes
archaeologyArchaeological rendering (local relief model)
colorColored rendering
otherOther rendering

Without lidar:render, the rendering is deduced from the title or the file name (« hillshade », « ombrage », « slope »…), otherwise raw (other if all its bands are 8-bit).

Collections

Fill in title, description, extent, license (SPDX identifier, or other with a license link), providers and keywords. License, providers and keywords are picked up as they are.

4. Example

A minimal static catalog:

catalog.json                     child links → lidar2024/collection.json
lidar2024/collection.json        item links  → tile-2546-1212.json
lidar2024/tile-2546-1212.json

A point cloud item:

{
  "type": "Feature",
  "stac_version": "1.1.0",
  "stac_extensions": [
    "https://stac-extensions.github.io/pointcloud/v2.0.0/schema.json",
    "https://stac-extensions.github.io/projection/v2.0.0/schema.json",
    "https://stac-extensions.github.io/file/v2.1.0/schema.json"
  ],
  "id": "tile-2546-1212",
  "geometry": { "type": "Polygon", "coordinates": [[[6.94, 46.99], [6.96, 46.99], [6.96, 47.00], [6.94, 47.00], [6.94, 46.99]]] },
  "bbox": [6.94, 46.99, 6.96, 47.00],
  "properties": {
    "datetime": "2024-04-15T00:00:00Z",
    "title": "Tile 2546-1212",
    "proj:code": "EPSG:2056",
    "pc:type": "lidar",
    "pc:count": 31250000,
    "pc:density": 25.0
  },
  "links": [
    { "rel": "self", "href": "https://example.ch/stac/lidar2024/tile-2546-1212.json" }
  ],
  "assets": {
    "data": {
      "href": "https://example.ch/data/lidar2024/2546-1212.copc.laz",
      "type": "application/vnd.laszip+copc",
      "roles": ["data"],
      "file:size": 401234567
    }
  }
}

For a raster model, only the properties and the asset change:

"properties": { "datetime": "2024-04-15T00:00:00Z", "product:type": "mnt", "lidar:render": "raw", "gsd": 0.5, "proj:code": "EPSG:2056" },
"assets": {
  "data": {
    "href": "https://example.ch/data/lidar2024/dtm-2024.tif",
    "type": "image/tiff; application=geotiff; profile=cloud-optimized",
    "roles": ["data"]
  }
}

5. What we publish

<Name>                         collection with your name
├── <Name> – Nuage de points   one item per COPC file
└── <Name> – Modèles raster    one item per COG file

6. Joining

Checking your catalog

# Range requests: the response must be "206 Partial Content"
curl -sI -H "Range: bytes=0-99" https://example.ch/data/lidar2024/2546-1212.copc.laz

# Catalog validation
pip install stac-validator
stac-validator https://example.ch/stac/catalog.json --recursive

Sending us your catalog

  1. Send the catalog's maintainers the name to display, the address of your catalog and, if needed, the parts not to publish.
  2. We check your catalog and tell you, per collection, whether it is picked up or why it is not.
  3. Your data is published at the next update, then every night.
Check messageFix
LAZ/LAS non COPCConvert the files to COPC
TIFF non COGConvert the files to COG
COG sans product:type de modèleAdd product:type (mnt, mns or mnc) to the items
archive zipPublish the files without an archive
URL non publiqueServe the files at a public address