Terrain, buildings and airports exist for Iceland alone, and nobody else's catalogue says why #84

Closed
opened 2026-08-09 10:35:59 +00:00 by art-bot · 2 comments
Collaborator

Found auditing every country against docs/country-requirements.md (#77). Flags R13 — a layer one country has and its neighbours do not is a parity gap until proven otherwise.

What the data says

Seven layers exist for Iceland and no other country:

layer zooms source
contours z10–14 IS 50V
peaks z11–14 IS 50V
buildings z12–14 IS 50V
airports z10–13 IS 50V
airport_points z8–13 derived
settlements, settlement_points z4–12 legacy, retired by the fix in the Iceland places issue

The first five are real capability. They are also the reason Iceland's map reads as a finished map and the other three read as basemaps: contour lines, named peaks, building footprints and airports are most of what makes a topographic map look topographic.

Where the other countries stand

  • Finland is the only one to have taken a position. conf/fimap.yaml records skipping MTK's contours (33 GB), terrain edges (28 GB), bogs (18 GB), rock (4 GB) and buildings (4 GB) as "out of scope for Sweden parity" — a size decision, not a data one. That reasoning reads oddly now: it names as the parity target the country with fewer layers, which is how a gap becomes permanent.
  • Sweden and Poland do not address these themes in their catalogues at all. Lantmäteriet Topo 10 and BDOT10k both carry buildings; both countries have national elevation products.

What this issue is for

Not to import five layers into three countries. It is to make R5/R13 true: each country's available → imported → worth-importing catalogue must state, for each of contours, peaks, buildings and airports, either yes and here is the source and the size or no and here is why. Once that exists, the actual imports are separately-scoped issues with a known cost.

Finland's entry is half-written already — the sizes are known, only the verdict needs revisiting.

Acceptance

docs/country-sweden.md, docs/country-poland.md and docs/country-finland.md each carry a line per layer in their catalogue, and any that are worth importing have their own issue.

Found auditing every country against `docs/country-requirements.md` (#77). Flags **R13** — a layer one country has and its neighbours do not is a parity gap until proven otherwise. ## What the data says Seven layers exist for Iceland and no other country: | layer | zooms | source | |---|---|---| | `contours` | z10–14 | IS 50V | | `peaks` | z11–14 | IS 50V | | `buildings` | z12–14 | IS 50V | | `airports` | z10–13 | IS 50V | | `airport_points` | z8–13 | derived | | `settlements`, `settlement_points` | z4–12 | legacy, retired by the fix in the Iceland `places` issue | The first five are real capability. They are also the reason Iceland's map reads as a *finished* map and the other three read as basemaps: contour lines, named peaks, building footprints and airports are most of what makes a topographic map look topographic. ## Where the other countries stand - **Finland** is the only one to have taken a position. `conf/fimap.yaml` records skipping MTK's contours (33 GB), terrain edges (28 GB), bogs (18 GB), rock (4 GB) and buildings (4 GB) as *"out of scope for Sweden parity"* — a size decision, not a data one. That reasoning reads oddly now: it names as the parity target the country with **fewer** layers, which is how a gap becomes permanent. - **Sweden** and **Poland** do not address these themes in their catalogues at all. Lantmäteriet Topo 10 and BDOT10k both carry buildings; both countries have national elevation products. ## What this issue is for Not to import five layers into three countries. It is to make **R5**/**R13** true: each country's available → imported → worth-importing catalogue must state, for each of `contours`, `peaks`, `buildings` and `airports`, either *yes and here is the source and the size* or *no and here is why*. Once that exists, the actual imports are separately-scoped issues with a known cost. Finland's entry is half-written already — the sizes are known, only the verdict needs revisiting. ## Acceptance `docs/country-sweden.md`, `docs/country-poland.md` and `docs/country-finland.md` each carry a line per layer in their catalogue, and any that are worth importing have their own issue.
Owner

Contours, peaks, airports, airport_points, buildings should all be layers that other countries have. I was hesitant to implement contours because they are always a very heavy layer and slow everything else down, but they should exist.

It will be extra exciting to see if the contour lines will match on the Sweden-Finland border (even here, I want to use the national data, not default to some global DEM).

Contours, peaks, airports, airport_points, buildings should all be layers that other countries have. I was hesitant to implement contours because they are always a very heavy layer and slow everything else down, but they should exist. It will be extra exciting to see if the contour lines will match on the Sweden-Finland border (even here, I want to use the national data, not default to some global DEM).
Owner

Result is in #111 — #111; the review note is the PR description. Ten follow-up issues filed from the catalogue lines: #101–#110.

Result is in #111 — https://git.blahonga.org/art/ismap/pulls/111; the review note is the PR description. Ten follow-up issues filed from the catalogue lines: #101–#110.
Sign in to join this conversation.
No milestone
No project
No assignees
2 participants
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#84
No description provided.