[null,null,["最后更新时间 (UTC)：2025-08-30。"],[[["\u003cp\u003eThe Places API provides features to search for places along a predefined route and calculate routing summaries, enhancing trip planning.\u003c/p\u003e\n"],["\u003cp\u003eText Search (New) enables searching for places near a route calculated by the Routes API, prioritizing those with minimal detour times.\u003c/p\u003e\n"],["\u003cp\u003eText Search (New) and Nearby Search (New) can calculate the travel duration and distance from a specified origin to each place in the search results.\u003c/p\u003e\n"],["\u003cp\u003eWhen searching along a route, Text Search (New) can calculate the detour duration and distance for each place, showing the impact of deviating from the original route.\u003c/p\u003e\n"]]],[],null,["Overview of search along route\n==============================\n\nSearch along route features are available in the following Places (New) APIs:\n\n- **Text Search (New) only:** Search for places along a predefined trip route.\n- **Text Search (New) and Nearby Search (New):** Calculate the routing summary from a specified routing origin location to each place in the search results.\n- **Text Search (New) only:** Calculate the routing summary for each place along a predefined trip route.\n\nSearch along a route\n--------------------\n\nYou use the [Routes API](/maps/documentation/routes) to calculate the trip route\nbetween two locations. The Routes API can calculate a route for a car, bicycle,\ntwo-wheel vehicle, transit system, or for walking.\n| **Note:** Transit system routes are not supported by the Places API.\n\n[Text Search (New)](/maps/documentation/places/android-sdk/text-search) lets you use this calculated route to perform a\n**search along a route**. With this option, you pass the precalculated route\nfrom the Routes API to the Text Search (New) request. The response then contains\nplaces that match the search criteria and are also located near the specified\nroute.\n\nSearching along a route is similar to using the `locationRestriction` or\n`locationBias` request options to bias the search results. `locationRestriction`\nreturns search results that fall within the viewport bounds, while\n`locationBias` may return search results outside of the viewport. However, while\nthe `locationBias` and `locationRestriction` options let you specify a region to\nbias the search results, the search along route feature in Text Search also lets\nyou bias the search results to include those with minimal detour times from the\nroute origin to the route destination. You can bias search results using either\n`locationBias` or `locationRestriction` in combination with the polyline.\n\nFor example, consider the route from the origin, referred to as a\n**waypoint** in the Routes API, to the destination as calculated by the Routes\nAPI:\n\nWhen you search along the route, the search is biased to return places near the\nroute with minimal detour times from the origin to the destination. In this\nexample, points A, B, and C are places returned by the search.\n\nCalculate routing summary\n-------------------------\n\n[Text Search (New)](/maps/documentation/places/android-sdk/text-search) and [Nearby Search (New)](/maps/documentation/places/android-sdk/nearby-search) can\ncalculate the **routing summary** , meaning the duration and distance, to each\nplace in the response based on the specified **routing origin location** in the\nrequest. When you specify the routing origin, the response not only contains a\nlist of places that match the search, but also the travel duration and distance\nfrom the routing origin to each place.\n\nIn the following image, points A, B, and C are places returned in the search\nresponse:\n\nFor each place in the results, the response contains the travel duration and\ndistance from the routing origin to the place, if available.\n| **Note:** This is only an estimate of the routing information. To get the actual route details, including step-by-step directions, use the [Routes\n| API](/maps/documentation/routes/compute_route_directions).\n\nBy default, the travel duration and distance is calculated using the [`TRAFFIC_UNAWARE`](/maps/documentation/routes/config_trade_offs#traffic_unaware)\noption in the Routes API. You can optionally set routing preferences to take\nlive traffic conditions [`TRAFFIC_AWARE_OPTIMAL`](/maps/documentation/routes/config_trade_offs#traffic_aware_optimal)\nor latency-reduced live traffic conditions [`TRAFFIC_AWARE`](/maps/documentation/routes/config_trade_offs#traffic_aware)\ninto consideration during calculations.\n| **Note:** `TRAFFIC_AWARE` and `TRAFFIC_OPTIMAL` only apply to the `DRIVE` and `TWO_WHEELER` travel modes. If either routing preference is specified with an unsupported travel mode, the routing summary calculation defaults to using the `TRAFFIC_UNAWARE` option. If `TWO_WHEELER` is specified in an [unsupported region](/maps/documentation/routes/coverage-two-wheeled), the API returns an empty routing summary.\n| When you set the [`TRAFFIC_AWARE`](/maps/documentation/routes/config_trade_offs#traffic_aware) routing preference, routes are calculated accounting for traffic conditions. As a result, the route and route details more accurately reflect real-world conditions. Since this increase in data quality comes at the expense of response latency, performance optimizations are applied to reduce much of the latency. When you set the [`TRAFFIC_AWARE_OPTIMAL`](/maps/documentation/routes/config_trade_offs#traffic_aware_optimal) routing preference, routes are calculated accounting for traffic conditions, but no performance optimizations are applied. In this mode, the server performs a more exhaustive search of the road network to find the optimal route.\n\n### About routes, legs, and waypoints\n\nSeveral components make up a route, as calculated by the Routes API:\n\nA route consists of the following components:\n\n- **Waypoint** : To calculate a route, you specify at a minimum the locations of the origin and destination. You define these locations as *waypoints* on the route. *Intermediate waypoints* are locations in between the origin and destination that you want the route to go through.\n- **Route** : The entire trip from the origin waypoint, through any\n intermediate waypoints, to the destination waypoint. A route consists of one\n or more **legs**.\n\n When passing a route to Text Search, you pass the [route's encoded\n polyline](/maps/documentation/routes/traffic_on_polylines) as returned by the [Routes API](/maps/documentation/routes). An encoded\n polyline is an encoded list of latitude and longitude points that lets you represent the\n route's polyline as a string.\n- **Leg** : The path from one waypoint in a route to the next waypoint in the\n route. Each leg consists of one or more discrete **steps**.\n\n A route contains a separate leg for the path from each waypoint to the next.\n For example, if the route contains a single origin waypoint and a single\n destination waypoint, then the route contains a single leg.\n\n For each additional waypoint you add to the route after the origin and\n destination, called an *intermediate* waypoint, the API adds a separate leg.\n\nFor more information on routes and calculating routes, see the [Routes\nAPI](/maps/documentation/routes).\n\nCalculate the routing summary with a search along route\n-------------------------------------------------------\n\nYou can combine **routing summary** calculations with **search along a route** .\nIn this case, [Text Search (New)](/maps/documentation/places/android-sdk/text-search) returns the travel duration and\ndistance to each place in the response, and then from each place to the final\ndestination of the route. Think of this calculation as providing a travel\nduration and distance if you detour from the specified route to travel to a\nplace in the search results, and then continue on to the final destination.\n\nFor example, consider the following route from the origin to the destination as\ncalculated by the Routes API. Pass this route to the Text Search (New) API along\nwith your search criteria.\n\nIn this example, location A is a place returned in the search results from\nText Search (New). For each place in the response, the search includes the duration\nand distance required to detour to that place as a **two-leg trip**:\n\n- The first leg contains the travel duration and distance from the route **origin** to the **place**. In this example, from the origin to place A.\n- The second leg contains the travel duration and distance from the **place** to the route **destination**. In this example, from A to the destination.\n\nFrom the information in the response, you can then calculate the **detour\nduration and distance**, where:\n\n- \\\\(t_{OD}\\\\) is the **trip duration** from the origin to the destination, \\\\(s_{OD}\\\\) is the **trip distance** from the origin to the destination\n- \\\\(t_{OA}\\\\) is the **trip duration** from the origin to A; \\\\(s_{OA}\\\\) is the **trip distance** from the origin to A\n- \\\\(t_{AD}\\\\) is the **trip duration** from A to the destination; \\\\(s_{AD}\\\\) is the **trip distance** from A to the destination\n\n**Detour duration** is the **duration difference** between the **original trip**\n(from the origin to the destination) and the **new trip** (from the origin to\nthe destination **through** A): \n$$ t_{detour} = t_{OA} + t_{AD} - t_{OD} $$\n\n**Detour distance** is the **distance difference** between the **original trip**\n(from the origin to the destination) and the **new trip** (from the origin to\nthe destination **through** A): \n$$ s_{detour} = s_{OA} + s_{AD} - s_{OD} $$"]]
