Laserfiche WebLink
<br />. <br /> <br />. <br /> <br />The activIties required to complete this foundational GIS database will include searching, <br />ordering and assessing the quality of data. Also, processing, editing and assimilating the data <br />layers into a coherent and comprehensive GIS database. <br /> <br />Approach: <br /> <br />94.1 Assess and Acquire Existing Coverages. Coverages to be assessed and acquired, and the <br />source and format of the data, are listed in Table 4. All data is expected to be in the public <br />domain or available from the State at no cost unless otherwise listed in Table 4. The <br />Contractor will assess data and make recommendations to the State as to which data should <br />be included in the GIS database. Based on the State's comments, the final GIS database will <br />be defined. <br /> <br />94.2 Produce Derived Coverages. All data sources will be converted to ArcView shapefile <br />format. The method of conversion will vary depending upon the source of data. USGS data <br />in general will be translated from DLG or SDTS format using ArclInfo and attribute data will <br />be added to the derived coverages. Data provided in section-township-range format will be <br />translated to the center of the appropriate section. The projection of all derived coverages <br />will be consistent with other CDSS products that are in UTM Zone 13, NAD27. <br /> <br />94.3 Cropping and Edge Matching of Coverages. All coverages acquired will be cropped to <br />cover the South Platte and North Platte River basins. Where several coverages must be <br />assembled, edge matching will be performed to the limits of the original data using ArclInfo. <br />Attribute data will be added as required to assure consistency when appending tiles to a <br />single seamless coverage. Where applicable, attribute fields will be added to maintain <br />consistency with existing state coverages developed for the CDSS. <br /> <br />94.4 Quality Assurance and Control. The GIS coverages will be checked for obvious errors <br />and inconsistencies in the original data. Corrections to the original data will be noted in the <br />metadata for the coverages. All coverages will also be checked and adjusted as necessary to <br />make sure that they register when displayed to assure they were derived in consistent units <br />and in the same projection. Also, coverages to be derived by the Contractor will also be <br />subjected to QA/QC procedures before incorporation into the SPDSS geodatabase. <br /> <br />Deliverables: <br /> <br />94.1 A memorandum detailing the structure and contents of the geodatabase. This document will <br />describe all coverages in the geodatabase, attributes associated with the coverages, <br />relationships with HydroBase, and editing rules for coverages. <br /> <br />94.2 Digital files, digital maps and up to five copies of 24x36 inch maps with all coverages in <br />Table 4 that are included in the geodatabase. The files and maps will be used for presenting <br />GIS deliverables and for assisting the other SPDSS contractors in executing their work. Each <br />digital map file will be provided in two formats consistent with other CDSS projects: <br />ArcView project files (.apr) and ArcExplorer project files (.aep). Each of these Arc projects <br />will include a layout and content that is consistent with other GIS products available under <br />the CDSS. <br /> <br />94.3 Metadata for all GIS deliverables developed in this task using FGDC compliant metadata <br />format as agreed with the State. Included in the metadata will be a description of known data <br /> <br />Page 13 of 26 Pages <br />