-
-
Notifications
You must be signed in to change notification settings - Fork 117
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
Error: Not signed up for Earth Engine or project is not registered #143
Comments
Yes, we are aware of that, initialize EE in a project will be mandatory in the near future but not now, and we are going to update some docs. But, I can run Info related: |
If you run
Your credentials file is stored here (in case you want to inspect):
|
Thanks so much for the info @jdbcode! Do you know when it is mandatory to link the project in GEE credentials or in ee.Initialize()? |
@XavierCLL we're encouraging everyone to use cloud projects now, if they can. A person can continue to not use a cloud project if they are authenticating with either the |
Thanks so much Justin for the information! |
The complete integration of using GEE project in the plugin is still a work in progress, but for now you can use this #133 (comment) update to initialize the project as you show in the figure 2, let me know if with that works for you. |
This finally worked, thank you so much Xavier! |
Thank you very much for reporting the issue and glad it is working now. I am going to close this issue. Please reopen if you run into more issues |
After installing the qgis-earthengine-plugin I registered for the Google Earth Engine through the web interface and created a new project. That all worked fine.
But in QGIS, in the python console I got the error: "Not signed up for Earth Engine or project is not registered" repeatedly if I did the following commands:
However the problem was solved if I entered the following commands in the Python console:
I'm not sure if this is a problem with my installation (Windows 10, Qgis 36.1, python 3.9) or something else but I spent 6-8 hours trying to figure this out. You might want to mention this solution in your documentation.
The text was updated successfully, but these errors were encountered: