earth engine not registered/initializing about coastsat HOT 9 CLOSED

Hey Spicer, just read your stack question. I've never seen this error before... error 404 usually means that the webpage you're trying to reach has been removed or moved to another URL. Could be that the version of earthengine-api package that I have listed in the environment.yml file is obsolete. You can try to change in that file earthengine-api=0.1.173 to the latest version and re-install the environment (after running conda clean --all)

from coastsat.

@SBFRF did you find a way around the initialization error? There is another person here at the lab who installed coastsat recently and also has that issue, so it must be an earth-engine update as on my desktop it still works fine...

from coastsat.

hey @kvos i actually haven't had the chance to try this again. :(

from coastsat.

@kvos update, I tried with the new environment yaml you have on master (has earthengine-api=0.1.173) and still no luck. This time on a new machine to see if it was something funny on the machine i'm using. (one uses Centos7 and the other is PopOS! , a spin off of ubuntu).

from coastsat.

@SBFRF I've tried re-installing the coastsat environment on one of my computers (windows) and it worked fine. My only suggestion at this stage would be to replace the content of the environment.yml file with the following (where no version numbers are specified) and let anaconda pick the most appropriate versions for your OS:

channels:
  - defaults
  - conda-forge
dependencies:
  - python=3.7
  - matplotlib
  - earthengine-api
  - gdal
  - geopandas
  - pytz
  - scikit-image
  - scikit-learn
  - shapely
  - spyder
  - notebook

from coastsat.

I also ran into the same 404 error code that Spicer and a few others have seen. To fix this and get CoastSat working on my computer - I had to directly request access to Google Earth Engine (https://signup.earthengine.google.com/) which took about a day for Google to approve for me. This is separate from the "earthengine authenticate" command which provided me a token even before I "officially" had access to GEE. After Google manually OK'd my access, all seems to be working.

from coastsat.

happy days! thanks @ncohn for sharing this fix, quite a few users were stuck on this lately, I will update the documentation asap

from coastsat.

so when i go there i get the below, but i think i did this like several months ago.....

.... i will wait again and post in a day or so any status changes

from coastsat.

That seems to have fixed it. I guess i got (several months ago) and email (or didn't) but was granted access. When i tried to run i was successfully brought to a place where i was digitizing shorelines. I guess the take away was to be patient :). Now i'm getting other errors, but i'll try to debug with available info or open another issue. Thanks everyone!

from coastsat.