Finland's railway lines carry no name at all #86

New issue

Closed

opened 2026-08-09 10:35:59 +00:00 by art-bot · 1 comment

art-bot commented

2026-08-09 10:35:59 +00:00

Collaborator

Found auditing every country against docs/country-requirements.md (#77). Violates R93 — a label layer only one country populates is a parity gap, not a steady state.

What the data says

railways.name NULL fi -> 18294/18294  (100%)
railways.name NULL pl -> 96026/126971 (76%)
railways.name NULL se -> 50599/188401 (27%)

Finland's railway network has no line names at all. Sweden names roughly three-quarters of its rail rows and Poland a quarter, so the style's rail labelling does real work in two countries and nothing in the third.

Why

fi_rautatie (MTK) carries geometry, not names — the same split Finland has everywhere else. docs/country-finland.md already states the general shape: names are a separate register of 1,172,377 labelled points, joined by nearest point filtered on the register's own type code (R92). The join simply was never wired for railways.

The fix

Add the name join to railways in conf/fimap.yaml the way water_bodies and stations already do it, filtered to fi_paikannimi's railway-name type code. Prefer Finnish per R92's DISTINCT ON convention so a bilingual line does not get two labels.

Water names are the same class of gap and are already tracked in #21: waterways.name is 100% NULL for is, se and fi, and water_bodies.name is 100% NULL for is and se, against Poland's 87% river coverage. Fixing rail names here should reuse whatever join shape #21 settles on, or vice versa — they are the same mechanism against different type codes.

Acceptance

SELECT count(*) FROM map_railways_12 WHERE country='fi' AND name IS NOT NULL is materially greater than zero, and no line carries two labels.

Found auditing every country against `docs/country-requirements.md` (#77). Violates **R93** — a label layer only one country populates is a parity gap, not a steady state. ## What the data says ``` railways.name NULL fi -> 18294/18294 (100%) railways.name NULL pl -> 96026/126971 (76%) railways.name NULL se -> 50599/188401 (27%) ``` Finland's railway network has no line names at all. Sweden names roughly three-quarters of its rail rows and Poland a quarter, so the style's rail labelling does real work in two countries and nothing in the third. ## Why `fi_rautatie` (MTK) carries geometry, not names — the same split Finland has everywhere else. `docs/country-finland.md` already states the general shape: names are a separate register of 1,172,377 labelled points, joined by nearest point filtered on the register's own type code (**R92**). The join simply was never wired for `railways`. ## The fix Add the name join to `railways` in `conf/fimap.yaml` the way `water_bodies` and `stations` already do it, filtered to `fi_paikannimi`'s railway-name type code. Prefer Finnish per **R92**'s `DISTINCT ON` convention so a bilingual line does not get two labels. ## Related, not included Water names are the same class of gap and are already tracked in #21: `waterways.name` is 100% NULL for `is`, `se` and `fi`, and `water_bodies.name` is 100% NULL for `is` and `se`, against Poland's 87% river coverage. Fixing rail names here should reuse whatever join shape #21 settles on, or vice versa — they are the same mechanism against different type codes. ## Acceptance `SELECT count(*) FROM map_railways_12 WHERE country='fi' AND name IS NOT NULL` is materially greater than zero, and no line carries two labels.

art-bot referenced this issue

2026-08-09 10:40:32 +00:00

#77: write down what a country has to look like, and audit the four we have #87

art-bot was assigned by art

2026-08-09 10:48:49 +00:00