|
RTi has previously created statewide layers for the CDSS Map Viewer and the ISFDSS,
<br />which may be appropriate for the Flood DSS. These layers include climate, streamflow,
<br />diversion, reservoir, well, fisheries, instream flow and natural lake levels, rivers, basins,
<br />political boundaries, land use, USGS topographic, orthophotos, digital elevation model,
<br />imagery, and other data. Although it is valuable for users to have access to as much data as
<br />possible, offering too much information can result in confusing interfaces that are difficult to
<br />use.
<br />Deliverable RTi will create a data inventory document containing a list of data layers,
<br />sources, whether metadata are available, data formats, data extent, and links to non - spatial
<br />data. This document will be used to guide the prototype Flood DSS web site implementation.
<br />The documentation will be provided to the State as part of normal correspondence and project
<br />management.
<br />3. Data Collection. Data collection involves collecting the actual data files for data types listed
<br />in the data inventory. In some cases, the collection will occur as the inventory is created. In
<br />other cases, additional follow up may be needed. Any help that the CWCB can provide in
<br />collecting and organizing data will allow RTi to focus more resources on extending the
<br />prototype implementation. Digitizing data can be a laborious and expensive effort.
<br />Therefore, it is assumed that for the prototype, little or no digitizing will occur, although
<br />CWCB effort could be utilized. Data layers from external sources (e.g., FEMA) will be
<br />collected and used with little or no modification (see next item). If necessary, RTi will
<br />Spatial
<br />Non-
<br />Scanned
<br />#
<br />Data Group
<br />Data Layer
<br />Source
<br />AvailaDoc.
<br />Av Metadata aila ble le
<br />Data
<br />Extent
<br />spatial
<br />Format
<br />Data
<br />6
<br />FEMA Digital Flood Insurance
<br />Rate Map (DFIRM) studies
<br />and data
<br />7
<br />Alluvial fan and debris flow
<br />floodplain maps and
<br />engineer n data
<br />8
<br />Historical Floods
<br />Past flood events and disaster
<br />declaration areas
<br />9
<br />Flood Insurance
<br />Community Assistance Visit
<br />Program
<br />reports for NFIP requirements
<br />10
<br />Community Rating System
<br />(C.R.S.) information for the
<br />NFIP
<br />11
<br />Participating and non-
<br />participating communities
<br />(NFIP
<br />12
<br />Flood Control
<br />Federal, state, and local levee
<br />systems
<br />13
<br />Flood control dams /reservoirs
<br />14
<br />Restoration
<br />Multi- objective stream
<br />restoration studies/ projects
<br />15
<br />Watershed restoration
<br />studies/ projects
<br />16
<br />Weather
<br />Cloud seeding areas and cloud
<br />Modification
<br />seeding permit data
<br />17
<br />Weather modification and hail
<br />suppress . on data
<br />RTi has previously created statewide layers for the CDSS Map Viewer and the ISFDSS,
<br />which may be appropriate for the Flood DSS. These layers include climate, streamflow,
<br />diversion, reservoir, well, fisheries, instream flow and natural lake levels, rivers, basins,
<br />political boundaries, land use, USGS topographic, orthophotos, digital elevation model,
<br />imagery, and other data. Although it is valuable for users to have access to as much data as
<br />possible, offering too much information can result in confusing interfaces that are difficult to
<br />use.
<br />Deliverable RTi will create a data inventory document containing a list of data layers,
<br />sources, whether metadata are available, data formats, data extent, and links to non - spatial
<br />data. This document will be used to guide the prototype Flood DSS web site implementation.
<br />The documentation will be provided to the State as part of normal correspondence and project
<br />management.
<br />3. Data Collection. Data collection involves collecting the actual data files for data types listed
<br />in the data inventory. In some cases, the collection will occur as the inventory is created. In
<br />other cases, additional follow up may be needed. Any help that the CWCB can provide in
<br />collecting and organizing data will allow RTi to focus more resources on extending the
<br />prototype implementation. Digitizing data can be a laborious and expensive effort.
<br />Therefore, it is assumed that for the prototype, little or no digitizing will occur, although
<br />CWCB effort could be utilized. Data layers from external sources (e.g., FEMA) will be
<br />collected and used with little or no modification (see next item). If necessary, RTi will
<br />
|