GCD can now produce really, really large projects because of all the batch processing and the potential to load really large rasters (e.g. the DEE is 110 km off LiDAR). Part of the advantage of GCD is the housekeeping. As long as we NEVER delete the xml project entries for derivative, intermediate and outputs of GCD, we can easily delete the raster datasets as they could be reproduced locally at any time if inputs still exist. It would be really nice to have a command that allowed you to:
Compact a project (to save disc space) - Finds all non-essential rasters (i.e. those that could be reproduced) and deletes the rasters, but keeps the
Compact and zip (for sharing) - Does above but adds to a zip file for easy transfer.
Zip up Share or upload to a Riverscapes Warehouse (e.g. S3 bucket) - i.e. what Matt's cool tool does.
Uncompact (whole project) - Re build all those rasters
Rederive raster output
The above is different than the 'Delete' commands, which both delete the data files and the XML project entries.
The Problem
GCD can now produce really, really large projects because of all the batch processing and the potential to load really large rasters (e.g. the DEE is 110 km off LiDAR). Part of the advantage of GCD is the housekeeping. As long as we NEVER delete the xml project entries for derivative, intermediate and outputs of GCD, we can easily delete the raster datasets as they could be reproduced locally at any time if inputs still exist. It would be really nice to have a command that allowed you to:
The above is different than the 'Delete' commands, which both delete the data files and the XML project entries.