FloodDSS SOW

• Title: FloodDSS Scope of Work
• Decision Support - Doc Type: Scope of Work
• Date: 4/10/2009
• DSS: Flood
• Basin: Statewide
• Contract/PO #: C154138
• Bill Number: HB08-1346
• Prepared By: Riverside Technology

PROJECT APPROACH

_z ~ ~,¢~ ~ _ 3 ~ ~:
,,. `'
e ~'
,_ . , Prototype
S anal Extent
Highways Statewide
Cities Statewide
Townshi s Statewide
Counties Statewide
Districts Statewide
Basins Statewide
Divisions Statewide
Land Use Land Cover Statewide
Larimer Aerial Photo Statewide
Satellite Image Statewide
Too a h (24K, 100K, 250K) Statewide
Background Elevation Statewide
Hi-Res Elevation Statewide
Shaded Relief Statewide
Approach
' Riverside and AMEC will develop an inventory of the data sources that have been identified for
potential inclusion in the Phase I Flood DSS. Potential data sources will be identified from the
user needs assessment, the Flood DSS prototype (Table 4-1), and the RFP. Each data source will
be evaluated in terms of data format, spatial extent, coordinate system, available metadata,
known issues, potential reporting products, and relevance to the Flood DSS (see Table 4-2).
Table 4-2. Example Data Inventory Layout
Data Data Source/ Spatial Coordinate Metadata Known potential Relevance

Group
Layer .
Contact .Format
Extent.
System
Available
Issues Reporting to Flood
products DSS

• The "Data Group" field will be used to organize the data.
• The "Data Layer" field will be used to identify the data layer.
• The "Source/Contact" field will identify a source agency or contact.
• The "Format" field will identify the data format. For non-spatial data, this could include
whether the data are available in a document management system.
• The "Spatial Extent" field will indentify whether the data are available statewide or locally.
• The "Coordinate System" field applies only to spatial datasets.
• The "Metadata Available" field will be used to identify the data attributes and existing level
of metadata.
• The "Known Issues" field will be a descriptive entry identifying known issues for integrating
the data into the Flood DSS.
• The "Potential Reporting Products" field will be a descriptive entry identifying potential
products that could be developed using the data to support decision-making by the end users.
• The "Relevance to Flood DSS" field will be a descriptive entry documenting the value of
including the data source in the Flood DSS.
DNR RFP PDA-923 35 R I V E R S I D E