Sweden: import Topo 10 tema Höjd — contours and peaks (hojdlinje 5 m, hojdpunkt) #101

Closed
opened 2026-08-12 21:40:59 +00:00 by art · 1 comment
Owner

Scope: Sweden's contours and peaks from Lantmäteriet Topo 10, tema Höjd — one fetch, two layers.

The source (verified against the GEODOK/51 documentation):

  • hojdlinje — Höjdkurva5 (objekttypnr 2401) and Gropkurva5 (2402), 5 m ekvidistans, hojdvarde (height) + stodkurva (every fifth line) + i_glaciar. Iceland's finest contour class is 20 m, so this is the dense end.
  • hojdpunkt — spot heights with hojdvarde, the exact analogue of Iceland's haedarpunktar: elevation markers, unnamed (names would come from the text theme's terrain labels).

The theme is part of the already-negotiated topo10 Geotorget order (approved 2026-07-20) — a new files: entry in conf/semap.yaml plus databases: + layer blocks, no new approval. Size: the theme's GB is in the Geotorget delivery listing (not public); record it on first fetch (R5) — for scale, the largest fetched theme, mark, is 6.4 GB zipped / 13.4 GB on disk.

First steps:

  1. Add hojd_sverige.zip to the topo10 files:; record the zipped/unzipped GB in the catalogue.
  2. Contours as a shared-vocabulary layer: elevation + interval_class like Iceland's (conf/ismap.yaml contours), zoom floors to be decided — 5 m contours are far denser than Iceland's 20 m.
  3. Peaks as elevation markers (filter_only, elevation thinning at coarse zoom), same shape as Iceland's peaks.

The Sweden–Finland border match (maintainer's interest on #84): both countries would then contribute national contours; the first place to check agreement is Tornio–Haparanda.

From #84 — the catalogue line lives in docs/country-sweden.md ("Terrain, buildings and airports").

Scope: Sweden's `contours` and `peaks` from Lantmäteriet Topo 10, tema **Höjd** — one fetch, two layers. The source (verified against the GEODOK/51 documentation): - `hojdlinje` — Höjdkurva5 (objekttypnr 2401) and Gropkurva5 (2402), 5 m ekvidistans, `hojdvarde` (height) + `stodkurva` (every fifth line) + `i_glaciar`. Iceland's finest contour class is 20 m, so this is the dense end. - `hojdpunkt` — spot heights with `hojdvarde`, the exact analogue of Iceland's `haedarpunktar`: elevation markers, unnamed (names would come from the `text` theme's terrain labels). The theme is part of the already-negotiated `topo10` Geotorget order (approved 2026-07-20) — a new `files:` entry in `conf/semap.yaml` plus `databases:` + layer blocks, no new approval. Size: the theme's GB is in the Geotorget delivery listing (not public); record it on first fetch (R5) — for scale, the largest fetched theme, `mark`, is 6.4 GB zipped / 13.4 GB on disk. First steps: 1. Add `hojd_sverige.zip` to the topo10 `files:`; record the zipped/unzipped GB in the catalogue. 2. Contours as a shared-vocabulary layer: elevation + interval_class like Iceland's (`conf/ismap.yaml` `contours`), zoom floors to be decided — 5 m contours are far denser than Iceland's 20 m. 3. Peaks as elevation markers (`filter_only`, elevation thinning at coarse zoom), same shape as Iceland's `peaks`. The Sweden–Finland border match (maintainer's interest on #84): both countries would then contribute national contours; the first place to check agreement is Tornio–Haparanda. From #84 — the catalogue line lives in docs/country-sweden.md ("Terrain, buildings and airports").
Author
Owner

Result is in #202 — #202; the review note is the PR description. (The PR shows mergeable:false against main only because it cherry-picks the #198/#199 contract commits Forgejo's heuristic overlaps; it is actually a clean fast-forward — verified merge-base — and rebases cleanly once #198/#199 land.)

Result is in #202 — https://git.blahonga.org/art/ismap/pulls/202; the review note is the PR description. (The PR shows mergeable:false against main only because it cherry-picks the #198/#199 contract commits Forgejo's heuristic overlaps; it is actually a clean fast-forward — verified merge-base — and rebases cleanly once #198/#199 land.)
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
art/ismap#101
No description provided.