CHM
CHM copied to clipboard
Chrismarsh
output netcdf file
netcdf files will be easier to work with than individual tiffs, especially for multiple year/scenario simulations. Also should be more space efficient.
Should be able to use the same vtu2geo tool, add option to write out to netcdf (using xarray module).
Optional length of time for individual netcdf file: time step (not efficient), 1 day, 1 month, 1 year, etc...
The RAM requirements are too large to hold every timestep in RAM. Can xarray incrementally update a netcdf file?
Maybe, it has some smart memory functions (dask) that might work.
But I was thinking of making many small netcdf files (1 time step to 1 month depending on RAM). Then its simple to load them all in to python to plot (xr.open_mfdataset(all_filse)).
Writing each timestep to a netcdf is possible -- the whole file does not need to be kept in ram like I originally thought.
This is the unstructured grid specification for netcdf files https://github.com/ugrid-conventions/ugrid-conventions
It's unclear if Paraview can handle loading this file convention though http://adsabs.harvard.edu/abs/2016EGUGA..18.6414B