We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
import os from samgeo import SamGeo Map = geemap.Map()
it prints out the following error:
RuntimeError: Error creating a Maps API session: {'error': {'code': 400, 'message': 'API key not valid. Please pass a valid API key.', 'errors': [{'message': 'API key not valid. Please pass a valid API key.', 'domain': 'global', 'reason': 'badRequest'}], 'status': 'INVALID_ARGUMENT', 'details': [{'@type': 'type.googleapis.com/google.rpc.ErrorInfo', 'reason': 'API_KEY_INVALID', 'domain': 'googleapis.com', 'metadata': {'service': 'tile.googleapis.com'}}]}}.
I found out that the culprit is this line
segment-geospatial/samgeo/common.py
Line 17 in 513020a
The text was updated successfully, but these errors were encountered:
It was used to use the Google base tiles. I guess it is no longer needed. It has been removed in #343. Will release a new version shortly.
Sorry, something went wrong.
I just released v0.12.1. Please try again.
thanks!!
Successfully merging a pull request may close this issue.
To reproduce
it prints out the following error:
RuntimeError: Error creating a Maps API session:
{'error': {'code': 400, 'message': 'API key not valid. Please pass a valid API key.', 'errors': [{'message': 'API key not valid. Please pass a valid API key.', 'domain': 'global', 'reason': 'badRequest'}], 'status': 'INVALID_ARGUMENT', 'details': [{'@type': 'type.googleapis.com/google.rpc.ErrorInfo', 'reason': 'API_KEY_INVALID', 'domain': 'googleapis.com', 'metadata': {'service': 'tile.googleapis.com'}}]}}.
I found out that the culprit is this line
segment-geospatial/samgeo/common.py
Line 17 in 513020a
The text was updated successfully, but these errors were encountered: