Skip to content

PB-2246: document Swissnames 3D Tiles #patch #178

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Draft
rotwurstesser wants to merge 1 commit into
base: master
Choose a base branch
from
Draft

PB-2246: document Swissnames 3D Tiles #patch #178

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
37 changes: 29 additions & 8 deletions visualize-data/3d-tiles.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -2,18 +2,24 @@

This service provides 3D tiles through a RESTful API, implementing the [Cesium 3D Tiles specification](https://github.com/CesiumGS/3d-tiles).

Start with the `tileset.json` file for a dataset. The manifest contains the content URLs
and the hierarchy that a 3D Tiles client requires. The content format depends on the
dataset.

The following direct B3DM request applies to datasets that publish B3DM content:

<ApiCodeBlock url="https://3d.geo.admin.ch/<LayerName>/<Version>/<Time>/<Z>/<X>/<Y>.b3dm" method="GET" />

Use the following parameters to define your request:

| Parameter | Example | Description |
| -------------- | -------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| layerName | ch.swisstopo.swissbuildings3d.3d | The technical name of the 3D layer. Possible values are: `ch.swisstopo.swissbuildings3d.3d`, `ch.swisstopo.swisstlm3d.3d`, `ch.swisstopo.swissnames3d.3d`, `ch.swisstopo.vegetation.3d` |
| Version | v1 | The API version |
| Time (optional | 20250501 | Date of tileset generation in ISO-8601 (YYYYMMDD). If you omit this parameter, the most recent tile is returned. |
| Z | 7 | Zoom level |
| X | 54 | Tile column index |
| Y | 21 | Tile row index |
| Parameter | Example | Description |
| --------------- | -------------------------------- | ---------------------------------------------------------------------------------------------------------------- |
| layerName | ch.swisstopo.swissbuildings3d.3d | The technical name of a 3D layer that publishes B3DM content |
| Version | v1 | The API version |
| Time (optional) | 20250501 | Date of tileset generation in ISO-8601 (YYYYMMDD). If you omit this parameter, the most recent tile is returned. |
| Z | 7 | Zoom level |
| X | 54 | Tile column index |
| Y | 21 | Tile row index |

A 3D tile request for swissBUILDINGS3D dataset:

Expand Down Expand Up @@ -62,6 +68,21 @@ example='{
}'
/>

## swissNAMES3D labels

The swissNAMES3D label dataset uses 3D Tiles 1.1. Use its stable manifest URL:

<ApiCodeBlock url="https://3d.geo.admin.ch/ch.swisstopo.swissnames3d.3d/v2/tileset.json" method="GET" />

The manifest references revisioned GLB content. Resolve each content URL from the
manifest. Do not construct GLB URLs directly.

The GLB content exposes these feature metadata properties:

- `text`, `type`, `sourceId`, and `tier`
- `fontSize`, `heightOffset`, and `maxDistance`
- `longitude`, `latitude`, `groundHeight`, and `labelHeight`

## Example: Cesium

An example of a Cesium application using terrain tiles, 3D buildings and a WMTS layer.
Expand Down
Loading