You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We want to improve the integration between cropharvest and crop-mask.
On the CropHarvest side this consists of:
Renaming the tif files to follow a <location>_<date> naming convention instead of coupling them to the labels.geojson
Rewriting the Engineer to handle variable length tifs, instead of expecting 12-month inputs
Storing tifs to a google cloud bucket
This has the advantage of not requiring tif files to be downloaded before updating the dataset, which should make it easier to contribute new datasets.
I supposed the real question may be: should we reexport all the unexported tifs in the 24 month timestep style starting from January to make it easy to run models from September to September for example.
We want to improve the integration between cropharvest and crop-mask.
On the CropHarvest side this consists of:
tif
files to follow a<location>_<date>
naming convention instead of coupling them to thelabels.geojson
This has the advantage of not requiring tif files to be downloaded before updating the dataset, which should make it easier to contribute new datasets.
cc @ivanzvonkov
The text was updated successfully, but these errors were encountered: