GTFS to OSM route matching: mdb-471
GoRaleigh —
6552 trips, 0 matched (0.0%).
bus 19 (1535): 0 of 471 trips matched (no current calendar: 471)
bus 15 (1531): 0 of 386 trips matched (no current calendar: 386)
bus 1 (1524): 0 of 384 trips matched (no current calendar: 384)
bus 7 (1549): 0 of 359 trips matched (no current calendar: 359)
bus 4 (1544): 0 of 330 trips matched (no current calendar: 330)
bus 22 (1538): 0 of 287 trips matched (no current calendar: 287)
bus 13 (1530): 0 of 260 trips matched (no current calendar: 260)
bus 2 (1536): 0 of 228 trips matched (no current calendar: 228)
bus 15L (1532): 0 of 220 trips matched (no current calendar: 220)
bus 5 (1546): 0 of 201 trips matched (no current calendar: 201)
bus 11 (1527): 0 of 195 trips matched (no current calendar: 195)
bus 21 (1537): 0 of 187 trips matched (no current calendar: 187)
bus 8 (1552): 0 of 184 trips matched (no current calendar: 184)
bus 16 (1533): 0 of 180 trips matched (no current calendar: 180)
bus 36 (12344): 0 of 175 trips matched (no current calendar: 175)
bus 27 (12343): 0 of 173 trips matched (no current calendar: 173)
bus 6 (1548): 0 of 173 trips matched (no current calendar: 173)
bus 25L (1541): 0 of 171 trips matched (no current calendar: 171)
bus 18 (12329): 0 of 169 trips matched (no current calendar: 169)
bus 26 (12342): 0 of 161 trips matched (no current calendar: 161)
bus 12 (1529): 0 of 159 trips matched (no current calendar: 159)
bus 11L (1528): 0 of 157 trips matched (no current calendar: 157)
bus 17 (12328): 0 of 153 trips matched (no current calendar: 153)
bus 7L (1551): 0 of 153 trips matched (no current calendar: 153)
bus 10 (1526): 0 of 149 trips matched (no current calendar: 149)
bus 3 (1542): 0 of 141 trips matched (no current calendar: 141)
bus 23L (1539): 0 of 129 trips matched (no current calendar: 129)
bus 24L (1540): 0 of 127 trips matched (no current calendar: 127)
bus 20-A (14218): 0 of 72 trips matched (no current calendar: 72)
bus 70X (1550): 0 of 68 trips matched (no current calendar: 68)
bus 20-B (18789): 0 of 64 trips matched (no current calendar: 64)
bus 33 (14219): 0 of 64 trips matched (no current calendar: 64)
bus 40X (1545): 0 of 48 trips matched (no current calendar: 48)
bus WFL-A (1554): 0 of 48 trips matched (no current calendar: 48)
bus WFL-B (18788): 0 of 48 trips matched (no current calendar: 48)
bus 55X (1547): 0 of 38 trips matched (no current calendar: 38)
bus 401X (14220): 0 of 24 trips matched (no current calendar: 24)
bus FRX (14478): 0 of 16 trips matched (no current calendar: 16)
ℹ️ 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.