Geodataset Name:       ACPORT_2010
Geodataset Type:       SHAPEFILE
Geodataset Feature:    Point
Feature Count:         415

DATA SOURCE(S):                    U.S. Army Corps of Engineers
SCALE OF ORIGINAL SOURCE MAPS:     Varies
GEODATASET EXTENT:                 State of Florida

PUBLICATION DATE:                  2010
TIME PERIOD OF CONTENT:            2010
DOWNLOAD LINK:                     http://www.fgdl.org/metadataexplorer/explorer.jsp

FEATURE ATTRIBUTE TABLES:

Datafile Name: ACPORT_2010.DBF

FEATURE ATTRIBUTE TABLES CODES AND VALUES:

Item	Item Description
OBJECTID	Internal feature number.
Shape	Feature geometry.
ID	Unique Identifier
NAME	Wharf Name
LOCATION	Location of wharf on wharf waterway or in port
ADDRESS	Street address for wharf location
COUNTY	County in which wharf is located
TOWN	Town in which wharf is located
STATE	State in which wharf is located
WATERWAY	Waterway on which wharf is located
PORT_NAME	Port in which the wharf is located
MILE	Waterway mile of wharf location above or below a datum point
BANK	Bank of river for wharf location (Left or Right)
LATDEC	WHARF LOCATION LATITUDE: DECIMAL
LONG_DEC	WHARF LOCATION LONGITUDE: DECIMAL
OPERATOR1	Operator of wharf
OWNER	Owner of wharf
PURPOSE	Purpose for which wharf is used, including commodities handled and/or services performed
RWY_CONN	Railway connections servicing wharf
PORTSERIES	Port Series Report Number (One of 57, Hard Copy)
SEQNO	Unique number that is generated within each port series number
LOC_CD	Location code generated by waterborne commerce statistics center (WCSC)
PWDNO	Pier, wharf or dock record sequence number from current edition of port series report
OLDPWD	Pier, wharf or dock record sequence number from previous edition of Port Series Report
DOCKCD	Location code designating where a dock is located generated by WCSC
NDCCODE	Internal code generated by the navigation data center for data integration and system interoperability
CNGDST	Congressional district of structure
COMMODITY1	Commodity code for first commodity handled at wharf
COMMODITY2	Commodity code for second commodity handled at wharf
COMMODITY3	Commodity code for third commodity handled at wharf
COMMODITY4	Commodity code for fourth commodity handled at wharf
REMARKS	Remarks, including description of wharf - related storage facilities and their operators
DATUM	Depth/Height Datum Used
DEPTH1	Depth alongside wharf's first operational element being described
DEPTH1A	Second depth alongside wharf's first operational element being described
DEPTH2	Depth alongside wharf's second operational element being described
DEPTH2A	Second depth alongside wharf's second operational element being described
DEPTH3	Depth alongside wharf's third operational element being described
DEPTH3A	Second depth alongside wharf's third operational element being described
TOTBERTH1	Berthing distance of wharf's first operational element being described
TOTBERTH2	Berthing distance of wharf's second operational element being described
TOTBERTH3	Berthing distance of wharf's third operational element being described
YEAR	Year of last survey
MAPNO	Port series report map no.
FIRSTNAME	First name of contact person
LASTNAME	Last name of contact person
PHONE	Telephone number of facility operator or contact person
FAX	Fax telephone number of facility operator or contact person
STFIPS	The 2-character FIPS code of the State or State equivalent
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	Based on NAME.
FGDLAQDATE	The date GeoPlan acquired the data from the source.
AUTOID	Unique ID added by GeoPlan

USER NOTES:

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 2010 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

REFERENCES:

U.S Waterway Data: http://www.iwr.usace.army.mil/ndc/data/datapwd.htm

DATA LINEAGE SUMMARY:

Extraction of the USACE identified port nodes from the National Waterway Network file. Process Date: 2006 In July 2010 Geoplan obtained the data from the Bureau of Transportation Statistics in CDROM format. During the QA/QC process, GeoPlan performed the following tasks. - Extracted features where "STATEFIPS" = '12' to select features in Florida - Reprojected Florida selection set from GCS_WGS_1984 to Albers Conical Equal Area (Florida Geographic Data Library) - Uppercased all fields - Added DESCRIPT field based on NAME - Added FGDLAQDATE field based on the date GeoPlan received the data - Renamed the dataset from ports to acport_2010 Process Date: 20100812 Data imported to ArcSDE and exported as a shapefile. Process Date: 20100914

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:

Research and Innovative Technology Administration's Bureau of Transportation Statistics (RITA/BTS)
BTS/RITA
1200 New Jersey Ave. S.E.
Washington, DC
20590
(202) 366-3282


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

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