I am trying to install Google Earth Engine api for Python, but am running into some problems. I am following the directions here. Within a conda environment, I can verify everything until step 6. When I enter python -c "import ee; ee.Initialize()" at the command line, I receive the error "No module named ee". However, conda list shows that ee has been installed via Pip.

Has anyone else had this problem? I have had ee successfully configured, but had to unfortunately delete everything because of ArcPro and so I am having trouble reinitializing ee.


The issue is that when you clone an environment with Anaconda within ArcPro, the cloned environment still links back to the old python executable. However, if you are in a cloned environment and start an IDE (e.g. Spyder), python links to the python executable in the cloned environment. This is not consistent, but appears to be the way it is.


Because you are using the conda package manager, you can install the earthengine-api conda package from the conda-forge channel instead of using pip.

conda install -c conda-forge earthengine-api

This approach has the advantage of taking care of the cryptography dependencies automatically.


Since you previously had ee successfully configured, not sure that this applies, but it looks like that if your account isn't whitelisted to use Earth Engine you will have an issue with step 6. From earthengine-API on Github: Unable to initialize the GEE python client while processing "ee.Initialize()"

  • The problem is a step before ee.Initialize(). I am unable to import ee into python, even though it is listed as an installed package. – user44796 Jul 10 '18 at 15:31
  • Do you receive "ee.ee_exception.EEException: Server returned HTTP code: 404"? I had the same problem when I just installed and it is bc my acct isn't whitelisted – dave Jul 10 '18 at 15:34
  • No, I was receiving the message "No module named ee". The problem is that I am using Anaconda within ArcPro 2.0. When I created a clone of the ArcGIS environment so that I could install packages, the link to the old python executable was used. Pip is looking in the old environment. When I provide the full path to the cloned python executable, it works. Now I just have to figure out how to set the cloned path to the python executable. – user44796 Jul 10 '18 at 15:55
  • I think that this is more of an ArcPro question, so I am going to request this question be removed and I start another question centered around ArcPro and Conda – user44796 Jul 10 '18 at 16:14

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.