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.
- Publish your files as COPC (point clouds) or COG (raster models), openly accessible.
- Describe them in a STAC catalog, static or API, with the metadata of this page.
- Send us the address of your catalog.
What your data gains
| Function | Where | What it needs |
|---|---|---|
| Search by area and date | STAC API, QGIS, Python | bbox, geometry and datetime on each item |
| Filters: density, resolution, rendering… | API, STAC Browser | The properties of the items table |
| Tile map: selection, download, total size | STAC Browser | bbox; file:size for the sizes |
| Point cloud in 3D | 3D viewer | Public COPC file, with a CORS header |
| Raster model on the map | 3D viewer, QGIS | Public COG file, with a CORS header; product:type and lidar:render |
| Collection figures: files, years, points, volume | Everywhere | pc:count and file:size on all items |
| License, producer, keywords | Everywhere | The metadata of your collections |
1. Your files
| Point clouds | Raster models | |
|---|---|---|
| Format | COPC (.copc.laz) | Cloud Optimized GeoTIFF (COG) |
| Content | Lidar point cloud | Digital terrain model (DTM), surface model (DSM) or canopy model (DCM), as elevations or as a rendering (hillshade, slopes…) |
| Requirement | Reason |
|---|---|
| HTTPS without authentication, at a public address | The 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: * Recommended | Web viewers, including the 3D viewer, can read your files. |
2. Your catalog
| Form | Address to send us | Links to provide |
|---|---|---|
| Static catalog | …/catalog.json | child to sub-catalogs and collections, item to items. |
| STAC API | Landing page of the API | child or data to /collections; items on each collection, next for the following pages; search recommended. |
- One collection per product and per acquisition (point cloud 2024, DTM 2024…), without other data: a collection is recognized from its items.
- The temporal extent of each collection is filled in.
- The depth of the tree is free. A collection reached through several paths is published only once.
- Parts not to publish (drafts, tests): give us their identifiers.
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):
| Product | Asset type | Item product:type |
|---|---|---|
| Point cloud | application/vnd.laszip+copc | – |
| Terrain model | image/tiff; application=geotiff; profile=cloud-optimized | mnt (or dtm) Required |
| Surface model | mns (or dsm) Required | |
| Canopy model | mnc (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
| Field | Level | Use |
|---|---|---|
geometry and bbox, in WGS84 (longitude, latitude) | Required | Search by area, tile map |
datetime, or start_datetime and end_datetime | Required | Acquisition date, filter by year |
Absolute self link | Required | Link to your item |
title | Recommended | Displayed name |
Absolute href for the assets | Recommended | |
file:size (on the asset) | Recommended | Size of the files and downloads |
proj:code, for example EPSG:2056 | Recommended | Système de coordonnées filter |
mission | Recommended | Mission filter |
Point clouds: pc:count, pc:density, pc:type | Recommended | Nombre de points, Densité (points/m²), Type de nuage de points filters |
Point clouds: pc:schemas, classification:classes (on the asset) | Recommended | Description of the attributes and classes |
Raster models: gsd (resolution in meters) | Recommended | Résolution (m) filter |
Raster models: lidar:render | Recommended | Type de rendu filter, display on the map (below) |
stac_extensions | Recommended | Each 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.
| Value | Rendering |
|---|---|
raw | Raw data: elevations |
hillshade | Hillshade |
multidirectional-hillshade | Multidirectional hillshade |
ambient-occlusion | Ambient occlusion / Sky view factor |
slope | Slopes |
slope-aspect | Aspect and slopes |
archaeology | Archaeological rendering (local relief model) |
color | Colored rendering |
other | Other 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
- Items: your metadata, the file under the
datakey and a link to your item. Point clouds have a « Voir en 3D » link. A missing field is filled in when possible (title,proj:codefromproj:epsg,gsdof the asset). - Collections: their description gives the number of files, the years and, if all your items declare them, the number of points and the volume.
- Tile indexes: one per collection of your catalog, under its title. On a collection's map, you select tiles in it, then download their files or view them in 3D.
- Updates: every night. A file removed from your catalog is removed from ours. If your catalog is unreachable, your last publication is kept. The status of each provider is in the harvest report.
6. Joining
Checking your catalog
- The
catalog.jsonor the API landing page answers over HTTPS, without authentication. - The files are COPC or COG, at a public address, answer range requests and declare their coordinate reference system.
- Each item has a
bboxin WGS84, a date and an absoluteselflink. - The raster models have a
product:typeproperty. - The catalog is valid.
# 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
- Send the catalog's maintainers the name to display, the address of your catalog and, if needed, the parts not to publish.
- We check your catalog and tell you, per collection, whether it is picked up or why it is not.
- Your data is published at the next update, then every night.
| Check message | Fix |
|---|---|
LAZ/LAS non COPC | Convert the files to COPC |
TIFF non COG | Convert the files to COG |
COG sans product:type de modèle | Add product:type (mnt, mns or mnc) to the items |
archive zip | Publish the files without an archive |
URL non publique | Serve the files at a public address |