常见问题解答
使用集合让一切井井有条
根据您的偏好保存内容并对其进行分类。
以下是有关实现 GTFS 时常见问题的问答。
问题:在公开 Feed 之前,是否有 Feed 测试环境?
答:是的,在您的 Feed 成功上传后,我们会准备测试环境。
问题:每次有更新时,我们是否需要手动上传 Feed?还是可以让 Google 从我们的服务器提取 Feed?
答:一般来说,Google 更倾向于设置定期提取(通过 FTP GET)。默认频率为每周一次。此外,您还可以通过控制台手动上传文件。
问题:如果我们同时提供快递线和本地线,可以分别提交 Feed 吗?
答:可以,代理机构可以提交多个单独的 Feed,但我们通常更倾向于使用单个 Feed。
问题:如果价格因座位而异(例如,经济舱与商务舱),我们需要做些什么?
答:请提供最常见的价格。
问题:如果价格因日期而异(例如旺季价格),我们需要做些什么?
答:请创建单独的路线。
问题:如果 agency.agency_fare_url
有多个预订网域,我们可以将它们全部添加,并用英文逗号分隔吗?
答:请仅添加一个网址。如果仅显示一个会出现问题,请将其留空。
问:routes.route_long_name
可以使用相同的名称吗?
答:可以,您可以为该属性设置相同的名称。
问题:如果我们为以下内容同时设置了父级充电站和子级充电站,系统会使用哪个充电站?
答:
stop_code
:停止
stop_name
:车站(未来,我们可能会使用“经停点”)
stop_desc
:无
stop_lat
:两者
stop_lon
:两者
zone_id
:停止
stop_url
:充电站
wheelchair_boarding
:两者
问:我们可以在更改时间表的确切日期更新 Feed 吗?
答:您可以在 GTFS 中指定 Feed 的有效截止日期。必须在上架日期前两周上传 Feed。请注意,日历信息必须重叠。
我们提供了一个用于“合并”两个 Feed 的工具。
问:我们可以使用一直在内部使用的现有唯一 ID 吗?
答:是的,GTFS 中的 ID 可以是任何值。
问题:我的 Feed 上传总是失败。可能存在什么问题?
答:请确保文件位于 ZIP 文件的顶级目录中。
问题:预览版中不会根据示例查询生成公交结果。问题可能是什么?
答:请检查这些示例的时间,并确保您的转场效果是在所选时间运行的。如果没有,则可能不会生成任何结果。
如未另行说明,那么本页面中的内容已根据知识共享署名 4.0 许可获得了许可,并且代码示例已根据 Apache 2.0 许可获得了许可。有关详情,请参阅 Google 开发者网站政策。Java 是 Oracle 和/或其关联公司的注册商标。
最后更新时间 (UTC):2025-07-25。
[null,null,["最后更新时间 (UTC):2025-07-25。"],[[["\u003cp\u003eGoogle prefers a regularly fetched GTFS feed via FTP, with weekly updates as the default.\u003c/p\u003e\n"],["\u003cp\u003eSeparate routes should be created for services with date-dependent pricing, such as peak season fares.\u003c/p\u003e\n"],["\u003cp\u003eFor stops with both parent and child stations defined, station information will be prioritized for \u003ccode\u003estop_name\u003c/code\u003e and \u003ccode\u003estop_url\u003c/code\u003e while stop information will be used for other attributes.\u003c/p\u003e\n"],["\u003cp\u003eGTFS feeds must be uploaded two weeks prior to their effective date and should specify the valid date range within the feed itself.\u003c/p\u003e\n"],["\u003cp\u003eTroubleshooting feed upload failures often involves ensuring all files are in the ZIP file's top-level directory and verifying transit schedules align with preview query times.\u003c/p\u003e\n"]]],["GTFS implementation involves a test environment after feed upload. Google prefers regular feed fetching (weekly default) via FTP, though manual uploads are possible. Multiple feeds are accepted, but a single feed is preferred. Include the most generic price; for date-dependent pricing, create separate routes. Only one URL is allowed for `agency_fare_url`. IDs can be internal values. Files should be at the top level of the ZIP. Feeds are needed two weeks prior to live date.\n"],null,["# Frequently Asked Questions\n\nThe following are questions and answers for common issues when implementing GTFS.\n\n##### Q: Is there a test environment for the feed before making it public?\n\nA: Yes, we will prepare the test environment once your feed is successfully uploaded.\n\n##### Q: Do we need to manually upload the feed every time there is an update or can we ask Google to\nfetch it from our server?\n\nA: In general, Google prefers to set up a regular fetch (via FTP GET). The frequency\nis weekly by default. In addition, you can manually upload a file from the console.\n\n##### Q: If we have both the express line and local line, can we submit separate feeds?\n\nA: Yes, it is possible for an agency to submit multiple separate feeds but we usually prefer having\na single feed.\n\n##### Q: In case the price is different depending on the seat --e.g., class C vs. class A, what do we need to do?\n\nA: Please include the most generic price.\n\n##### Q: If the price is different depending on the date --e.g., peak season price, what do we need to do?\n\nA: Please create separate routes.\n\n##### Q: When there are multiple booking domains for `agency.agency_fare_url`, can we add them all separating\nthem with comma?\n\nA: Please only include one URL. If there is a problem in just showing one, please leave it blank.\n\n##### Q: Is it ok to have the same name for `routes.route_long_name`?\n\nA: Yes, you can set the same name for that attribute.\n\n##### Q: If we set both the parent station and child station for the following, which will be used?\n\nA:\n\n- `stop_code`: stop\n- `stop_name`: station (in the future, we might use stop)\n- `stop_desc`: none\n- `stop_lat`: both\n- `stop_lon`: both\n- `zone_id`: stop\n- `stop_url`: station\n- `wheelchair_boarding`: both\n\n\u003cbr /\u003e\n\n##### Q: Can we update the feed exactly on the date when the schedule is changed?\n\nA: You can specify to which date the feed is valid in GTFS. The feeds must be uploaded\ntwo weeks prior to the date when it should go live. Note that the calendar information must overlap.\nThere is a tool for \"merging\" two feeds.\n\n##### Q: Can we use our existing unique ids we have been using internally?\n\nA: Yes, IDs in GTFS can be any value.\n\n##### Q: My feed upload keeps failing. What could be a problem?\n\nA: Please ensure that the files are in the top level directory in your ZIP file.\n\n##### Q: Transit results are not generated from the sample queries in Preview. What could be the issue?\n\nA: Please check the time of those samples and make sure that your transits are running at those selected\ntimes. If not, it is possible that there is no result generated."]]