Bermigrasi dari rilis Pratinjau
Tetap teratur dengan koleksi
Simpan dan kategorikan konten berdasarkan preferensi Anda.
Developer Wilayah Ekonomi Eropa (EEA)
Routes API dirilis sebagai Pratinjau publik (pra-GA) pada September 2022. Penawaran Pra-GA tercakup dalam Persyaratan Khusus Layanan Google Maps Platform.
Untuk mengetahui informasi selengkapnya, lihat deskripsi tahap peluncuran.
Bagian ini menjelaskan cara memigrasikan aplikasi dari rilis Pratinjau ke rilis GA.
Fitur baru yang ditambahkan ke rilis GA
Rilis GA menambahkan fitur baru berikut yang tidak disertakan dalam
Pratinjau:
Selain ID tempat dan koordinat lintang/bujur, Anda kini dapat menentukan lokasi dalam rilis GA menggunakan:
String alamat ("Chicago, IL" atau
"Darwin, NT, Australia")
String alamat sering kali merupakan cara pengguna memasukkan alamat. Namun, {product_name} harus terlebih dahulu melakukan geocoding string alamat secara internal untuk mengonversinya menjadi koordinat lintang/bujur sebelum dapat menghitung rute.
Selain itu, dukungan untuk parameter permintaan regionCode telah ditambahkan, yang memungkinkan Anda menentukan untuk menampilkan hasil geocoding untuk wilayah geografis tertentu.
Kode Plus
Plus Codes berfungsi seperti alamat untuk orang atau tempat yang tidak memiliki alamat sebenarnya. Daripada alamat dengan nama jalan dan nomor, Plus Codes didasarkan pada lintang dan bujur, serta ditampilkan sebagai angka dan huruf.
compute routes response kini berisi array
geocodingResults. Untuk setiap lokasi dalam permintaan (asal, tujuan, atau titik jalan perantara) yang ditentukan sebagai string alamat atau sebagai Kode plus, API akan melakukan penelusuran ID tempat. Setiap
elemen array ini berisi ID tempat yang sesuai dengan lokasi
beserta metadata tambahan tentang lokasi tersebut. Lokasi dalam permintaan yang ditentukan sebagai ID tempat atau sebagai koordinat lintang/bujur akan diabaikan.
Perubahan pada fitur Pratinjau yang ada
Sekarang Anda harus mengaktifkan fitur berikut secara eksplisit di GA dengan
menambahkan kolom array extraComputations baru ke permintaan:
Dalam rilis Pratinjau, Anda menggunakan masker kolom untuk menentukan informasi yang akan ditampilkan untuk fitur ini dalam respons. Sekarang, Anda berdua harus:
- Tetapkan parameter permintaan array
extraComputations baru untuk mengaktifkan fitur ini.
- Tetapkan mask kolom untuk menentukan informasi yang akan ditampilkan dalam respons.
Apa yang perlu saya ketahui?
Kolom berikut tidak akan lagi disertakan dalam
respons computeRouteMatrix
kecuali jika diaktifkan secara eksplisit dengan menyetel extraComputations:
travelAdvisory.tollInfo (Info jalan tol)
Kolom berikut tidak akan lagi disertakan dalam
respons computeRoutes
kecuali jika diaktifkan secara eksplisit dengan menyetel extraComputations:
routes.legs.travelAdvisory.tollInfo(Info tol)routes.travelAdvisory.tollInfo(Info tol)routes.travelAdvisory.fuelConsumptionMicroliters(Konsumsi bahan bakar)routes.travelAdvisory.speedReadingIntervals(Lalu lintas di polyline)routes.legs.travelAdvisory.speedReadingIntervals(Lalu lintas di polyline)
Apa yang harus saya lakukan?
Untuk menerima kolom respons info tol, konsumsi bahan bakar, atau lalu lintas di
polyline, Anda harus menetapkan kolom array permintaan baru, extraComputations, untuk
menyertakan satu atau beberapa nilai berikut:
Kecuali dinyatakan lain, konten di halaman ini dilisensikan berdasarkan Lisensi Creative Commons Attribution 4.0, sedangkan contoh kode dilisensikan berdasarkan Lisensi Apache 2.0. Untuk mengetahui informasi selengkapnya, lihat Kebijakan Situs Google Developers. Java adalah merek dagang terdaftar dari Oracle dan/atau afiliasinya.
Terakhir diperbarui pada 2025-07-22 UTC.
[null,null,["Terakhir diperbarui pada 2025-07-22 UTC."],[[["\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\"`."]]
