2025년 7월 8일부터 프로젝트가 EEA 결제 계정에 연결된 경우 새로운 EEA용 Google Maps Platform 서비스 약관(EEA 약관)이 사용자를 위한 애플리케이션 및 환경을 빌드하는 방식에 영향을 미칩니다.
세부정보는 Google Maps Platform을 통합하는 기존 및 신규 애플리케이션에 영향을 미칠 수 있으므로 공지사항을 읽고 이해하시기 바랍니다.
이 문서에서는 Solar API의 사용 및 Google Maps Platform 기능 변경사항을 설명합니다.
이 문서에 설명된 정보는 2025년 7월 8일 현재 Google Maps Platform 서비스 사용에 적용되는 EEA 약관을 반영하며, 이는 시간이 지남에 따라 변경될 수 있습니다. 귀하에게 적용되는 최신 구속력 있는 약관은 Google과의 Google Maps Platform 계약을 참고하세요.
EEA 고객을 위한 Solar API 조정
이 조정은 (a) 2025년 7월 8일 이후에 생성되었으며 EEA 결제 주소가 있는 계정에 연결된 프로젝트 또는 (b) 2025년 7월 8일 이후에 더 이상 수정되지 않은 상태가 아닌 프로젝트에 적용됩니다.
다음 표에는 각 Google Maps Platform 서비스에 대해 EEA 서비스별 약관에 설명된 조정이 요약되어 있습니다.
[[["이해하기 쉬움","easyToUnderstand","thumb-up"],["문제가 해결됨","solvedMyProblem","thumb-up"],["기타","otherUp","thumb-up"]],[["필요한 정보가 없음","missingTheInformationINeed","thumb-down"],["너무 복잡함/단계 수가 너무 많음","tooComplicatedTooManySteps","thumb-down"],["오래됨","outOfDate","thumb-down"],["번역 문제","translationIssue","thumb-down"],["샘플/코드 문제","samplesCodeIssue","thumb-down"],["기타","otherDown","thumb-down"]],["최종 업데이트: 2025-08-31(UTC)"],[],[],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)."]]
Google Maps Platform EEA 통합 가이드