Closed GriffinBabe closed 8 months ago
Additional comments from my side:
It could be also nice to have the output of the process in a single NetCDF format instead of numerous GeoTiff files. There are less files to track that way and I believe that it matches better the xarray.DataArray
structure, having all the 4 dimensions (x, y, bands and time) in a single cube
It could be also nice to have the output of the process in a single NetCDF format instead of numerous GeoTiff files. There are less files to track that way and I believe that it matches better the
xarray.DataArray
structure, having all the 4 dimensions (x, y, bands and time) in a single cube
I could be wrong here @GriffinBabe , but can't you just specify a netCDF output format when starting the CropSAR batch job as shown here?
As discussed during the review meeting of the enhancements:
Closing this topic as the internal VITO team is working on a new version of CropSAR where the values aren't rescaled, recognizing that this is inconvenient for users of the service.
When working with the CropSAR process, the results are multiple files that will be downloaded in a folder. Once loaded in memory using for example the
xarray.open_mfdataset
method, they must be linearly rescaled with two parameters $NDVI{rescaled} = NDVI{original} * 0.00432 - 0.08$This is not necessarily hard to do, but while the scaling factors can be found in some parts of the repository, they are not explicitly documented in the FuseTS API methods, impacting the user-friendliness of the library.
Alternatively, a function that automatically loads in memory the rescaled NDVI data from a directory path or a list of file paths, could also be useful.
@JanssenBrm