My WebLink
|
Help
|
About
|
Sign Out
Home
Browse
Search
WSPC00275
CWCB
>
Water Supply Protection
>
Backfile
>
12000-12999
>
WSPC00275
Metadata
Thumbnails
Annotations
Entry Properties
Last modified
7/29/2009 7:35:36 AM
Creation date
10/9/2006 2:03:19 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
7/22/1994
Title
Consumptive Use Modeling-Progress Report for June 1994
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.
/
10
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 />OGlj60 <br /> <br />Colorado River Decision Support System <br /> <br />Progress Report for June, 1994 <br /> <br />Task 1.06 Spatial Database Development (Phase IIa) <br /> <br />1.0 Technical progress this period: <br /> <br />Subtask 1: Populate Soatial Database <br /> <br />1, The main activities done for this subtask were data collection, revision, and the <br />dissecting of the state of data needed for the project, Spatial data were collected in <br />ARC/lNFO, ASCII, and DBase formal. Each of these formats needs to be <br />processed to migrate them into GRASS format and then converted into a UTM <br />projection and meter units, Finally, CRDSS areas are selected, this involves <br />clipping the data by the Colorado State boundaries (including a 100 mile buffer in <br />some cases) and then by selecting the area west of the continental divide, <br /> <br />2, Data currently in ARC/lNFO format include the following: <br /> <br />. Dams, basic data for reservoirs, These data were obtained in dbase format from <br />Division of Water Resources, State Engineer's Office in Greely and more work <br />needs to be done to populate the data, <br /> <br />. Population Density, used to determine residential consumptive use, This is from <br />1990 Census data from Tiger files, These data will be updated with 1992 census <br />data in the next month, <br /> <br />. General hydrography, surface water features, The stream network includes the <br />location of streams in vector format at SOOK scale, edited by Mario Mejia- <br />Navarro from SOOK scale USGS map, Currently we are working on the Tiger <br />files from DOLA as a potentially better source for these data, this would include <br />streams and ditches for the western slope, <br /> <br />. Elevation Contours, state contour lines every 250 meters elevation, lOOK scale, <br />built using Top030 from NOAA, It was originally provided in DOS format and <br />was converted to UNIX ARC/lNFO coverages by the USGS GIS departmenL A <br />TIN coverage was then created by Mario Mejia-Navarro and then reduced to a <br />lattice format which is the base for contour (arcs) and shade relief (grid) covers, <br /> <br />. Hydrologic Units, drainage boundaries, A 250Kscale data set was obtained from <br />the USGS in addition to the 2,000K data previously gathered, <br /> <br />. Irrigated Parcels of Land, crop type for irrigated land areas, obtained through the <br />Colorado DepL of Natural Resources Division of Water Resources, A <br />preliminary overview showed some data missing, therefore additional work <br />needs to be done to identify these data gaps, <br /> <br />3, The procedure for transferring the data from ARC/lNFO to GRASS has been <br />explored, <br /> <br />Subtask 2: Establish GIS Infomix Link <br /> <br />L We have two datasets-- irrig, acre coverage and the dams file-- that have both <br />township-range-section data as well as latitude-longitude data available, The irrig, <br />acre coverage was supplied with township-range-section data and the label points <br />
The URL can be used to link to this page
Your browser does not support the video tag.