Pasa el parámetro routingParameters.origin en la solicitud para especificar las coordenadas de latitud y longitud del origen del enrutamiento. Este parámetro es obligatorio para calcular la duración y la distancia a cada lugar en la respuesta.
Incluye routingSummaries en la máscara de campo para que la respuesta incluya el array routingSummaries. Este array contiene la duración y la distancia desde el origen de la ruta hasta cada lugar de la respuesta.
El Explorador de APIs te permite realizar solicitudes en vivo para que puedas familiarizarte con la API y sus opciones:
La respuesta contiene dos arrays JSON: el array places contiene los lugares coincidentes, y el array routingSummaries contiene la duración y la distancia para viajar a cada lugar:
Cada elemento del array routingSummaries se encuentra en la ubicación del array correspondiente al lugar del array places. Es decir, el elemento en routingSummaries[0] corresponde al lugar en places[0].
La longitud del array de routingSummaries es la misma que la del array de places. En el caso de que el routingSummary de un lugar no esté disponible, la entrada del array estará vacía.
Dado que este ejemplo calcula la duración y la distancia desde el origen del enrutamiento hasta cada lugar, el campo routingSummaries.legs de la respuesta contiene un solo objeto Leg que incluye los objetos duration y distanceMeters desde el origen del enrutamiento hasta el lugar.
{"places":[{"formattedAddress":"1, Westfield Sydney Central Plaza, 450 George St, Sydney NSW 2000, Australia","displayName":{"text":"Gözleme King Sydney","languageCode":"en"}},{"formattedAddress":"367 Pitt St, Sydney NSW 2000, Australia","priceLevel":"PRICE_LEVEL_MODERATE","displayName":{"text":"Mother Chu's Vegetarian Kitchen","languageCode":"en"}},…]"routingSummaries":[{"legs":[{"duration":"597s","distanceMeters":2607}],"directionsUri":"https://www.google.com/maps/dir/-33.8688,151.1957362/''/data=!4m6!4m5!1m0!1m2!1m1!1s0x6b12ae3fa97cd745:0x6aecf365bf497c08!3e0"},{"legs":[{"duration":"562s","distanceMeters":2345}],"directionsUri":"https://www.google.com/maps/dir/-33.8688,151.1957362/''/data=!4m6!4m5!1m0!1m2!1m1!1s0x6b12ae3da97f60c1:0x845f3273bd764f6c!3e0"},…]}
En este ejemplo, puedes ver que la duración y la distancia desde el origen de la ruta hasta el primer lugar en los resultados son de 597 segundos y 2,607 metros.
Cómo usar la Búsqueda cercana
En este ejemplo, calcularás la duración y la distancia del viaje a cada lugar en la respuesta de la Búsqueda cercana. En este ejemplo, se buscan restaurantes en Sídney, Australia, y se establecen la restricción de ubicación y el origen de la ruta en las mismas coordenadas de latitud y longitud:
No es necesario que uses las mismas coordenadas para el locationRestriction y el origen de la ruta. Por ejemplo, puedes establecer locationRestriction en el punto central de Sídney para sesgar los resultados de la búsqueda hacia ese círculo. Sin embargo, luego estableces el origen de la ruta en las coordenadas de tu casa, es decir, en una ubicación diferente dentro del círculo de búsqueda. Luego, la solicitud sesga los resultados de la búsqueda hacia el círculo y calcula los resúmenes de la ruta en función de la ubicación de tu casa.
Especifica las opciones de viaje
De forma predeterminada, los cálculos de duración y distancia son para un automóvil. Sin embargo, puedes controlar el tipo de vehículo, así como otras opciones, en la búsqueda.
Usa el parámetro routingParameters.travelMode para establecer el modo de transporte en DRIVE, BICYCLE, WALK o TWO_WHEELER. Para obtener más información sobre estas opciones, consulta Tipos de vehículos disponibles para las rutas.
Usa la propiedad routingParameters.routingPreference para establecer la opción de preferencia de enrutamiento en TRAFFIC_UNAWARE (predeterminada), TRAFFIC_AWARE o TRAFFIC_AWARE_OPTIMAL. Cada opción tiene diferentes niveles de calidad y latencia de los datos. Para obtener más información, consulta Cómo especificar si se deben incluir datos de tráfico y de qué manera.
La propiedad routingParameters.routingPreference sí afecta las indicaciones que se incluyen en el campo directionsUri de la versión preliminar (pre-DG), ya que Google Maps muestra las opciones de tráfico cuando se abre el vínculo.
[[["Fácil de comprender","easyToUnderstand","thumb-up"],["Resolvió mi problema","solvedMyProblem","thumb-up"],["Otro","otherUp","thumb-up"]],[["Falta la información que necesito","missingTheInformationINeed","thumb-down"],["Muy complicado o demasiados pasos","tooComplicatedTooManySteps","thumb-down"],["Desactualizado","outOfDate","thumb-down"],["Problema de traducción","translationIssue","thumb-down"],["Problema con las muestras o los códigos","samplesCodeIssue","thumb-down"],["Otro","otherDown","thumb-down"]],["Última actualización: 2025-09-05 (UTC)"],[[["\u003cp\u003eCalculate travel duration and distance to places returned by Text Search (New) or Nearby Search (New) by specifying the \u003ccode\u003eroutingParameters.origin\u003c/code\u003e and including \u003ccode\u003eroutingSummaries\u003c/code\u003e in the field mask.\u003c/p\u003e\n"],["\u003cp\u003eThe \u003ccode\u003eroutingSummaries\u003c/code\u003e array contains duration and distance from the origin to each place, mirroring the order of the \u003ccode\u003eplaces\u003c/code\u003e array.\u003c/p\u003e\n"],["\u003cp\u003eCustomize routing calculations by using \u003ccode\u003eroutingParameters\u003c/code\u003e to set travel mode (DRIVE, BICYCLE, WALK, TWO_WHEELER), routing preference (TRAFFIC_UNAWARE, TRAFFIC_AWARE, TRAFFIC_AWARE_OPTIMAL), and route modifiers (avoidTolls, avoidHighways, avoidFerries, avoidIndoor).\u003c/p\u003e\n"],["\u003cp\u003eThe \u003ccode\u003edirectionsUri\u003c/code\u003e field in the \u003ccode\u003eroutingSummaries\u003c/code\u003e (Preview, Pre-GA) provides a link to Google Maps directions for each place, using the specified routing parameters.\u003c/p\u003e\n"]]],[],null,["Calculate routing summary\n=========================\n\nTo use [Text Search (New)](/maps/documentation/places/web-service/text-search) or [Nearby Search (New)](/maps/documentation/places/web-service/nearby-search)\nto calculate the travel duration and distance to each place in the response:\n\n1. Pass the `routingParameters.origin` parameter in the request to specify the\n latitude and longitude coordinates of the routing origin. This parameter is\n required to calculate the duration and distance to each place in the\n response.\n\n2. Include `routingSummaries` in the field mask so that the response includes\n the `routingSummaries` array. This array contains the duration and distance\n from the routing origin to each place in the response.\n\n | **Note:** Adding `routingSummaries` in the field mask without also including either the `routingParameters.origin` parameter or the `searchAlongRouteParameters.polyline.encodedPolyline` parameter in the request causes an error.\n\nThe APIs Explorer lets you make live requests so that you can get familiar with\nthe API and the API options: \n[Try it!](#try_it)\n\nUse Text Search (New)\n---------------------\n\nIn the following request, you calculate the travel duration and distance to each\nplace in the Text Search (New) response: \n\n```scdoc\ncurl -X POST -d '{\n \"textQuery\" : \"Spicy Vegetarian Food in Sydney, Australia\",\n \"routingParameters\": {\n \"origin\": {\n \"latitude\": -33.8688,\n \"longitude\": 151.1957362\n }\n }\n}' \\\n-H 'Content-Type: application/json' -H 'X-Goog-Api-Key: API_KEY' \\\n-H 'X-Goog-FieldMask: places.displayName,places.formattedAddress,places.priceLevel,routingSummaries' \\\n'https://places.googleapis.com/v1/places:searchText'\n```\n\nThe response contains two JSON arrays: the `places` array contains the matching\nplaces, and the `routingSummaries` array containing the duration and distance to\ntravel to each place: \n\n```yaml\n{\n \"places\": [\n {\n object (/maps/documentation/places/web-service/reference/rest/v1/places)\n }\n ]\n \"routingSummaries\": [\n {\n object (/maps/documentation/places/web-service/reference/rest/v1/RoutingSummary)\n }\n}\n```\n\nEach element in the `routingSummaries` array is at the corresponding array\nlocation as the place in the `places` array. That is, the element at\n`routingSummaries[0]` corresponds to the place at `places[0]`.\n\nThe array length of `routingSummaries` is the same as the array length of\n`places`. In the case where the `routingSummary` for a place is not available,\nthe array entry is empty.\n\nBecause this example calculates the duration and distance from the routing\norigin to each place, the `routingSummaries.legs` field in the response contains a single\n`Leg` object that contains the `duration` and `distanceMeters` from\nthe routing origin to the place.\n| **Note:** This response also includes the Preview (pre-GA) `directionsUri` field in the routing summary for each place. This field contains a link to open directions to the place in Google Maps. The `routingParameters.origin` parameter is used as the directions origin, the place location is used as the destination, and the travel mode defaults to drive.\n| This product or feature is in Preview (pre-GA). Pre-GA products and features might have limited support, and changes to pre-GA products and features might not be compatible with other pre-GA versions. Pre-GA Offerings are covered by the [Google\n| Maps Platform Service Specific Terms](https://cloud.google.com/maps-platform/terms/maps-service-terms). For more information, see the [launch stage\ndescriptions](/maps/launch-stages). \n\n```json\n{\n \"places\": [\n {\n \"formattedAddress\": \"1, Westfield Sydney Central Plaza, 450 George St, Sydney NSW 2000, Australia\",\n \"displayName\": {\n \"text\": \"Gözleme King Sydney\",\n \"languageCode\": \"en\"\n }\n },\n {\n \"formattedAddress\": \"367 Pitt St, Sydney NSW 2000, Australia\",\n \"priceLevel\": \"PRICE_LEVEL_MODERATE\",\n \"displayName\": {\n \"text\": \"Mother Chu's Vegetarian Kitchen\",\n \"languageCode\": \"en\"\n }\n },\n ...\n ]\n \"routingSummaries\": [\n {\n \"legs\": [\n {\n \"duration\": \"597s\",\n \"distanceMeters\": 2607\n }\n ],\n \"directionsUri\": \"https://www.google.com/maps/dir/-33.8688,151.1957362/''/data=!4m6!4m5!1m0!1m2!1m1!1s0x6b12ae3fa97cd745:0x6aecf365bf497c08!3e0\"\n },\n {\n \"legs\": [\n {\n \"duration\": \"562s\",\n \"distanceMeters\": 2345\n }\n ],\n \"directionsUri\": \"https://www.google.com/maps/dir/-33.8688,151.1957362/''/data=!4m6!4m5!1m0!1m2!1m1!1s0x6b12ae3da97f60c1:0x845f3273bd764f6c!3e0\"\n },\n ...\n ]\n}\n```\n\nFrom this example, you can see that the duration and distance from the routing\norigin to the first place in the results is 597 seconds and 2607 meters.\n\nUse Nearby Search\n-----------------\n\nIn this example, you calculate the travel duration and distance to each place in\nthe Nearby Search response. This example searches for restaurants in Sydney,\nAustralia and sets the location restriction and the routing origin to the same\nlatitude and longitude coordinate: \n\n```scdoc\n curl -X POST -d '{\n \"includedTypes\": [\"restaurant\"],\n \"maxResultCount\": 10,\n \"locationRestriction\": {\n \"circle\": {\n \"center\": {\n \"latitude\": -33.8688,\n \"longitude\": 151.1957362},\n \"radius\": 500.0\n }\n },\n \"routingParameters\": {\n \"origin\": {\n \"latitude\": -33.8688,\n \"longitude\": 151.1957362\n }\n }\n }' \\\n -H 'Content-Type: application/json' -H \"X-Goog-Api-Key:API_KEY\" \\\n -H \"X-Goog-FieldMask: places.displayName,routingSummaries\" \\\n https://places.googleapis.com/v1/places:searchNearby\n```\n\nYou don't have to use the same coordinates for the `locationRestriction` and the\nfor routing origin. For example, you set the `locationRestriction` to the center\npoint of Sydney to bias the search results to that circle. But you then set the\nrouting origin to the coordinates of your house, meaning to a different location\nwithin the search circle. The request then biases the search results to the\ncircle, and calculates the routing summaries based on the location of your\nhouse.\n\nSpecify travel options\n----------------------\n\nBy default, the duration and distance calculations are for a car. However, you\ncan control the vehicle type, as well as other options, in the search.\n\n- Use the `routingParameters.travelMode` parameter to set the mode of\n transportation to `DRIVE`, `BICYCLE`, `WALK`, or `TWO_WHEELER`. For more\n information on these options, see [Available vehicle types for\n routes](/maps/documentation/routes/vehicles).\n\n | **Note:** The Routes API also supports a mode of `TRANSIT`, but that mode is not supported by the Places API.\n | **Note:** The `TWO_WHEELER` option is only supported in those countries listed at [Countries and regions supported for two-wheeled\n | vehicles](/maps/documentation/routes/coverage-two-wheeled).\n- Use the `routingParameters.routingPreference` property to set the routing preference option to `TRAFFIC_UNAWARE` (default), `TRAFFIC_AWARE`, or `TRAFFIC_AWARE_OPTIMAL`. Each option has varying levels of data quality and latency. For more information, see [Specify how and if to include traffic\n data](/maps/documentation/routes/config_trade_offs).\n\n The `routingParameters.routingPreference` property does affect the\n directions contained in the Preview (Pre-GA) `directionsUri` field because\n Google Maps displays traffic options when it opens the link.\n- Use the `routingParameters.routeModifiers` property to specify to `avoidTolls`, `avoidHighways`, `avoidFerries`, and `avoidIndoor`. For more information on these options, see [Specify route features to\n avoid](/maps/documentation/routes/route-modifiers).\n\nIn the next example, you specify the travel mode as `DRIVE` and to avoid\nhighways: \n\n```scdoc\ncurl -X POST -d '{\n \"textQuery\" : \"Spicy Vegetarian Food in Sydney, Australia\",\n \"routingParameters\": {\n \"origin\": {\n \"latitude\": -33.8688,\n \"longitude\": 151.1957362\n },\n \"travelMode\":\"DRIVE\",\n \"routeModifiers\": {\n \"avoidHighways\": true\n }\n }\n}' \\\n-H 'Content-Type: application/json' -H 'X-Goog-Api-Key: API_KEY' \\\n-H 'X-Goog-FieldMask: places.displayName,places.formattedAddress,places.priceLevel,routingSummaries' \\\n'https://places.googleapis.com/v1/places:searchText'\n```\n\nTry it!\n-------\n\nThe APIs Explorer lets you make sample requests so\nthat you can get familiar with the API and the API options.\n\n1. Select the API icon api\n on the right side of the page.\n\n2. Optionally edit the request parameters.\n\n3. Select the **Execute** button. In the dialog, choose the account\n that you want to use to make the request.\n\n4. In the APIs Explorer panel, select the fullscreen icon\n fullscreen to expand the APIs Explorer window."]]
