-
Notifications
You must be signed in to change notification settings - Fork 11
New issue
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
Bug: ee Authenticate method is deprecated and blocking requests #211
Comments
The paragraph below explains how the new method of authentication works. New Authentication Method with GEESource: https://developers.google.com/earth-engine/guides/auth Python and Command Line
This will first select the best authentication mode for your environment, and prompt you to confirm access for your scripts. If credentials already exist, they are automatically reused - run ee.Authenticate(force=True) to create new credentials. The initialization step verifies that valid credentials exist, either created from ee.Authenticate() or pre-existing as Google default credentials. It then initializes the Python client library with methods that the backend server supports. You will need to provide a project that you own, or have permissions to use, that also has the Earth Engine API enabled. This project will be used for running all Earth Engine operations. On the command line, the equivalent call is earthengine authenticate. Provide a project for further calls using earthengine set_project {my-project}. Command line invocations will initialize automatically as needed. |
CoastSeg only runs on the user's local computer, which means we can use Solution
|
|
Tools like Geemap have run into the same issue as we have that Google is deprecating how their 0Auth method works. Apartently a project id now needs to be manually entered into the
ee.Initialize(project='my-project-id')
as discovered by giswqs.Tasks
Related Issues
gee-community/geemap#1870
Resources
Screenshots
The text was updated successfully, but these errors were encountered: