GTFS to OSM route matching: mdb-465

NFTA —
4350 trips, 0 matched (0.0%).

All feeds

bus 3 (3): 0 of 197 trips matched (no current calendar: 197)

bus 19 (19): 0 of 192 trips matched (no current calendar: 192)

bus 23 (23): 0 of 190 trips matched (no current calendar: 190)

bus 20 (20): 0 of 187 trips matched (no current calendar: 187)

bus 5 (5): 0 of 187 trips matched (no current calendar: 187)

bus 12 (12): 0 of 186 trips matched (no current calendar: 186)

bus 24 (24): 0 of 173 trips matched (no current calendar: 173)

bus 8 (8): 0 of 165 trips matched (no current calendar: 165)

bus 32 (32): 0 of 157 trips matched (no current calendar: 157)

bus 13 (13): 0 of 153 trips matched (no current calendar: 153)

bus 25 (25): 0 of 151 trips matched (no current calendar: 151)

bus 6 (6): 0 of 150 trips matched (no current calendar: 150)

bus 15 (15): 0 of 143 trips matched (no current calendar: 143)

bus 4 (4): 0 of 141 trips matched (no current calendar: 141)

bus 16 (16): 0 of 136 trips matched (no current calendar: 136)

bus 34 (34): 0 of 135 trips matched (no current calendar: 135)

bus 14 (14): 0 of 128 trips matched (no current calendar: 128)

bus 26 (26): 0 of 124 trips matched (no current calendar: 124)

bus 2 (2): 0 of 120 trips matched (no current calendar: 120)

bus 55 (55): 0 of 120 trips matched (no current calendar: 120)

bus 40 (40): 0 of 118 trips matched (no current calendar: 118)

bus 1 (1): 0 of 116 trips matched (no current calendar: 116)

bus 50 (50): 0 of 113 trips matched (no current calendar: 113)

bus 11 (11): 0 of 95 trips matched (no current calendar: 95)

bus 22 (22): 0 of 89 trips matched (no current calendar: 89)

bus 42 (42): 0 of 89 trips matched (no current calendar: 89)

bus 48 (48): 0 of 88 trips matched (no current calendar: 88)

bus 18 (18): 0 of 84 trips matched (no current calendar: 84)

bus 35 (35): 0 of 82 trips matched (no current calendar: 82)

bus 52 (52): 0 of 63 trips matched (no current calendar: 63)

bus 44 (44): 0 of 55 trips matched (no current calendar: 55)

bus 59 (59): 0 of 50 trips matched (no current calendar: 50)

bus 46 (46): 0 of 43 trips matched (no current calendar: 43)

bus 47 (47): 0 of 29 trips matched (no current calendar: 29)

bus 77 (77): 0 of 27 trips matched (no current calendar: 27)

bus 49 (49): 0 of 15 trips matched (no current calendar: 15)

bus 60 (60): 0 of 6 trips matched (no current calendar: 6)

bus 74 (74): 0 of 6 trips matched (no current calendar: 6)

bus 76 (76): 0 of 6 trips matched (no current calendar: 6)

bus 101 (101): 0 of 5 trips matched (no current calendar: 5)

bus 61 (61): 0 of 4 trips matched (no current calendar: 4)

bus 64 (64): 0 of 4 trips matched (no current calendar: 4)

bus 66 (66): 0 of 4 trips matched (no current calendar: 4)

bus 69 (69): 0 of 4 trips matched (no current calendar: 4)

bus 70 (70): 0 of 4 trips matched (no current calendar: 4)

bus 72 (72): 0 of 4 trips matched (no current calendar: 4)

bus 111 (111): 0 of 3 trips matched (no current calendar: 3)

bus 103 (103): 0 of 2 trips matched (no current calendar: 2)

bus 106 (106): 0 of 2 trips matched (no current calendar: 2)

bus 81 (81): 0 of 2 trips matched (no current calendar: 2)

bus 102 (102): 0 of 1 trips matched (no current calendar: 1)

bus 104 (104): 0 of 1 trips matched (no current calendar: 1)

bus 110 (110): 0 of 1 trips matched (no current calendar: 1)

ℹ️ 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.