rr_hydra

Metadata also available as

Metadata:


Identification_Information:
Citation:
Citation_Information:
Originator:
The original statewide layers of HYDROLINES and HYDROPOLYGONS were developed as coverages named hydrarca and hydrpola by the Teale Data Center and the California Department of Fish and Game. Rr_hydra.shp was created by Circuit Rider Productions, Inc. Rr_hydra represents a portion of the hydrarca coverage that describes the streams of the Russian River basin. The hydrarca line features were selected based on their spatial location within the extent of the Russian River basin. The resulting selection is what forms this layer, illustrating the streams of the Russian River basin. This metadata file incorporates information that is specific to this layer as well as information that is available in the original metadata file for the HYDROLINES and HYDROPOLYGONS coverages (hydrogra.txt). Portions of this metadata file that borrow text from hydrogra.txt are indicated in quotation marks.
Publication_Date:
September 2002..
Title: rr_hydra
Geospatial_Data_Presentation_Form: vector digital data
Online_Linkage: \\DAVID\C$\rrgis_phase_1\Base\rr_hydra.shp
Description:
Abstract:
"The hydrography layer consists of flowing waters (rivers and streams),
standing waters (lakes and ponds), and wetlands -- both natural and manmade.
Two separate feature types are represented: polygons (areas) and lines.
Polygon features have attribute codes that identify water bodies such as
lakes, wide river segments, or swamps. Line features have attribute codes
that represent streams or shorelines."
Purpose:
Users can utilize this layer for the purposes of mapping the flowing waters of the Russian River basin at 1:100,000. For additional applications, refer to the documentation included in the "Supplemetal Information" portion of this metadata file.

Supplemental Information:
The information included below is taken directly from the hydrogra.txt meatadata file that describes the hydrarca and hydrpola coverages developed by the Teale Data Center and the California Department of Fish and Game. This information is included for reference purposes, as it directly describes the original source data from which this layer was created.

"The following are subjective comments regarding this data.

The USGS DLG features of this layer are fairly complete. The density of
line work representing drainage networks appears to vary arbitrarily from
quad to quad, and there are discontinuities in lines depicting streams at
the edges of 100k quads. The geographic feature accuracy is fair.
Contiguous features are not always matched across map sheet boundaries.
The attribute completeness and accuracy of MAJOR/MINOR code pairs is good.
The US EPA River Reach File version 3-alpha (RF3-alpha) as archived at
Teale is an alpha release (prototype). As such, users are cautioned to
verify drainage network connectivity and water feature names before
undertaking extensive processing using RF3 data.

County lines (a separate Teale data layer) and hydrography lines are not
reconciled with each other and discrepancies between the two will occur
when a county boundary follows a water feature.

-----

SUPPLEMENTARY INFORMATION (courtesy of Calif. Department of Fish and Game)

In 1993, US EPA changed the Reach File table DS2 to DS3 and changed the
MILE and related items from numeric type to character type. No data content
changes were made. DFG compiled over 150 US EPA National Computer Center
(NCC) CU-based DS3 tables into a set of 33 Teale tile-based tables in
October 1996. DFG and cooperators have also made extensive corrections
and additions of primary names/name codes in the DS3 tables. Forwarding
of these updates is expected in October 1996 to US EPA for inclusion in
RF3 final processing.

The DS3 item UPDTSRC1 concatenates HYSNUM and HSCKEY (in that order) for
those records that have a corresponding AAT record. UPDTSRC1 contains the
value 9999 for DS3 records created by US EPA that have no corresponding
record in the hydrography layer. UPDTSRC1 contains leading zeroes for
single-digit HYSNUM values. The Teale primary key, TDCKEY, is similar to
UPDTSRC1 except that the concatenation order is HSCKEY + HYSNUM."

"The hydrography layer was assembled from data originally published by the
U.S. Geological Survey (USGS) in Digital Line Graph (DLG-3) format.
DLG-3 data were generated by USGS from 1:100,000-scale maps by manual
digitizing and raster scanning. Approximately 3200 original USGS DLG files
were processed by Teale to create the statewide hydrography data layer.

Edits to the original linework have been made during the data conversion by
Teale from the original DLG-3 format to the ARC/INFO(tm) GIS format. Such
changes include line movements (due to the map edge-matching process), minor
corrections of attribute coding, and the closing of open polygons. Flow
direction for streams (feature type line) has also been added. Stream arcs are
flagged (where item FLOW = 1) to indicate whether or not the direction of
a given stream (line) has been defined and/or verified by Teale.

Hydrography of the entire state is stored in 2 statewide coverages and in 33
separate ARC/INFO coverages or tiles. Statewide coverage names HYDRARCA (arc
feature type) and HYDROPOLA (polygon feature type). The tiles coverages
whose individual boundaries correspond to the USGS 1:250,000-scale quad series
(see index coverage called hydroindexa and index diagram below). Coverage
names consist of two unique characters plus a suffix -JHYSA. Most of the
two-letter codes abbreviate a quad name, for example: RDJHYSA, for the Redding
quad. The tiles are also numbered from 1 to 33, northwest to southest, and
this numeric code is contained in the item HYSNUM. A separate item, HSCKEY,
contains a number unique to each arc within a tile. HSCKEY and HYSNUM are
combined to form a primary key item, TDCKEY, which uniquely identifies every
hydrography arc record statewide.

In 1992, the Teale hydrography data layer was sent upon request to the U.S.
Environmental Protection Agency (US EPA) Office of Water for use as a basemap
for the River Reach File version 3-alpha, also known as Reach File 3 or
RF3-alpha. RF3 is US EPA's national hydrographic addressing system which
contains unique water feature identification codes, names, and update
documentation. RF3 was developed by Horizon Systems Corporation, under
contract to the US EPA Office of Water. RF3 as archived at Teale consists of
a separate data table for each of the 33 Teale hydrography coverages,
designated by the filename extension .DS3 (for example: RDJHYSA.DS3).

Hydrographic feature records in Teale's arc attribute tables (AAT) may be
related (linked or joined) with corresponding RF3 records in DS3 tables on
the item TDCKEY, which is present in both tables. Users are cautioned to
verify the integrity of AAT - DS3 relations, as instances of many DS3 records
relating to one AAT record are known to occur. Use of the relate item
RF3RCHID in older versions of Teale AATs has been discontinued.

Statewide hydrographic feature records in Teale's polygon attribute table (PAT)
may be related (linked or joined) with corresponding WRCB records in DAT
table on the item wrcblakes, which is present in both PAT and DAT tables.

Reach File data, documentation, and technical support are provided through
the US EPA Office of Water's STORET User Assistance Group at 800-424-9067.
STORET is the US EPA's national water quality information system.

-----

UPDATES


December 1998
-------------

Added in statewide polygon and line coverages, areas that were removed from
Nevada and Arizona. The "STATECODE" attribute is also added to identify features
are:

1- Completely within CA
2- Partially with CA
3- Completely outside CA

PNAME and PNMCD attributes are added to the statewide line feature coverage.
attributes were extracted from the Reach File DS3 table.

NAME attribute is added to the STATEWIDE and the TILE (250K quad) polygon
coverages. Features included lakes, ponds, reservoirs, etc., the names were
manually entered based on the USGS's 100K quad maps. Names from the 24K quad
maps and the DFG's lakes coverage were used respectively to populate names
where names were not found on the USGS's 100K quad maps.

An additional database of lakes species/environment quality and ecological
factors was attached to the statewide polygon coverage. New item WRCBLAKES
in the PAT table will be is used to relate records to the HYDRPOLA.DAT table.
The DAT table came from DFG's lakes coverage lakes.DAT table. See table
description below for detail.

Added Appendix A (EPA River Reach File detail attribute descriptions) to the
documentation.


November 1998
-------------

Posted current version of DS3 table with DFG's updates. Approximately 3400
records were updated. Names, name codes and RF3 identifiers were entered and
corrected by DFG in cooperation with the CA Rivers Assessment (CARA) program
at UC Davis. Updates were flagged in the item UPDTSRC2 in each DS3 table.

Lookup tables contain descriptions of the hydrographic features in the polygon
and line coverages. Tables are available for each of the 33 tile coverages and
the statewide Teale hydrography coverages. These separate lookup tables carry
all the MINOR codes and a description for each. Lookup tables are named
with an .LUT file name extension (for example: WEJHYSA.LUT).


May 1998
--------

Attribute updates in 6 quad coverages and in the statewide polygon coverage.
Enhanced MINOR1 and MINOR2 codes.
ACJHYSA
SJJHYSA
SOJHYSA
FOJHYSA
ZPJHYSA
MZJHYSA


April 1997
----------

New edition of River Reach (DS3) files. DFG and UC Davis enhanced RF3
attributes (primarily stream names and unique codes).


February 1997
-------------

DFG reported inconsistency in DLG MINOR1 coding in Amboy (100k quad name),
99% of arcs were coded as WASHES. Apparently localized in a single 100K
quad. Modification were made so the coding consistent with the adjacent
quads. The changes were made to 2 coverages: NEJHYSA and KIJHYSA.


1996
----

The California Department of Fish and Game (DFG) assembled the most current
RF3 tables from copies downloaded directly from US EPA's National Computer
Center (NCC) in September 1996. These DS3 tables, organized by hydrologic
basins, were appended and Teale tile-based tables extracted from them.
A significant volume of water feature names/name codes and RF3
identifiers were input and corrected by DFG in cooperation with the
California Rivers Assessment (CARA) program at UC Davis. All such updates
are flagged in the item UPDTSRC2 in each DS3 table."

Time_Period_of_Content:
Time_Period_Information:
Single_Date/Time:
Calendar_Date:
Last update made in September 1998..
Currentness_Reference:
Original source data: USGS DLG-3.
Status:
Progress:
Complete.
Maintenance_and_Update_Frequency:
None scheduled.
Spatial_Domain:
Bounding_Coordinates:
West_Bounding_Coordinate: -123.381694
East_Bounding_Coordinate: -122.530543
North_Bounding_Coordinate: 39.395694
South_Bounding_Coordinate: 38.306986
Keywords:
Theme:
Theme_Keyword_Thesaurus:
hydrology
Theme_Keyword:
Russian River, Sonoma County, Mendocino County, watersheds
Access_Constraints:
None.
Use_Constraints:
 
The responsibility of the risks associated in regards to the results and representations of using this type of spatial data is understood by the user. In all cases, the user should refer to the associated metadata files or the original source data for accuracy, currentness and appropriate contact information. CRP shall not have any liability to any person or entity with respect to liability, loss or damage caused or alleged to be caused directly or indirectly by information contained in this file.
 
Native_Data_Set_Environment:
Microsoft Windows 2000 Version 5.1 (Build 2600) ; ESRI ArcCatalog 8.2.0.700

Spatial_Data_Organization_Information:
Direct_Spatial_Reference_Method: Vector
Point_and_Vector_Object_Information:
SDTS_Terms_Description:
SDTS_Point_and_Vector_Object_Type: String
Point_and_Vector_Object_Count: 2095

Spatial_Reference_Information:
Horizontal_Coordinate_System_Definition:
Planar:
Grid_Coordinate_System:
Grid_Coordinate_System_Name: Universal Transverse Mercator
Universal_Transverse_Mercator:
UTM_Zone_Number: 10
Transverse_Mercator:
Scale_Factor_at_Central_Meridian: 0.999600
Longitude_of_Central_Meridian: -123.000000
Latitude_of_Projection_Origin: 0.000000
False_Easting: 500000.000000
False_Northing: 0.000000
Planar_Coordinate_Information:
Planar_Coordinate_Encoding_Method: coordinate pair
Coordinate_Representation:
Abscissa_Resolution: 0.000256
Ordinate_Resolution: 0.000256
Planar_Distance_Units: meters
Geodetic_Model:
Horizontal_Datum_Name: North American Datum of 1983
Ellipsoid_Name: Geodetic Reference System 80
Semi-major_Axis: 6378137.000000
Denominator_of_Flattening_Ratio: 298.257222

Entity_and_Attribute_Information:
Detailed_Description:
Entity_Type:
Entity_Type_Label: rr_hydra
Attribute:
Attribute_Label: FID
Attribute_Definition: Internal feature number.
Attribute_Definition_Source: ESRI
Attribute_Domain_Values:
Unrepresentable_Domain:
Sequential unique whole numbers that are automatically generated.
Attribute:
Attribute_Label: Shape
Attribute_Definition: Feature geometry.
Attribute_Definition_Source: ESRI
Attribute_Domain_Values:
Unrepresentable_Domain: Coordinates defining the features.
 
" ARC ATTRIBUTE TABLE (AAT)

DATAFILE NAME: <xx>JHYSA.AAT where xx = tile code (see index)

LINE attribute fields (USGS DLG Hydrography line elements):

COLUMN ITEM NAME WIDTH OUTPUT TYPE N.DEC
-------------------------------------------------------------

1 FNODE# 4 5 B -
5 TNODE# 4 5 B -
9 LPOLY# 4 5 B -
13 RPOLY# 4 5 B -
17 LENGTH 8 18 F 5
25 <xx>JHYSA# 4 5 B -
29 <xx>JHYSA-ID 4 5 B -
33 MAJOR1 4 6 B - described below
37 MINOR1 4 6 B -
41 MAJOR2 4 6 B -
45 MINOR2 4 6 B -
49 MAJOR3 4 6 B -
53 MINOR3 4 6 B -
57 MAJOR4 4 6 B -
61 MINOR4 4 6 B -
65 MAJOR5 4 6 B -
69 MINOR5 4 6 B -
73 FLOW 1 1 I -
74 TDCKEY 8 8 I - primary key
82 DCU 8 8 I - DFG-inserted CU
90 PNAME 30 30 C - RF3 attribute, Primary name
of surface water feature
120 PNMCD 11 11 C - RF3 attribute, Primary name
code
131 STATECODE 1 1 C - 1 - completely within CA
2 - partially with CA
3 - completely outside CA
** REDEFINED ITEMS **
74 HSCKEY 6 6 I - described below
80 HYSNUM 2 2 I - described below


FNODE# : The id number of the node feature that represents
the beginning point (the From NODE) of the arc.

TNODE# : The id number of the node feature that represents
the ending point (To NODE) of the arc.

LPOLY# : The <coverage name># id of the polygon that lies to the
left of this arc when facing in the direction of the
TNODE.

This is blank if there is no polygon topology.


RPOLY# : The <coverage name># id of the polygon that lies to the
right of this arc when facing in the direction of the
TNODE.

This is blank if there is no polygon topology.

LENGTH : The length of the arc in coverage units.

<xx>JHYSA# : The software-assigned unique integer identification
number.

<xx>JHYSA-ID : A user-assigned identifier number.
Where <xx>JHYSA-ID is negative (-ID < 0), arc is an
artificial neat line (coverage or tile boundary).

MAJOR[1 - 5]: See below.

MINOR[1 - 5]: See below.

FLOW: If equal to 1, flow direction is defined; if equal
to 0, no direction is defined.

TDCKEY: Concatenates HSCKEY + HYSNUM to form a primary key for
all hydro features statewide; links hydrography features
in .AAT to US EPA River Reach File (RF3) records in DS3.

DCU: Item inserted by DFG into Teale AAT; was derived from DFG-refined
Cataloging Unit (CU) boundaries for use with USGS 1:100K hydrography.
Coverage in development "hucdfg1d" was used to resolve cases where
more than one RF3RCHID related to a single Teale feature. Unresolved
CU boundaries still exist in vicinity of Central Valley and Delta.
Expect minor changes to DCU as CU boundaries are refined and
standardized.

PNAME: Primary Name of water feature (see Appendix A for details).

PNMCD: Primary Name Code of water feataure (see Appendix A for details).

STATECODE: Identifies feature location: 1 - completely within CA state
boundary, 2 - outside of CA or 3 - partially with CA. This
is useful for reselecting to get just the state for cartographic
purposes.

HSCKEY: Unique number for each hydrographic feature within a single
tile. Ranges from 1 to over 20,000 in some tiles. Item was
created for RF3 use. Concatenated with HYSNUM to create TDCKEY.

HYSNUM: Hydrography tile sequence number, ranges from 1 to 33.
Item was created for RF3 use.
Concatenated to HSCKEY to produce TDCKEY.

MAJOR1-5: Major codes denote hydrography (code 50) as the major
feature category to which a line element belongs (as
opposed to property boundaries, roads, etc within DLGs).

MINOR1-5: Minor codes assign up to five descriptive subcategories
to any single hydrography line element.

Major Minor
Code # Code # Element Description
------ ------ -------------------
50 200 Shoreline
50 201 Man-made shoreline
50 202 Closure line
50 203 Indefinite shoreline
50 204 Apparent Limit
50 205 Outline of a Carolina bay
50 206 Danger curve
50 400 Rapids
50 401 Falls
50 402 Gravel pit/quarry filled w/water
50 403 Gauging station
50 404 Pumping station
50 405 Water intake
50 406 Dam or weir
50 407 Canal lock or sluice gate
50 408 Spillway
50 409 Gate(flood,tidal,head,check)
50 410 Rock
50 411 Crevasse
50 412 Stream
50 413 Braided stream
50 414 Ditch or canal
50 415 Aqueduct
50 416 Flume
50 417 Penstock
50 418 Siphon
50 419 Channel in water area
50 420 Wash or ephemeral drain
50 421 Lake or pond
50 422 Coral reef
50 423 Sand in open water
50 424 Spoil area
50 425 Fish ladders
50 601 Underground
50 602 Overpassing
50 603 Elevated
50 604 Tunnel
50 605 Right bank
50 606 Left bank
50 607 Under construction
50 608 Salt
50 609 Unsurveyed
50 610 Intermittent
50 611 Abandoned or discontinued
50 612 Submerged or sunken
50 613 Wooded
50 614 Dry
50 615 Mineral or hot ( sulphur, alkali, etc. )
50 616 Navigable transportation
50 617 Underpassing
50 618 Earthen construction
50 000 Photo-revised feature
05N --- Water surface elevation, actual or
interpolated.
N = elevation units
1 = feet
2 = meters
6 = feet below datum
7 = meters below datum

053 --- Angle of clockwise rotation (nearest
whole degree)
055 --- River mile, value in four spaces, right
justified
058 000 Best estimate of classification or
position
059 0-- Coincident feature
----

RELATED TABLE

The US EPA River Reach File version 3 (RF3-alpha) DS3 table structure
is presented below. One DS3 table exists for each of the 33 ARC/INFO
hydrography coverages. Each DS3 table is related to its respective
hydrography coverage arc attribute table (AAT) on the item TDCKEY.
The file is sorted by TDCKEY in sequential order.

Reach File Reference Information and DS3 attribute Descriptions, please see
appendix A below or go to the World Wide Web site:
http://www.epa.gov/OWOW/NPS/rf


US EPA River Reach File, version 3-alpha (RF3-alpha) attributes:

DATAFILE NAME: <xx>JHYSA.DS3 Where xx = tile code (see index)
RECORD LENGTH: 433

COL ITEM NAME WIDTH TYPE DESCRIPTION (see details below)
------------------------------------------------------------------------
1 TDCKEY 8 I Teale hydrography primary key
9 CU 8 I Cataloging Unit (aka HUC); 149 total in CA
17 SEG 4 I Segment, unique within a CU
21 MI 5 C Marker Index, unique within a SEG
26 UPMI 5 C Upstream Marker Index
31 RFLAG 1 C Routing flag (0,1)
32 OWFLAG 1 C Open Water reach flag (0,1)
33 TFLAG 1 C Terminal reach flag (0,1)
34 SFLAG 1 C Start reach flag (0,1)
35 REACHTYPE 1 C Type of Reach (A to Z)
36 LEVEL 2 I Stream level code
38 JUNC 2 I Level of downstream reach
40 DIVERGENCE 1 I Divergent junction type code
41 USDIR 1 C Direction of flow of upstream reach
42 TERMID 5 I Terminal stream ID
47 TRMBLV 1 I Terminal base level code
48 PNAME 30 C Primary name of surface water feature
78 PNMCD 11 C Primary name code
89 CNAME 30 C Compliment name
119 CNMCD 11 C Compliment name code
130 OWNAME 30 C Open water name
160 OWNMCD 11 C Open water name code
171 DSCU 8 I Downstream CU
179 DSSEG 4 I Downstream SEG
183 DSMI 5 C Downstream MI
188 CCU 8 I Compliment CU
196 CSEG 4 I Compliment SEG
200 CMI 5 C Compliment MI
205 CDIR 1 C Compliment direction, looking upstream
206 ULCU 8 I Upstream, left CU
214 ULSEG 4 I Upstream, left SEG
218 ULMI 5 C Upstream, left MI
223 URCU 8 I Upstream, right CU
231 URSEG 4 I Upstream, right SEG
235 URMI 5 C Upstream, right MI
240 SEGL 6 N Length of reach (miles and hundredths)
246 RFORGFLAG 1 I Reach File origin flag (1,2,3)
247 ALTPNMCD 8 I Alternate primary name code
255 ALTOWNMC 8 I Alternate open water name code
263 DLAT 8 N Downstream latitude (decimal degrees)
271 DLONG 8 N Downstream longitude
279 ULAT 8 N Upstream latitude
287 ULONG 8 N Upstream longitude
295 MINLAT 8 N Minimum latitude
303 MINLONG 8 N Minumum longitude
311 MAXLAT 8 N Maximum latitude
319 MAXLONG 8 N Maximum longitude
327 NDLGREC 4 I Number of DLG records
331 LN1AT2 4 I DLG line attribute
335 LN2AT2 4 I DLG line attribute
339 AR1AT2 4 I DLG area attribute
343 AR1AT4 4 I DLG area attribute
347 AR2AT2 4 I DLG area attribute
351 AR2AT4 4 I DLG area attribute
355 UPDATE1 6 C Update date #1
361 UPDTCD1 8 C Update code #1
369 UPDTSRC1 8 C Update source #1
377 UPDATE2 6 C Update date #2
383 UPDTCD2 8 C Update code #2
391 UPDTSRC2 8 C Update source #2
[DFG Note: all DFG updates are flagged
in item UPDTSRC2; details below]
399 UPDATE3 6 C Update date #3
405 UPDTCD3 8 C Update code #3
413 UPDTSRC3 8 C Update source #3
421 DIVCU 8 I Divergent CU
429 DIVSEG 4 I Divergent SEG
433 DIVMI 5 C Divergent MI
438 DLGID 6 I DLG number (special use)
444 FILLER 7 C Empty character field (future use)
** REDEFINED ITEMS **
9 RF3RCHID 17 C ID of instant reach (RF3-alpha primary key)
171 DSRF3RCHID 17 C ID of reach downstream of instant reach
188 CURF3RCHID 17 C ID of reach compliment to instant reach
206 ULRF3RCHID 17 C ID of reach upstream left of instant reach
223 URRF3RCHID 17 C ID of reach upstream right of instant reach
421 DIVRF3RCHID 17 C ID of reach divergent from instant reach

-----


POLYGON ATTRIBUTE TABLE (PAT)

DATAFILE NAME: <xx>JHYSA.PAT
RECORD LENGTH: 56

POLYGON attribute fields (USGS DLG Hydrography Area Elements):

COLUMN ITEM NAME WIDTH OUTPUT TYPE N.DEC
-----------------------------------------------------

1 AREA 8 18 F 5
9 PERIMETER 8 18 F 5
17 <xx>JHYSA# 4 5 B -
21 <xx>JHYSA-ID 4 5 B -
25 MAJOR1 4 6 B -
29 MINOR1 4 6 B -
33 MAJOR2 4 6 B -
37 MINOR2 4 6 B -
41 MAJOR3 4 6 B -
45 MINOR3 4 6 B -
49 MAJOR4 4 6 B -
53 MINOR4 4 6 B -
57 NAME 30 30 C -
87 STATECODE 1 1 C -


AREA : The area of the polygon in square coverage units.

PERIMETER : The length of the polygon perimeter of the polygon
in coverage units.

<xx>JHYSA# : The software-assigned unique integer identification
number.

<xx>JHYSA-ID : A user-assigned identification number.

MAJOR1-4: Major codes denote hydrography (code 50) as the major
feature category to which an area element belongs.

MINOR1-4: Minor codes assign up to four descriptive subcategories
to any single hydrography area element.

NAME : Feature name (name of a lake, reservior, etc.).

STATECODE: Identifies feature loacation: 1 - completely within CA state
boundary, 2 - outside of CA or 3 - partially with CA. This
is useful for reselecting to get just the state for cartographic
purposes.


Major Minor
Code # Code # Element Description
------ ------- -------------------
50 100 Alkali flat
50 101 Reservoir
50 102 Covered reservoir
50 103 Glacier or permanent snowfield
50 104 Salt evaporator
50 105 Inundation area
50 106 Fish hatchery or farm
50 107 Industrial water impoundment
50 108 Area to be submerged
50 109 Sewage disposal pond/filtration bed
50 110 Tailings pond
50 111 Marsh, wetland, swamp, bog
50 112 Mangrove area
50 113 Rice Field
50 114 Cranberry bog
50 115 Flats(tidal, mud, sand, gravel)
50 116 Bays, estuaries, gulfs, oceans, seas
50 117 Shoal
50 118 Soda evaporator
50 119 Duck pond
50 400 Rapids
50 401 Falls
50 402 Gravel pit/quarry filled w/water
50 403 Gauging station
50 404 Pumping station
50 405 Water intake
50 406 Dam or weir
50 407 Canal lock or sluice gate
50 408 Spillway
50 409 Gate(flood, tidal, head, check)
50 410 Rock
50 411 Crevasse
50 412 Stream
50 413 Braided stream
50 414 Ditch or canal
50 415 Aqueduct
50 416 Flume
50 417 Penstock
50 418 Siphon
50 419 Channel in water area
50 420 Wash or ephemeral drain
50 421 Lake or pond
50 422 Coral reef
50 423 Sand in open water
50 424 Spoil area
50 425 Fish ladders
50 601 Underground
50 602 Overpassing
50 603 Elevated
50 604 Tunnel
50 605 Right bank
50 606 Left bank
50 607 Under construction
50 608 Salt
50 609 Unsurveyed
50 610 Intermittent
50 611 Abandoned or discontinued
50 612 Submerged or sunken
50 613 Wooded
50 614 Dry
50 615 Mineral or hot (sulphur, alkali,etc.)
50 616 Navigable transportation
50 617 Underpassing
50 618 Earthen construction
50 000 Photo-revised feature

----

RELATE ATTRIBUTE TABLE (DAT)

DATAFILE NAME: HYDRPOLA.DAT )
RECORD LENGTH: 1118

Statewide file, sorted in WRCBLAKES sequential order.
* = see below for unique codes

COLUMN ITEM NAME WIDTH OUTPUT TYPE N.DEC
-----------------------------------------------------

1 AREA 4 12 F 3
5 PERIMETER 4 12 F 3
9 WRCBLAKES# 4 5 B -
13 WRCBLAKES-ID 4 5 B -
17 F_G_CD 1 1 C - Need code
18 OWNER 34 34 C - Owner
52 OWNRTYPE 3 3 C - Owner Type
(Code): BPP, PRV, PUB
55 REC_NUM 40 40 C -
95 MAX_AREA 16 16 I - Maximum Area (Units??)
111 MXAREF 7 7 C - Code??
118 SUM_SURF 16 16 I - Summer Surface area??
134 S_S_REF 7 7 C -
141 MAXDEPTH 16 16 I - Maximum Depth (Units?)
157 M_D_REF 7 7 C -
164 AB_G_F1 20 20 C - something about fish species
184 AB_G_F2 20 20 C - ""
204 AB_G_F3 20 20 C - ""
224 OTH_NAM 25 25 C - Other Lake Name
249 DEP_FL 16 16 I -
265 DP_F_REF 7 7 C -
272 MIN_SURF 16 16 I - Minimum surface area??
288 M_S_REF 7 7 C -
295 PRI_PROD 16 16 I - Primary Productivity
311 L_Q_REF 7 7 C - empty
318 DAM 16 16 I - Dam?? (numeric)
334 D_NAME 25 25 C - Dam name
359 LATITUDE 9 9 C - Latitude
368 LATD 2 2 I - Latitude, Degrees
370 LATM 2 2 I - Latitude, Minutes
372 LATS 4 4 N 1 Latitude, Seconds
376 LONGITUD 10 10 C - Longitude
386 LOND 3 3 I - Longitude, Degrees
389 LONM 2 2 I - Longitude, Minutes
391 LONS 4 4 N 1 Longitude, Seconds
395 TOWNSHIP 13 13 C - Township
408 OPERATOR 25 25 C - Operator of Dam?
433 INFLOW1 15 15 C - Inflow Stream 1
448 INFLOW2 15 15 C Inflow Stream 2
463 INFLOW3 15 15 C - Inflow Stream 3
478 MAX_VOL 16 16 I - Maximum Volume (units)
494 M_V_REF 7 7 C -
501 MIN_VOL 16 16 I - Minimum Volume (units)
517 AV_DPTH 16 16 I - Average Depth (units)
533 A_D_REF 7 7 C -
540 N_G_FSH1 20 20 C - something with fish species
560 N_G_FSH2 20 20 C - ""
580 N_G_FSH3 20 20 C - ""
600 FISH_YLD 16 16 I - Fish Yield ? (units)
616 F_Y_REF 7 7 C -
623 FSH_CROP 16 16 I - Fish Crop?/
639 F_C_REF 7 7 C -
646 EUPHOT 4 4 C -
650 E_Z_REF 7 7 C -
657 THERMO 16 16 I -
673 COUNTY 40 40 C - County
*713 QUAD 12 12 C - Quadcodes?
725 OUTFLOW 15 15 C - Outflow Stream
740 DRN_AREA 16 16 I -
756 D_A_REF 7 7 C -
763 ELEVAT 16 16 I - Elevation of lake in feet
779 ELE_REF 7 7 C -
786 T_S_REF 7 7 C -
793 DOM_FSH1 20 20 C - Dominant Fish 1?
813 DOM_FSH2 20 20 C - Dominant Fish 2?
833 DOM_FSH3 20 20 C - Dominant Fish 3?
853 D_F_REF 7 7 C -
860 NUISANCE 24 24 C - Nuisance - Codes?
884 N_REF 7 7 C -
891 IMP_WTR 16 16 I -
907 I_W_REF 7 7 C - Empty
914 LKNAM_FM 25 25 C - Lake name
939 LAK_NM_F 16 16 I - Lake name code??
955 ACC_FMT 9 9 C - Open/closed/fee/desig
964 LAK_FMT 11 11 C - Lake/reservoir/etc/
975 ACCR_FM 8 8 C - time periods
983 CAL_FM 10 10 C - Empty
993 TRO_FM 12 12 C - trophic level???
1005 FISH_FM 13 13 C - Fish productivity??
1018 FSHRY_FM 7 7 C - Fishery temperature related?
1025 F_PLT_FM 8 8 C - Fish planting
1033 SIGN_FM 3 3 C - No/yes?? Sign for lake name
1036 STRAT_FM 3 3 C - No/yes??
1039 OFLO_FM 3 3 C - No/yes??
1042 N_PK_FM 19 19 C - National Park
1061 N_F_FM 14 14 C - National Forest
1075 W_P_FM 19 19 C - Wilderness area??
1094 DWR_FM 16 16 C - District??
1110 LAK_Q_FM 4 4 C - Lake quality
1114 LAKES 1 1 I - Matched to lakes.pat
1115 WRCBLAKES 4 5 B - Primary key"


 
 
INDEX TO 1:100,000 DLG HYDROGRAPHY

ARC/INFO coverage names are composed of the prefixes shown in the statewide
grid below (some are abbreviations of the USGS 1:250,000-scale quad map
series names), plus the suffix JHYSA for the line and polygon data layers
(for example, RDJHYSA, for the Redding quad).

The item HYSNUM in the ARC/INFO feature attribute tables contains the
indicated numeric values to reference the tile within which a given
feature falls.

HYSNUM QUAD NAME
126 124 122 120W
42N _____ OREGON _____ 1 CRESCENT CITY
| ZF | WE | AC | 2 WEED
| 1 | 2 | 3 | N 3 ALTURAS
41 |_____|_____|_____| E 4 EUREKA
| EA | RD | XJ | V 5 REDDING
| 4 | 5 | 6 | A 6 SUSANVILLE
40 |_____|_____|_____| D 7 UKIAH
| UK | CQ | A 8 CHICO
| 7 | 8 | 118 9 SANTA ROSA
39 |_____|_____|_____ 10 SACRAMENTO
| X9 | SO | WK | 11 WALKER LAKE
| 9 | 10 | 11 | 116 12 SAN FRANCISCO
38 |_____|_____|_____|_____ 13 SAN JOSE
| SF | SJ | MZ | GU | 14 MARIPOSA
| 12 | 13 | 14 | 15 | 15 GOLDFIELD
37 |_____|_____|_____|_____| 16 (no USGS name)
| SX | ZP | FO | DV | 17 MONTEREY
| 16 | 17 | 18 | 19 | 114 18 FRESNO
36 |_____|_____|_____|_____|_____ 19 DEATH VALLEY
| SL | BF | TJ | KI | 20 SAN LUIS OBISPO
| 20 | 21 | 22 | 23 | 21 BAKERSFIELD
35 |_____|_____|_____|_____| A 22 TRONA
| SM | LA | SB | NE | R 23 KINGMAN
| 24 | 25 | 26 | 27 | I 24 SANTA MARIA
34 |_____|_____|_____|_____| Z 25 LOS ANGELES
| SV | LB | SN | S6 | O 26 SAN BERNARDINO
| 28 | 29 | 30 | 31 | N 27 NEEDLES
33 |_____|_____|_____|_____| A 28 SANTA ROSA ISLAND
| SD | EL | 29 LONG BEACH
| 32 | 33 | 30 SANTA ANA
32 |--------------| 31 SALTON SEA
MEXICO 32 SAN DIEGO
33 EL CENTRO

Each quad covers an area one degree of latitude by two degrees of longitude,
except as noted: ZF, WE, AC, XJ, DV and CQ coverage boundaries have been
extended to include hydrographic features between the quad lines and the
State Boundary;
SD and SV include Channel Islands;
no Teale data beyond the Mexico border (---).

See the coverage hydroindexa in /callib/hydro for an ARC/INFO version of the
above index diagram.

------------------------------------------------------------------------------
Appendix A
------------------------------------------------------------------------------

RF3-Alpha Attribute Descriptions


Reach codes - The Unique Feature Identifier - RF3RCHID

Reach codes are the unique identifiers of all reaches; they consist of 17
digits. As shown below, each number is constructed to include the USGS
eight-digit catalog unit code, a four-digit segment number, and a
five-place fixed decimal number referred to as the marker index.

CU - Cataloging Unit - an eight digit code uniquely assigned to a watershed
and defined as a Federal Information Processing Standard (FIPS) maintained
by the USGS. There are 2123 Catalog Units in the continental US plus Hawaii,
Puerto Rico, the Panama Canal, and the US Virgin Islands. The data field
name for the catalog unit is CU.

SEG - Segment - The segment number is a unique four digit number assigned
to each new surface water feature within a given catalog unit. Segment
numbers are assigned serially, starting at 0001, without regard for the
hydrologic order of the segments. The data field name for the segment
is SEG.

MI - Marker Index - When a segment, that exists in the Reach File, is
subsequently divided by a new tributary, the two pieces of the segment
are assigned a marker index. Their segment numbers remain the same, thus
identifying them as once being a single reach. The new downstream piece
receives a marker index of zero. The new upstream piece receives a marker
index which is defined as the proration or ratio of the distance from the
base of the reach segment to the point of sub-division to the total length
of the reach segment. Note that some Marker Indexes were assigned in RF2
when the spatial length of the reach was based on the sparse geometry from
GNIS. DO NOT USE THE MARKER INDEX AS AN INDICATOR OF ACTUAL REACH LENGTH.
The only valid use of the Marker Indicator is as a coding approach that
enables the pieces within one Segment to be hydrologically ordered. The
data field name for the marker index is MI.

In order to facilitate easy handling of updates, a fourth variable is used
to identify the upstream point of the reach.

UPMI - Upstream Marker Index - This number is the marker index associated
with the most upstream end of the reach. The basis of this number is (in
general) the distance measured from the start of the segment to the
upstream end of the instant reach. For reaches derived from RF1 and RF2,
this marker index is proportionally related to the reach lengths in the RF1
and RF2 spatial representations, respectively. The data field name for
the upstream marker index is UPMI.


Data Sources

RFORGFLAG records the version of the Reach File in which a given reach
first occurred. A "1" denotes that the reach was first included in the RF1
version of the file. A "2" identifies those reaches added when the RF2
version was created and a "3" indicates this reach was added during the
RF3 compilation.


Navigation Between Reaches

The navigation attributes in RF3-Alpha support two reaches converging and
two reaches diverging, as illustrated in Figure A-1. The navigation
attributes are associated with the "instant" reach. Points of convergence
connect two input reaches with one output reach, points of divergence
connect one or two input reaches with two output reaches, and points of
simple connection connect one input reach to one output reach.

Figure A-1:

UpLeft \ / UpRight
\ /
\ /
|
|
Instant | / Compliment
| /
|/
/ \
/ \
Divergent / \ Downstream


DSCU, DSSEG, DSMI:
The CU, SEG, and MI, respectively, of the reach downstream of the
instant reach. The downstream reach is the reach into which the
instant reach flows, except that if the downstream end of the instant
reach is a divergent junction, then the reach identified as the
downstream reach is the major recipient of the outflow from the
instant reach and the reach identified as the divergent reach is
the recipient of the minor portion of the outflow.

CCU, CSEG, CMI:
The CU, SEG, and MI, respectively, of the complement reach.
The complement is the reach that flows into the confluence at the
downstream end of the instant reach.

CDIR:
The complement direction. Looking downstream, this is the left or
right (L or R) side of the instant reach to which the complement
reach is connected.

ULCU, ULSEG, ULMI:
The CU, SEG, and MI, respectively, of the reach branching to the
left from the upstream end of the instant reach.

URCU, URSEG, URMI:
The CU, SEG, and MI, respectively, of the reach branching to the
right from the upstream end of the instant reach.

USDIR:
Looking upstream, this attribute specifies which reach (up left or
up right) is the direction of the main network path.

DIVCU, DIVSEG, DIVMI:
The CU, SEG, and MI, respectively, of the divergent reach which is
the minor recipient of outflow from the instant reach.

DIVERGENCE:
A one-digit divergence code which is assigned a value when there is
a divergent junction at either end of a reach. A reach flowing into
a divergent junction is referred to as the "input reach"; the reach
which receives the majority of the flow from a divergent junction
is the "major reach"; and the reach which receives the minority of
the flow from a divergent junction is the "minor reach".

Value
Definition
0
Not part of a divergent junction
1
Input reach where minor reach is downstream left
2
Input reach where minor reach is downstream right
3
Minor reach of a divergence
4
Combination of divergence values 1 and 3
5
Combination of divergence values 2 and 3
6
Major reach of a divergence
7
Combination of divergence values 1 and 6
8
Combination of divergence values 2 and 6


Stream Levels

Each reach is assigned a stream level which defines the hierarchical
relationship between streams and tributaries in a given drainage network.
A tributary to a given stream is always one level higher than the stream
into which it flows. For instance, the Mississippi River is a level-one
stream, the Ohio River is a level-two stream, and the Tennessee River is a
level-three stream. Stream levels are useful in retrieval algorithms.
A "level path" can be followed to identify all mainstem reaches for a given
river. For instance, the mainstem of the Mississippi River can be readily
identified by retrieving all level-one reaches upstream of the Mississippi
River terminus.

Where RF1 and RF2 were successfully overlaid on the 1:100,000-scale DLG
hydrography during RF3 compilation, the stream levels were inherited from
RF1 and RF2. The RF1 stream levels were manually determined from source
data during the creation of RF1. RF2 stream levels, by definition, were one
level greater than those in RF1. For 1:100,000-scale DLG streams not
successfully overlaid by RF1 or RF2 during RF3 compilation, stream levels
were assigned based upon the assumption that the "straightest" path was the
continuation of the current level. Where this approach did not adequately
discriminate between the two upstream reaches, the rightmost reach was
assumed to be the continuation of the current level.

LEV:
The stream level of the instant reach.

JUNC:
The junction code pertaining to the junction at the downstream end
of the instant reach. In the case of a convergent junction, this is
equal to the level of the reach downstream of the instant reach. For
simple junctions (junctions with one stream flowing into the junction
and one stream flowing out of the junction) and divergent junctions
this variable is assigned the value of zero.

TRMBLV:
The terminal base level: The level of the terminal reach of the
stream system to which the instant reach belongs. Terminal reaches
are assigned levels according to the manner in which the streams
terminate, as follows:

TRMBLV
Description
1
Stream outlet is Atlantic, Pacific, or Gulf of Mexico;
2
Stream outlet is one of the Great Lakes, or the Great Salt Lake;
3
Stream exits from US into Canada or Mexico;
4
Isolated drainage (flows into the ground).


Currently, TRMBLV is valued only for terminal reaches.


Sequence Numbers

The Reach File is designed with the capability to perform routing of flow
and other constituents. While there are many attributes in the Reach File
that assist in routing, using the sequence numbers, stored in the attribute
SEQNO, is the fastest and easiest method. When the Reach File is ordered by
the sequence numbers, it is in upstream to downstream order. Originally,
used in RF1.

SEQNO: Not currently valued. [Not implemented in DFG DS3 tables]


Navigation-Related Attributes

Each reach has attributes which define the start and stop of its level
path. For example, if the instant reach is a level 3, then these
attributes provide the terminal CU-SEG and start CU-SEG of this
level 3 path.

-- begin -- [Not implemented in DFG DS3 tables]:

STARTCU:
The catalog unit number of the start reach of the same level path
on the instant reach.
STARTSEG:
The segment number of the start reach of the same level path on
the instant reach.
STOPCU:
The catalog unit number of the most downstream reach on the same
level path as the instant reach.
STOPSEG:
The segment number of the most downstream reach on the same level
path as the instant reach.


Using the STARTCU/STARTSEG values, it is possible to "jump" through
several CUs, finding the next STARTCU/STARTSEG in the each CU.
-- end -- [Not implemented in DFG DS3 tables] --


Reach Types

REACHTYPE - The term "reach type" refers to a one-character code which has
been assigned to each reach. These type codes were generated, in part,
from the DLG-3 area and line attribute codes. Where DLG attribute codes
appeared to be incorrectly assigned, temporary code changes were used to
allowcorrect reach typing and to permit networking to be completed.
For example, some lake shorelines had the DLG3 attribute code indicating
that they were single line streams and, during compilation, the code would
be temporarily changed to correctly indicate a lake shoreline. The original
codes are stored in the DLG-3 code attributes.

The valid reach type codes are as follows:

A = Artificial Lake (RF1/RF2) Reach

C = Continental Coastline Reach
Refers to a reach which represents a coastline on the Atlantic,
Pacific or Gulf coasts.

F = Falls Reach
A reach which is either a waterfall, drop spillway, or a reach
of rapids.

G = Great Lakes Shoreline Reach
Refers to a reach which represents a coastline in the Great Lakes.

H = Headwater Lake Reach
A headwater reach, identified as a lake, which has no reaches
above it in the reach file. This type of reach has either one or
two reaches connected to its downstream end.

I = Island Shoreline Reach
Identifies a reach whose DLG-3 attributes identified it as an
island shoreline.

J = Braided Stream Envelope
Stream reaches which are around the perimeter of an unnetworked
braided stream system.

L = Lake Shoreline Reach
A reach which follows the shoreline of a lake other than the
Great Lakes.

N = Isolated Stream Reach
A stream reach not having navigation links in to other reaches.

O = Apparent Limit Reach
A non-transport reach, usually designated by the DLG attributes
as a marsh or wetlands.

P = Indefinite or Intermittent Shoreline Reach
A non-transport reach, usually designated by the DLG attributes
as a shoreline without definite boundaries.

Q = Questionable Shoreline Reach
A reach which could be either an island or another closed area.

R = Regular Reach
A reach which has upstream and downstream reaches connected to
it and which is not classified as another type of reach.

S = Start Reach
A headwater reach which has no reaches above it in the reach file.
This type of reach has either one or two reaches connected to its
downstream end.

T = Terminal Reach
A reach downstream of which there is no other reach (for example,
a reach which terminates into an ocean, a land-locked lake, or
the ground). This type of reach has either one or two reaches
connected to its upstream end.

U = Unknown Reach
Reach cannot be classified.

V = Open Water Terminal Reach
A reach which is both a terminal reach and an artificial
open water reach.

W = Wide-River Shoreline Reach
A reach which identifies either the Right or Left bank of a
wide river.

X = Terminal Start Reach
A reach which is both a terminal reach and a start reach.

Z = Terminal Entry Reach
A reach which is both a terminal reach and an entry reach.


Routing Flags

Each reach has four (4) one-character flag attributes which can be used in
various routing schemes. The flags are given values of 0 or 1, corresponding
to "no" or "yes", respectively. Only connected reaches can have routing flag
values of 1. The four flags are defined below:

RFLAG - Routing Flag for transport reaches:

0 = Reach is not a connected reach.
1 = Reach is a connected reach.

OWFLAG - Open Water Flag: (valid if RFLAG = 1)
(i.e. not set for isolated lakes)

0 = Reach is not in a lake, reservoir, wide river, bay,
or other open water.
1 = Reach is part of an open water (types A, H, L, M, V, or W).

TFLAG - Terminal Flag:

0 = Reach is not a terminal reach.
1 = Reach is terminal (types T, V, X, or Z)

SFLAG - Start Flag:

0 = Reach is not a start reach.
1 = Reach is a start reach (types E, H, S, X, or Z).


Reach Length

SEGL - The length of the instant reach measured to the nearest one-hundredth
(0.01) of a mile is stored in the attribute SEGL. This length was calculated
from all of the latitude/longitude coordinate values for the entire length
of the reach.

NOTE: The difference between MI and UPMI will NOT always equal SEGL.
MI/UPMI are proportionally related indexes based upon mileage calculations
from RF1/RF2 and the DLG. For all mileage calculations, SEGL should
be used.


Names and Name Codes

The name, or names, associated with a given reach may have a maximum length
of thirty (30) characters. Pseudo-names are included where reach names could
not be identified when data was being compiled for RF1 and RF2. Pseudo-names
in all cases consist of an asterisk followed by a single letter, e.g. "*A".
[DFG Note: DFG assigned pseudo names of the form "Unnamed n"
e.g. Unnamed 1,2, etc.]

Each reach name has an eleven (11) digit name code associated with it in
order to uniquely identify the surface water represented by the reach.

Names that were assigned to the original RF1 reaches are stored in upper
case letters. These names were developed manually from the source maps
used to compile RF1. Names that were assigned to reaches that originated
in RF2 and RF3-Alpha are stored in upper and lower case letters. These
names came from a blind conflation of the 1988 version of the Geographic
Names Information System (GNIS) data onto the RF3-Alpha data.

Up to three different names and name codes may be associated with a given
reach:

PNAME, PNMCD:
These attributes are the primary name and name code, respectively,
associated with the reach. For connected reaches, including open water
reaches, this is a stream name. Each connected shoreline reach around an
open waterbody will bear the name of the stream which feeds that open
waterbody. All reaches of a given stream have been assigned the same name
and the same primary name code. Other streams having that same name will
have different primary name codes. For example, a Back Creek in Virginia
would have a different PNMCD from any other Back Creek in Virginia or any
other state.

CNAME, CNMCD:
These attributes are the common name and name code, respectively, which
are reserved for the storage of alternate names.
[DFG Note: DFG DS3 tables use CNAME to denote Compliment Name. This was
the original application of the field. The compliment to the instant
reach is the reach joining the instant reach at their common downstream
confluence.]

OWNAME, OWNMCD:
These attributes are the open water name and name code respectively.
For open water reaches (OWFLAG =1), this is the name of the lake or
wide river in which the reach resides.

TERMID: Terminal Stream System Identifier
Each reach within a given terminal stream system is assigned a 5-digit code,
unique to that terminal system. This code can be used to readily identify
all reaches in a given stream system. Currently, TERMID is not valued.


Latitude/Longitude Coordinates

There are numerous attributes in the Structure File that contain
latitude/longitude coordinates. These attributes can be used for certain
types of geographically-based retrieval and analysis, without the need to
access the Coordinate ("LL") File. All latitude/longitude data are given
in decimal degrees to the nearest 0.0001 degree.

Large-scale areal retrievals can be performed using the minimum and maximum
latitude/longitude pairs. These coordinates define the smallest
north-south/east-west rectangle containing the reach.

MINLAT, MINLON, MAXLAT, MAXLON:
North-south box window coordinates. The largest and smallest
latitudes and longitudes found in the digitized trace of the instant reach.

ULAT, ULON, DLAT, DLON:
Coordinate points for the end points of the reach. A "skeleton" trace
can be generated using these coordinates.


Update Codes

Nine attributes are available to track updates to RF3-Alpha. Three sets
of three variables allow for the historical tracking of the updates
(where n = 1, 2, or 3):

UPDATEn: Date of the update.
UPDTCDn: Unique code for a set of updates.
UPDTSRCn: Code identifying the party performing the updates.


"1" series:
Set during the initial production. UPDTSRC equals "DLG100K" except for
California where the first two digits are equal to the Teale Data
Center dataset block number ("01" through "33") plus the six digit
California-assigned line identifier (different from the DLG line id in
their datasets). UPDATE equals the date when PCRF3 compilation was
completed. UPDTCD equals "PCRF8RF3."

"2" and "3" series:
Set during future update procedures. Refer to "River Reach File (RF3-Alpha)
Update and Quality Control Standards, Procedures and Management," internal
EPA draft document, for more detailed instructions and descriptions on
updates. [DFG Note: All DFG/CARA updates are flagged in "2" series items.]


USGS DLG Attributes

Many of the attribute codes associated with the original DLG data were
included in the Structure File. DLG3 major codes were not included, since
only hydrographic features (major code 050) were included in RF3-Alpha.
Two pairs of area attributes and two line attributes were kept.

[DFG Note: see also Minor 1,2 etc in Teale Arc Attribute Table (AAT)]

LN1AT2, LN2AT2:
Line attribute 1 and 2.
AREA1, AREA2:
Area identifier 1 and 2.
AR1AT2, AR1AT4:
First pair of area attributes.
AR2AT2, AR2AT4:
Second pair of area attributes.
DLGID:
This field is blank except for Arizona, California and
Hawaii where it is equal to the DLG line id from their
enhanced DLG files.

 

Distribution_Information:
Resource_Description: Downloadable Data
Standard_Order_Process:
Digital_Form:
Digital_Transfer_Information:
Transfer_Size: 1.315

Metadata_Reference_Information:
Metadata_Date: 20020824
Metadata_Contact:
Contact_Information:
Contact_Organization_Primary:
Contact_Organization:
Circuit Rider Productions, Inc.
Contact_Person:
David Bennett
Contact_Address:
Address_Type:
Mailing: 9619 Old Redwood Highway
City: Windsor
State_or_Province: California.
Postal_Code: 95492.
Contact_Voice_Telephone:
707.838.6641
Metadata_Standard_Name: FGDC Content Standards for Digital Geospatial Metadata
Metadata_Standard_Version: FGDC-STD-001-1998
Metadata_Time_Convention: local time
Metadata_Extensions:
Online_Linkage: <http://www.esri.com/metadata/esriprof80.html>
Profile_Name: ESRI Metadata Profile
 
 

Generated by mp version 2.7.3 on Sat Aug 24 14:52:43 2002