GTFS to OSM route matching: ntd-40056
Pee Dee Regional Transportation Authority —
231 trips, 0 matched (0.0%).
bus FDS (3960): 0 of 24 trips matched (no OSM route of this type in the grid cell: 24)
bus Marion (5974): 0 of 19 trips matched (no OSM route of this type in the grid cell: 19)
bus Dillon County County Area Connect (4936): 0 of 18 trips matched (no OSM route of this type in the grid cell: 18)
bus R2 (3895): 0 of 18 trips matched (no OSM route of this type in the grid cell: 18)
bus R3 (3912): 0 of 18 trips matched (no OSM route of this type in the grid cell: 18)
bus Marlboro (4041): 0 of 16 trips matched (no OSM route of this type in the grid cell: 16)
bus DART (3953): 0 of 12 trips matched (no OSM route of this type in the grid cell: 12)
bus R1 (3822): 0 of 12 trips matched (no OSM route of this type in the grid cell: 12)
bus R4 (3914): 0 of 12 trips matched (no OSM route of this type in the grid cell: 12)
bus HART (4411): 0 of 11 trips matched (no OSM route of this type in the grid cell: 11)
bus LakeTran (3957): 0 of 10 trips matched (no OSM route of this type in the grid cell: 10)
bus R7 (3916): 0 of 10 trips matched (no OSM route of this type in the grid cell: 10)
bus Cheraw Express (5114): 0 of 9 trips matched (no OSM route of this type in the grid cell: 9)
bus CCE (6316): 0 of 7 trips matched (no OSM route of this type in the grid cell: 7)
bus T.Ville Exp. (5986): 0 of 7 trips matched (no OSM route of this type in the grid cell: 7)
bus CCW (6322): 0 of 6 trips matched (no OSM route of this type in the grid cell: 6)
bus Cheraw Conn. (5183): 0 of 6 trips matched (no OSM route of this type in the grid cell: 6)
bus R15 (5668): 0 of 6 trips matched (no OSM route of this type in the grid cell: 6)
bus Soc. HL. (5791): 0 of 6 trips matched (no OSM route of this type in the grid cell: 6)
bus Lake City to Myrtle Beach (3991): 0 of 2 trips matched (no OSM route of this type in the grid cell: 2)
bus Mar. to MB (3965): 0 of 2 trips matched (no OSM route of this type in the grid cell: 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.