GTFS to OSM route matching: tdg-83757/GTFS BAAG 17122025
BAAG CCA —
1470 trips, 0 matched (0.0%).
bus LIGNE 6 (7412): 0 of 238 trips matched (no current calendar: 238)
bus LIGNE 5 (7411): 0 of 224 trips matched (no current calendar: 224)
bus LIGNE 3 (7409): 0 of 214 trips matched (no current calendar: 214)
bus LIGNE 4 (7410): 0 of 209 trips matched (no current calendar: 209)
bus LIGNE 1 (7407): 0 of 168 trips matched (no current calendar: 168)
bus LIGNE 2 (7408): 0 of 167 trips matched (no current calendar: 167)
bus PMR (8341): 0 of 75 trips matched (no current calendar: 75)
bus TAD (8342): 0 of 75 trips matched (no current calendar: 75)
bus LIGNE 7 (7413): 0 of 44 trips matched (no current calendar: 44)
bus SCOL 10 (8608): 0 of 4 trips matched (no current calendar: 4)
bus SCOL 10R (8617): 0 of 4 trips matched (no current calendar: 4)
bus SCOL 3 (8607): 0 of 4 trips matched (no current calendar: 4)
bus SCOL 3R (8616): 0 of 4 trips matched (no current calendar: 4)
bus SCOL 1R (8622): 0 of 3 trips matched (no current calendar: 3)
bus SCOL 2R (8623): 0 of 3 trips matched (no current calendar: 3)
bus SCOL 4R (8619): 0 of 3 trips matched (no current calendar: 3)
bus SCOL 5R (8620): 0 of 3 trips matched (no current calendar: 3)
bus SCOL 6R (8624): 0 of 3 trips matched (no current calendar: 3)
bus SCOL 7R (8621): 0 of 3 trips matched (no current calendar: 3)
bus SCOL 8R (8625): 0 of 3 trips matched (no current calendar: 3)
bus SCOL 9R (8618): 0 of 3 trips matched (no current calendar: 3)
bus SCOL 1 (8613): 0 of 2 trips matched (no current calendar: 2)
bus SCOL 2 (8614): 0 of 2 trips matched (no current calendar: 2)
bus SCOL 4 (8610): 0 of 2 trips matched (no current calendar: 2)
bus SCOL 5 (8611): 0 of 2 trips matched (no current calendar: 2)
bus SCOL 6 (8615): 0 of 2 trips matched (no current calendar: 2)
bus SCOL 7 (8612): 0 of 2 trips matched (no current calendar: 2)
bus SCOL 8 (8626): 0 of 2 trips matched (no current calendar: 2)
bus SCOL 9 (8609): 0 of 2 trips matched (no current calendar: 2)
ℹ️ 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.