Laserfiche WebLink
<br />.., ~..' ~ <br /> <br />000062 <br /> <br />South Platte Water Rights Management System <br /> <br />more, changes in a single map layer require changes in other layers in order to maintain <br />consistency within the spatial database. <br /> <br />lr is helpful to keep in mind that the three primary map layers-stream gauges, structures. <br />and the stream network-are the only map layers which are associated in any way with the <br />relational side of the data model. The remaining layers are simply display layers <br />containing information that the application draws for locational context. The procedures <br />for making modifications to the three primary layers are inherently complex due to the <br />relationship between these layers and the relational tables, while modifications to the <br />display layers are relatively simple. <br /> <br />As described in an earlier section, the SPWRMS application traces the arcs of the stream <br />network layer to find points in the structures and gauges layers. The tracing algorithm <br />requires that: 1) points in the structures and gauges layers lie on one of the arcs in the <br />stream network, 2) a node occurs in the network layer at the site of each of those point, <br />and 3) a number identifying the corresponding stream network node is attached to the <br />points in the structures and gauges layers. Modifications of the spatial layers can cause <br />renumbering of nodes and points within ArclInfo. For this reason, changes in any of these <br />three layers requires that the other layers be updated to reestablish the stream network <br />relationship. <br /> <br />Additions to the set of points in the spatial layers (structures and streamgauges) must be <br />performed in conjunction with additions to the relational tables. If a new stream gauge is <br />added to the spatial database. there must be a new entry in the gagingstations table. which <br />contains the gauge name as well as other information about that gauge. Similarly, when a <br />new diversion structure is added to the spatial database, it must be verified that the proper <br />entries exist for that structure in the structures and rights tables within the rela~ianal data- <br />base. New entries to the relational tables may be necessary if the new diversion structure <br />represents a new Water Court decree. <br /> <br />Laglloss reaches within the SPWRMS application have been defined as the smallest iden- <br />tifiable unit on the stream network. In other words, a reach is a section of the stream <br />network that lies between two adjacent points of interest (structures, stream gauges, or <br />confluences). If a new point of interest is added to the spatial database, two new reaches <br />are defined by splitting an existing reach. <br /> <br />Map layers which contain line data, such as the stream nerwork layer. are partially defined <br />by an Arcllnfo binary file describing the location of lines in the layer. This file. used by the <br />SPWRMS application for displaying the map layers, must be recreated after any changes <br />are made to the configuration of lines in the layer. In addition to this binary file, a second <br />binary file defining polygon topology exists for the reservoirs layer. Both binary files must <br />be recreated after changes are made to the reservoirs layer. <br /> <br />Modifying Display-Only Coverages <br /> <br />This section is intended to provide guidelines for maintaining SPWRMS Data. It is meant <br />to be used by persons experienced in the use of Arcllnfo. UNIX, and Infonnix SQL. As <br />such, not every command necessary to perform an operation is included. <br /> <br />The coverages used by SPWRMS for display-only purposes (see Table 4) can be modified <br />without referencing the changes to the stream network. Any changes made within these <br />coverages are immediately available to SPWRMS. <br /> <br />Database Manual <br /> <br />19 <br />