Finland: airports from MTK-muut lentokenttaalue (already on disk) + airport_points #110

Closed
opened 2026-08-12 21:41:00 +00:00 by art · 2 comments
Owner

Scope: Finland's airports (+ derived airport_points) from MTK lentokenttaalue — the source is already on disk.

Measured (data/fi/fi_mtk_muut.gpkg, 2025-04-03): lentokenttaalue holds 835 airport polygons (kohdeluokat 32411–32418) in the already-fetched MTK-muut file — no fetch change needed, only staging + layers. Like every MTK feature they are unnamed (no name column — measured), so names come from the paikannimi register via the same spatial join water_bodies and stations use (R92).

First steps:

  1. Stage lentokenttaalue (fi_lentokentta staging) and add airports reading it; kohdeluokka gives the airport-type ladder.
  2. Names via the register join (paikannimi, Finnish-preferred).
  3. airport_points per R140.

From #84 — catalogue line in docs/country-finland.md.

Scope: Finland's `airports` (+ derived `airport_points`) from MTK `lentokenttaalue` — the source is **already on disk**. Measured (data/fi/fi_mtk_muut.gpkg, 2025-04-03): `lentokenttaalue` holds **835** airport polygons (kohdeluokat 32411–32418) in the already-fetched `MTK-muut` file — no fetch change needed, only staging + layers. Like every MTK feature they are unnamed (no name column — measured), so names come from the `paikannimi` register via the same spatial join `water_bodies` and `stations` use (R92). First steps: 1. Stage `lentokenttaalue` (fi_lentokentta staging) and add `airports` reading it; kohdeluokka gives the airport-type ladder. 2. Names via the register join (paikannimi, Finnish-preferred). 3. `airport_points` per R140. From #84 — catalogue line in docs/country-finland.md.
Author
Owner

Result is in #147 — #147; the review note is the PR description.

Result is in #147 — https://git.blahonga.org/art/ismap/pulls/147; the review note is the PR description.
Author
Owner

Resolved by !147

Resolved by !147
art closed this issue 2026-08-17 22:10:52 +00:00
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#110
No description provided.