Poland roads: comma-delimited numerdrogi leaks into ref (R63 live-failing) #135

New issue

Open

opened 2026-08-16 00:48:08 +00:00 by art · 0 comments

art commented

2026-08-16 00:48:08 +00:00

Owner

Poland roads: comma-delimited numerdrogi leaks into ref (R63's check fails live)

While porting R63's acceptance test in #123 (2026-08-16): SELECT count(*) FROM map_roads_14_pl WHERE ref ~ '[;,]' returns 114 rows — the requirement's check is live-failing.

The #19 split (regexp_replace(numerdrogi, ';', '|', 'g'), the #39 fix for E77;S7;62) handles the semicolon form only. BDOT10k also delivers comma-delimited refs, which pass through whole:

 75, 28                  | 82  rows | 11 km
 964,768                 |  9
 222, 211207G, 211208G   |  8
 973,202517K             |  8
 964, 768                |  5
 964, 2011K              |  2

The fix is one character in conf/plmap.yaml's roads ref CASE: split on '[;,]' instead of ';' (the existing btrim + "prefer E-number, else first part with a digit" logic then does the right thing for the comma form). It needs a roads reimport (-layer roads; Poland's roads are the heavy layer — the z14 table is ~1.6 GB from 6.8M staging rows, and the merge_from_zoom 12 step is the slow part; budget ~1 h at -jobs 4 -batch-rows 10000).

The acceptance test ships with the fix (the #120 pattern) — the requirement's own check, on the roads layer in conf/plmap.yaml:

SELECT count(*) = 0 AS passed, count(*) AS delimited
FROM map_roads_14_pl WHERE ref ~ '[;,]'

#123's note records the same spec.

Poland roads: comma-delimited `numerdrogi` leaks into `ref` (R63's check fails live) While porting R63's acceptance test in #123 (2026-08-16): `SELECT count(*) FROM map_roads_14_pl WHERE ref ~ '[;,]'` returns **114** rows — the requirement's check is live-failing. The #19 split (`regexp_replace(numerdrogi, ';', '|', 'g')`, the #39 fix for `E77;S7;62`) handles the semicolon form only. BDOT10k also delivers comma-delimited refs, which pass through whole: ``` 75, 28 | 82 rows | 11 km 964,768 | 9 222, 211207G, 211208G | 8 973,202517K | 8 964, 768 | 5 964, 2011K | 2 ``` The fix is one character in `conf/plmap.yaml`'s roads ref CASE: split on `'[;,]'` instead of `';'` (the existing `btrim` + "prefer E-number, else first part with a digit" logic then does the right thing for the comma form). It needs a roads reimport (`-layer roads`; Poland's roads are the heavy layer — the z14 table is ~1.6 GB from 6.8M staging rows, and the merge_from_zoom 12 step is the slow part; budget ~1 h at `-jobs 4 -batch-rows 10000`). The acceptance test ships with the fix (the #120 pattern) — the requirement's own check, on the `roads` layer in `conf/plmap.yaml`: ```sql SELECT count(*) = 0 AS passed, count(*) AS delimited FROM map_roads_14_pl WHERE ref ~ '[;,]' ``` #123's note records the same spec.

art referenced this issue from a commit

2026-08-16 00:48:37 +00:00

#123: Poland's remaining R-checks as acceptance tests (R105, R119)