[null,null,["最終更新日 2025-08-31 UTC。"],[],[],null,["# Navigation points\n\n| **Important:** This experimental feature has been replaced by the [SearchDestinations](/maps/documentation/geocoding/search-for-destinations) endpoint of the new Geocoding API v4. Use that endpoint instead if you want to get the navigation points of a place.\n\n\u003cbr /\u003e\n\n| This product or feature is Experimental (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 descriptions](/maps/launch-stages).\n\n\u003cbr /\u003e\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 `navigation_points` field within the Geocoding response contains a list of\npoints that are useful for navigating to the place. Specifically, they should be\nused either as the starting or ending points when routing on a road network from\nor to the place. Each navigation point contains the following values:\n\n- `location` contains the latitude, longitude value of the navigation point. This location will always be very close to the road network and represents an ideal stopping or starting point for navigating to and from a place. The point is intentionally slightly offset from the road's centerline to clearly mark the side of the road where the place is located.\n- `restricted_travel_modes` is a list of travel modes that the navigation point is not accessible from:\n - `\"DRIVE\"` is the travel mode corresponding to driving directions.\n - `\"WALK\"` is the travel mode corresponding to walking directions.\n- `road_name` contains the name of the road the navigation point is offset from.\n\n\u003cbr /\u003e\n\nNavigation points are returned for most places with a precise location, such as\nstreet addresses, buildings, and establishments. Places that represent large\nareas, such as cities and regions, where a precise location can be ambiguous\nmight not return any navigation points.\n\nMigration notice\n----------------\n\nStarting April 17th, you must now supply the `NAVIGATION_POINTS` extra\ncomputations parameter in the request to receive navigation points. Clients can\ntest this by confirming that the `road_name` field within some navigation points\nis returned and that the `location` field within each navigation point has the\nfollowing four subfields (`lat`, `lng`, `latitude`, `longitude`).\n\nAdditionally, you must migrate to the `location.lat` and `location.lng` fields\nrather than the `location.latitude` and `location.longitude` fields. In a future\nrelease, requests that don't contain the `NAVIGATION_POINTS` extra computations\nparameter won't include any navigation points in the response and the\n`location.latitude` and `location.longitude` fields will no longer be returned.\n\nRequest details\n---------------\n\nYou can obtain navigation points in the following kinds of requests:\n\n- [Geocoding request](/maps/documentation/geocoding/requests-geocoding)\n- [Reverse geocoding request](/maps/documentation/geocoding/requests-reverse-geocoding)\n- [Place geocoding request](/maps/documentation/geocoding/requests-places-geocoding)\n\nFor any of these requests, you supply this parameter:\n`extra_computations=NAVIGATION_POINTS`.\n\n### Example request\n\nThe following query uses [place geocoding](/maps/documentation/geocoding/requests-places-geocoding) to obtain navigation points for a\nrestaurant in Mountain View, California, United States: \n\n https://maps.googleapis.com/maps/api/geocode/json?place_id=ChIJZ54APTS3j4ARBYZD956MHq8&extra_computations=NAVIGATION_POINTS&key=YOUR_API_KEY\n\n### Example response\n\nThe response from the query above shows an array of navigation points: \n\n {\n \"navigation_points\": [\n {\n \"location\": {\n \"lat\": 37.3940894,\n \"lng\": -122.0788389,\n },\n \"restricted_travel_modes\": [\"WALK\"],\n \"road_name\": \"Castro Street\"\n },\n {\n \"location\": {\n \"lat\": 37.394273,\n \"lng\": -122.0793078,\n },\n \"restricted_travel_modes\": [\"WALK\"],\n \"road_name\": \"Wild Cherry Lane\"\n },\n {\n \"location\": {\n \"lat\": 37.3941202,\n \"lng\": -122.0789189,\n },\n \"restricted_travel_modes\": [\"DRIVE\"]\n }\n ]\n }\n\nFeedback\n--------\n\nThis is an experimental feature. We would appreciate feedback at\n[geocoding-feedback-channel@google.com](mailto:geocoding-feedback-channel@google.com)."]]