FLORIDA GEOGRAPHIC DATA LIBRARY DOCUMENTATION
VERSION 2003, RELEASED NOVEMBER, 2002.
TITLE: RIVERS DIGITAL GEOGRAPHY
Geodataset Name: RIVRF Geodataset Type: SHAPE Geodataset Feature: LINE
GENERAL DESCRIPTION:
This dataset contains rivers for the state of Florida. It is a subset of the Rivers Digital Geography dataset, which was derived from the Environmental Protection Agency's River Reach 1 (RF1) geography. The attributes associated with the river segments have been added by the National Oceanic & Atmospheric Administration (NOAA) Special Projects Office (SPO). WHAT DOES THIS MEAN? The digital geographies provided contain only those River Reach segments attributed (by NOS) as appropriate for display purposes (i.e., no 'artificial, 'island', 'shoreline' or 'outlier' arcs. DATA SOURCE(S): National Oceanic & Atmospheric Administration (NOAA) National Ocean Service (NOS) Special Projects Office (SPO) U.S. Environmental Protection Agency SCALE OF ORIGINAL SOURCE MAPS: 1:500000 DATE OF AUTOMATION OR SOURCE: 8/18/99 GEODATASET EXTENT: FLORIDA
Datafile Name: RIVRF.DBF ITEM NAME WIDTH TYPE PRECISION SHAPE 9 LINE 0 CUSEG 11 CHARACTER - HR 2 CHARACTER - SR 4 CHARACTER - AU 6 CHARACTER - CU 8 CHARACTER - SEQNO 11 CHARACTER - TYPE 1 CHARACTER - SEGL 8 DECIMAL 1 LEV 4 DECIMAL - PMILE 8 DECIMAL 2 ARBSUM 8 DECIMAL 2 TERMID 5 CHARACTER - PNAME 30 CHARACTER - PNMCD 11 CHARACTER - NEW_RFTHIN 8 DECIMAL 0 OUTLIER 4 CHARACTER - DISPLAY 3 CHARACTER - UNIQUE_ID 51 CHARACTER - EDACDA 12 CHARACTER - NAME 53 CHARACTER - SUB_NAME 55 CHARACTER - SUBEDA 12 CHARACTER - REGION 11 CHARACTER - DR_CODE 12 CHARACTER - EDASUBEDA 5 CHARACTER - CAF_INTRST 40 CHARACTER - LAKE_NAME 50 CHARACTER - RIVER_NAME 50 CHARACTER - PRIMARY_R 16 CHARACTER - DESCRIPT 30 CHARACTER -
FEATURE ATTRIBUTE TABLES CODES AND VALUES:
ITEM ITEM DESCRIPTION SHAPE Data attribute inherent to the ESRI shapefile format, which defines the data as a point, polyline, or polygon. CUSEG This is the unique identifier for each reach. It is an 11-digit alphanumeric number. It contains CATUNIT, the nationally unique 8-digit alphanumeric identifier for the cataloging unit in which the reach occurs, and SEG, a 3-digit alphanumeric reach number HR Unique 2-digit identifier for each hydrologic region. SR Unique 4-digit identifier for each hydrologic subregion. AU Unique 6-digit identifier for hydrologic accounting unit. CU Unique 8-digit identifier for hydrologic cataloging unit. SEQNO Sequence Number: An eleven (11)-digit hydrologic sequence number. Reaches are processed in SEQNO order for flood routing and water quality modeling, beginning anywhere in the file. The sequencing in the database begins at the most upstream reach of the lowest level stream in cataloging unit 01010001. From there on, the next transport reach in this sequence is either the next reach downstream of the immediate reach, or the most upstream reach in the tributary system above the complement reach (if a complement reach having a level higher than the immediate reach is present at the base of the immediate reach). This progression continues until a terminal reach has been encountered. After a terminal reach has been encountered, the sequence continues with the most upstream reach of the lowest level stream of a different terminal stream system, which may or may not be in the same cataloging unit. The above sequencing progresses from terminal stream system to terminal stream system until end of file. (Note: The user may ignore non- transport reaches when encountered while flow routing. To determine if a reach is a non-transport reach, test the value of the RFLAG data element. If it is zero, then the reach is a non-transport reach.) TYPE Reach Type - The term "reach type", not to be confused with any of the Reach File record types, refers to a one-character code assigned to each RF1 reach to categorize transport reaches and shoreline reaches as follows: (see Type sheet). SEGL Reach Length (miles): The length of the immediate reach calculated from its reach trace record to the nearest tenth of a mile. LEV Stream Level: The stream level of the immediate reach. Non-zero values are assigned to transport reaches, and shoreline segments are assigned a level of zero. Each transport reach is assigned a stream level which may be used to define 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 the retrieval algorithms which traverse the Reach File. A "level path" can be followed to identify all mainstem reaches of 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 PMILE Path mile: the distance, in miles, from the downstream end of the immediate reach to the terminus, as measured along the hydraulic transport path. (A terminus is the downstream point of a drainage system where a stream enters an ocean, the ground, a land-locked lake, one of the Great Lakes, or where it flows into Canada or Mexico.) ARBSUM Arbolate Sum: The sum of the lengths, in miles, of all digitized reaches upstream from the base of the immediate reach, including all branches of all streams above it. This gives an indication of the size of the drainage system upstream of the reach. TERMID Terminal Stream System Identifier. Each transport reach is either a terminal reach or is upstream of a terminal reach. A terminal reach is the most downstream reach in a stream system. The base of a terminal reach connects to an ocean, gulf, great lake, or other sink. All such points of connection have been assigned a terminal identification code (TERMID). All reaches, including the terminal reach, which deliver water to a given terminal point are said to belong to the terminal system designated by TERMID in each reach record. PNAME Primary Name For transport reaches, including open water reaches, this is a stream name. For shoreline reaches, this is the name of the open water body. Each transport reach of a given stream level within an open water body will bear the name of the stream which feeds that open water reach at that level (See OWNAME below). Thus the entire watercourse of any given named river in RF1 could be shown by its name alone. For instance, the entire Mississippi River, or the entire Colorado River, or the full course of Four Mile Run or Rock Creek. This is convenient for more reasons than simply showing or accessing data on rivers of a given name; it provides a basis for assigning stream levels, an important attribute in building and using databases of rivers. Where names were not given on the source maps, psuedo names were inserted into the file based on visual interpretation of the source maps to help in automatically assigning levels and to provide at least a presumed watercourse where streams were not named on the source maps. The pseudo names begin with an asterisk in a form such as "*A", "*B", "*C", etc., to bring attention to the users that names were needed for these streams. PNMCD 11-digit Primary Name Code: 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. NEW_RFTHIN An enhanced version of EPA's RFTHIN. This attribute includes consistent NEW_RFTHIN values for the shorelines around lakes (reach type = L). It provides the capability to select a range of thinned, connected river networks that include lake shorelines. Code which can be used to thin RF1 0 unnetworked reach 1 reach in the main networked path that connects catalog units or is the lowest level path in headwater catalog units. 2 tributaries to reaches with NEW_RFTHIN =1 3 tributaries to reaches with NEW_RFTHIN =2. 4 tributaries to reaches with NEW_RFTHIN =3 5 tributaries to reaches with NEW_RFTHIN =4 6 tributaries to reaches with NEW_RFTHIN =5 7 tributaries to reaches with NEW_RFTHIN =6 OUTLIER Code used (by NOS) to identify reach segments containing questionable coordinates, also referred to as outliers (yes = outlier exists, no = accurate coordinates). DISPLAY Code used to simplify displaying a clean RF1 version for graphical purposes (yes = reaches desired for display use, no = reaches not desired for display use). Allows specific reach Types that are extraneous for graphical presentations to be eliminated in one step. "No" where Type A - Artificial Lake Reach C - Coastal or Continental Shoreline Segment G - Great Lakes Shoreline Segment I - Island Shoreline Segment M - Artificial Open Water Reach V - Open Water Terminal Reach * W - Wide-River Shoreline Segment Y - International Boundary Reach * Note: In some cases the display value was changed to yes because the wide river shoreline extended further inland than NOAAüs Coastal Assessment Framework shoreline. COLUMBIA R, SUSQUEHANNA R, WILLAMETTE R only part of the river has a "yes" code for display DETROIT R, SNAKE R -- entire river has "yes" code to be displayed. "Yes" where Type = B. Bi-directional Reach - A reach for which the direction of flow is ambiguous. D. Dam Reach - A reach which is a dam through which and/or around which water flows. E. Entry Reach - A reach which receives flow from Canada or Mexico. F. Falls Reach - A reach which is either a waterfall, drop spillway, or a reach of rapids. L. Lake Shoreline Segment - A segment which follows the shoreline of a lake other than one of the Great Lakes. N. Non-Connected Reach - A reach not having codes to link it to other reaches. 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 and either one or two transport 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). 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. UNIQUE_ID A unique character string assigned to every spatial area in the Coastal Assessment Framework. Composed of a concatenation of each polygon's EDACDA code and its polygon type (e.g., Estuarine Drainage Area, Coastal Drainage Area, Fluvial Drainage Area, etc.). EDACDA The major watershed in which the reach has it's greatest length. A code assigned to each major watershed area (e.g., an Estuarine Drainage Area, Coastal Drainage Area, Fluvial Drainage Area, Interior Drainage Area, etc.). NAME A geographic name associated with each major watershed area. Names of EDAs come from NOAAüs National Estuarine Inventory; names of CDAs are a combination of edacda code plus USGS cataloging unit name. Unique Names have corresponding EDACDA Codes. SUB_NAME For EDAs with component sub-major watershed drainages (subEDAs) defined (e.g., the Chesapeake Bay), a subEDA specific name. SUBEDA Alphabetical code indicating the subEDA. a - t Identifies individual subEDAs found in estuaries where subEDAs have been defined (e.g., Chesapeake Bay). Only EDAs have subEDAs. w Identifies those polygons in an EDA not already assigned to a subEDA. The remaining core of the major EDACDA Watershed. Applies only to EDAs that have subEDAs. x All other polygons. These include all major watersheds (EDAs) that do not have SubEDAs. REGION Region of the Coastal Assessment Framework. N -Rivers of the North Atlantic region. M -Rivers of the Middle Atlantic region. S -Rivers of the South Atlantic region. G -Rivers of the Gulf of Mexico region. P -Rivers of the Pacific region. L -Rivers of the Great Lakes region. U -Rivers within the US border, but not a part of the CAF. X -Rivers outside US boundaries. DR_CODE Drainage Code - A single character identifier for the coastal component of the polygon. The coastal component having the greatest length of the reach. E -Coastal Component - Either an Estuarine Drainage Area (EDA), Coastal Drainage Area (CDA), or Great Lake / St Lawrence River CDA polygon. F -Upstream Component - Either an Fluvial Drainage Area (FDA), Fluvial Coastal Drainage Area (FCDA) or Great Lake / St Lawrence River CDA polygon. I -An Interior Watershed polygon (includes self-contained, groundwater drainage only, and those draining to areas other than the United States). EDASUBEDA The watershed in which the reach has it's greatest length. A code assigned to each derived spatial area (e.g., an EDA or CDA). Concatenated from the EDACDA attribute and SUBEDA attribute. CAF_INTRST Coastal Assessment Framework Intersect. Identifies if the reach segment was fully contained within one watershed or multiple watersheds. Also identifies if the reach segment was fully within the Estuarine/Coastal Drainage Areas (EDA/CDA) component or the Fluvial (upstream - FDA) component of the watershed. Possibilities are; Multiple Drainages, One CAF Drainage, One EDA/CDA, One FDA/FCDA, and One Interior Drainage. LAKE_NAME For all Type þLü reaches, and for reaches that appeared to be lake shorelines despite having a þtypeü other than þLü, Lake Name was set to þOWNAMEü (Open Water Name). In cases where OWNAME was blank, NOS named the lake according to the county and state in which it was primarily located. Special Note: A special 'Lakes Digital Geography' has been created by NOS by extracting these Lake Reaches and building topology. The Digital Geography is available at the following URL; ftp://sposerver.nos.noaa.gov/datasets/CADS/GIS_Files/ShapeFiles/Rivers_and_Lakes/Rf1 _Lakes_as_Polygons/ RIVER_NAME Lake reaches were assigned an associated River Name reflecting the river that flows through and out of the lake. All non-lake reaches were assigned a þNAü (Not Applicable) for this variable. PRIMARY_R Primary River field identifies at least one primary river for each estuarine and coastal watershed in NOAAüs Coastal Assessment Fr amework. Its purpose is to provide a highly thinned version of the RF_Thin 1 cover to mo re rapidly identify and map rivers with the highest average discharge and /or longest length DESCRIPT FGDL added item based on PNAME
USER NOTES:
The Rivers Digital Geography was developed using geographic information system (GIS) technology. It is derived from the Environmental Protection Agency's River Reach 1 (RF1) (http://www.epa.gov/nsdi/projects/rf1_meta.html) The attributes associated with the geography have been enhanced by the Special Projects Office (NOAA). The digital geographies provided contain only those River Reach segments attributed (by NOS) as appropriate for display purposes (i.e., no 'artificial, 'island', 'shoreline' or 'outlier' arcs). NOTE: It is recognized that this digital geography is not perfectly aligned with many of the other digital geographies supplied on this site. It remains however, the best consistently derived and complete river file for the coterminous United States of America. A document is available that describes the attribute tables of this digital geography in detail. A note concerning data scale: Scale is an important factor in data usage. Certain scale datasets are not suitable for some project, analysis, or modelling purposes. Please be sure you are using the best available data. 1:24000 scale datasets are recommended for projects that are at the county level. 1:24000 data should NOT be used for high accuracy base mapping such as property parcel boundaries. 1:100000 scale datasets are recommended for projects that are at the multi-county or regional level. 1:250000 scale datasets are recommended for projects that are at the regional or state level or larger. Vector datasets with no defined scale or accuracy should be considered suspect. Make sure you are familiar with your data before using it for projects or analyses. Every effort has been made to supply the user with data documentation. For additional information, see the References section and the Data Source Contact section of this documentation. For more information regarding scale and accuracy, see our web pages at: http://www.geoplan.ufl.edu/education.html
-Projected data to FGDL Albers HPGN (See "Map Projection Parameters" below). -Clipped to the State of Florida -DESCRIPT item added based on PNAME -Upcased all character records
REFERENCES:
NOAA National Ocean Service Special Projects Office (NOAA/NOS/SPO) Environmental Protection Agency
DATA LINEAGE SUMMARY:
Data originally released by NOAA/NOS/SPO in 1999. Data was downloaded by GeoPlan in shapefile format from NOAA (ftp://sposerver.nos.noaa.gov/datasets/CADS/GIS_Files/ ShapeFiles/Rivers_and_Lakes/RF1_Rivers/RF1_display/)in 2002. When received, data was in the following projection: Geographic, Datum: NAD 83, Spheroid: GRS80, Units: Decimal Degrees. The shapefile was then clipped to the State of Florida, projected to FGDL Albers HPGN, DESCRIPT item was added and all character records were upcased.
MAP PROJECTION PARAMETERS:
Projection ALBERS Units METERS Datum HPGN Spheroid GRS1980 1st standard parallel 24 0 0.000 2nd standard parallel 31 30 0.000 Central meridian -84 0 0.000 Latitude of projection's origin 24 0 0.000 False easting (meters) 400000.00000 False northing (meters) 0.00000
DATA SOURCES CONTACT(S):
Name: NOAA National Ocean Service Special Projects Office
Abbr.name: NOAA/NOS/SPO
Address: NOAA, N/SPO, 9th Floor
1305 East-West Highway
Silver Spring, MD 20910
Phone: (301) 713-3000 x204
Fax: (301) 713-4384
Web site: http://cammp.nos.noaa.gov/spo/prodlist.taf?alltype=3
Ftp site:
ftp://sposerver.nos.noaa.gov/datasets/CADS/GIS_Files/ShapeFiles/Rivers_and_Lakes/RF1
_Rivers/RF1_display/
Contact Person: Jacobsen, Mark
Phone: (301) 713-3000 x204
Email: mark.jacobsen@noaa.gov
FGDL CONTACT:
Name: Florida Geographic Data Library
Abbr. Name: FGDL
Address: Florida Geographic Data Library
431 Architecture
PO Box 115706
Gainesville, FL 32611-5706
Web site: http://www.fgdl.org
Contact FGDL:
Technical Support: http://www.fgdl.org/fgdlfeed.html
FGDL Frequently Asked Questions: http://www.fgdl.org/fgdlfaq.html
FGDL Mailing Lists: http://www.fgdl.org/fgdl-l.html
For FGDL Software: http://www.fgdl.org/software.html