Glossary of Google Static Transit terminology
Stay organized with collections
Save and categorize content based on your preferences.
This page provides a list of static transit terms and definitions to help transit partners and
data aggregators use the terms consistently across multiple documents or user interfaces.
| Terms |
| Agency |
A company or an organization that operates the transit services or that's known by
passengers to be responsible for those services. |
| Aggregator |
A company or an organization that provides software services and works on the transit data
aggregation. |
| Calendar |
A schedule that contains days and times when transit service is available for one or more
routes. |
| Departure board |
On the transit layer of Google Maps, when you click a stop icon, the departure board
appears. It shows the stop name, route type, route name, headsign, and estimated time to
arrival. |
| Exact timetable |
A schedule that's clearly defined in calendar.txt and
calendar_dates.txt, which shows the availability of transit services. |
| Frequency-based trip |
A trip based on a certain time period between the previous trip and subsequent one. For
example, a trip with the description "every 3 minutes." |
| Headsign |
The text that appears on signage and shows the destination to passengers. |
| Pathway |
A particular way that has only two nodes, to represent the beginning and ending. This path
helps passengers travel through a station. |
| Platform |
A particular location for passengers to get on board or leave a vehicle. |
| Route |
A particular way between the start location and destination, along which the passengers
travel in the public transit vehicle. |
| Static feed |
A ZIP package that complies with the GTFS format and provides information about planned
routes running on fixed schedules. |
| Station |
A physical structure or area that contains one or more stops. |
| Stop |
A location where a vehicle stops to let passengers get on board or leave the vehicle. |
| Transit layer |
A layer on Google Maps that shows the public transit routes, stops, vehicles, and other
information. |
| Transit partner dashboard |
A dashboard that lets transit partners set up, manage, and monitor their transit feeds,
and configure account access for users in their organization. |
| Trip |
A sequence of two or more stops within a specific time. |
| Trip directions page |
In the page with trip search results, when you click one result, the trip directions page
displays. It shows details about your trip from the start location to the destination. |
| Trip search results |
On Google Maps, when you click Directions, a page displays for you to specify the
start location and destination. After you specify them, the page with trip search results
displays. |
Except as otherwise noted, the content of this page is licensed under the Creative Commons Attribution 4.0 License, and code samples are licensed under the Apache 2.0 License. For details, see the Google Developers Site Policies. Java is a registered trademark of Oracle and/or its affiliates.
Last updated 2024-10-16 UTC.
[null,null,["Last updated 2024-10-16 UTC."],[[["\u003cp\u003eThis page defines common static transit terms for data consistency among transit partners and data aggregators.\u003c/p\u003e\n"],["\u003cp\u003eThe terms cover various aspects of public transit, including schedules, routes, stops, and platforms, as well as Google Maps features like the transit layer and trip directions.\u003c/p\u003e\n"],["\u003cp\u003eUnderstanding these terms ensures clear communication and accurate data exchange within the transit ecosystem.\u003c/p\u003e\n"],["\u003cp\u003eThis glossary helps to standardize transit data for better integration and usage by various stakeholders.\u003c/p\u003e\n"]]],["This document defines static transit terms for consistent use by transit partners and data aggregators. Key terms include: **Agency**, the operating organization; **Aggregator**, a software service provider; **Calendar**, a service schedule; **Departure board**, a display showing stop information; **Headsign**, the destination signage; **Route**, the path between the origin and destination; **Station**, a structure with multiple stops; and **Stop**, a location for boarding/alighting. Also defined are terms related to data representation such as **Static feed**, **Trip**, **Pathway**, **Platform**.\n"],null,["# Glossary of Google Static Transit terminology\n\nThis page provides a list of static transit terms and definitions to help transit partners and\ndata aggregators use the terms consistently across multiple documents or user interfaces.\n\n| Terms ||\n|---------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|\n| Agency | A company or an organization that operates the transit services or that's known by passengers to be responsible for those services. |\n| Aggregator | A company or an organization that provides software services and works on the transit data aggregation. |\n| Calendar | A schedule that contains days and times when transit service is available for one or more routes. |\n| Departure board | On the transit layer of Google Maps, when you click a stop icon, the departure board appears. It shows the stop name, route type, route name, headsign, and estimated time to arrival. |\n| Exact timetable | A schedule that's clearly defined in `calendar.txt` and `calendar_dates.txt`, which shows the availability of transit services. |\n| Frequency-based trip | A trip based on a certain time period between the previous trip and subsequent one. For example, a trip with the description \"every 3 minutes.\" |\n| Headsign | The text that appears on signage and shows the destination to passengers. |\n| Pathway | A particular way that has only two nodes, to represent the beginning and ending. This path helps passengers travel through a station. |\n| Platform | A particular location for passengers to get on board or leave a vehicle. |\n| Route | A particular way between the start location and destination, along which the passengers travel in the public transit vehicle. |\n| Static feed | A ZIP package that complies with the GTFS format and provides information about planned routes running on fixed schedules. |\n| Station | A physical structure or area that contains one or more stops. |\n| Stop | A location where a vehicle stops to let passengers get on board or leave the vehicle. |\n| Transit layer | A layer on Google Maps that shows the public transit routes, stops, vehicles, and other information. |\n| Transit partner dashboard | A dashboard that lets transit partners set up, manage, and monitor their transit feeds, and configure account access for users in their organization. |\n| Trip | A sequence of two or more stops within a specific time. |\n| Trip directions page | In the page with trip search results, when you click one result, the trip directions page displays. It shows details about your trip from the start location to the destination. |\n| Trip search results | On Google Maps, when you click **Directions**, a page displays for you to specify the start location and destination. After you specify them, the page with trip search results displays. |"]]