Flood DSS Prototype Report - Laserfiche WebLink

Home Browse Search

Appendix A — Inventory of Data Layers Used in the Flood DSS Prototype Table A.1 below lists data layers used in the Flood DSS Prototype, in the order listed in the Flood DSS Viewer. A.1 Data Inventory Table Organization Table A.1 is grouped into categories to help users find information. The columns "Data Group" (1) and "Data Layer name and Description" (2) are used to organize and identify data layers. The "Source /Contact" (3) and "Metadata" (4) columns were used to collect data, identify its source agency and key personnel, and to identify its attributes. The "Spatial Data Format" (5) column was used to document the spatial data format, while the "Extent" column (6) indicates whether a single statewide layer is available or can be created, or whether individual layers from Larimer County, City of Fort Collins, or other locations are used. "Content Manager and Other Non - spatial Information" (7) indicates whether relevant scanned documents are available in Content Manager and are related to spatial data via hot - links. Column (8), "Key Pre - Integration Processing Tasks" describes processing required to integrate data into the Flood DSS, and provides useful information on the level of work that may typically be required for such a dataset to be integrated into a full system. The final column (9) provides comments to clarify the Flood DSS database development process and offer suggestions to assist with full Flood DSS development. A.2 Organization and Relevance of Data Groups Data layers were organized and grouped into logical thematic categories to help users find information. Groups identify major themes such as "Flood Maps ", which in this example contains all existing, automated and contemporary FIRM, DFIRM and City floodplain maps (i.e. County and Community scale). Historical flood map data are held under a separate data group, "Historical Floods ", and contains both local information (Fort Collins City flood extent and damage maps for the 1997 flood) as well as statewide data (an inventory of major floods in Colorado). At the bottom of Table A.1, several statewide data layers are listed. These were developed previously by RTi for the CDSS Map Viewer, and are selected here for their utility in Flood Decision Support. Although it is valuable for users to have access to as much data as possible, offering too much information can result in confusing interfaces that are difficult to use, therefore the layers in these base, background and other data groups have been selected with guidance from the State. Details on these layers have not been included in Table A.1 as CWCB and DWR staff is already familiar with these. One new layer included in the "Background" data group is the Larimer Aerial Photo. This image is National Agriculture Imagery Program (NAIP) data, available at lm- resolution for the entire state. A.3 Metadata Metadata is always desirable, but is expensive to develop, especially if this is done retroactively. For the Flood DSS prototype, much of the information provided by various agencies had little or, no metadata, and where it existed often came in hardcopy format. In order to focus on tasks more important to prototype evaluation, only basic metadata has been created for most layers. The full scale Flood DSS should include metadata for all layers. 17