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
see prototype code under heading "Create Best Fit Raster Dataset" in sub-sections "Create a base raster for the model domain" and "Create a raster clipped to the coverage. " at Raster Mashups #55
Let's talk through the logic of doing this step last, ie., it could be beneficial from the standpoint of saving time/storage space, and also fitting into a work flow as a separate step. Or, it could be iniefficient given that evidence suggests that loadin rasters into memory for processing is a large part of processing time. see resampling performance testing results in section "Use Explicit Feature IDs to simplify query planner" of Tiling and raster performance #70
Develop ability to export coverage raster data for a given day for external visulization. Follow instructions in "Export Sample Records as geotiff or ping" in Raster Mashups #55
We may put this into the analyze step of geo workflow, or even create a separate qa branch so as not to create too many visualizations, or even make a completely separate, non-flowable script.
Finalize the above into robust, modular workflowable scripts
generate new hourly precip value for alternate raster dataset
run QA steps
The text was updated successfully, but these errors were encountered:
geo
workflow, or even create a separateqa
branch so as not to create too many visualizations, or even make a completely separate, non-flowable script.The text was updated successfully, but these errors were encountered: