2011 ITS World Congress - GO-Sync - A Framework to Synchronize Transit Agency Datasets with Online...
Click here to load reader
-
Upload
sean-barbeau -
Category
Technology
-
view
90 -
download
0
description
Transcript of 2011 ITS World Congress - GO-Sync - A Framework to Synchronize Transit Agency Datasets with Online...
GO-SYNCA FRAMEWORK TO SYNCHRONIZE TRANSIT
AGENCY DATASETS WITH ONLINE COMMUNITIES
Khoa Tran, Ed Hillsman, Sean Barbeau, Miguel [email protected], [email protected], [email protected],
[email protected] 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:
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
MOTIVATION
CHALLENGES• 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
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
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
EVALUATION
1. Output as a GTFS file, using GTFS-defined fields when possible2. Additional “OSM_TAGs” field name is inserted at the end of the row3. 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
QUESTIONS?
Sean J. Barbeau, M.S. Comp.Sci.
Research Associate Center for Urban Transportation Research University of South Florida http://locationaware.usf.edu
5