"Inputs" Tree Container and its 2nd Level Contents

[joewheaton]

In #81 Inputs are proposed as one of two 1st level tree containers. What should be inputs? From #81 @joewheaton offered:

Inputs - This would be where all Assessments go, all Context, and all Sampling Frames go, which are subsequently used to support analyses. Stuff in this category can still include useful tools, mapping, digitizing, attribute calculation, summary statistics, etc. However, this is where we catalog the basis (e.g. aerial photos and photos) for mapping of features at snap shots in time in assessments, and the subsequent analysis and/or sampling of that mapping. This would house (may be further nested or collected, but):

DEM Surveys (may go under Assessments)
Reference Surfaces - Techncially these are derived from either a constant surface specification or from existing DEM Surveys
Masks - This is a little polygon mask library of AOIs, Regular Masks, and Directional Masks (e.g. riverscape segments with topology)
Profile Routes - This is a little polyline library of transects, long profiles and other paths used to extract values off of underlying "surfaces".

Lets refine the 2nd Level Contents (e.g. Assessments, but not say dam/jam counts or inundation maps, that would be third level)?

[joewheaton]

As a start, what if we did:

We need homes from current QRiS for:

• Assessments
• Designs
• Project Extents (maybe AKA Masks or Mask Library)
• Project Layers (at some point referred to as "scratch space")

We know we also need:

• DEM Surveys
• AP Surveys
• Mask Library
• Profile Library