Laserfiche WebLink
3. Approximately 75% of required data were estimated to be available internally (CWCB) with 25% <br />being available from external sources. <br />4. The CDSS Map Viewer look and feel is to be maintained. <br />5. CDSS data layers should be shared with the CDSS Map Viewer, where possible. <br />6. The prototype can initially be evaluated from RTi but the final installation will be on a DWR <br />server, similar to the CDSS Map Viewer. <br />2.2 Data Inventory <br />The initial data inventory was developed at the kickoff meeting and in subsequent communications with <br />the State. The primary activity was to identify data types, sources, formats, extents, links to non - spatial <br />data, and relevance to the project. This inventory evolved through the course of the project with data <br />layers being added as appropriate, and comments entered into the inventory table regarding data <br />availability, status of data collection, processing tasks conducted on data, and other relevant information. <br />This inventory (see Appendix A) forms the main record of Flood DSS Prototype data, data collection, and <br />data processing tasks. It quickly became obvious that a limited amount of spatial data were available <br />from the CWCB and that identifying additional sources for spatial data would need to occur. <br />2.3 Data Collection <br />The data inventory (Appendix A) was utilized to perform data collection activities. <br />Data that were collected were subsequently reviewed for suitability and were processed as appropriate for <br />inclusion in the prototype (see Section 2.4 Data Processing). <br />2.3.1 Statewide Data <br />The majority of statewide spatial data were available from the CWCB, or were created by the CWCB or <br />RTi by linking tabular data to spatial data using a join on common attributes such as county or city name <br />(e.g. National Flood Insurance Program [NFIP] City and NFIP County layers and the Flood History <br />layer). <br />2.3.2 Larimer County and the City of Fort Collins <br />Other major sources of spatial data were the City of Fort Collins and Larimer County. Both agencies <br />were helpful with provision of data, yet provided different experiences. Collection of data from the <br />County involved the arrangement of a face -to -face meeting to discuss the DSS, and to request appropriate <br />data for input into the system. Larimer County attempts to recover costs of their investment in GIS data <br />using a subscription service; however, this was waived following the meeting. The process of receiving <br />this waiver and access to the data involved Carolyn Fritz (CWCB) calling the data salesperson at Larimer <br />County to inform the salesperson the data were for a State project. The CWCB was then given a <br />username and password that allowed RTi to download all of the Larimer County GIS data. On request, <br />the County later provided metadata for various data layers. <br />Collection of data from the City of Fort Collins involved face -to -face meetings with the GIS Manager and <br />a City Floodplain Administrator to clarify what useful data existed. A Fort Collins GIS Analyst then <br />provided all requested data on CD. Contacts for both agencies are included in Table A.1. <br />2.3.3 Digitizing Data <br />Digitizing data can be a laborious and expensive effort; therefore, it was agreed at the kickoff meeting <br />that digitizing should be limited for the prototype. The only digitizing necessary was to generate an <br />example of the Flood Threat Bulletin and the 7 -15 Day Flood warning produced by HDR for CWCB. <br />R1 <br />