常見問題
透過集合功能整理內容
你可以依據偏好儲存及分類內容。
以下是有關 GTFS 導入作業的常見問題和解答。
問:動態饋給公開前是否有測試環境?
答:有。動態饋給成功上傳後,我們就會準備測試環境。
問:每次有更新時,是否必須手動上傳動態饋給?還是可以要求 Google 從我們的伺服器中擷取動態饋給?
答:一般來說,Google 傾向安排透過 FTP GET 定期擷取,頻率預設為每週。此外,您也可以透過控制台手動上傳檔案。
問:如果特快車和普通車兩種都有,是否可以提交個別的動態饋給?
答:可以。運輸公司可以提交多項不同的動態饋給,但通常建議只提交一項。
問:如果價格因座位而異 (例如 C 等和 A 等),該怎麼辦?
答:請加入最泛用的價格。
問:如果價格因日期而異 (例如旺季適用特定價格),該怎麼辦?
答:請建立不同的路線。
問:如果 agency.agency_fare_url
有多個預訂網域,是否可以全部加入並使用半形逗號分隔?
答:請只加入一個網址。如果無法僅顯示一個,請將其留白。
問:routes.route_long_name
是否可以使用相同的名稱?
答:可以。您可以為該屬性設定相同的名稱。
問:如果同時設定母車站和子車站,系統會使用哪一個?
答:
stop_code
:停靠站
stop_name
:車站 (未來我們可能會使用停靠站)
stop_desc
:無
stop_lat
:兩者皆是
stop_lon
:兩者皆是
zone_id
:停靠站
stop_url
:車站
wheelchair_boarding
:兩者皆是
問:是否可以在時間表變更當天更新動態饋給?
答:您可以在 GTFS 中指定動態饋給的有效期限。動態饋給必須在上線日期的兩週前上傳。請注意,日曆資訊必須重疊。有一項工具可用來「合併」兩項動態饋給。
問:是否可以使用我們內部慣用的現有專屬 ID?
答:可以。GTFS 中的 ID 可以是任何值。
問:我的動態饋給一直上傳失敗,問題可能出在哪裡?
答:請確認這些檔案位於 ZIP 檔案的頂層目錄中。
問:在「預先發布版」中無法根據範例查詢產生任何大眾運輸搜尋結果,問題可能出在哪裡?
答:請檢查這些範例的時間,並確認您的大眾運輸服務是在這些指定時間營運。如果不是,可能就不會產生任何搜尋結果。
除非另有註明,否則本頁面中的內容是採用創用 CC 姓名標示 4.0 授權,程式碼範例則為阿帕契 2.0 授權。詳情請參閱《Google Developers 網站政策》。Java 是 Oracle 和/或其關聯企業的註冊商標。
上次更新時間:2025-07-25 (世界標準時間)。
[null,null,["上次更新時間: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."]]