1 / 5

GO-Sync A Framework to Synchronize transit agency datasets with online communities

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 &

melody
Download Presentation

GO-Sync A Framework to Synchronize transit agency datasets with online communities

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. GO-SyncA 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 Open-Source on: • http://code.google.com/p/gtfs-osm-sync/

  2. GO-Sync Motivation & Challenges Motivation • 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 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

  3. GtfsOsm(GO)-Sync Framework Design • Determine what has already been mapped in the OSM in the area covered by the GTFS data. • Identify bus stops that may be in conflict between OSM and an agency’s GTFS data • Make decisions on how to manage conflicts, with the aid of user input. • 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 Evaluation • July 2010 - 3,812 new HART stops uploaded (133 stops previously existed) • Jan. 2011 -173 modifications were made Retrieving Improvements To Transit Agency Output as a GTFS file, using GTFS-defined fields when possible Additional “OSM_TAGs” field name is inserted at the end of the row 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

More Related