Laserfiche WebLink
<br />\~t -,'>-l . <br /> <br />OOOOG(} <br /> <br />South Platte Water Rights Management System <br /> <br />Spatial Data Types <br /> <br />Linear Data The map features used by the SPWRMS application are of two types -linear and point. <br />The layers which contain linear features, such as aqueducts, ditches, reservoirs, and <br />streams, were distilled from files purchased from the Earth Science Infonnation Center <br />(ESIC), a branch of the U.S. Geologic Survey (USGS) which handles digital cartographic <br />data. Layers containing point data, such as diversion structures and stream gauges, were <br />compiled by CADSWES personnel and digitized from various paper map sources. <br /> <br />Most of the data which make up the map layers were purchased from the ESIC. These data <br />were in the fonn of digital line graphs (DLGs) from the USGS 1: l00.ooo-scale topo- <br />graphic map series. DLGs consist of linear features which have many associated attributes <br />in a coded. numerical fonnat. Each quadrangle has four DLG layers of coded line infor- <br />mation. Only the hydrography layer, which contains all natural and human-made water <br />features, was used to develop data for SPWRMS database. <br /> <br />The South Platte River basin falls on portions of fifteen maps from the USGS <br />1: l00,ooo-scale topographic map series. Hydrography data were taken from the following <br />USGS quadrangles: Bailey. Castle Rock, Denver East, Denver West, Eaton, Estes Park, <br />Fott Collins, Fort Morgan. Greeley, Gunnison. Julesburg, Leadville. Pike's Peak. Sterling. <br />and Wray. <br /> <br />The DLG files obtained from ESIC were converted to Arc/Info layers using import utili- <br />ties. These layers were then mosaic-ed to produce one large coverage containing the <br />whole basin project area. Coded line attributes were preserved during the conversion from <br />DLG to Arc/Info format and used to separate the mosaic map into the six layers used by <br />the SPWRMS application. Specific data development considerations for each of these six <br />layers are mentioned in the following sections. . <br /> <br />Point Data Point data for SPWRMS database, such as locations and names of stream gauges and <br />diversion structures, were obtained primarily through personal contact with Division 1 <br />water officials. These data were entered into the spatial database by hand digitizing the <br />locations from paper 1 :24,000-scale topographic maps. <br /> <br />Streams Layer <br /> <br />The streams linear layer contains all rivers and tributaries in the project area which contain <br />diversion structures and/or stream gauges referenced by SPWRMS. This layer forms the <br />skeleton of the in-memory data structure (the network tree) used for modelling basin <br />dynamics. . <br /> <br />Development The spatial data of the streams layer required extensive manual editing to be developed <br />into a usable fonnat. The topology of this layer must be defined such that it can be used to <br />generate a directed graph connecting all stream gauges and diversion structures. There- <br />fore, aHline segments must be connected, have consistent direction and not be continuous <br />through a point where a gauge or structure is located. Problems with the raw data that <br />interfered with this topology were mismatched line segments where edge matching had <br />been performed between quadrangles, inconsistent line directions relative to flow direc- <br />tion, and line segments that did not break at the site of structures and stream gauges. <br />Arc/Info macros were developed by CADSWES for processing the stream network to <br />ensure that connectedness and directedness requirements were satisfied (hand editing was <br />performed where necessary). Where streams passed through a reservoir, one of the reser- <br /> <br />Database Manual 15 <br />