這項產品或功能為舊版。如要進一步瞭解舊版狀態，請參閱「
舊版產品和功能」。如要改用 Places API (新版)，請參閱
遷移指南。
Place Search
透過集合功能整理內容
你可以依據偏好儲存及分類內容。
Places API 可讓您使用各種類別搜尋地點資訊，包括建築物、重要搜尋點和地理位置。您可以依據鄰近性或文字字串搜尋地點。Place Search 會傳回地點清單，以及每個地點的摘要資訊；您可以使用 Place Details (Legacy) 查詢取得其他資訊。
比較搜尋類型
有三個搜尋端點可供使用，各自具有不同的特性。下表重點列出其中一些差異。
欄位選取
您無法限制「搜尋附近」(舊版) 或「搜尋文字」(舊版) 只傳回特定欄位。為避免要求並支付不需要的資料，請改用 Find Place (舊版) 要求。
含糊不清的文字
Find Place (舊版) 和 Text Search (舊版) 已針對在多個欄位中比對含糊不清的文字進行最佳化調整，而 Nearby Search (舊版) 則會限制在部分欄位上進行嚴格比對。
其他篩選條件
Nearby Search (舊版) 和 Text Search (舊版) 允許使用額外參數篩選結果 (例如 minprice、maxprice、opennow 和 type)。
除非另有註明，否則本頁面中的內容是採用創用 CC 姓名標示 4.0 授權，程式碼範例則為阿帕契 2.0 授權。詳情請參閱《Google Developers 網站政策》。Java 是 Oracle 和/或其關聯企業的註冊商標。
上次更新時間：2025-08-31 (世界標準時間)。
[null,null,["上次更新時間：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`)."]]
