My WebLink
|
Help
|
About
|
Sign Out
Home
Browse
Search
Flood DSS Prototype Report
CWCB
>
Decision Support Systems
>
DayForward
>
Flood DSS Prototype Report
Metadata
Thumbnails
Annotations
Entry Properties
Last modified
4/17/2013 10:19:58 AM
Creation date
10/27/2010 10:59:40 AM
Metadata
Fields
Template:
Decision Support Systems
Title
Prototype FloodDSS Project Summary and Recommendations
Description
Project Summary and Report document
Decision Support - Doc Type
Report
Date
6/30/2006
DSS
Flood
Basin
Statewide
Prepared By
Riverside
There are no annotations on this page.
Document management portal powered by Laserfiche WebLink 9 © 1998-2015
Laserfiche.
All rights reserved.
/
24
PDF
Print
Pages to print
Enter page numbers and/or page ranges separated by commas. For example, 1,3,5-12.
After downloading, print the document using a PDF reader (e.g. Adobe Reader).
Show annotations
View images
View plain text
Table 1— Level of Effort Estimates for Flood DSS Data Collection/Processing Tasks <br />13 <br />TASK/ <br />TOTAL <br /># <br />DATA <br />INVENTORY/ <br />PROCESSING <br />ESTIMATED <br />COMMENTS <br />TYPE <br />COLLECTION <br />EFFORT <br />(STATEWIDE <br />1 <br />NFIP <br />2 days <br />2 days <br />4 days <br />Effort should be minimal — update <br />Participation <br />of existing data with CWCB <br />Status <br />assistance. <br />Task may be required to be <br />repeated every 6 months. <br />2 a <br />DFIRM <br />4 -6 hrs /county <br />6 -8 hrs /county <br />80 -112 days <br />DFIRM availability may vary <br />maps <br />widely by county, depending on <br />progress. <br />Effort required for collecting data <br />for both 2a and 2b will vary. <br />Estimates reflect rapid collection <br />for most counties (phone calls and <br />ftp transfers) with some travel time <br />for others. The national FEMA <br />web site may be a resource; <br />however, the CWCB likely has <br />more timely access to data. <br />2 b <br />FIRM maps <br />4 -6 hrs /county <br />6 -8 hrs /county <br />80 -112 days <br />FIRM panels may require <br />digitizing for GIS. <br />Scanned documents may be <br />sufficient. <br />3 <br />Historical <br />6 hrs /county <br />1 1 hrs /county <br />136 days <br />Will require queries into existence <br />Flood data <br />of data — electronic data unlikely <br />to exist for more than 10% <br />counties. <br />4 <br />Weather <br />6 days /season <br />6 days /season <br />12 days per <br />DSS Contractor will need to work <br />Modification <br />season <br />with CWCB to obtain information. <br />More regular updates may be <br />required through each season as <br />use of this technology becomes <br />more prevalent. <br />5 <br />Flood <br />3 -4 hrs /county <br />5 -6 hrs /county <br />64 -80 days <br />Most of this effort will be invested <br />Control <br />locating and extracting these data <br />(dams, <br />from other sources where they <br />levees) <br />exist. <br />Two different dams data layers <br />exist in the Prototype DSS, and <br />will require some updates as <br />a ro riate. <br />6 <br />Multi- hazard <br />6 -8 hrs /county <br />8 -10 <br />112-144 days <br />A considerable part of this effort <br />hrs /county <br />will be invested in locating and <br />integrating multi- hazards data <br />based on a common methodology <br />and cartographic representation. <br />13 <br />
The URL can be used to link to this page
Your browser does not support the video tag.