Geodataset Name:       BTSWW_2012
Geodataset Type:       SHAPEFILE
Geodataset Feature:    Polyline
Feature Count:         458
This dataset contains the Florida subset of the National Waterway Network. The National Waterway Network is a comprehensive network database of the nation's navigable waterways. The data set covers the 48 contiguous states plus the District of Columbia, Hawaii, Alaska, Puerto Rico and water links between. The nominal scale of the dataset varies with the source material. The majority of the information is at 1:100,000 with larger scales used in harbor/bay/port areas and smaller scales used in open waters. This is an update to the btsww_2011 layer.
DATA SOURCE(S):                    Vanderbilt Engineering Center for Transportation Operations, U.S. Army Corps of Engineers Navigation Data Center, & RITA/BTS
GEODATASET EXTENT:                 State of Florida
PUBLICATION DATE: 2012 TIME PERIOD OF CONTENT: 2012 DOWNLOAD LINK: http://www.fgdl.org/metadataexplorer/explorer.jsp


Datafile Name: BTSWW_2012.DBF
4 Geometry
8 Double
8 Double
8 Double
8 Double
8 Double
35 String
35 String
8 Double
8 Double
8 Double
1 String
6 String
10 String
8 Double
10 String
1 String
2 String
4 Integer
15 String
4 Integer
3 String
8 String
1 String
2 String
2 String
2 String
2 String
31 String
36 Date
4 Integer
0 Double


Item Description
OBJECTID Internal feature number.

Shape Feature geometry.
Polyline = Polylinear shapes as defined by ArcView

ID Unique Link identification number

LENGTH Link length in Miles
real = with one explicit decimal place

LINKNUM 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 = Vanderbilt 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

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

DESCRIPT GeoPlan added field based on RIVERNAME.

FGDLAQDATE The date GeoPlan acquired the data from the source.

AUTOID Unique ID added by GeoPlan

SHAPE.LEN Length in meters

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
GeoPlan relied on the integrity of the attribute information within
the original data.
Links in the waterway network represent actual shipping 
lanes or serve as representative paths in open water 
where no defined shipping lanes exist. Nodes may 
represent physical entities such as river confluences, 
ports/facilities, and intermodal terminals, US Army Corps 
of Engineers (USACE nodes), or may be inserted for 
analytical purposes. Approximately 180 USACE ports are 
geo-coded in the node database.

The National Waterway Network is a geographic database 
of navigable waterways in and around the United States, 
for analytical studies of waterway performance, for compiling 
commodity flow statistics, and for mapping 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

Acknowledgment of Research and Innovative Technology 
Administration's Bureau of Transportation Statistics (RITA/BTS) 
National Transportation Atlas Databases (NTAD) 2012 
would be appreciated in products derived from these data.

The Florida Geographic Data Library is a collection of Geospatial Data
compiled by the University of Florida GeoPlan Center with support from
the Florida Department of Transportation. GIS data available in FGDL is
collected from various state, federal, and other agencies (data sources)
who are data stewards, producers, or publishers. The data available in
FGDL may not be the most current version of the data offered by the
data source. University of Florida GeoPlan Center makes no guarantees
about the currentness of the data and suggests that data users check
with the data source to see if more recent versions of the data exist.

Furthermore, the GIS data available in the FGDL are provided 'as is'.
The University of Florida GeoPlan Center makes no warranties, guaranties
or representations as to the truth, accuracy or completeness of the data
provided by the data sources. The University of Florida GeoPlan Center
makes no representations or warranties about the quality or suitability
of the materials, either expressly or implied, including but not limited
to any implied warranties of merchantability, fitness for a particular
purpose, or non-infringement. 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:

National Transportation Atlas Database:

Bureau of Transportation Statistics:

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: 19950101

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: 19940101
Specification of offshore, coastal and Great Lake network nodes and links on NOAA, followed by direct digitization of specified nodes and links. Process Date: 19950101
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: 19990101
Extraction of spatial and type attributes for waterway features from NA, DLG and TIGER Process Date: 19940101
In September 2012 GeoPlan obtained the data from the Bureau of Transportation Statistics (BTS) in CDROM format. The data was in the following geographical coordinate system: WGS 1984 Datum, Units: Degrees. During the QA/QC process GeoPlan performed the following tasks. - Extracted features where "FIPS" = '12' or "FIPS2" = '12 to select features in Florida. Hand selected additional features in the vicinity of the coast of Florida. - Reprojected the data to FGDL Albers HPGN. - Uppercased all fields. - Removed empty fields. - Added DESCRIPT field based on RIVERNAME. - Added FGDLAQDATE field based on the date GeoPlan received the data from the source. - Renamed the dataset from waterway to btsww_2012 Process Date: 20120918

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


Abbr. Name:


Web site:
Contact Person:
Research and Innovative Technology Administration's Bureau of Transportation Statistics (RITA/BTS)
1200 New Jersey Ave. SE
Washington, DC

http://www.bts.gov/programs/geographic_information_services/ answers@bts.gov Office of Geospatial Information Systems

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