適用於歐洲經濟區 (EEA) 客戶的 Solar API 調整
透過集合功能整理內容
你可以依據偏好儲存及分類內容。
Google 地圖平台歐洲經濟區整合指南
自 2025 年 7 月 8 日起,如果您的專案已連結至歐洲經濟區帳單帳戶,則新的歐洲經濟區專屬《Google 地圖平台服務條款》(歐洲經濟區條款)將影響您為使用者建構應用程式和體驗的方式。
我們強烈建議您詳閱這則公告,因為其中的細節可能會影響您現有和新整合 Google 地圖平台的應用程式。
本文件說明 Solar API 的使用情形和 Google 地圖平台功能異動。
本文件所述資訊反映自 2025 年 7 月 8 日起,適用於您使用 Google 地圖平台服務的歐洲經濟區條款,這些條款可能隨時間變更。如需查看適用於您且具法律約束力的最新條款,請參閱與 Google 簽訂的 Google 地圖平台協議。
歐洲經濟區客戶的 Solar API 調整
這些調整適用於 (a) 2025 年 7 月 8 日後建立的專案,且已連結至具備歐洲經濟區帳單地址的帳戶,和/或 (b) 2025 年 7 月 8 日後不再處於「未修改狀態」的專案。
下表列出各項 Google 地圖平台服務的調整內容,詳情請參閱《歐洲經濟區服務專屬條款》。
Solar API 功能調整 |
服務條款異動 |
建築洞察資料中的下列欄位無法使用:
postalCode
administrativeArea
regionCode
|
無
|
替代整合
受影響的地址欄位對太陽能資格和太陽能板陣列設計用途而言並非必要,因此建議您考慮在沒有該內容的情況下繼續操作應用程式。
如果該內容對應用程式運作至關重要,BuildingInsights
方法也會在名稱欄位中傳回 Place ID,可將其傳遞至 Places UI Kit 以取得 Place 的詳細資料。如需歐洲經濟區使用 Places 內容的相關指南,請參閱「適用於歐洲經濟區 (EEA) 客戶的 Places API 調整」。
如果我有這份文件未涵蓋的其他問題,該怎麼辦?
如果您有任何技術問題,而這份文件或常見問題未提供解答,請與 Google 地圖平台支援團隊聯絡。
如果您與 Google 達成協議,並對合約有疑問,可以與 Google 地圖平台代表聯絡。如果不確定自己的客戶經理是誰,請填寫「與銷售人員聯絡」表單與我們聯絡。
除非另有註明,否則本頁面中的內容是採用創用 CC 姓名標示 4.0 授權,程式碼範例則為阿帕契 2.0 授權。詳情請參閱《Google Developers 網站政策》。Java 是 Oracle 和/或其關聯企業的註冊商標。
上次更新時間:2025-08-31 (世界標準時間)。
[null,null,["上次更新時間:2025-08-31 (世界標準時間)。"],[],[],null,["**Google Maps Platform EEA integration guides**\n\n- [Announcement \\& FAQ](/maps/comms/eea/faq) \n- [Address Validation API](/maps/comms/eea/address-validation)\n- [Directions API (Legacy)](/maps/comms/eea/directions)\n- [Distance Matrix API (Legacy)](/maps/comms/eea/distance-matrix)\n- [Geocoding API](/maps/comms/eea/geocoding)\n- [iOS Geocoder](/maps/comms/eea/ios-geocoder)\n- [Map Tiles API](/maps/comms/eea/map-tiles)\n- [Maps Static API](/maps/comms/eea/maps-static)\n- [Places API (New \\& Legacy)](/maps/comms/eea/places)\n- [Roads API](/maps/comms/eea/roads)\n- [Routes API](/maps/comms/eea/routes)\n- [Routes Preferred API](/maps/comms/eea/routes-preferred)\n- [Street View Static API](/maps/comms/eea/street-view-static)\n- **Solar API**\n\nEffective **8 July 2025** , new **EEA-specific Google Maps Platform Terms of Service\n(EEA terms)** will impact how you build applications and experiences for users if your project\nis linked to an EEA billing account.\n\nWe strongly recommend that you read and understand the\n[announcement](/maps/comms/eea/faq), as the details potentially impact your\nexisting and new applications that integrate Google Maps Platform.\n\nThis document describes **usage and Google Maps Platform functionality changes** for the\n**Solar API**.\n\nThe information described in this document reflects the\n[EEA terms\ngoverning your use of Google Maps Platform Services](https://cloud.google.com/terms/maps-platform/eea) as of 8 July 2025,\nwhich may change over time. For the most recent and binding terms applicable to you,\nsee your Google Maps Platform Agreement with Google.\n\nSolar API adjustments for EEA customers\n\nThese adjustments apply to (a) projects created after 8 July 2025 that\nare linked to an account with an EEA billing address,\nand/or to (b) projects that are no longer in the\n[Unmodified State](/maps/comms/eea/faq#material-modification)\nafter 8 July 2025.\n\nThe following table summarizes the adjustments, delineated in the\n[EEA\nService Specific Terms](https://cloud.google.com/terms/maps-platform/eea/maps-service-terms), for each Google Maps Platform service.\n\n| Solar API Functionality Adjustments | Terms of Service Changes |\n|------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------|\n| The following fields in [Building Insights](/maps/documentation/solar/building-insights) are not available: - `postalCode` - `administrativeArea` - `regionCode` | None |\n\n\u003cbr /\u003e\n\nAlternative integrations\n\nThe impacted address fields are not essential to the solar qualification\nand solar array design use cases, and you should consider continuing to operate\nyour application without that content.\n\nShould that content be necessary for the functioning of your application,\nthe [`BuildingInsights`](/maps/documentation/solar/building-insights)\nmethod also returns a Place ID in the name field, which can be passed to\nPlaces UI Kit to obtain the details of the Place. For EEA guidance on\nusing Places content, see\n[Places API adjustments for European Economic\nArea (EEA) customers](/maps/comms/eea/places).\n\n\nWhat if I have additional questions not covered in this document?\n\nIf you have any technical questions not addressed in this document or the\n[General FAQ](/maps/comms/eea/faq),\nyou can contact [Google Maps Platform Support](/maps/support?utm_medium=MSA&utm_source=GMP_Billing_Admin&utm_campaign=Dec_24&utm_content=GMP_Support).\n\nIf you have a negotiated agreement with Google and have questions about your contract,\nyou can contact your Google Maps Platform representative. If you are unsure who your\naccount representative is, reach out using our\n[Contact Sales form](https://mapsplatform.google.com/contact-us/?utm_medium=MSA&utm_source=GMP_Billing_Admin&utm_campaign=Dec_24&utm_content=Contact_Sales)."]]