针对欧洲经济区 (EEA) 客户的 Solar API 调整
使用集合让一切井井有条
根据您的偏好保存内容并对其进行分类。
Google Maps Platform 欧洲经济区集成指南
自 2025 年 7 月 8 日起,如果您的项目与欧洲经济区 (EEA) 结算账号相关联,则适用于欧洲经济区的 Google Maps Platform 服务条款 (EEA 条款)将影响您为用户构建应用和体验的方式。
我们强烈建议您阅读并了解公告,因为其中的详细信息可能会影响您已集成 Google Maps Platform 的现有应用和新应用。
本文档介绍了 Solar API 的用量和 Google Maps Platform 功能变更。
本文档中所述的信息反映了自 2025 年 7 月 8 日起适用于您使用 Google Maps Platform 服务的欧洲经济区条款,这些条款可能会随时间推移而发生变化。如需了解适用于您的最新且具有约束力的条款,请参阅您与 Google 签订的 Google Maps Platform 协议。
针对欧洲经济区 (EEA) 客户的 Solar API 调整
这些调整适用于:(a) 2025 年 7 月 8 日之后创建且与具有欧洲经济区结算地址的账号关联的项目,和/或 (b) 2025 年 7 月 8 日之后不再处于未修改状态的项目。
下表总结了欧洲经济区服务条款中针对每项 Google Maps Platform 服务做出的调整。
Solar API 功能调整 |
服务条款变更 |
大楼数据分析中的以下字段不可用:
postalCode
administrativeArea
regionCode
|
无
|
备选集成方式
受影响的地址字段对太阳能资格认证和太阳能阵列设计用例而言并不是必需的,因此您应考虑在不使用这些内容的情况下继续运营您的应用。
如果该内容对应用的正常运行至关重要,BuildingInsights
方法还会在名称字段中返回地点 ID,该 ID 可传递给地点界面 Kit 以获取地点的详细信息。如需了解有关使用地图内容的欧洲经济区 (EEA) 指南,请参阅面向欧洲经济区 (EEA) 客户的 Places API 调整。
如果我还有本文档未涵盖的其他问题,该怎么办?
如果本文件或常见问题解答中未涵盖您的任何技术问题,您可以与 Google Maps Platform 支持团队联系。
如果您与 Google 达成了协议,并且对合同有疑问,可以与您的 Google 地图平台代表联系。如果您不确定自己的客户代表是谁,请使用“与销售团队联系”表单与我们联系。
如未另行说明,那么本页面中的内容已根据知识共享署名 4.0 许可获得了许可,并且代码示例已根据 Apache 2.0 许可获得了许可。有关详情,请参阅 Google 开发者网站政策。Java 是 Oracle 和/或其关联公司的注册商标。
最后更新时间 (UTC):2025-08-31。
[null,null,["最后更新时间 (UTC):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)."]]