GTFS: GENERAL TRANSIT FEED SPECIFICATION
What is GTFS? A standard in representing schedule and route information Public Transportation Schedules GIS Data Route, trip, and stop information in one zipfile Publicly available
GTFS and Google Maps
GTFS & Google Maps Continued
GTFS Format Thirteen text files (13) zipped together. Six (6) files required Seven (7) files optional Within each file there are required and optional fields. Each file has a unique identifier.
GTFS Files Filename agency.txt stops.txt routes.txt trips.txt stop_times.txt calendar.txt calendar_dates.txt fare_attributes.txt fare_rules.txt shapes.txt frequencies.txt transfers.txt feed_info.txt Required Required Required Required Required Required Required Optional Optional Optional Optional Optional Optional Optional
Agency Fare Attributes Fare Routes Fare Rules Contains Destination Fare Origin Shapes Shape Trips Block Direction Shape Stop Times Zone Stops Service Frequencies Transfers From stop ID To stop ID Calendar Calendar Dates
Agency Required Operator of public transit network Multiple agencies can be defined in one file Example: ConnDOT Agency Routes Zone Stops Trips Block Direction Shape Stop Times Service Calendar
Routes Required Lines in a network Made up of one or more trips Time independent Example: Route 47 Agency Routes Zone Stops Trips Block Direction Shape Stop Times Service Calendar
Trips Required Time specific Represents one journey along a route Minimum of two stops Agency Routes Zone Stops Trip Trips Block Direction Shape Stop Times Service Calendar
Stop Times Required When a vehicle arrives at a location and departs The path and schedule of a trip Example: 7:10 am 7:17 am 7:21 am Agency Routes Trips Block Direction Shape Zone Stops Stop Times Service Calendar
Stop Required Spatial data Latitude and Longitude of all locations where a vehicle stops. Agency Routes Zone Stops Trips Block Direction Shape Stop Times Service Calendar
Calendar Required Days and times when a bus is available Example: weekends, weekdays seasonal Agency Routes Zone Stops Trips Block Direction Shape Stop Times Service Calendar
Agency Fare Attributes Fare Routes Fare Rules Contains Destination Fare Origin Shapes Shape Trips Block Direction Shape Stop Times Zone Stops Service Frequencies Transfers From stop ID To stop ID Calendar Calendar Dates
RIDERSHIP DATA
Title VI Circular Mention of Ridership Data Requirement for large transit providers to collect and report survey data regarding customer demographics and travel patterns Those that have not conducted passenger surveys in the last five years will have until December 31, 2013, to conduct these surveys Determining the frequency in which LEP persons come into contact with program Evaluating the impacts of proposed service changes Fare equity analysis Anytime ridership is not reflected by the characteristics of the census block, block group, or traffic analysis zone
Specified Data Demographic Race Color National origin English proficiency Language spoken at home Household income Fare usage by fare type Travel Patterns Not specified What form of travel patterns? What other type of demographic data should be collected?
DATABASE DEVELOPMENT
Multi-Source Data GIS Spatial Data GTFS Feeds Routes US Census Demographic Defines a location Static Visual Links to demographics, trip and stop Selects demographic data Demographic data Static
Visualization of Multi-Source Data
t-hub: Multi-Source Data DB GIS Spatial Data GTFS Feeds Routes US Census Dem t-hub geo DB Q1? connection A1 queries t-hub SQL DB tables