GTFS to OSM route matching: odpt-TokyoTaitoCity-megurinCCBY40

台東区役所 — Japan_Kanto_Tokyo
290 trips, 0 matched (0.0%).

bus 北めぐりん（浅草まわり） (ROT_000002): 0 of 89 trips matched

Stops	From	To	Trips	OSM candidate	ref	count	distance	direction	points	names	mean
25	① 浅草駅	① 浅草駅	82	宮06 (12343139)	0.00	0.72	0.93	–	0.00	0.17	–	map
9	① 浅草駅	⑨ 清川一丁目	7	東42-3 (13566766)	0.00	0.82	0.74	0.92	0.55	0.45	–	map

bus 南めぐりん (ROT_000003): 0 of 72 trips matched

Stops	From	To	Trips	OSM candidate	count	distance	direction	points	names	mean
37	① 上野駅	① 上野駅終	58	西川11 (12153534)	0.76	0.76	–	0.00	0.18	–	map
29	① 上野駅	㉘台東病院	4	草39 (13705912)	0.97	0.71	0.99	0.07	0.17	–	map
20	⑱ 浅草菊水通り	① 上野駅終	4	上26 (13678213)	0.83	0.61	0.85	0.08	0.18	–	map
9	㉘台東病院	① 上野駅終	3	西柏05 (13990703)	1.00	0.60	0.71	0.00	0.10	–	map
17	① 上野駅	⑰ 田原町駅	2	宮06 (12343139)	0.94	0.72	–	0.00	0.15	–	map
9	① 上野駅	⑨ 浅草橋駅北	1	東大03 (12340870)	0.82	0.61	0.98	0.00	0.17	–	map

bus 東西めぐりん (ROT_000004): 0 of 71 trips matched

Stops	From	To	Trips	OSM candidate	count	distance	direction	points	names	mean
37	① 台東区役所	① 台東区役所	27	上69 (9443874)	0.74	0.74	–	0.02	0.17	–	map
41	① 台東区役所	① 台東区役所	26	上69 (9443874)	0.82	0.71	–	0.02	0.17	–	map
10	㉜浅草駅	① 台東区役所	5	空01(ST01) (13724006)	0.70	0.79	0.94	0.10	0.18	–	map
32	⑩ 谷中霊園入口	① 台東区役所	4	草63 (3198044)	0.84	0.76	0.61	0.10	0.17	–	map
28	① 台東区役所	㉜浅草駅	3	上58 (14264141)	0.89	0.95	0.99	0.18	0.18	–	map
24	① 台東区役所	㉔京成上野駅・上野公園	2	上26 (13678213)	1.00	0.70	0.64	0.12	0.21	–	map
40	① 台東区役所	㊵永寿総合病院東	2	草41 (12863535)	0.68	0.71	0.85	0.05	0.19	–	map
32	① 台東区役所	㉜浅草駅	1	上23 (13712158)	0.94	0.89	0.96	0.12	0.21	–	map
36	① 台東区役所	㊵永寿総合病院東	1	東42-1 (13566615)	0.61	0.64	0.61	0.08	0.16	–	map

bus 北めぐりん（根岸まわり） (ROT_000001): 0 of 58 trips matched

Stops	From	To	Trips	OSM candidate	ref	count	distance	direction	points	names	mean
21	① 台東病院	① 台東病院	57	宮06 (12343139)	0.00	0.86	0.93	–	0.00	0.15	–	map
16	① 台東病院	⑯ 入谷駅入口	1	里22 (13540873)	0.00	0.75	0.94	0.92	0.06	0.20	–	map

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