My WebLink
|
Help
|
About
|
Sign Out
Home
Browse
Search
WSPC05429
CWCB
>
Water Supply Protection
>
Backfile
>
18000-18999
>
WSPC05429
Metadata
Thumbnails
Annotations
Entry Properties
Last modified
7/29/2009 11:10:30 AM
Creation date
10/9/2006 5:13:20 AM
Metadata
Fields
Template:
Water Supply Protection
File Number
8283.200
Description
Colorado River Basin-Colorado River Computer Models-Colorado River Decision Support System-Ray
State
CO
Water Division
5
Date
1/1/1996
Author
CADSWES
Title
South Platte Water Rights Management System-Programmers Manual
Water Supply Pro - Doc Type
Report/Study
There are no annotations on this page.
Document management portal powered by Laserfiche WebLink 9 © 1998-2015
Laserfiche.
All rights reserved.
/
51
PDF
Print
Pages to print
Enter page numbers and/or page ranges separated by commas. For example, 1,3,5-12.
After downloading, print the document using a PDF reader (e.g. Adobe Reader).
Show annotations
View images
View plain text
<br />Q~uu70 <br /> <br />7 <br /> <br />Description <br /> <br />reach <br /> <br />nodeJecord <br /> <br />using an expensive algorithm and stored in the in-memory graph. It is much faster to <br />use the stored information than to derive this list every time it is needed. <br /> <br />In addition, the in-memory graph contains infonnation not available in the database. <br />For example, upstream-downstream relationships are not represented in the database, <br />yet operations requiring this information are simple to perform using the in-memory <br />network graph. Determining the current call at a diversion structure requires knowing <br />the call structure in place on the river, as well as upstream-downstream spatial rela~ <br />tionships between structures. The current call at a structure could not be determined <br />from the contents of the database alone, but by accessing both the database and the <br />spatial ArclInfo data. However, on-demand calculations using both of these sources <br />would be far too expensive. <br /> <br />The in-memory network graph is bupt from three primary components: reaches, <br />nodes, and node_link-pairs. A reach is a segment of the river system, corre- <br />sponding to a single arc in the Arc/Info stream network coverage. Nodes define the <br />ends of reaches, and are possible locations for confluences, stream gauges, or diver- <br />sion structures. Node_link_pairs are the structures that link the nodes and <br />reaches together to form a graph. <br /> <br />typedef struct { <br />(various members for graphic display) <br />lag_lass_record *lag_Ioss~record; <br />double length; <br />reach; <br /> <br />Where: <br /> <br />. lag_lass_record: A pointer to a lag_loss_record for a physical reach to <br />which this reach record refers. <br /> <br />. length: The length of the reach in meters. <br /> <br />The reach structure corresponds to a segment of the river as defined by a single arc in <br />the ArclInfo stream network coverage. Besides containing several numbers for <br />graphic display (of the current call structure), this structure contains a pointer to <br />lag_lass_record containing information about this reach. <br /> <br />typedef struct node_rec_struct{ <br />short node_id; <br />short type; <br />Boolean visited; <br />double current_call; <br />double previous_call; <br />node_l ink_pair *connected_upstream; <br />node_l ink_pair *connected_downstrearn; <br />Boolean is_confluence; <br />node_type_description *description; <br />node_location location; <br />struct node rec struct *next; <br />} node_record; <br />
The URL can be used to link to this page
Your browser does not support the video tag.