Matching GTFS Transit Route Data to a Roadway Network for Travel Modeling

COLLABORATE. INNOVATE. EDUCATE.

Matching GTFS Transit Route Data to

a Roadway Network for Travel

Modeling

Kenneth A. PerrineResearch Associate

Monday, March 2, 2015


Google Maps


Google Maps

GTFS Shape

*

*

*

*

*

*


?

?

?Roads?

??

?

??

?

?

*

*

*

*

*

*


Google Maps


Google Maps


Google Maps

*

*

*

*

*

*


*

*

*

*

*

*

Google Maps


Google Maps

*

*

**

**

****


Google Maps

*

*

* *

**

***

*


Google Maps***

**


Google Maps

*

*

*

*

*

*


*

*

*

*

*

*


Google Maps

*

*

*

*

*

*

!?


Google Maps


*

**

**

**

Google Maps


*

**

*

*Google Maps


*

**

**

**

**

*

Google Maps

*


*

*

*

*

*

*Global & local

Multiple hypotheses

Topological

Heuristic-free


GTFS shapes

Initial match

Simulator files

Underlying topology

Fix underlying topology

Problem report

Workflow

Refine matches

Problem report

Goodenough?

Y

N


OpenStreetMap• 123,046 nodes• 300,199 links

NMC CAMPO DTA• 11,393 nodes• 13,353 links

Austin Region

Google Maps


CapMetro GTFS• 84 routes• 170 shapes• 45,476 points• 1,383 miles• 2 in - 3472 ft apart

(avg. 161 ft) GPS 1-sec• 22 routes• 44 journeys• 44,298 points• 283 miles• 0 to 114 ft apart

(avg. 34 ft)

*

*

*

*

*

*


GPS 1-sec overNMC CAMPO DTA• Discontinuities: 0• Accuracy: 100%

CapMetro GTFS overNMC CAMPO DTA• Discontinuities: 0• Accuracy: 95.9%*• (Had to fix 80 links!)

CapMetro GTFS overOpenStreetMap• Discontinuities: 0• Accuracy: 99.8%*• (Had to fix 1 link!)

RESULTS

* In hand-checked cases, 3,068 of 45,476 GTFS points

FUTURE

Link curvature

Compute speed

*

*

*

*

*

*


Open source!

http://ctr.utexas.edu/nmc/nmc-map-matcher

Kenneth [email protected]

Technology

Matching GTFS Transit Route Data to a Roadway Network for Travel Modeling