My WebLink
|
Help
|
About
|
Sign Out
Home
Browse
Search
FLOOD09060
CWCB
>
Floodplain Documents
>
Backfile
>
8001-9000
>
FLOOD09060
Metadata
Thumbnails
Annotations
Entry Properties
Last modified
1/26/2010 10:07:50 AM
Creation date
10/5/2006 4:04:05 AM
Metadata
Fields
Template:
Floodplain Documents
County
Statewide
Community
Statewide
Basin
Statewide
Title
Statewide River Rehabilitation and Flood Plain Management Needs Inventory
Date
2/18/1998
Prepared For
State of Colorado
Prepared By
McLaughlin Water Engineers, Ltd.
Floodplain - Doc Type
Floodplain Report/Masterplan
There are no annotations on this page.
Document management portal powered by Laserfiche WebLink 9 © 1998-2015
Laserfiche.
All rights reserved.
/
90
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
<br />I I <br />I <br />I <br />I <br />I <br />I <br />I <br />I <br />I <br />I <br />I <br />II <br />I <br />I <br />I <br />I <br />I <br />II <br />I <br /> <br />more efficient to use, room was allotted to record these comments. <br /> <br />TYPE OF INFORMA nON OBTAINED <br /> <br />The number and quality of the responses were generally very good. There were some that were very <br />detailed and had great ideas, and others, due to inexperience or lack of familiarity with floodplain <br />management did not fully answer panicular questions. On the other hand, some communities felt there <br />was no reason for them to be filling out the questionnaire. Either there were no streams running through <br />the community or their town was on top of a hill. Bear in mind, when reviewing the data in Chapter 5. <br />the total number of respondents will not always add up to the total number of questionnaires received due <br />to the number of communities who returned a questionnaire but did not completely fill it out. <br /> <br />DATABASE CONTENTS <br /> <br />Questions were phrased differently throughout the questionnaires. In an attempt to get the most use out <br />of the questions, different types of responses were stored in the database. For the Needs Assessment <br />database, there are four basic types of responses; text, yes/no, listed, and descriptive. Below are <br />descriptions of each type of response followed by a brief table of contents for the community questionnaire <br />and the organization questionnaire. <br /> <br />Types of Responses <br />Text ResDonses. Text responses are very shon and contain exact information. Most text responses allow <br />only 30 characters to be typed, Examples of text responses can be found in most of the community or <br />organization information responses. Items such as the address, telephone number, and respondent's name <br />are not questions that need to be deciphered or divided into smaller ideas, <br /> <br />Yes/No ResDonses. Yes/no responses were the checked items in the questionnaire. Some of these <br />questions were also associated with a descriptive response for further explanations or a text response for <br />including a cost, length, or location. All yes/no responses used a list box. Basically, only the accepted <br />answers are allowed to be entered for that question. A good example of this, which is not quite a yes/no <br />response, is the effectiveness of existing or planned mitigation measures. The questionnaires asked for a <br />'poor,' 'fair' or 'good' rating. In the database, however, the rating is not stored as a text but as a number. <br />If a query of this type is planned, the assigned number will have to be looked up in a table showing that <br />relationship. The number is needed to properly son the data. <br /> <br />Listed Resconses. Listed responses are for those questions that asked for either a list or were left open- <br />ended so that a community could answer with any number of responses. For instance, communities were <br /> <br />III-2 <br /> <br />97-060.001 <br />
The URL can be used to link to this page
Your browser does not support the video tag.