此产品或功能处于旧版状态。如需详细了解“旧版”状态,请参阅
旧版产品和功能。如需迁移到 Places API(新版),请参阅
迁移指南。
地点搜索
使用集合让一切井井有条
根据您的偏好保存内容并对其进行分类。
借助 Places API,您可以使用各种类别(包括场所、著名地图注点和地理位置)搜索地点信息。您可以按距离或文本字符串搜索地点。地点搜索会返回地点列表以及每个地点的摘要信息;您可以使用地点详情(旧版)查询获取更多信息。
比较搜索类型
有三种搜索端点可供选择,各有不同特点。下表着重说明了其中的一些差异。
字段选择
您无法将“附近搜索”(旧版)或“文本搜索”(旧版)限制为仅返回特定字段。为避免请求不需要的数据并为之付费,请改用“查找地点(旧版)”请求。
模糊不清的文本
“查找地点(旧版)”和“文本搜索(旧版)”针对在多个字段中匹配模糊文本进行了优化,而“附近搜索(旧版)”则仅限于在部分字段中进行严格匹配。
其他过滤条件
“附近搜索(旧版)”和“文本搜索(旧版)”允许使用其他参数来过滤结果(例如 minprice
、maxprice
、opennow
和 type
)。
如未另行说明,那么本页面中的内容已根据知识共享署名 4.0 许可获得了许可,并且代码示例已根据 Apache 2.0 许可获得了许可。有关详情,请参阅 Google 开发者网站政策。Java 是 Oracle 和/或其关联公司的注册商标。
最后更新时间 (UTC):2025-08-31。
[null,null,["最后更新时间 (UTC):2025-08-31。"],[],[],null,["# Place Search\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**Note: Server-side\nand client-side libraries**\n\nThe Places API is also available with the\n[Java Client,\nPython Client, Go Client and Node.js Client for Google Maps Services](/maps/documentation/places/web-service/client-library).\nThe Places API and the client libraries are for\nuse in server applications.\n\nIf you're building a client-side\napplication, take a look at the\n[Places SDK for Android (New)](/maps/documentation/places/android-sdk), the\n[Places SDK for iOS (New)](/maps/documentation/places/ios-sdk), and the\n[Places Library, Maps JavaScript API](/maps/documentation/javascript/places).\n\nThe Places API lets you search for place information\nusing a variety of categories, including establishments, prominent points of\ninterest, and geographic locations. You can search for places either by\nproximity or a text string. A Place Search returns a list of places along with\nsummary information about each place; additional information is available using\na [Place Details (Legacy)](/maps/documentation/places/web-service/details) query.\n\nCompare search types\n--------------------\n\nThere are three search endpoints available with different characteristics. The following table\nhighlights some of these differences.\n\n| Type | [Field selection](#field-selection) | Text Search (Legacy) | [Ambiguous text](#ambiguous-text) | Location filter | [Additional filters](#additional-filters) |\n|----------------------------------------------------------------------------------------|-------------------------------------|----------------------|-----------------------------------|-----------------|-------------------------------------------|\n| [Find Place (Legacy)](/maps/documentation/places/web-service/legacy/search-find-place) | | `input` | | | |\n| [Nearby Search (Legacy)](/maps/documentation/places/web-service/legacy/search-nearby) | | `keyword` | | | |\n| [Text Search (Legacy)](/maps/documentation/places/web-service/legacy/search-text) | | `query` | | | |\n\n### Field selection\n\nThere is no way to constrain Nearby Search (Legacy) or Text Search (Legacy) to only return specific fields. To\nkeep from requesting (and paying for) data that you don't need, use a Find Place (Legacy) request instead.\n\n### Ambiguous text\n\nFind Place (Legacy) and Text Search (Legacy) are optimized for matching ambiguous text across a number of fields\nwhile Nearby Search (Legacy) is constrained to strict matches on a subset of fields.\n\n### Additional filters\n\nNearby Search (Legacy) and Text Search (Legacy) allow additional parameters to filter results,\n(e.g. `minprice`, `maxprice`, `opennow`, and `type`)."]]