Flood DSS Prototype Scope

• Title: Prototype FloodDSS Project Scope of Work
• Description: Project Scope of work
• Decision Support - Doc Type: Scope of Work
• Date: 6/30/2006
• DSS: Flood
• Basin: Statewide
• Prepared By: Riverside

attempt at these groups is shown below but final decisions will be discussed with the CWCB.
RTi can also suggest and evaluate additional data products from the NWS, NRCS, and other
agencies. The information in Table 1 should be completed during data collection and before
finalizing the map displays:
• The "Data Group" and "Data Layer" will be used to organize and identify data layers.
• The "Source" and "Metadata" will be used to collect data and identify its attributes (and
in an operational system will be used in update procedures). Although it is desirable that
all spatial data include metadata, the cost of creating metadata will be evaluated as the
inventory is completed. The full scale Flood DSS should include metadata for all layers.
• The "Spatial Data Format" column will be used to document the format for spatial data, if
available. If not available, RTi will discuss with the CWCB the feasibility of creating a
single layer (e.g., "Engineering models ") that indicates locations of studies. A hyperlink
can be included in the spatial data layer to point to the electronic files for the study. The
inventory will also indicate whether only hard -copy information is available.
• The "Extent" indicates whether a single statewide layer is available or can be created, or
whether multiple individual layers are used. For example, some studies may be
significant enough that they include their own spatial data layer(s) at a local scale. For
technical or cost reasons, it may not be possible to combine such data into a single
statewide layer containing similar features.
• "Non- spatial Data" indicates whether additional data are available and need to be linked
(e.g., reports, model files). The non - spatial data, if made available from the web site, will
need to be organized and managed. If data are not available in spatial form, then the map
interface cannot be used as a primary link to the secondary data. In this case, documents
will need to be retrieved directly from the website. This is discussed in the Implement
Access to Non - spatial Data item below.
• "Scanned Doc." indicates whether scanned documents are available in Content Manager
or other document management system. In this case, the proper keys will need to be
identified to link spatial data to Content Manager.
RTi understands that the State will be replacing Content Manager with another product and
RTi will accommodate the change in the prototype.
Table 1. Example Flood DSS Data Layer Inventory for Internet Map Server'
t The information shown is for illustration of the approach and is not complete. This information, and other information needed for
the project will be completed during implementation.
Metadata
Spatial
Non-
Scanned
#
Data Group
Data Layer
Source
Available
Availa ble le
Data
Extent
spatial
Doc.
Data
1
Flood Outlook
Flood outlook and snowmelt
flood preparation data
2
Flood Maps,
Designated and approved
Studies
approximate flood lain reaches
3
Designated and approved
detailed floodplain reaches
4
Hydrologic, hydraulic, and
related technical information
for flood projects
5
Engineering models for
flood lain studies
t The information shown is for illustration of the approach and is not complete. This information, and other information needed for
the project will be completed during implementation.