2011 ITS World Congress - GO-Sync - A Framework to Synchronize Transit Agency Datasets with Online Communities
Download as PPS, PDF1 like611 views
Go-sync is an open-source framework designed to synchronize transit agency datasets with OpenStreetMap (OSM), addressing issues such as the limitations of General Transit Feed Specification (GTFS) data and the lack of transit information in OSM for many U.S. cities. The framework facilitates the sharing of transit data with the OSM community, helping improve bus stop inventory through crowd-sourcing while managing conflicts between agency data and OSM. Initial evaluations showed significant updates to transit stops in Tampa, indicating successful integration of agency data into the OSM system.
2011 ITS World Congress - GO-Sync - A Framework to Synchronize Transit Agency Datasets with Online Communities
- 1. GO-SYNC A FRAMEWORK TO SYNCHRONIZE TRANSIT AGENCY DATASETS WITH ONLINE COMMUNITIES Khoa Tran, Ed Hillsman, Sean Barbeau, Miguel Labrador ktran9@mail.usf.edu, hillsman@cutr.usf.edu, barbeau@cutr.usf.edu, mlabrador@usf.edu Department of Computer Science and Engineering & Center for Urban Transportation Research University of South Florida http://code.google.com/p/gtfs-osm-sync/ Open-Source on:
- 2. GO-SYNC MOTIVATION & CHALLENGES • Shortcomings of official transit General Transit Feed Spec. (GTFS) datasets • Lack of transit data in OpenStreetMap (OSM) for many U.S. cities • Goal – create an open-source software tool that can: – Share transit agency data with OSM community – Leverage social mapping model to improve bus stop inventory, and allow agency to retrieve these improvements MOTIVATIO N CHALLENGE S • Lack of a strict tagging system in OSM • Avoid duplicating OSM data & respect work done by other users • Ongoing updates to GTFS (and OSM) data • Integration of crowd-sourced data into transit agency internal datasets
- 3. GTFSOSM(GO)-SYNC FRAMEWORK DESIGN 1. Determine what has already been mapped in the OSM in the area covered by the GTFS data. 2. Identify bus stops that may be in conflict between OSM and an agency’s GTFS data 3. Make decisions on how to manage conflicts, with the aid of user input. 4. Upload GTFS data into OSM, managing any conflicts that the agency cannot reconcile. 1) Input GTFS data and Agency Info 2) Analyze before Upload
- 4. EVALUATION IN TAMPA & COLLABORATION •July 2010 - 3,812 new HART stops uploaded (133 stops previously existed) •Jan. 2011 -173 modifications were made RETRIEVING IMPROVEMENTS TO TRANSIT AGENCY EVALUATIO N 1. Output as a GTFS file, using GTFS-defined fields when possible 2. Additional “OSM_TAGs” field name is inserted at the end of the row 3. Additional tags from OSM (i.e. “key=value”) are separated by “|” (i.e., pipe-delimited) Example: stop_id,stop_name,stop_lat,stop_lon, OSM_TAGs 881,Fletcher Av @ Livingston Av,28.0693,-82.4272, shade=no|ntd_id=4041 |shelter=no|bench=no| note=field checked after upload
- 5. QUESTIONS? Sean J. Barbeau, M.S. Comp.Sci. Research Associate Center for Urban Transportation Research University of South Florida http://locationaware.usf.edu 813.974.7208 barbeau@cutr.usf.edu 5
- 6. QUESTIONS? Sean J. Barbeau, M.S. Comp.Sci. Research Associate Center for Urban Transportation Research University of South Florida http://locationaware.usf.edu 813.974.7208 barbeau@cutr.usf.edu 5