FLORIDA GEOGRAPHIC DATA LIBRARY DOCUMENTATION TITLE: U.S. ARMY CORP OF ENGINEERS PORTS IN FLORIDA - 2013 Geodataset Name: ACPORT_2013 Geodataset Type: SHAPEFILE Geodataset Feature: Point Feature Count: 1117 |
|
GENERAL DESCRIPTION:
|
|
DATA SOURCE(S): U.S. Army Corps of Engineers SCALE OF ORIGINAL SOURCE MAPS: Varies GEODATASET EXTENT: State of Florida |
FEATURE ATTRIBUTE TABLES:
Datafile Name: ACPORT_2013.DBF
ITEM NAME | WIDTH | TYPE |
OBJECTID
|
4 | OID |
Shape
|
4 | Geometry |
ID
|
8 | Double |
NAV_UNIT_I
|
4 | String |
UNLOCODE
|
3 | String |
NAV_UNIT_N
|
150 | String |
LOCATION_D
|
254 | String |
FACILITY_T
|
100 | String |
STREET_ADD
|
100 | String |
CITY_OR_TO
|
50 | String |
STATE_POST
|
2 | String |
ZIPCODE
|
10 | String |
COUNTY_NAM
|
31 | String |
CONGRESS
|
3 | String |
CONGRESS_F
|
2 | String |
WTWY_NAME
|
130 | String |
LOCATION
|
4 | Integer |
PORT_NAME
|
130 | String |
LATITUDE1
|
8 | Double |
LONGITUDE1
|
8 | Double |
OPERATORS
|
254 | String |
OWNERS
|
254 | String |
HIGHWAY_NO
|
254 | String |
RAILWAY_NO
|
254 | String |
DOCK
|
2 | SmallInteger |
COMMODITIE
|
254 | String |
CONSTRUCTI
|
254 | String |
MECHANICAL
|
254 | String |
MILE
|
8 | Double |
VERTICAL_D
|
50 | String |
DEPTH_MIN
|
8 | Double |
DEPTH_MAX
|
8 | Double |
BERTHING_L
|
4 | Integer |
BERTHING_T
|
4 | Integer |
DECK_HEIGH
|
8 | Double |
DECK_HEIG1
|
8 | Double |
SERVICE_IN
|
50 | String |
BANK
|
11 | String |
CTFIPS
|
3 | String |
PURPOSE
|
254 | String |
REMARKS
|
254 | String |
STFIPS
|
2 | String |
DESCRIPT
|
100 | String |
FGDLAQDATE
|
36 | Date |
AUTOID
|
4 | Integer |
FEATURE ATTRIBUTE TABLES CODES AND VALUES:
Item | Item Description | |
OBJECTID |
Internal feature number. |
|
Shape |
Feature geometry. |
|
ID |
Unique Identifier |
|
NAV_UNIT_I |
Alphanumeric unique identifier for a facility |
|
UNLOCODE |
United Nations Location Code |
|
NAV_UNIT_N |
Name of facility |
|
LOCATION_D |
Textual description of the location of the facility |
|
FACILITY_T |
Facility type i.e. ('Dock', 'Fleeting Area', 'Lock and/or Dam', 'Milepoint', etc.) |
|
STREET_ADD |
Address of facility |
|
CITY_OR_TO |
City or town where facility is located |
|
STATE_POST |
State where facility is located |
|
ZIPCODE |
Postal zip code |
|
COUNTY_NAM |
County name |
|
CONGRESS |
Congress number (i.e. 108, 109, etc.) |
|
CONGRESS_F |
Congressional District FIPS code |
|
WTWY_NAME |
Name of waterway where facility is located |
|
LOCATION |
Location of wharf on wharf waterway or in port |
|
PORT_NAME |
Port in which the wharf is located |
|
LATITUDE1 |
Latitude |
|
LONGITUDE1 |
Longitude |
|
OPERATORS |
Current operators of the facility with phone and fax numbers |
|
OWNERS |
Current owner or owner/operators of the facility with phone and fax numbers |
|
HIGHWAY_NO |
Surface road connections |
|
RAILWAY_NO |
Railway connections |
|
DOCK |
Waterborne Commerce Statistics Center's three digit dock code |
|
COMMODITIE |
List of commodities handled at the facility at the two digit Lock Performance Monitoring System level |
|
CONSTRUCTI |
Description of type of construction |
|
MECHANICAL |
Description of equipment available at the facility |
|
MILE |
Waterway mile of wharf location above or below a datum point |
|
VERTICAL_D |
Depth/Height Datum used |
|
DEPTH_MIN |
Minimum depth alongside facility |
|
DEPTH_MAX |
Maximum depth alongside facility |
|
BERTHING_L |
Largest single berthing space in feet |
|
BERTHING_T |
Total berthing space in feet |
|
DECK_HEIGH |
Minimum deck height |
|
DECK_HEIG1 |
Maximum deck height |
|
SERVICE_IN |
Date facility started service |
|
BANK |
Bank of river for wharf location (Left or Right) |
|
CTFIPS |
The 3-character FIPS code of the County |
|
PURPOSE |
Purpose for which wharf is used, including commodities handled and/or services performed |
|
REMARKS |
Remarks, including description of wharf - related storage facilities and their operators |
|
STFIPS |
The 2-character FIPS code of the State or State equivalent |
|
DESCRIPT |
GeoPlan added field based on NAV_UNIT_N |
|
FGDLAQDATE |
The date GeoPlan acquired the data from the source. |
|
AUTOID |
Unique ID added by GeoPlan |
RITA/BTS quality checks were to cross reference the place dataset with the state dataset, to determine that the spatial data and attribute data were accurate |
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. |
A description of the physical and Intermodal (infrastructure) characteristics of the ports in Florida. |
The Navigation Data Center had several objectives in developing the U.S. Waterway Data. These objectives support the concept of a National Spatial Data Provide public access to national waterway data. Foster interagency and intra-agency cooperation through data sharing. Provide a mechanism to integrate waterway data (U.S. Army Corps of Engineers Port/Facility and U.S. Coast Guard Accident Data, for example) Provide a basis for intermodal analysis. Assist standardization of waterway entity definitions (Ports/Facilities, Locks, etc.). Provide public access to the National Waterway Network, which can be used as a basemap to support graphical overlays and analysis with other spatial data (waterway and modal network/facility databases, for example). Provide reliable data to support future waterway and intermodal applications. |
The accuracy of each point element is correlated to the data source used to derive that element. For example, links and nodes derived from 1:100,000 scale Digital Line Graphs are more accurate than links and nodes derived from 1:500,000 scale NOAA Navigational Charts. Elements with an "M" in the source field (indicating an unknown or missing source) are the least accurate. |
This data is provided 'as is' and its vertical positional accuracy has not been verified by GeoPlan |
None. Acknowledgment of the Research and Innovative Technology Administration's Bureau of Transportation Statistics National Transportation Atlas Database 2013 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: http://geoplan.ufl.edu/education.html |
U.S Waterway Data: http://www.iwr.usace.army.mil/ndc/data/datapwd.htm |
Extraction of the USACE identified port nodes from the National Waterway Network file. Process Date: 2006 |
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: |
Research and Innovative Technology Administration's Bureau of Transportation Statistics, U.S. Army Corps of Engineers BTS/RITA/USACE 1200 New Jersey Ave. S.E. Washington, D.C. 20590 (202) 366-3282 |
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