GTFS to OSM route matching: mdb-516

MTA New York City Transit —
20621 trips, 0 matched (0.0%).

All feeds

subway L (L): 0 of 1498 trips matched (route type not matched (rail, subway, ferry, ...): 1498)

subway 7 (7): 0 of 1347 trips matched (route type not matched (rail, subway, ferry, ...): 1347)

subway S (GS): 0 of 1190 trips matched (route type not matched (rail, subway, ferry, ...): 1190)

subway 1 (1): 0 of 1142 trips matched (route type not matched (rail, subway, ferry, ...): 1142)

subway 6 (6): 0 of 1097 trips matched (route type not matched (rail, subway, ferry, ...): 1097)

subway A (A): 0 of 940 trips matched (route type not matched (rail, subway, ferry, ...): 940)

subway 4 (4): 0 of 902 trips matched (route type not matched (rail, subway, ferry, ...): 902)

subway Q (Q): 0 of 859 trips matched (route type not matched (rail, subway, ferry, ...): 859)

subway 2 (2): 0 of 848 trips matched (route type not matched (rail, subway, ferry, ...): 848)

subway E (E): 0 of 830 trips matched (route type not matched (rail, subway, ferry, ...): 830)

subway G (G): 0 of 814 trips matched (route type not matched (rail, subway, ferry, ...): 814)

subway F (F): 0 of 806 trips matched (route type not matched (rail, subway, ferry, ...): 806)

subway M (M): 0 of 804 trips matched (route type not matched (rail, subway, ferry, ...): 804)

subway 5 (5): 0 of 800 trips matched (route type not matched (rail, subway, ferry, ...): 800)

subway S (H): 0 of 792 trips matched (route type not matched (rail, subway, ferry, ...): 792)

subway J (J): 0 of 777 trips matched (route type not matched (rail, subway, ferry, ...): 777)

subway 3 (3): 0 of 763 trips matched (route type not matched (rail, subway, ferry, ...): 763)

subway R (R): 0 of 735 trips matched (route type not matched (rail, subway, ferry, ...): 735)

subway D (D): 0 of 728 trips matched (route type not matched (rail, subway, ferry, ...): 728)

subway N (N): 0 of 717 trips matched (route type not matched (rail, subway, ferry, ...): 717)

subway S (FS): 0 of 714 trips matched (route type not matched (rail, subway, ferry, ...): 714)

subway C (C): 0 of 534 trips matched (route type not matched (rail, subway, ferry, ...): 534)

train SIR (SI): 0 of 341 trips matched (no OSM route of this type in the grid cell: 341)

subway B (B): 0 of 220 trips matched (route type not matched (rail, subway, ferry, ...): 220)

subway W (W): 0 of 187 trips matched (route type not matched (rail, subway, ferry, ...): 187)

subway 6X (6X): 0 of 113 trips matched (route type not matched (rail, subway, ferry, ...): 113)

subway 7X (7X): 0 of 107 trips matched (route type not matched (rail, subway, ferry, ...): 107)

subway Z (Z): 0 of 12 trips matched (route type not matched (rail, subway, ferry, ...): 12)

subway FX (FX): 0 of 4 trips matched (route type not matched (rail, subway, ferry, ...): 4)

ℹ️ How to read this
Every GTFS trip is matched against the OSM route relations of the same type whose bounding box covers the trip's area. A candidate must pass five gates — platform count, stop-to-stop length, direction, platform positions and platform names — and the best one is accepted when the mean of its scores exceeds 0.70. If no candidate carries the trip's own ref, the best other candidate needs a mean above 0.75 and a 0.05 lead over any other line. Trips of one stop pattern (the same stop sequence) are decided together, so each row below is one stop pattern, matched ones (green candidate cell) included so a route's matched and unmatched patterns can be compared; the candidate shown is the one that decided the result or, when nothing passed, the one that got furthest. The pink cell says why: a signal — the first gate the candidate failed; the ref — no relation of the trip's own line passed the gates (or none is a candidate at all, when the ref score is 0), so this is another line; the mean — the candidate passed every gate but the mean is not above the threshold, or, when a "lost its margin to" row follows, it leads that other line by less than 0.05. Hover a pink cell for the full wording. "map" opens the pattern over OpenStreetMap: GTFS stops in red, the candidate's platforms in green, the runner-up's in orange, and the platform–stop pairs the points signal assigned as dashed lines.