how to deal with too big surfaces ?

[12rambau]

I'm trying to run the analysis over the cote d'Ivoir country, with specific interest on restoration sites (I'm using a shapefile to deal with it). The country is too big to be exported, it's even too big to be run as a dashboard due to EarthEngine limitation.

Several options exist:

• reduce resolution to the optimally usable one (the option BestEffort is our friend pros: we don't bother cons: we loose the control over the final resolution
• compute the result in chunks pros: we keep the native resolution, cons: I don't know if it's possible

[jdilger]

Hmm, computing in chunks would not be ideal for display (or export if we can avoid it...). For the dashboard stats, BestEffort could help in some areas. Do you recall if BestEffort controls both scale and tile size or one or the other? Changing the scale will change the area estimates.

I'll take a look and report back!

[jdilger]

Also, what is the export error? Is it too many pixels? It looks like we're using the default when exporting. If we add maxPixels:1e13

https://github.com/12rambau/restoration_planning_module/blob/ea6365b4f0315cf12c87a74fec5d91a2dfc0eea1/component/widget/export_map.py#L105

Can you share the shapefile of restoration sites? I wonder if it's a geometry issue if they're particularly complex. I was able to populate the dashboard in the no_ui.ipynb for cote d'Ivoir with 2 drawn sub aois.

[12rambau]

so the restoration sites are all over the cote d'ivoir surface, the main issue is that they also want to run the analysis over the all country (restauration sites are sub AOI). In the end it's a very classic too many pixel issue but I think we should handle it upstream. The sites are not public yet so i can't share them without asking first