GTFS to OSM route matching: mdb-729
Brampton Transit —
9428 trips, 0 matched (0.0%).
bus 511 (511-338): 0 of 531 trips matched (no current calendar: 531)
bus 502 (502-338): 0 of 515 trips matched (no current calendar: 515)
bus 7 (7-338): 0 of 514 trips matched (no current calendar: 514)
bus 501 (501-338): 0 of 493 trips matched (no current calendar: 493)
bus 18 (18-338): 0 of 476 trips matched (no current calendar: 476)
bus 4 (4-338): 0 of 476 trips matched (no current calendar: 476)
bus 11 (11-338): 0 of 416 trips matched (no current calendar: 416)
bus 50 (50-338): 0 of 393 trips matched (no current calendar: 393)
bus 1 (1-338): 0 of 384 trips matched (no current calendar: 384)
bus 30 (30-338): 0 of 354 trips matched (no current calendar: 354)
bus 14 (14-338): 0 of 345 trips matched (no current calendar: 345)
bus 15 (15-338): 0 of 330 trips matched (no current calendar: 330)
bus 5 (5-338): 0 of 296 trips matched (no current calendar: 296)
bus 505 (505-338): 0 of 271 trips matched (no current calendar: 271)
bus 2 (2-338): 0 of 255 trips matched (no current calendar: 255)
bus 3 (3-338): 0 of 252 trips matched (no current calendar: 252)
bus 23 (23-338): 0 of 241 trips matched (no current calendar: 241)
bus 29 (29-338): 0 of 225 trips matched (no current calendar: 225)
bus 115 (115-338): 0 of 204 trips matched (no current calendar: 204)
bus 53 (53-338): 0 of 140 trips matched (no current calendar: 140)
bus 57 (57-338): 0 of 140 trips matched (no current calendar: 140)
bus 8 (8-338): 0 of 130 trips matched (no current calendar: 130)
bus 35 (35-338): 0 of 129 trips matched (no current calendar: 129)
bus 24 (24-338): 0 of 119 trips matched (no current calendar: 119)
bus 52 (52-338): 0 of 116 trips matched (no current calendar: 116)
bus 6 (6-338): 0 of 114 trips matched (no current calendar: 114)
bus 26 (26-338): 0 of 106 trips matched (no current calendar: 106)
bus 17 (17-338): 0 of 100 trips matched (no current calendar: 100)
bus 31 (31-338): 0 of 99 trips matched (no current calendar: 99)
bus 60 (60-338): 0 of 94 trips matched (no current calendar: 94)
bus 54 (54-338): 0 of 93 trips matched (no current calendar: 93)
bus 16 (16-338): 0 of 88 trips matched (no current calendar: 88)
bus 27 (27-338): 0 of 88 trips matched (no current calendar: 88)
bus 19 (19-338): 0 of 86 trips matched (no current calendar: 86)
bus 12 (12-338): 0 of 84 trips matched (no current calendar: 84)
bus 51 (51-338): 0 of 84 trips matched (no current calendar: 84)
bus 13 (13-338): 0 of 64 trips matched (no current calendar: 64)
bus 20 (20-338): 0 of 59 trips matched (no current calendar: 59)
bus 56 (56-338): 0 of 59 trips matched (no current calendar: 59)
bus 32 (32-338): 0 of 58 trips matched (no current calendar: 58)
bus 10 (10-338): 0 of 56 trips matched (no current calendar: 56)
bus 561 (561-338): 0 of 48 trips matched (no current calendar: 48)
bus 25 (25-338): 0 of 39 trips matched (no current calendar: 39)
bus 104 (104-338): 0 of 38 trips matched (no current calendar: 38)
bus 9 (9-338): 0 of 37 trips matched (no current calendar: 37)
bus 55 (55-338): 0 of 27 trips matched (no current calendar: 27)
bus 58 (58-338): 0 of 26 trips matched (no current calendar: 26)
bus 33 (33-338): 0 of 22 trips matched (no current calendar: 22)
bus 36 (36-338): 0 of 22 trips matched (no current calendar: 22)
bus 28 (28-338): 0 of 21 trips matched (no current calendar: 21)
bus 81 (81-338): 0 of 20 trips matched (no current calendar: 20)
bus 199 (199-338): 0 of 12 trips matched (no current calendar: 12)
bus 40 (40-338): 0 of 7 trips matched (no current calendar: 7)
bus 207 (207-338): 0 of 3 trips matched (no current calendar: 3)
bus 200 (200-338): 0 of 2 trips matched (no current calendar: 2)
bus 201 (201-338): 0 of 2 trips matched (no current calendar: 2)
bus 202 (202-338): 0 of 2 trips matched (no current calendar: 2)
bus 205 (205-338): 0 of 2 trips matched (no current calendar: 2)
bus 206 (206-338): 0 of 2 trips matched (no current calendar: 2)
bus 208 (208-338): 0 of 2 trips matched (no current calendar: 2)
bus 209 (209-338): 0 of 2 trips matched (no current calendar: 2)
bus 211 (211-338): 0 of 2 trips matched (no current calendar: 2)
bus 212 (212-338): 0 of 2 trips matched (no current calendar: 2)
bus 213 (213-338): 0 of 2 trips matched (no current calendar: 2)
bus 214 (214-338): 0 of 2 trips matched (no current calendar: 2)
bus 215 (215-338): 0 of 2 trips matched (no current calendar: 2)
bus 216 (216-338): 0 of 2 trips matched (no current calendar: 2)
bus 203 (203-338): 0 of 1 trips matched (no current calendar: 1)
bus 204 (204-338): 0 of 1 trips matched (no current calendar: 1)
bus 217 (217-338): 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.