#106 - Poland: BDOT10k KU* — airport areas (KUKO02 lotnisko lub lądowisko) + airport_points - art/ismap

art commented

2026-08-12 21:41:00 +00:00

Owner

Scope: Poland's airports (+ derived airport_points) from the BDOT10k KU* group.

The source (2021 schema + the fetched OIKM_P, both verified):

OT_KUKO_A/P rodzaj lotnisko lub lądowisko (KUKO02) — the airport/landing-site areas. Not among the 17 fetched classes; it is an overlay over the PTKM transport-surface coverage (which has no RODZAJ column — measured — so cover cannot split airports out of PTKM today; see the cover comment in conf/plmap.yaml). Folding it in needs the same nationwide ST_Difference design as Sweden's sankmark (issue #14).
Already in hand: OIKM_P carries 436 lądowisko dla helikopterów points nationally (measured across all 380 counties) and 0 pas startowy rows — so helicopter pads are available with no fetch change; runways/airport areas need KU*.

First steps:

R6 check: fetch two sample county packages, count OT_KUKO_A rodzaj=lotnisko rows, record GB/rows.
Design the overlay (same problem as #14) or take the airport areas as their own layer without subtracting from PTKM.
airport_points per R140, scheduled-airport filter at coarse zoom.

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

Scope: Poland's `airports` (+ derived `airport_points`) from the BDOT10k KU* group. The source (2021 schema + the fetched OIKM_P, both verified): - **OT_KUKO_A/P** rodzaj `lotnisko lub lądowisko` (KUKO02) — the airport/landing-site *areas*. Not among the 17 fetched classes; it is an overlay over the PTKM transport-surface coverage (which has no RODZAJ column — measured — so `cover` cannot split airports out of PTKM today; see the `cover` comment in conf/plmap.yaml). Folding it in needs the same nationwide ST_Difference design as Sweden's sankmark (issue #14). - Already in hand: OIKM_P carries **436** `lądowisko dla helikopterów` points nationally (measured across all 380 counties) and 0 `pas startowy` rows — so helicopter pads are available with no fetch change; runways/airport areas need KU*. First steps: 1. R6 check: fetch two sample county packages, count `OT_KUKO_A` rodzaj=lotnisko rows, record GB/rows. 2. Design the overlay (same problem as #14) or take the airport areas as their own layer without subtracting from PTKM. 3. `airport_points` per R140, scheduled-airport filter at coarse zoom. From #84 — catalogue line in docs/country-poland.md.

art referenced this issue

2026-08-12 21:44:05 +00:00

#84: R5/R13 catalogue — contours, peaks, buildings and airports now have a line per country, and ten import issues are filed #111

art-bot was assigned by art

2026-08-13 03:49:05 +00:00

art-bot referenced this issue

2026-08-13 19:13:42 +00:00

Closes #14 #116

art referenced this issue

2026-08-13 19:53:14 +00:00

importer: overlay carve as a declared staging kind — base table, overlay table, class map, priority (Poland #106 needs it) #118

art commented

2026-08-13 19:53:20 +00:00

Author

Owner

The "pattern to copy" line in docs/workstream-a.md now points at the generalisation: #118 — overlay carve as a declared staging kind, so #106 is config, not copy-pasted SQL from #14.

art referenced this issue from a commit

2026-08-15 01:58:20 +00:00

#14 review: the sankmark carve is a cell-clipped coverage — ST_CoverageInvalidEdges 1 415 → 0 on partition 23105

art referenced this issue

2026-08-15 01:58:44 +00:00

Closes #14 #116

art added the

claude-wip

label

2026-08-16 23:18:07 +00:00

art referenced this issue from a commit

2026-08-16 23:37:33 +00:00

#106: Poland airports + airport_points from BDOT10k KU* land-use complexes

art commented

2026-08-16 23:37:38 +00:00

Author

Owner

Worked end to end up to the national data (branch issue-106-pl-airports, commit eb55ef0, pushed).

R6 check done — three county packages inspected end to end (1465 Warszawa 88.5 MB, 1206 krakowski 71.3 MB, 1261 m. Kraków 35.2 MB): OT_KUKO_A/P are in every delivery; rodzaj 'lotnisko lub lądowisko' carries 2/2/5 rows. Measured the ladder: TYPLOTNISKA 'port lotniczy' vs 'inne lotnisko lub lądowisko' (the lotnisko register tier → class 1/2); NAZWA populated for registered airports, NULL for the unnamed lądowiska (all 5 of m. Kraków's); IDIATA unusable (registration numbers like '23/2012', wrong codes like '4E' for Chopin) while IDICAO is real where it exists (EPKK/EPWA/EPBC/EPKP).

Implemented + verified on the sample data: staging pl_kuko_a/p; airports (z10–z13, standalone layer over the PTKM fill — the carve is #118's open staging kind) + airport_points (R140, z9 class-1 filter); Makefile class/marker widening (pt-sw-sk-oikm-oipr-skpp-kuk); sources: [pl] in plmap + mapsrv; style layers airports_pl/airport_labels_pl; docs. Acceptance: pl 34 tests, 33 passed / 0 failed / 1 skipped (R105 needs pl_kuko_p, which only loads on a full import); R121 tiles --check PASS; style validates; CDP render shows the Chopin fill + label at z11 and class-1-only labels at z9. Full tally + measurements in run/issues/issue-106.md.

Blocked on the national data: the widened make fetch-bdot10k re-pulls all 380 county zips (~25 GB, multi-hour) before make import-pl can build the national layer — the run rules say never re-download and to flag multi-hour steps rather than start them silently. What I need: run make fetch-bdot10k (marker already widened on this branch) and then the full pl import, or approve this worker to do the fetch. The config/tests/docs are complete and green on the three R6 counties either way.

Worked end to end up to the national data (branch `issue-106-pl-airports`, commit eb55ef0, pushed). **R6 check done** — three county packages inspected end to end (1465 Warszawa 88.5 MB, 1206 krakowski 71.3 MB, 1261 m. Kraków 35.2 MB): `OT_KUKO_A/P` are in every delivery; `rodzaj 'lotnisko lub lądowisko'` carries 2/2/5 rows. Measured the ladder: `TYPLOTNISKA` 'port lotniczy' vs 'inne lotnisko lub lądowisko' (the lotnisko register tier → class 1/2); `NAZWA` populated for registered airports, NULL for the unnamed lądowiska (all 5 of m. Kraków's); `IDIATA` unusable (registration numbers like '23/2012', wrong codes like '4E' for Chopin) while `IDICAO` is real where it exists (EPKK/EPWA/EPBC/EPKP). **Implemented + verified on the sample data**: staging pl_kuko_a/p; `airports` (z10–z13, standalone layer over the PTKM fill — the carve is #118's open staging kind) + `airport_points` (R140, z9 class-1 filter); Makefile class/marker widening (`pt-sw-sk-oikm-oipr-skpp-kuk`); `sources: [pl]` in plmap + mapsrv; style layers airports_pl/airport_labels_pl; docs. Acceptance: pl 34 tests, 33 passed / 0 failed / 1 skipped (R105 needs pl_kuko_p, which only loads on a full import); R121 tiles --check PASS; style validates; CDP render shows the Chopin fill + label at z11 and class-1-only labels at z9. Full tally + measurements in run/issues/issue-106.md. **Blocked on the national data**: the widened `make fetch-bdot10k` re-pulls all 380 county zips (~25 GB, multi-hour) before `make import-pl` can build the national layer — the run rules say never re-download and to flag multi-hour steps rather than start them silently. What I need: run `make fetch-bdot10k` (marker already widened on this branch) and then the full pl import, or approve this worker to do the fetch. The config/tests/docs are complete and green on the three R6 counties either way.

art referenced this issue from a commit

2026-08-17 00:10:33 +00:00

fetch-bdot10k: list the KU* classes as KUKO_A/KUKO_P — the pattern loop already prepends OT_, so OT_KUKO_A produced *OT_OT_KUKO_A* and extracted nothing (25 GB re-pull #106)

art commented

2026-08-17 00:11:45 +00:00

Author

Owner

Correction after the first fetch pass: the widened BDOT10K_CLASSES listed the KU* classes as OT_KUKO_A/OT_KUKO_P, but the fetch recipe's pattern loop already prepends OT_ — so the pattern was OT_OT_KUKO_A, matched nothing, and the first ~25 GB pass touched all 380 markers with zero KU* extraction. Fixed on the branch (37c9ad5c: KUKO_A/KUKO_P) and pushed to origin/issue-106-pl-airports; the 380 bogus markers were removed and the fetch re-ran. Note for whoever finishes: the LOCAL branch ref still points at eb55ef0 — fetch origin and reset before continuing (or just branch from origin/issue-106-pl-airports).

Correction after the first fetch pass: the widened BDOT10K_CLASSES listed the KU* classes as OT_KUKO_A/OT_KUKO_P, but the fetch recipe's pattern loop already prepends OT_ — so the pattern was *OT_OT_KUKO_A*, matched nothing, and the first ~25 GB pass touched all 380 markers with zero KU* extraction. Fixed on the branch (37c9ad5c: KUKO_A/KUKO_P) and pushed to origin/issue-106-pl-airports; the 380 bogus markers were removed and the fetch re-ran. Note for whoever finishes: the LOCAL branch ref still points at eb55ef0 — fetch origin and reset before continuing (or just branch from origin/issue-106-pl-airports).

art referenced this issue from a commit

2026-08-17 07:02:07 +00:00

#110: Finland airports + airport_points from MTK-muut lentokenttaalue

art referenced this issue

2026-08-17 07:02:10 +00:00

# #110: Finland airports + airport_points from MTK-muut lentokenttaalue #147

art referenced this issue

2026-08-17 07:53:53 +00:00

Shared airports + airport_points layer — fold is/se/pl/fi into one MVT source (was: Iceland-only style layers) #149

art referenced this issue

2026-08-17 17:45:59 +00:00

#106: Poland airports + airport_points from BDOT10k KU* land-use complexes #153