Warszawa commuter stations from the ZTM GTFS (route_type 2) #63

Open
opened 2026-08-05 10:07:02 +00:00 by art · 0 comments
Owner

Follow-up from PR #60's review (issue #24 — Warszawa stations): the ZTM GTFS that already feeds Poland's stations partition carries commuter rail too, and it is deliberately not imported yet pending a scope decision.

The data (probed 2026-08-05)

  • route_type 2 (rail) = 245 routes, split by agency:
    • agency_id 2 (ZTM itself): the S-lines S1, S2, S3, S4, S40 — SKM, Warsaw's own urban commuter rail, 5 routes, Warsaw-scoped.
    • agency_id 5 (Marszałek Województwa Mazowieckiego): WKD (A1, A12) + KM (R1…R90, RE1…RE92, RL, Z7) — regional rail reaching well beyond Warsaw across Mazovia.
  • The style needs no change: station_icons already filters on commuter and the J sprite exists (Sweden populates it). gtfsMode (importer/gtfs.go) would need 2 → commuter (currently the default type2), and the stations query gains a commuter branch with importance 2 (fills the z11 band) — Poland's z9–z11 station levels are empty today, and once #57 lands Warsaw will render transit lines at z9–z11 with no stations on them at all, where Stockholm shows both.
  • The loader's per-type agencies: narrowing (importer/gtfs.go:166,206 — the mechanism Sweden uses for pendeltåg) can scope the import: agencies: {2: ["2"]} keeps it to SKM.

The decision

How far out should the map go? Options, roughly:

  1. SKM only (agencies: {2: ["2"]}) — stays "Warszawa stations" in spirit.
  2. SKM + WKD — the loader cannot split agency 5 by route without a code change, so this means all 245 routes (scatters stations across Mazovia).

Verify against the live DB

Row counts per zoom, the z11/z9 bands filling, a decoded tile with mode='commuter' rows, real-browser render with the J badge at z11+.

Follow-up from PR #60's review (issue #24 — Warszawa stations): the ZTM GTFS that already feeds Poland's `stations` partition carries commuter rail too, and it is deliberately not imported yet pending a scope decision. ## The data (probed 2026-08-05) - route_type 2 (rail) = 245 routes, split by agency: - agency_id 2 (ZTM itself): the S-lines S1, S2, S3, S4, S40 — SKM, Warsaw's own urban commuter rail, 5 routes, Warsaw-scoped. - agency_id 5 (Marszałek Województwa Mazowieckiego): WKD (A1, A12) + KM (R1…R90, RE1…RE92, RL, Z7) — regional rail reaching well beyond Warsaw across Mazovia. - The style needs **no change**: `station_icons` already filters on `commuter` and the J sprite exists (Sweden populates it). `gtfsMode` (importer/gtfs.go) would need `2 → commuter` (currently the default `type2`), and the stations query gains a commuter branch with importance 2 (fills the z11 band) — Poland's z9–z11 station levels are empty today, and once #57 lands Warsaw will render transit lines at z9–z11 with no stations on them at all, where Stockholm shows both. - The loader's per-type `agencies:` narrowing (importer/gtfs.go:166,206 — the mechanism Sweden uses for pendeltåg) can scope the import: `agencies: {2: ["2"]}` keeps it to SKM. ## The decision How far out should the map go? Options, roughly: 1. SKM only (`agencies: {2: ["2"]}`) — stays "Warszawa stations" in spirit. 2. SKM + WKD — the loader cannot split agency 5 by route without a code change, so this means all 245 routes (scatters stations across Mazovia). ## Verify against the live DB Row counts per zoom, the z11/z9 bands filling, a decoded tile with mode='commuter' rows, real-browser render with the J badge at z11+.
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#63
No description provided.