search

JesJehle / earthEngineGrabR

Simplify the acquisition of remote sensing data
https://jesjehle.github.io/earthEngineGrabR/
53 stars 5 forks source link

Deprecation of Fusion Table #8

Open mgmanalili opened 5 years ago

mgmanalili commented 5 years ago

Hello!

Since Google Fusion Table will be deprecated on 3 December 2019, do you already have a fix for this? Like the user can get vector features for aggregation from the GEE Assets?

Thanks!

Michael

JesJehle commented 5 years ago

Hi Michael, This is a problem I am still struggling with. To my knowledge, except the fusion table API, it's not possible to upload vector data to earth engine without a google cloud account. This would require registration with a credit card, and introduce potential costs and with this additional cost management. This is something I want to avoid. An easy solution would be to let the user manually upload vector data with the code editors shapefile uploader. The earthEngineGrabR could finally use the GEE Assets instead of the fusion tables.

I guess I will implement this approach before the deprecation of the API, though I would love to provide an automated approach which is controlled from within R. If anyone has suggestions or ideas, feel free!

mmaelicke commented 4 years ago

Hey @JesJehle , just came across this issue. I can remember darkly the discussion sessions we had at good old alma mater while you were developing the first version of this package.

Based on that knowledge and without being into the workflow too deep, wouldn't it be possible to utilize the earthengine cli for doing so: https://developers.google.com/earth-engine/command_line#upload ?

To manage the users cloud storage, the gcloud cli could be used. If you don't want your users force to manage a cloud storage, you could even set up a dummy service role that can upload to a 5GB bucket and a cloud function that will empty the bucket every 20 minutes to avoid costs. A bit risky though.

Just thinking loudly...