Skip to main content

You are not logged in. Your edit will be placed in a queue until it is peer reviewed.

We welcome edits that make the post easier to understand and more valuable for readers. Because community members review edits, please try to make the post substantially better than how you found it, for example, by fixing grammar or adding additional resources and hyperlinks.

Required fields*

5
  • 1
    I'm encountering the same error with code that previously worked correctly. A new folder with the same name is being created for each task I run, even though a folder with that name already existed before running the code. Maybe EE changed something? It's strange because they still state in their documentation: > The Google Drive Folder that the export will reside in. Note: (a) if > the folder name exists at any level, the output is written to it, (b) > if duplicate folder names exist, output is written to the most > recently modified folder, (c) if the folder name does not exist, a new > Commented Apr 28 at 11:45
  • 1
    Same issue here... a previously working code is now creating a new folder with the exact same name for each export tasks. This looks like a mistake on Google Earth Engine side. Hopefully, this will be solved soon enough. Jason Commented Apr 30 at 16:31
  • 1
    I am having the same problem for code that previously worked. I have even switched from service key to OAuth 2.0. Nothing I have done will fix it. What is interesting is that I can write to my Google Drive, but when I try to use python api to see any folders, they are not visible. Strange behavior. A colleague just joined and is able to download to a single folder. Commented May 8 at 14:08
  • I'm experiencing the same thing. This issue has started recently without any changes to my code, so it seems to be something on the gee side... Commented Aug 13 at 13:26
  • I don't have the reputation to answer, but if anyone is still running into this, it seems to have been fixed in newer versions of earthengine-api. I had this issue with 1.1.5 and lower versions, but not with 1.6.4. Commented Aug 21 at 16:54