Places API（新）的发布现已支持新一代 Places API。

此页面由 Cloud Translation API 翻译。

地点自动补全

请选择平台： Android iOS JavaScript 网络服务

</ph> 注意：服务器端库和客户端库

Places API 还可用于 Java 客户端适用于 Google 地图服务的 Python 客户端、Go 客户端和 Node.js 客户端。 Places API 和客户端库适用于在服务器应用中使用

如果您要构建客户端请参阅 Places SDK for Android、 Places SDK for iOS 和 Maps JavaScript API 地点库。

地点自动补全服务是一项可返回地点的网络服务响应 HTTP 请求。该请求指定了一个搜索字符串和可选的地理边界。该服务可用于为基于文本的地理搜索提供自动补全功能，返回商家、地址和地图注点等用户类型。

“地点自动补全”请求

地点自动补全服务是 Places API 会分享 API 密钥和配额 Places API。

地点自动补全服务可以匹配完整字词和子字符串，解析地点名称、地址，以及代码。这样，应用就可以在用户输入内容时发送查询，实时进行地点预测。

您必须正确设置 Plus 代码的格式。也就是说，您必须对加号进行网址转义， %2B，并且您必须对空格进行网址转义，使其成为 %20。

全局代码是包含 4 个字符的区号，并且包含至少 6 个字符的区号本地代码。例如，网址转义全局代码 849VCWC8+R9 是 849VCWC8%2BR9。
复合代码是包含 6 个字符（或更长）的本地代码，带有。例如，经过网址转义的复合代码 “CWC8+R9 Mountain View, CA, USA”现为 CWC8%2BR9%20Mountain%20View%20CA%20USA。

返回的预测旨在呈现给用户，以帮助他们选择所需地点您可以发送地点详情请求返回。

地点自动完成请求是一个 HTTP URL，其格式如下：

https://maps.googleapis.com/maps/api/place/autocomplete/output?parameters

其中，output 可以是以下值之一：

json（推荐）表示以 JavaScript 形式输出对象表示法 (JSON)
xml 表示以 XML 格式输出

您需要使用某些参数，才能发起地点自动补全请求。根据网址的标准，所有参数均使用“&”符号分隔 (&) 个字符。参数列表及其可能的下面枚举了值。

Required parameters

input
The text string on which to search. The Place Autocomplete service will return candidate matches based on this string and order results based on their perceived relevance.

Optional parameters

components
A grouping of places to which you would like to restrict your results. Currently, you can use components to filter by up to 5 countries. Countries must be passed as a two character, ISO 3166-1 Alpha-2 compatible country code. For example: components=country:fr would restrict your results to places within France. Multiple countries must be passed as multiple country:XX filters, with the pipe character | as a separator. For example: components=country:us|country:pr|country:vi|country:gu|country:mp would restrict your results to places within the United States and its unincorporated organized territories.
Note: If you receive unexpected results with a country code, verify that you are using a code which includes the countries, dependent territories, and special areas of geographical interest you intend. You can find code information at Wikipedia: List of ISO 3166 country codes or the ISO Online Browsing Platform.
language
The language in which to return results.
- See the list of supported languages. Google often updates the supported languages, so this list may not be exhaustive.
- If language is not supplied, the API attempts to use the preferred language as specified in the Accept-Language header.
- The API does its best to provide a street address that is readable for both the user and locals. To achieve that goal, it returns street addresses in the local language, transliterated to a script readable by the user if necessary, observing the preferred language. All other addresses are returned in the preferred language. Address components are all returned in the same language, which is chosen from the first component.
- If a name is not available in the preferred language, the API uses the closest match.
- The preferred language has a small influence on the set of results that the API chooses to return, and the order in which they are returned. The geocoder interprets abbreviations differently depending on language, such as the abbreviations for street types, or synonyms that may be valid in one language but not in another. For example, utca and tér are synonyms for street in Hungarian.
location
The point around which to retrieve place information. This must be specified as latitude,longitude. The radius parameter must also be provided when specifying a location. If radius is not provided, the location parameter is ignored.
When using the Text Search API, the `location` parameter may be overriden if the `query` contains an explicit location such as `Market in Barcelona`.
locationbias
Prefer results in a specified area, by specifying either a radius plus lat/lng, or two lat/lng pairs representing the points of a rectangle. If this parameter is not specified, the API uses IP address biasing by default.
- IP bias: Instructs the API to use IP address biasing. Pass the string ipbias (this option has no additional parameters).
- Circular: A string specifying radius in meters, plus lat/lng in decimal degrees. Use the following format: circle:radius@lat,lng.
- Rectangular: A string specifying two lat/lng pairs in decimal degrees, representing the south/west and north/east points of a rectangle. Use the following format:rectangle:south,west|north,east. Note that east/west values are wrapped to the range -180, 180, and north/south values are clamped to the range -90, 90.
locationrestriction
Restrict results to a specified area, by specifying either a radius plus lat/lng, or two lat/lng pairs representing the points of a rectangle.
- Circular: A string specifying radius in meters, plus lat/lng in decimal degrees. Use the following format: circle:radius@lat,lng.
- Rectangular: A string specifying two lat/lng pairs in decimal degrees, representing the south/west and north/east points of a rectangle. Use the following format:rectangle:south,west|north,east. Note that east/west values are wrapped to the range -180, 180, and north/south values are clamped to the range -90, 90.
offset
The position, in the input term, of the last character that the service uses to match predictions. For example, if the input is Google and the offset is 3, the service will match on Goo. The string determined by the offset is matched against the first word in the input term only. For example, if the input term is Google abc and the offset is 3, the service will attempt to match against Goo abc. If no offset is supplied, the service will use the whole term. The offset should generally be set to the position of the text caret.
origin
The origin point from which to calculate straight-line distance to the destination (returned as distance_meters). If this value is omitted, straight-line distance will not be returned. Must be specified as latitude,longitude.
radius
Defines the distance (in meters) within which to return place results. You may bias results to a specified circle by passing a location and a radius parameter. Doing so instructs the Places service to prefer showing results within that circle; results outside of the defined area may still be displayed.
The radius will automatically be clamped to a maximum value depending on the type of search and other parameters.
- Autocomplete: 50,000 meters
- Nearby Search:
  - with keyword or name: 50,000 meters
  - without keyword or name
    - Up to 50,000 meters, adjusted dynamically based on area density, independent of rankby parameter.
    - When using rankby=distance, the radius parameter will not be accepted, and will result in an INVALID_REQUEST.
- Query Autocomplete: 50,000 meters
- Text Search: 50,000 meters
region
The region code, specified as a ccTLD ("top-level domain") two-character value. Most ccTLD codes are identical to ISO 3166-1 codes, with some notable exceptions. For example, the United Kingdom's ccTLD is "uk" (.co.uk) while its ISO 3166-1 code is "gb" (technically for the entity of "The United Kingdom of Great Britain and Northern Ireland").
sessiontoken
A random string which identifies an autocomplete session for billing purposes.
The session begins when the user starts typing a query, and concludes when they select a place and a call to Place Details is made. Each session can have multiple queries, followed by one place selection. The API key(s) used for each request within a session must belong to the same Google Cloud Console project. Once a session has concluded, the token is no longer valid; your app must generate a fresh token for each session. If the sessiontoken parameter is omitted, or if you reuse a session token, the session is charged as if no session token was provided (each request is billed separately).
We recommend the following guidelines:
- Use session tokens for all autocomplete sessions.
- Generate a fresh token for each session. Using a version 4 UUID is recommended.
- Ensure that the API key(s) used for all Place Autocomplete and Place Details requests within a session belong to the same Cloud Console project.
- Be sure to pass a unique session token for each new session. Using the same token for more than one session will result in each request being billed individually.
strictbounds
Returns only those places that are strictly within the region defined by location and radius. This is a restriction, rather than a bias, meaning that results outside this region will not be returned even if they match the user input.
types
You can restrict results from a Place Autocomplete request to be of a certain type by passing the types parameter. This parameter specifies a type or a type collection, as listed in Place Types. If nothing is specified, all types are returned.
A place can only have a single primary type from types listed in Table 1 or Table 2. For example, a hotel where food is served may by returned only with types=lodging and not with types=restaurant.
For the value of the types parameter you can specify either:
- Up to five values from Table 1 or Table 2. For multiple values, separate each value with a | (vertical bar). For example:
  types=book_store|cafe
- Any single supported filter in Table 3. You cannot mix type collections.
Note: Although geocode and establishment are part of Table 2, they cannot be combined with any other type in Tables 1, 2, or 3 in Place Autocomplete request filters.
The request will be rejected with an INVALID_REQUEST error if:
- More than five types are specified.
- Any unrecognized types are present.
- Any types from in Table 1 or Table 2 are mixed with any of the filters in Table 3.
Note: The types parameter only works on the primary type of the place, not all types associated with the place. Although every place has a primary type, not every primary type is supported by Places API (New). Supported types include those listed in Table 1 or Table 2.

地点自动补全示例

对包含字符串“Amoeba”的场所的请求范围内以加利福尼亚州旧金山为中心的区域：

网址

https://maps.googleapis.com/maps/api/place/autocomplete/json
  ?input=amoeba
  &location=37.76999%2C-122.44696
  &radius=500
  &types=establishment
  &key=YOUR_API_KEY

cURL

curl -L -X GET 'https://maps.googleapis.com/maps/api/place/autocomplete/json?input=amoeba&types=establishment&location=37.76999%2C-122.44696&radius=500&key=YOUR_API_KEY'

同一个请求，只搜索位于阿什伯里街 500 米以内的结果，海特街旧金山：

网址

https://maps.googleapis.com/maps/api/place/autocomplete/json
  ?input=amoeba
  &location=37.76999%2C-122.44696
  &radius=500
  &strictbounds=true
  &types=establishment
  &key=YOUR_API_KEY

cURL

curl -L -X GET 'https://maps.googleapis.com/maps/api/place/autocomplete/json?input=amoeba&types=establishment&location=37.76999%2C-122.44696&radius=500&strictbounds=true&key=YOUR_API_KEY'

以下示例请求包含“Vict”的地址，并以法语显示结果：

网址

https://maps.googleapis.com/maps/api/place/autocomplete/json
  ?input=Vict
  &language=fr
  &types=geocode
  &key=YOUR_API_KEY

cURL

curl -L -X GET 'https://maps.googleapis.com/maps/api/place/autocomplete/json?input=Vict&types=geocode&language=fr&key=YOUR_API_KEY'

针对包含“Vict”的城市的请求有巴西葡萄牙语结果：

网址

https://maps.googleapis.com/maps/api/place/autocomplete/json
  ?input=Vict
  &language=pt_BR
  &types=%28cities%29
  &key=YOUR_API_KEY

cURL

curl -L -X GET 'https://maps.googleapis.com/maps/api/place/autocomplete/json?input=Vict&types=(cities)&language=pt_BR&key=YOUR_API_KEY'

请注意，您需要将 API 密钥使用您自己的密钥。

地点自动补全响应

地点自动补全响应以请求的网址路径中的 output 标志。结果如下：指示针对以下查询可能返回的内容参数：

网址

https://maps.googleapis.com/maps/api/place/autocomplete/json
  ?input=Paris
  &types=geocode
  &key=YOUR_API_KEY

cURL

curl -L -X GET 'https://maps.googleapis.com/maps/api/place/autocomplete/json?input=Paris&types=geocode&key=YOUR_API_KEY'

JSON

{
  "predictions":
    [
      {
        "description": "Paris, France",
        "matched_substrings": [{ "length": 5, "offset": 0 }],
        "place_id": "ChIJD7fiBh9u5kcRYJSMaMOCCwQ",
        "reference": "ChIJD7fiBh9u5kcRYJSMaMOCCwQ",
        "structured_formatting":
          {
            "main_text": "Paris",
            "main_text_matched_substrings": [{ "length": 5, "offset": 0 }],
            "secondary_text": "France",
          },
        "terms":
          [
            { "offset": 0, "value": "Paris" },
            { "offset": 7, "value": "France" },
          ],
        "types": ["locality", "political", "geocode"],
      },
      {
        "description": "Paris, TX, USA",
        "matched_substrings": [{ "length": 5, "offset": 0 }],
        "place_id": "ChIJmysnFgZYSoYRSfPTL2YJuck",
        "reference": "ChIJmysnFgZYSoYRSfPTL2YJuck",
        "structured_formatting":
          {
            "main_text": "Paris",
            "main_text_matched_substrings": [{ "length": 5, "offset": 0 }],
            "secondary_text": "TX, USA",
          },
        "terms":
          [
            { "offset": 0, "value": "Paris" },
            { "offset": 7, "value": "TX" },
            { "offset": 11, "value": "USA" },
          ],
        "types": ["locality", "political", "geocode"],
      },
      {
        "description": "Paris, TN, USA",
        "matched_substrings": [{ "length": 5, "offset": 0 }],
        "place_id": "ChIJ4zHP-Sije4gRBDEsVxunOWg",
        "reference": "ChIJ4zHP-Sije4gRBDEsVxunOWg",
        "structured_formatting":
          {
            "main_text": "Paris",
            "main_text_matched_substrings": [{ "length": 5, "offset": 0 }],
            "secondary_text": "TN, USA",
          },
        "terms":
          [
            { "offset": 0, "value": "Paris" },
            { "offset": 7, "value": "TN" },
            { "offset": 11, "value": "USA" },
          ],
        "types": ["locality", "political", "geocode"],
      },
      {
        "description": "Paris, Brant, ON, Canada",
        "matched_substrings": [{ "length": 5, "offset": 0 }],
        "place_id": "ChIJsamfQbVtLIgR-X18G75Hyi0",
        "reference": "ChIJsamfQbVtLIgR-X18G75Hyi0",
        "structured_formatting":
          {
            "main_text": "Paris",
            "main_text_matched_substrings": [{ "length": 5, "offset": 0 }],
            "secondary_text": "Brant, ON, Canada",
          },
        "terms":
          [
            { "offset": 0, "value": "Paris" },
            { "offset": 7, "value": "Brant" },
            { "offset": 14, "value": "ON" },
            { "offset": 18, "value": "Canada" },
          ],
        "types": ["neighborhood", "political", "geocode"],
      },
      {
        "description": "Paris, KY, USA",
        "matched_substrings": [{ "length": 5, "offset": 0 }],
        "place_id": "ChIJsU7_xMfKQ4gReI89RJn0-RQ",
        "reference": "ChIJsU7_xMfKQ4gReI89RJn0-RQ",
        "structured_formatting":
          {
            "main_text": "Paris",
            "main_text_matched_substrings": [{ "length": 5, "offset": 0 }],
            "secondary_text": "KY, USA",
          },
        "terms":
          [
            { "offset": 0, "value": "Paris" },
            { "offset": 7, "value": "KY" },
            { "offset": 11, "value": "USA" },
          ],
        "types": ["locality", "political", "geocode"],
      },
    ],
  "status": "OK",
}

XML

<AutocompletionResponse>
 <status>OK</status>
 <prediction>
  <description>Paris, France</description>
  <type>locality</type>
  <type>political</type>
  <type>geocode</type>
  <reference>ChIJD7fiBh9u5kcRYJSMaMOCCwQ</reference>
  <term>
   <value>Paris</value>
   <offset>0</offset>
  </term>
  <term>
   <value>France</value>
   <offset>7</offset>
  </term>
  <matched_substring>
   <offset>0</offset>
   <length>5</length>
  </matched_substring>
  <place_id>ChIJD7fiBh9u5kcRYJSMaMOCCwQ</place_id>
  <structured_formatting>
   <description>Paris</description>
   <subdescription>France</subdescription>
   <description_matched_substring>
    <offset>0</offset>
    <length>5</length>
   </description_matched_substring>
  </structured_formatting>
 </prediction>
 <prediction>
  <description>Paris, TX, USA</description>
  <type>locality</type>
  <type>political</type>
  <type>geocode</type>
  <reference>ChIJmysnFgZYSoYRSfPTL2YJuck</reference>
  <term>
   <value>Paris</value>
   <offset>0</offset>
  </term>
  <term>
   <value>TX</value>
   <offset>7</offset>
  </term>
  <term>
   <value>USA</value>
   <offset>11</offset>
  </term>
  <matched_substring>
   <offset>0</offset>
   <length>5</length>
  </matched_substring>
  <place_id>ChIJmysnFgZYSoYRSfPTL2YJuck</place_id>
  <structured_formatting>
   <description>Paris</description>
   <subdescription>TX, USA</subdescription>
   <description_matched_substring>
    <offset>0</offset>
    <length>5</length>
   </description_matched_substring>
  </structured_formatting>
 </prediction>
 <prediction>
  <description>Paris, TN, USA</description>
  <type>locality</type>
  <type>political</type>
  <type>geocode</type>
  <reference>ChIJ4zHP-Sije4gRBDEsVxunOWg</reference>
  <term>
   <value>Paris</value>
   <offset>0</offset>
  </term>
  <term>
   <value>TN</value>
   <offset>7</offset>
  </term>
  <term>
   <value>USA</value>
   <offset>11</offset>
  </term>
  <matched_substring>
   <offset>0</offset>
   <length>5</length>
  </matched_substring>
  <place_id>ChIJ4zHP-Sije4gRBDEsVxunOWg</place_id>
  <structured_formatting>
   <description>Paris</description>
   <subdescription>TN, USA</subdescription>
   <description_matched_substring>
    <offset>0</offset>
    <length>5</length>
   </description_matched_substring>
  </structured_formatting>
 </prediction>
 <prediction>
  <description>Paris, Brant, ON, Canada</description>
  <type>neighborhood</type>
  <type>political</type>
  <type>geocode</type>
  <reference>ChIJsamfQbVtLIgR-X18G75Hyi0</reference>
  <term>
   <value>Paris</value>
   <offset>0</offset>
  </term>
  <term>
   <value>Brant</value>
   <offset>7</offset>
  </term>
  <term>
   <value>ON</value>
   <offset>14</offset>
  </term>
  <term>
   <value>Canada</value>
   <offset>18</offset>
  </term>
  <matched_substring>
   <offset>0</offset>
   <length>5</length>
  </matched_substring>
  <place_id>ChIJsamfQbVtLIgR-X18G75Hyi0</place_id>
  <structured_formatting>
   <description>Paris</description>
   <subdescription>Brant, ON, Canada</subdescription>
   <description_matched_substring>
    <offset>0</offset>
    <length>5</length>
   </description_matched_substring>
  </structured_formatting>
 </prediction>
 <prediction>
  <description>Paris, KY, USA</description>
  <type>locality</type>
  <type>political</type>
  <type>geocode</type>
  <reference>ChIJsU7_xMfKQ4gReI89RJn0-RQ</reference>
  <term>
   <value>Paris</value>
   <offset>0</offset>
  </term>
  <term>
   <value>KY</value>
   <offset>7</offset>
  </term>
  <term>
   <value>USA</value>
   <offset>11</offset>
  </term>
  <matched_substring>
   <offset>0</offset>
   <length>5</length>
  </matched_substring>
  <place_id>ChIJsU7_xMfKQ4gReI89RJn0-RQ</place_id>
  <structured_formatting>
   <description>Paris</description>
   <subdescription>KY, USA</subdescription>
   <description_matched_substring>
    <offset>0</offset>
    <length>5</length>
   </description_matched_substring>
  </structured_formatting>
 </prediction>
</AutocompletionResponse>

PlacesAutocompleteResponse

Field	Required	Type	Description
`predictions`	required	Array<PlaceAutocompletePrediction>	Contains an array of predictions. See PlaceAutocompletePrediction for more information.
`status`	required	PlacesAutocompleteStatus	Contains the status of the request, and may contain debugging information to help you track down why the request failed. See PlacesAutocompleteStatus for more information.
`error_message`	optional	string	When the service returns a status code other than `OK<`, there may be an additional `error_message` field within the response object. This field contains more detailed information about thereasons behind the given status code. This field is not always returned, and its content is subject to change.
`info_messages`	optional	Array<string>	When the service returns additional information about the request specification, there may be an additional `info_messages` field within the response object. This field is only returned for successful requests. It may not always be returned, and its content is subject to change.

这些结果中尤其值得关注的是 place_id 元素，可用于请求获取关于查询地点。请参阅地点详情请求。

XML 响应包含单个具有两种类型的子项的 <AutocompletionResponse> 元素元素：

单个 <status> 元素包含请求。请参阅状态代码。
零个或更多个 <prediction> 元素，每个元素均包含有关单个地点的信息。请参阅地点自动补全结果：这些结果的相关信息。Places API 会返回最多 5 条结果。

我们建议您使用 json 作为首选输出标志除非您的应用出于某些原因需要 xml。处理 XML 树时要小心，以便引用正确的节点和元素请参阅处理 XML with XPath，以帮助您处理 XML。

在某些自动补全预测结果中，地点 ID 的“地点详情”响应中可能不包含 street_number 地址组件。通常，在无法针对某一地点插入地址时会出现这种情况。在这种情况下，预测结果的 types 数组将包含“路线”。对于在说明中包含数字的自动补全预测结果（输入查询匹配时，则地点 ID 的“地点详情”响应包含仅当预测结果的 types 数组包含至少以下其中一项： <ph type="x-smartling-placeholder">

street_address
premise
establishment

PlacesAutocompleteStatus

Status codes returned by service.

OK indicating the API request was successful.
ZERO_RESULTS indicating that the search was successful but returned no results. This may occur if the search was passed a bounds in a remote location.
INVALID_REQUEST indicating the API request was malformed, generally due to the missing input parameter.
OVER_QUERY_LIMIT indicating any of the following:
- You have exceeded the QPS limits.
- Billing has not been enabled on your account.
- The monthly $200 credit, or a self-imposed usage cap, has been exceeded.
- The provided method of payment is no longer valid (for example, a credit card has expired).
See the Maps FAQ for more information about how to resolve this error.
REQUEST_DENIED indicating that your request was denied, generally because:
- The request is missing an API key.
- The key parameter is invalid.
UNKNOWN_ERROR indicating an unknown error.

当地点服务返回搜索所获得的 JSON 结果时，会将这些结果放置放在 predictions 数组中。即使服务返回没有结果（例如，如果 location 是远程执行的）仍然会返回一个空的 predictions 数组。XML 响应包含零个或零个以上的 <prediction> 元素。

PlaceAutocompletePrediction

Field	Required	Type	Description
`description`	required	string	Contains the human-readable name for the returned result. For `establishment` results, this is usually the business name. This content is meant to be read as-is. Do not programmatically parse the formatted address.
`matched_substrings`	required	Array<PlaceAutocompleteMatchedSubstring>	A list of substrings that describe the location of the entered term in the prediction result text, so that the term can be highlighted if desired. See PlaceAutocompleteMatchedSubstring for more information.
`structured_formatting`	required	PlaceAutocompleteStructuredFormat	Provides pre-formatted text that can be shown in your autocomplete results. This content is meant to be read as-is. Do not programmatically parse the formatted address. See PlaceAutocompleteStructuredFormat for more information.
`terms`	required	Array<PlaceAutocompleteTerm>	Contains an array of terms identifying each section of the returned description (a section of the description is generally terminated with a comma). Each entry in the array has a `value` field, containing the text of the term, and an `offset` field, defining the start position of this term in the description, measured in Unicode characters. See PlaceAutocompleteTerm for more information.
`distance_meters`	optional	integer	The straight-line distance in meters from the origin. This field is only returned for requests made with an `origin`.
`place_id`	optional	string	A textual identifier that uniquely identifies a place. To retrieve information about the place, pass this identifier in the placeId field of a Places API request. For more information about place IDs, see the Place IDs overview.
`reference`	optional	string	`reference` is deprecated. See place_id.
`types`	optional	Array<string>	Contains an array of types that apply to this place. For example: `[ "political", "locality" ]` or `[ "establishment", "geocode", "beauty_salon" ]`. The array can contain multiple values. Learn more about Place types.

PlaceAutocompleteMatchedSubstring

Field	Required	Type	Description
`length`	required	number	Length of the matched substring in the prediction result text.
`offset`	required	number	Start location of the matched substring in the prediction result text.

PlaceAutocompleteStructuredFormat

Field	Required	Type	Description
`main_text`	required	string	Contains the main text of a prediction, usually the name of the place.
`main_text_matched_substrings`	required	Array<PlaceAutocompleteMatchedSubstring>	Contains an array with `offset` value and `length`. These describe the location of the entered term in the prediction result text, so that the term can be highlighted if desired. See PlaceAutocompleteMatchedSubstring for more information.
`secondary_text`	optional	string	Contains the secondary text of a prediction, usually the location of the place.
`secondary_text_matched_substrings`	optional	Array<PlaceAutocompleteMatchedSubstring>	Contains an array with `offset` value and `length`. These describe the location of the entered term in the prediction result text, so that the term can be highlighted if desired. See PlaceAutocompleteMatchedSubstring for more information.

PlaceAutocompleteTerm

Field	Required	Type	Description
`offset`	required	number	Defines the start position of this term in the description, measured in Unicode characters
`value`	required	string	The text of the term.

地点自动补全优化

本部分介绍了帮助您充分利用地点自动补全服务的最佳实践。

下面列出了一些一般准则：

若要开发可正常运行的界面，最快的方式是使用 Maps JavaScript API Autocomplete widget、Places SDK for Android Autocomplete widget 或 Places SDK for iOS Autocomplete 界面控件。
从一开始就了解重要的地点自动补全数据字段。
位置自定义调整和位置限制字段是可选的，但可能会对自动补全性能产生重大影响。
使用错误处理可确保您的应用在 API 返回错误时妥善降级。
请确保您的应用可以处理没有选择任何内容的情况，并能够让用户继续操作。

费用优化最佳实践

基本费用优化

为了优化地点自动补全服务的使用费用，请在地点详情和地点自动补全 widget 中使用字段掩码，以便仅返回所需的地点数据字段。

高级费用优化

请考虑通过程序化方式实现地点自动补全，以便采用“按请求”定价模式，并请求关于所选地点（而不是地点详情）的 Geocoding API 结果。如果同时满足以下两个条件，与采用“按会话”（基于会话）定价模式相比，将“按请求”定价模式与 Geocoding API 搭配使用的性价比更高：

如果您只需要用户所选地点的纬度/经度或地址，那么采用 Geocoding API 提供此类信息所需的费用会低于调用地点详情。
如果用户平均在不超过四次自动补全预测请求之内选择自动补全预测结果，那么“按请求”定价模式可能会比“按会话”定价模式的性价比更高。

如果在选择符合您需求的地点自动补全实现方面需要帮助，请选择与以下问题的答案相对应的标签页。

除了所选预测结果的地址和纬度/经度外，您的应用是否需要任何其他信息？

是，需要更多详细信息

将基于会话的地点自动补全与地点详情搭配使用。
由于您的应用需要地点名称、商家状态或营业时间等地点详情，因此您的地点自动补全实现应使用会话令牌（以程序化方式构建，或内置到 JavaScript、Android 或 iOS widget 中），总费用为每次会话 0.017 美元，外加相应的地点数据 SKU 费用（具体取决于您申请的地点数据字段）。¹

widget 实现
会话管理功能自动内置于 JavaScript、Android 或 iOS widget 中。这包括针对所选预测结果的“地点自动补全”请求和“地点详情”请求。请务必指定 fields 参数，以确保您只请求所需的地点数据字段。

程序化实现
在“地点自动补全”请求中使用会话令牌。在请求关于所选预测结果的地点详情时，添加以下参数：

“地点自动补全”响应中的地点 ID
“地点自动补全”请求中使用的会话令牌
fields 参数，用于指定您所需的地点数据字段

否，只需要地址和位置信息

对于您的应用，Geocoding API 可能比地点详情性价比更高，具体取决于您使用地点自动补全的性能。每个应用的自动补全效率各有不同，具体取决于用户输入的内容、使用应用所在的位置，以及是否遵循了性能优化最佳实践。

为了回答以下问题，请分析用户在您的应用中选择地点自动补全预测结果之前平均会输入多少个字符。

平均而言，用户是否能够在不超过四次请求之内选择地点自动补全预测结果？

是

在不使用会话令牌的情况下以程序化方式实现地点自动补全，并针对所选的地点预测调用 Geocoding API。
Geocoding API 提供地址和纬度/经度坐标，价格为每个请求 0.005 美元。发出四次地点自动补全 - 按请求结算请求的费用为 0.01132 美元，因此四次请求加上针对所选地点预测调用 Geocoding API 的总费用将为 0.01632 美元，低于按会话结算的自动补全价格（即每次会话 0.017 美元）。¹

您可以考虑采用性能最佳实践，帮助用户以更少的字符找到所需的预测结果。

否

将基于会话的地点自动补全与地点详情搭配使用。
由于您预计在用户选择地点自动补全预测结果之前应用发出的平均请求次数较多，所需费用会超过“按会话”定价模式的费用，因此建议您在实现地点自动补全时，针对“地点自动补全”请求和关联的“地点详情”请求使用会话令牌，总费用为每次会话 0.017 美元。¹

widget 实现
会话管理功能自动内置于 JavaScript、Android 或 iOS widget 中。这包括针对所选预测结果的“地点自动补全”请求和“地点详情”请求。请务必指定 fields 参数，以确保您只请求基本数据字段。

程序化实现
在“地点自动补全”请求中使用会话令牌。在请求关于所选预测结果的地点详情时，添加以下参数：

“地点自动补全”响应中的地点 ID
“地点自动补全”请求中使用的会话令牌
fields 参数，用于指定地址和几何图形等基本数据字段

考虑延迟“地点自动补全”请求
您可以采取一些策略，例如延迟“地点自动补全”请求，直到用户输入前三个或四个字符，从而减少应用发出的请求数量。例如，在用户输入第三个字符后针对每个字符发出“地点自动补全”请求，也就是说，如果用户输入七个字符，然后选择了您发出一次 Geocoding API 请求所获得的预测结果，总费用将为：0.01632 美元（4 * 0.00283 美元 [自动补全 - 按请求结算] + 0.005 美元 [地理编码]）。¹

如果延迟请求会导致平均程序化请求次数低于四次，您可以按照使用 Geocoding API 提高地点自动补全性能的实现指南操作。请注意，如果用户希望每次输入新的字符后都能看到预测结果，可能会将延迟请求视为时间上的延迟。

您可以考虑采用性能最佳实践，帮助用户以较少的字符找到所需的预测结果。

此处所列的费用以美元为单位。如需了解完整的定价信息，请参阅 Google Maps Platform 结算页面。

性能最佳实践

下面的指南介绍了优化地点自动补全性能的方式：

向地点自动补全实现添加国家/地区限制、位置自定义调整和语言偏好设置（适用于程序化实现）。您无需为 widget 进行语言偏好设置，因为它们会从用户的浏览器或移动设备中选择语言偏好设置。
如果地点自动补全附有地图，您可以根据地图视口来设置位置偏向。
如果用户未选择任一自动补全预测结果，通常是因为这些预测结果都不是所需的结果地址，您可以重复使用原始用户输入来尝试获取更相关的结果：
- 如果您希望用户仅输入地址信息，请在调用 Geocoding API 时重复使用原始用户输入。
- 如果您希望用户按名称或地址查询某个地点，请使用“查找地点”请求。如果希望仅显示特定区域内的结果，请使用位置自定义调整。
适合回退到 Geocoding API 的其他场景包括：
- 用户在针对 subpremise 地址的地点自动补全支持不完整的国家/地区（例如捷克、爱沙尼亚和立陶宛）输入 subpremise 地址。例如，捷克地址“Stroupežnického 3191/17, Praha”会在地点自动补全中生成部分预测结果。
- 用户在输入地址时，需要输入路段前缀，例如纽约的“23-30 29th St, Queens”或夏威夷考爱岛“47-380 Kamehameha Hwy, Kaneohe”。

位置自定义调整

通过传递 location 参数和 radius，使结果偏向于指定区域参数。这会指示地点自动补全服务优先显示结果在指定区域内指定区域之外的搜索结果可能仍存在。您可以使用 components 参数过滤结果仅显示指定国家/地区内的那些地点。

</ph> 警告：如果未提供 radius，系统会忽略 location 参数。

提示：场所结果通常排名不高，以便在搜索区域较大时显示在搜索结果中。如果您想要在场所/地理编码结果的混合结果中显示场所，您可以指定较小的半径。或者，您也可以使用 types=establishment 用于将结果限定为仅显示场所。

位置限制

通过传递 locationrestriction 参数，将结果限制在指定区域。

您还可以将结果限制为 location 定义的区域和 radius 参数，方法是添加 strictbounds 参数。此参数用于指示地点自动补全服务仅返回结果。

地点自动补全

“地点自动补全”请求

Required parameters

input

Optional parameters

components

language

location

locationbias

locationrestriction

offset

origin

radius

region

sessiontoken

strictbounds

types

地点自动补全示例

网址

cURL

网址

cURL

网址

cURL

网址

cURL

地点自动补全响应

网址

cURL

JSON

XML

PlacesAutocompleteResponse

predictions

status

error_message

info_messages

PlacesAutocompleteStatus

PlaceAutocompletePrediction

description

matched_substrings

structured_formatting

terms

distance_meters

place_id

reference

types

PlaceAutocompleteMatchedSubstring

length

offset

PlaceAutocompleteStructuredFormat

main_text

main_text_matched_substrings

secondary_text

secondary_text_matched_substrings

PlaceAutocompleteTerm

offset

value

地点自动补全优化

费用优化最佳实践

基本费用优化

高级费用优化

是，需要更多详细信息

否，只需要地址和位置信息

是

否

性能最佳实践

位置自定义调整

位置限制

`predictions`

`status`

`error_message`

`info_messages`

`description`

`matched_substrings`

`structured_formatting`

`terms`

`distance_meters`

`place_id`

`reference`

`types`

`length`

`offset`

`main_text`

`main_text_matched_substrings`

`secondary_text`

`secondary_text_matched_substrings`

`offset`

`value`