Plus Code 就像是街道地址,適用於沒有實際地址的人或地點。Plus code 是以經緯度為依據,並以數字和字母顯示,而非街道名稱和號碼。
計算路線回應現在包含 geocodingResults 陣列。對於要求中以地址字串或 Plus Code 指定的每個位置 (起點、目的地或中途停靠點),API 都會執行地點 ID 查詢。這個陣列的每個元素都包含與位置相應的地點 ID,以及位置的其他中繼資料。系統會忽略要求中指定為地點 ID 或經緯度座標的位置。
現有預先發布版功能的異動
您現在必須在正式發布的 GA 中,將新的陣列 extraComputations 欄位新增至要求,明確啟用下列功能:
[[["容易理解","easyToUnderstand","thumb-up"],["確實解決了我的問題","solvedMyProblem","thumb-up"],["其他","otherUp","thumb-up"]],[["缺少我需要的資訊","missingTheInformationINeed","thumb-down"],["過於複雜/步驟過多","tooComplicatedTooManySteps","thumb-down"],["過時","outOfDate","thumb-down"],["翻譯問題","translationIssue","thumb-down"],["示例/程式碼問題","samplesCodeIssue","thumb-down"],["其他","otherDown","thumb-down"]],["上次更新時間:2025-07-22 (世界標準時間)。"],[[["\u003cp\u003eThe Routes API has transitioned from Preview to General Availability (GA), introducing new features and changes to existing ones.\u003c/p\u003e\n"],["\u003cp\u003eYou can now specify locations using address strings and Plus Codes in addition to place IDs and coordinates.\u003c/p\u003e\n"],["\u003cp\u003eToll info, fuel consumption, and traffic on a polyline now require explicit enablement using the \u003ccode\u003eextraComputations\u003c/code\u003e field in requests.\u003c/p\u003e\n"],["\u003cp\u003eThe \u003ccode\u003egeocodingResults\u003c/code\u003e array has been added to the response, providing place IDs and metadata for locations specified as address strings or Plus Codes.\u003c/p\u003e\n"],["\u003cp\u003eExisting implementations relying on implicit inclusion of toll info, fuel consumption, or traffic on a polyline data need to be updated to utilize the \u003ccode\u003eextraComputations\u003c/code\u003e field.\u003c/p\u003e\n"]]],["The Routes API's GA release introduces new location specification options, including address strings and Plus Codes, and includes a `geocodingResults` array in the response. To enable toll info, fuel consumption, and traffic on a polyline, users must now set the `extraComputations` array in their requests. `extraComputations` values are \"TOLLS\", \"FUEL_CONSUMPTION\", and \"TRAFFIC_ON_POLYLINE\". The field mask must still be used. Certain fields will be omitted in the response unless enabled by `extraComputations`.\n"],null,["# Migrate from the Preview release\n\n**European Economic Area (EEA) developers** If your billing address is in the European Economic Area, effective on 8 July 2025, the [Google Maps Platform EEA Terms of Service](https://cloud.google.com/terms/maps-platform/eea) will apply to your use of the Services. Functionality varies by region. [Learn more](/maps/comms/eea/faq).\n\nThe Routes API was released as a public Preview (pre-GA) in September of\n2022. Pre-GA Offerings are covered by the [Google Maps Platform Service Specific\nTerms](https://cloud.google.com/maps-platform/terms/maps-service-terms).\nFor more information, see the [launch stage descriptions](/maps/launch-stages).\n\nThis section describes how to migrate an app from the Preview release to the GA\nrelease.\n\nNew features added to the GA release\n------------------------------------\n\nThe GA release adds the following new features that were not included in the\nPreview:\n\n- Along with place IDs and latitude/longitude coordinates, you can now\n [specify a location](/maps/documentation/routes/specify_location) in the GA release by using:\n\n - [Address strings](/maps/documentation/routes/specify_location#text_string) (\"Chicago, IL\" or\n \"Darwin, NT, Australia\")\n\n Address strings are often how a user inputs an address. However,\n {product_name} must first geocode the address string internally to convert\n it to latitude/longitude coordinates before it can calculate a route.\n\n In addition, support for the `regionCode` request parameter has been\n added, which lets you specify to return geocoded results for a specific\n geographic region.\n - [Plus Codes](/maps/documentation/routes/specify_location#plus_code)\n\n Plus Codes are like street addresses for people or places that don't\n have an actual address. Instead of addresses with street names and\n numbers, Plus Codes are based on latitude and longitude, and are\n displayed as numbers and letters.\n- The [compute routes response](/maps/documentation/routes/understand-route-response) now contains the\n `geocodingResults` array. For every location in the request (origin,\n destination, or intermediate waypoint) that was specified as an **address\n string** or as a **Plus code**, the API performs a place ID lookup. Each\n element of this array contains the place ID corresponding to a location\n along with additional metadata about the location. Locations in the request\n specified as a place ID or as latitude/longiiture coordinates are ignored.\n\nChanges to existing Preview features\n------------------------------------\n\nYou must now explicitly enable the following features in the GA by\nadding the new array `extraComputations` field to the request:\n\n- [Toll info](/maps/documentation/routes/calculate_toll_fees)\n\n- [Fuel consumption](/maps/documentation/routes/eco-routes)\n\n- [Traffic on a polyline](/maps/documentation/routes/traffic_on_polylines)\n\nIn the Preview release, you used a [field mask](/maps/documentation/routes/choose_fields) to specify to\nreturn information for these features in the response. Now, you must both:\n\n- Set the new `extraComputations` array request parameter to enable these features.\n- Set a field mask to specify to return the information in the response.\n\n### What do I need to know?\n\nThe following fields will no longer be included in\n[computeRouteMatrix responses](/maps/documentation/routes/reference/rest/v2/TopLevel/computeRouteMatrix#response-body)\nunless explicitly enabled by setting `extraComputations`:\n\n- `travelAdvisory.tollInfo` (Toll info)\n\nThe following fields will no longer be included in\n[computeRoutes responses](/maps/documentation/routes/reference/rest/v2/TopLevel/computeRoutes#response-body)\nunless explicitly enabled by setting `extraComputations`:\n\n- `routes.legs.travelAdvisory.tollInfo`(Toll info)\n- `routes.travelAdvisory.tollInfo`(Toll info)\n- `routes.travelAdvisory.fuelConsumptionMicroliters`(Fuel consumption)\n- `routes.travelAdvisory.speedReadingIntervals`(Traffic on a polyline)\n- `routes.legs.travelAdvisory.speedReadingIntervals`(Traffic on a polyline)\n\n### What do I need to do?\n\nTo receive the response fields for toll info, fuel consumption, or traffic on a\npolyline, you must set the new request array field, `extraComputations`, to\ninclude one or more of the following values:\n\n- To receive [toll info](/maps/documentation/routes/calculate_toll_fees), set the new\n `extraComputations` array field to `\"TOLLS\"`.\n\n- To receive [fuel consumption](/maps/documentation/routes/eco-routes), set the new `extraComputations`\n array field to `\"FUEL_CONSUMPTION\"`.\n\n- To receive [traffic information on polylines](/maps/documentation/routes/traffic_on_polylines), set the\n new `extraComputations` array field to `\"TRAFFIC_ON_POLYLINE\"`."]]