You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Description:
I encountered a RuntimeError while trying to initialize geemap.Map() in Geemap version 0.34.03. The issue seems related to the Google Maps API key validation, even when no explicit API key is provided.
Steps to Reproduce:
importgeemapimporteeee.Initialize()
Map=geemap.Map() # No API key passed
Error Message:
RuntimeError: Error creating a Maps API session:
{'error': {'code': 400, 'message': 'API key not valid. Please pass a valid API key.'}}
Expected Behavior:
Geemap should initialize the Map() object without requiring an API key when using default basemaps.
Observed Behavior:
Geemap attempts to validate a Google Maps API key, even when no key is explicitly provided, resulting in a failure due to invalid or missing API credentials.
Additional Context:
A similar issue was reported earlier (#342) and fixed in October with version 0.12.1. However, it seems to have resurfaced in 0.34.03.
Environment:
OS: Windows 11
Python version: 3.8.10
Geemap version: 0.34.03
Earth Engine version: 1.1.4
Temporary Workaround:
Setting os.environ["GOOGLE_MAPS_API_KEY"] = "" as an empty string prevents the error, but this should not be required for the default basemaps.
Request:
Please investigate this regression and ensure that the fix from #342 is applied consistently across recent versions.
The text was updated successfully, but these errors were encountered:
Description:
I encountered a RuntimeError while trying to initialize
geemap.Map()
in Geemap version 0.34.03. The issue seems related to the Google Maps API key validation, even when no explicit API key is provided.Steps to Reproduce:
Error Message:
Expected Behavior:
Geemap should initialize the
Map()
object without requiring an API key when using default basemaps.Observed Behavior:
Geemap attempts to validate a Google Maps API key, even when no key is explicitly provided, resulting in a failure due to invalid or missing API credentials.
Additional Context:
A similar issue was reported earlier (#342) and fixed in October with version 0.12.1. However, it seems to have resurfaced in 0.34.03.
Environment:
Temporary Workaround:
Setting
os.environ["GOOGLE_MAPS_API_KEY"] = ""
as an empty string prevents the error, but this should not be required for the default basemaps.Request:
Please investigate this regression and ensure that the fix from #342 is applied consistently across recent versions.
The text was updated successfully, but these errors were encountered: