Transit Data FAQs and Definitions
Can I use MTA's name or Logo?
No, MTA's name and logo are trademarked by MTA and may not be used in your application. We only allow our logo or name to be used by products created by MTA.
Is there a monetary charge to use MTA's data?
How will I know if MTA's data changes?
We will send out electronic notification when our data changes, so be sure you have entered the correct email address in your application.
What is GTFS?
GTFS stands for General Transit Feed Specification. It is a standardized format for transit data that many agencies use. You can find out more about it at http://code.google.com/transit/spec/transit_feed_specification.html
Will you help me trouble shoot?
Sorry, we do not have the resources to help you trouble shoot your code of the GTFS. We work hard to ensure the GTFS data error free, but if you find an error, please let us know by emailing email@example.com.
Block: A collection of trips assigned to a vehicle for a day.
Direction: One of two possible directions of travel — to downtown "Nashville" or from downtown "Destination" end of line — on a route.
Stop ID: The unique number that identifies each bus stop.
Pattern: A unique travel path through the street network to visit selected stops for one trip.
Route: A collection of ordered stops presented publicly as a "line" with a name (such as "12 - Nolensville")
and represented internally as an integer.
Timepoint: One of several stops on each route that serves as a benchmark for whether a trip is running on time.
Timepoints are the only stops that appear on our printed schedules.
Trip: An iteration of a vehicle traveling along a given pattern.
Headsign: Route description that appears on the display on the front of the bus. (such as "12 - Nolensville")