FLORIDA GEOGRAPHIC DATA LIBRARY DOCUMENTATION
VERSION 2006

TITLE: WATERWAY NETWORK 

Geodataset Name:       BTSWW_2006
Geodataset Type:       SHAPEFILE
Geodataset Feature:    Polyline
Feature Count:         388
GENERAL DESCRIPTION:
The Waterway Network is a comprehensive network database of the Florida's navigable waterways. Included in this dataset are areas of deep-water access, shallow-water accress, harbors, and bays. 
DATA SOURCE(S):                    Bureau of Transportation Statistics (RITA/BTS)
SCALE OF ORIGINAL SOURCE MAPS:     240001.2M100,000varies24000no scalenonenonevariesvariesvaries
DATE OF AUTOMATION OF SOURCE:      2006
GEODATASET EXTENT:                 State of Florida

FEATURE ATTRIBUTE TABLES: 

Datafile Name: BTSWW_2006.DBF
ITEM NAME WIDTH TYPE N. DECIMAL DEGREES
OBJECTID
4 OID ---
ID
12 Number ---
LENGTH
17 Number 2
DATA
12 Number ---
FEATURID
10 Number ---
ANODE
10 Number ---
BNODE
10 Number ---
LINKNAME
35 String ---
RIVERNAME
35 String ---
AMILE
14 Number 1
BMILE
14 Number 1
LENGTH1
11 Number 1
LENGTH_SRC
1 String ---
SHAPE_SRC
6 String ---
LINKTYPE
10 String ---
CTRL_DEPTH
10 Number ---
WATERWAY
10 String ---
GEO_CLASS
1 String ---
FUNC_CLASS
2 String ---
WTWY_TYPE
6 Number ---
CHART_ID
15 String ---
NUM_PAIRS
9 Number ---
WHO_MOD
3 String ---
DATE_MOD
8 String ---
HEADING
1 String ---
STATE
2 String ---
FIPS
2 String ---
FIPS2
2 String ---
NON_US
2 String ---
VERSION
2 String ---
DESCRIPT
50 String ---
FGDLAQDATE
8 Date ---
SHAPE
4 Geometry ---
AUTOID
4 Integer ---
SHAPE.LEN
0 Double ---

FEATURE ATTRIBUTE TABLES CODES AND VALUES:

Item

Item Description





OBJECTID

Internal feature number.
















ID

Unique Link identification number
















LENGTH

Link length in Miles




real = with one explicit decimal place

AT = Atlantic Ocean

BS = Bering Sea

CB = Caribbean Sea

CD = Canada

GM = Gulf of Mexico

PC = Pacific Ocean

PM = Panama

XX = Unidentified Area













DATA

Feature revision number
















FEATURID

Unique Identifier
















ANODE

Identifies a record (NODEID) in the node file that corresponds to the starting position of the link
















BNODE

Identifies a record (NODEID) in the node file that corresponds to the ending position of the link
















LINKNAME

USACE link description
















RIVERNAME

Name of the water that the object belong to.
















AMILE

Milepost at the ANODE, inland Corps links, only
















BMILE

Milepost at the BNODE, inland Corps links, only
















LENGTH1

Line length, in miles
















LENGTH_SRC

Indication of how the length was calculated




V = Vanderbilt; length was calculated using GIS software

M = Milepoints; length was calculated by subtracting 'B' milepoint from 'A' milepoint













SHAPE_SRC

Indicates the data source used for each link




CM = Corps Milepoints

DD = Digitized from 1:100K DLGs (CD-ROM)

DN = Digitized from NOAA Charts

DQ = Digitized from 1:100K USGS Quads

J = Rough shape (guessed)

JR = Original shape modified by ORNL

JV = Original shape modified by Vanderbilt

M = Missing / Unknown

NA = Digitized from 1:2M National Atlas Points

RR = ORNL link modified by ORNL

RV = ORNL link modified by Vanderbilt

VR = Vanderbilt link modified by ORNL













LINKTYPE

Indicates the originator of the link or the type of feature represented by the link




CORPS = Corps of Engineers original link

CWIS = Corps of Engineers civil works improvement addition

ORNL = Oak Ridge National Laboratory

VANDERBUILT = Vanderbuilt University

LOCK = Corps of Engineers lock













CTRL_DEPTH

Control depth of link, in feet,Corps links only
















WATERWAY

4-digit waterway code from Corps Master_port_waterway
















GEO_CLASS

Geographic Class




G = Great Lakes

O = Ocean / Offshore

I = Inland













FUNC_CLASS

Functional Class




N = no traffic, non-navigable

S = shallow draft (i.e., no deep draft ocean vessels)

D = deep draft

B = Both

U = special vessels only (fishing, pleasure craft, etc; normally no freight traffic)













WTWY_TYPE

Waterway Type




1 = Harbor (including harbor channels), Bay

2 = Intracoastal Waterway

3 = Sealane

4 = Sealane with separation zone

5 = Open water

6 = River, creek, thoroughfare, lake

7 = Estuary

8 = Channel (not including harbor channels)

9 = Canal

10 = Great Lakes direct link (major ports)

11 = Great Lakes indirect link

12 = Corps of Engineers Lock













CHART_ID

4 or 5 digit NOAA chart number or 15 character 1:100K USGS Quad Map ID
















NUM_PAIRS

Number of coordinate pairs that make up the link
















WHO_MOD

Composite code designating what organization modified the link




V = Vanderbilt addition

R = Oak Ridge addition

J = guessed

H = screen digitization from DLGs or TIGER

1 = 94 May

2 = 94 June

R = attributes modified by ORNL

A = attributes modified by Vanderbilt













DATE_MOD

The MODDATE (or modification date)indicates when each record in the database was last changed. As changes are made to a record, the modification date is entered in the format 'mmddyyy'.
















HEADING

Compass Direction




N = North

S = South

E = East

W = West













STATE

State Postal Abbreviation
















FIPS

Primary State FIPS Code
















FIPS2

State FIPS Code
















NON_US

Abbreviation for non-US areas




AC = Arctic Ocean

AT = Atlantic Ocean

BS = Bering Sea

CB = Caribbean Sea

CD = Canada

GM = Gulf of Mexico

PC = Pacific Ocean

PM = Panama

XX = Unidentified Area













VERSION

The VERSION is a 2-digit number that will be incremented for all records in the database whenever a new release is distributed.




00 = 99













DESCRIPT

Based on RIVERNAME
















FGDLAQDATE

Date Geoplan acquired the data
















SHAPE

Feature geometry.
















AUTOID

Unique ID added by GeoPlan
















SHAPE.LEN

Length




























USER NOTES:








RITA/BTS quality checks were completed to cross reference the dataset 
with the state dataset to determine if the spatial data and attribute data 
were accurate within each state.













This data is provided "as is" by GeoPlan and is complete to our knowledge.













GeoPlan relied on the integrity of the attribute information within
the original data.

























The data was created to serve as base information for use in GIS 
systems for a variety of planning and analytical purposes.















The "shape source" field in the link database, and the "node source" field in 
the node database indicate the data sources used to derive link and node 
placements.  The accuracy of each network element is correlated to the 
data source used to derive that element.  For example, links and nodes 
derived from 1:100,000 scale DLGs are more accurate than links and 
nodes derived from 1:500,000 scale NOAA Navigational Charts. Links 
with unknown/missing sources are usually schematic representations of 
USACE links.
Off-Shore:  NOAA Charts vary in scale.  Larger scale charts were used in 
harbor/port areas, while smaller scale charts were used in open water. 
For channels, sea lanes, and Intracoastal Waterways, shape points were 
placed as needed to ensure that link segments fall within waterway boundaries.
Inland:  Links digitized from 1:100,000 DLG files, or large scale NOAA charts 
are the most accurate representations.  Shape points were placed as needed 
to ensure that link segments fall between waterway shorelines.  Links derived 
from Corps milepoints have shape points approximately one mile apart.  
The Corps milepoints were mainly derived from 1:24,000 and 1:100,000 scale maps. 
Therefore, the shape points derived from Corps milepoints are often as accurate 
as shape points derived from 1:100,000 DLG files.  However, line segments 
connecting the shape points may not accurately represent the curvature of 
the waterway.















This data is provided 'as is' and its vertical positional accuracy
has not been verified by GeoPlan















THE DATA INCLUDED IN FGDL ARE 'AS IS' AND SHOULD NOT BE CONSTRUED
AS LEGALLY BINDING. THE UNIVERSITY OF FLORIDA GEOPLAN CENTER SHALL
NOT BE LIABLE FOR ANY DAMAGES SUFFERED AS A RESULT OF USING,
MODIFYING, CONTRIBUTING OR DISTRIBUTING THE MATERIALS.

A note about data scale: 

Scale is an important factor in data usage.  Certain scale datasets
are not suitable for some project, analysis, or modeling 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:125000 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 analysis. 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 webpage at:
http://geoplan.ufl.edu/education.html








REFERENCES: 














DATA LINEAGE SUMMARY: 








Extraction of spatial and type attributes for waterway features from NA, 
DLG and TIGER
Process Date: 1994


Specification of offshore, coastal and Great Lake network nodes and 
links on NOAA, followed by direct digitization of specified nodes and links.
Process Date: 1995


Merging of inland and offshore waterway networks.  A specialized program
was written to merge the two networks.  In general, Vanderbilt node 
locations were accepted as authoritative when both data  sets had 
the same elements.  This meant moving an Oak Ridge link incident to 
that node.  If the link was classified geographically ocean or Great Lakes,
and a Vanderbilt link or chain existed with the same ID and endpoints, 
the Oak Ridge link was discarded, after transfer of Oak Ridge attributes.  
If the Oak Ridge link was within 2 km of the new end nodes' location: and 
1) if a duplicate Vanderbilt link existed with a higher source code, it replaced
 the Oak Ridge link, or 2) the Oak Ridge link was moved by a logistic 
adjustment to the new location.  (This causes modest disruption to the 
preponderance of the shape, yet assured that the angle of approach to the 
displaced end node location was preserved.)  If the link was functionally 
classed "deep draft" and a duplicate Vanderbilt link had an authoritative 
source code, the Oak Ridge link was replaced.  Otherwise an additional 
shape point was added at the end to snap to the new node location without 
disrupting the original link shape.  If the link had a Vanderbilt duplicate with 
the same ID, the Oak Ridge link was so flagged to be manually resolved.  
The composite network was then cleaned manually, resolving all cases of 
still remaining duplicate links and deciding case-by-case how to smooth 
or otherwise accommodate a highly displaced Oak Ridge shape into the 
Vanderbilt digitized node location, using TIGER shorelines as a background.
Process Date: 1994


Heads-up digitizing of WWAY10 to add shape points to inland waterways 
where straight links still existed.  Incorporation of comments from users 
(Vanderbilt, ORNL, and USACE Waterborne Commerce Statistics Center) 
of WWAY10 and error correction.
Process Date: 1995


Upgrades to link shape and attribute data based on information from 
US Army Corps of Engineers CWIS projects as published in their digital 
projects notebook.  Includes the addition of new links, removal of 
unnecessary links/nodes, and splitting of links to more effectively relate 
the digital waterway network to the physical network as maintained by 
the Corps of Engineers.
Process Date: 1999


GeoPlan, during the QA/QC process included the following aspects:
1.) Clipped the dataset to the State of Florida boundary
2.) Reprojected data to FGDL Albers HPGN
3.) DESCRIPT added to attribute table based on RIVERNAME
4.) FGDLAQDATE field added to attribute table
5.) Upcased all character records
Process Date: 20060914









MAP PROJECTION PARAMETERS: 



Projection                          ALBERS
Datum                               HPGN
Units                               METERS
Spheroid                            GRS1980
1st Standard Parallel               24  0  0.000
2nd Standard Parallel               31 30  0.000
Central Meridian                   -84 00  0.000
Latitude of Projection's Origin     24  0  0.000
False Easting (meters)              400000.00000
False Northing (meters)             0.00000




DATA SOURCE CONTACT (S):








Name:
Abbr. Name:
Address:


Phone:

Web site:
E-mail:
Contact Person:
         Phone:
        E-mail:




Bureau of Tranportation Statistics
RITA/BTS
400 7th Street, SW Room 4117
Washington, DC
20590
202-366-DATA


http://www.bts.gov/programs/geographic_information_services/
answers@bts.gov
Geospatial Information Program









FGDL CONTACT:

Name:                   FLORIDA GEOGRAPHIC DATA LIBRARY
Abbr. Name:             FGDL
Address:                Florida Geographic Data Library
                        431 Architecture Building
                        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