implementing full automation of workflows (i.e. explicit linkage to raw inputs, automated execution of all steps, and automated uploading of outputs to cloud data servers) - except from firing them up (this would be done locally by a developer)
users will interact with CCISS data/outputs in two ways:
via the CCISS Tool ShinyApp
via Climate Summaries Spatial App -- allows downloading spatial layers.
April Sprint discussions pointed to:
ccissrR package -- allows them to supply a set of point locations (eventually a polygon shapefile/raster; see https://github.com/bcgov/climr/issues/239)see https://github.com/bcgov/CCISS/issues/49 and https://github.com/bcgov/CCISS/issues/50
Closing issue as it feels it's more or less "decided"