GTFS Feed 集成
使用集合让一切井井有条
根据您的偏好保存内容并对其进行分类。
您可以使用 GTFS 在 Google 地图中显示开放式环路横幅，并在公交收据中显示 Google 地图。
在 Google 地图中显示“开放式环路”横幅
Google 钱包和 Google 地图使用 GTFS Feed 来识别在 Google 中显示的路线
地图。要实现此功能，公交公司必须执行以下操作：
- 公交公司必须发布至少包含以下字段的 GTFS Feed：
- Feed 必须准确反映支持开放式循环的路线和经停点。
- GTFS Feed 不包含不受支持的车站、经停点或路线。这样做是为了确保不会向使用不受支持的路线的用户显示横幅。
- 目前不支持部分发布。公交公司必须完成完整 GTFS Feed 的发布，或者创建新的 GTFS Feed。
在公交收据中显示 Google 地图
您可以使用 GTFS 在固定式和移动式终端的公共交通收据中显示 Google 地图。
固定式终端
如需在 Google 钱包中显示 Google 地图，请提供 Google 链接以关联车站
以及用户的可以点按终端。为此，请提供
商家名称标记和相应的 GTFS Feed，如以下示例所示：
STOPS.txt: field(stop_id)
您还必须填写开放式公交表单。
移动终端
对于移动终端（例如公交车上的终端），您可以动态地更新商家名称
或提供终端上的点按与 GTFS 之间的关系
路由 Feed。在后一种情况下，系统只会向用户显示路线，而不会显示相应经停点。请参阅以下示例：
ROUTES.txt field(route_id)
您还必须填写开放式公交表单。
如未另行说明，那么本页面中的内容已根据知识共享署名 4.0 许可获得了许可，并且代码示例已根据 Apache 2.0 许可获得了许可。有关详情，请参阅 Google 开发者网站政策。Java 是 Oracle 和/或其关联公司的注册商标。
最后更新时间 (UTC)：2025-07-25。
[null,null,["最后更新时间 (UTC)：2025-07-25。"],[[["\u003cp\u003eTransit 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.\u003c/p\u003e\n"],["\u003cp\u003eGTFS feeds can be used to integrate Google Maps into transit receipts for both stationary and mobile terminals, providing users with visual location information.\u003c/p\u003e\n"],["\u003cp\u003eFor 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.\u003c/p\u003e\n"],["\u003cp\u003eMobile 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.\u003c/p\u003e\n"]]],["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"],null,["# GTFS feed integration\n\nYou can use GTFS to display the open loop banner in Maps, and to show Maps in transit\nreceipts.\n\nDisplay the open loop banner in Maps\n------------------------------------\n\nGoogle Wallet and Google Maps use GTFS feeds to identify which routes are shown in Google\nMaps. To implement this feature, transit agencies must do the following:\n\n- The transit agency must publish a GTFS feed with the following fields at a minimum:\n - Agency\n - Stops\n - Routes\n- The feed must be an accurate representation of the routes and stops that support open loop.\n - 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.\n - Partial rollouts aren't currently supported. Agencies must either complete the rollout for the complete GTFS feed or create a new GTFS feed.\n\nShow Maps in transit receipts\n-----------------------------\n\nYou can use GTFS to show Maps in transit receipts for stationary and mobile terminals.\n\n### Stationary terminals\n\nTo display Google Maps in Google Wallet, provide Google links to link the station stops\nwith users' taps on a terminal. To do this, provide the relationship between information in the\nMerchant Name tag and the appropriate GTFS feed, as shown in the following example: \n\n```scdoc\nSTOPS.txt: field(stop_id)\n```\n\nYou must also complete the\n[open loop transit form](https://support.google.com/pay/merchants/contact/open_loop_transit_onboarding).\n\n### Mobile terminals\n\nFor mobile terminals, such as those on a bus, you can either dynamically update the Merchant Name\non the terminal tag (9F4E), or provide a relationship between the taps on a terminal and a GTFS\nroute feed. In the latter case, the user is only shown the route, not the stop. See the following\nexample: \n\n```scdoc\nROUTES.txt field(route_id)\n```\n\nYou must also complete the\n[open loop transit form](https://support.google.com/pay/merchants/contact/open_loop_transit_onboarding)."]]
