GTFS feed integration
Stay organized with collections
Save and categorize content based on your preferences.
You can use GTFS to display the open loop banner in Maps, and to show Maps in transit
receipts.
Display the open loop banner in Maps
Google Wallet and Google Maps use GTFS feeds to identify which routes are shown in Google
Maps. To implement this feature, transit agencies must do the following:
- The transit agency must publish a GTFS feed with the following fields at a minimum:
- The feed must be an accurate representation of the routes and stops that support open loop.
- The GTFS feed doesn't include stations, stops, or routes that aren't supported. This is
done to ensure that the banner isn't shown to users on an unsupported route.
- Partial rollouts aren't currently supported. Agencies must either complete the rollout for
the complete GTFS feed or create a new GTFS feed.
Show Maps in transit receipts
You can use GTFS to show Maps in transit receipts for stationary and mobile terminals.
Stationary terminals
To display Google Maps in Google Wallet, provide Google links to link the station stops
with users' taps on a terminal. To do this, provide the relationship between information in the
Merchant Name tag and the appropriate GTFS feed, as shown in the following example:
STOPS.txt: field(stop_id)
You must also complete the
open loop transit form.
Mobile terminals
For mobile terminals, such as those on a bus, you can either dynamically update the Merchant Name
on the terminal tag (9F4E), or provide a relationship between the taps on a terminal and a GTFS
route feed. In the latter case, the user is only shown the route, not the stop. See the following
example:
ROUTES.txt field(route_id)
You must also complete the
open loop transit form.
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.
[[["Easy to understand","easyToUnderstand","thumb-up"],["Solved my problem","solvedMyProblem","thumb-up"],["Other","otherUp","thumb-up"]],[["Missing the information I need","missingTheInformationINeed","thumb-down"],["Too complicated / too many steps","tooComplicatedTooManySteps","thumb-down"],["Out of date","outOfDate","thumb-down"],["Samples / code issue","samplesCodeIssue","thumb-down"],["Other","otherDown","thumb-down"]],["Last updated 2024-10-16 UTC."],[[["Transit agencies can leverage GTFS feeds to display an open loop banner in Google Maps, indicating routes that support open loop payments, by ensuring their feed accurately represents these routes and stops."],["GTFS feeds can be used to integrate Google Maps into transit receipts for both stationary and mobile terminals, providing users with visual location information."],["For stationary terminals, linking station stops with user taps requires providing the relationship between the Merchant Name tag and the corresponding GTFS feed, along with completing an onboarding form."],["Mobile terminals can either dynamically update the Merchant Name or link taps to a GTFS route feed, displaying the route to the user, and also require completion of the onboarding form."]]],["Transit agencies use GTFS feeds to display open loop banners and maps in Google Maps and transit receipts. To show banners, agencies must publish a complete GTFS feed (agency, stops, routes) accurately representing supported routes. To show maps in stationary terminal receipts, link the Merchant Name tag to the `STOPS.txt` stop ID field. For mobile terminals, link the Merchant Name or terminal taps to the `ROUTES.txt` route ID field. Submitting the open loop transit form is mandatory.\n"]]
