FLORIDA GEOGRAPHIC DATA LIBRARY DOCUMENTATION VERSION 2006 TITLE: US ARMY CORP OF ENGINEERS PORTS Geodataset Name: ACPORT_2006 Geodataset Type: SHAPEFILE Geodataset Feature: Point Feature Count: 416 |
|
GENERAL DESCRIPTION:
|
|
DATA SOURCE(S): US Army Corps of Engineers (USACE)Research and Innovative Technology Administration's Bureau of Transportation Statistics (RITA/BTS) SCALE OF ORIGINAL SOURCE MAPS: 100000 DATE OF AUTOMATION OF SOURCE: 2006 GEODATASET EXTENT: State of Florida |
FEATURE ATTRIBUTE TABLES:
Datafile Name: ACPORTS_2006.DBF
ITEM NAME | WIDTH | TYPE | N. DECIMAL DEGREES |
OBJECTID
|
4 | OID | --- |
ID
|
10 | Number | --- |
LONGITUDE
|
10 | Number | --- |
LATITUDE
|
10 | Number | --- |
NAME
|
200 | String | --- |
LOCATION
|
30 | String | --- |
ADDRESS
|
50 | String | --- |
COUNTY
|
30 | String | --- |
COUNTY_FIP
|
2 | String | --- |
TOWN
|
30 | String | --- |
STATE
|
2 | String | --- |
WTRWY
|
50 | String | --- |
PORT
|
21 | String | --- |
MILE
|
5 | Number | --- |
BANK
|
5 | String | --- |
LATDEC
|
17 | Number | 5 |
LONGDEC
|
18 | Number | 5 |
OPERTOR1
|
150 | String | --- |
OWNER
|
120 | String | --- |
PURPOSE
|
254 | String | --- |
RWYCONN
|
250 | String | --- |
PORTSER
|
4 | String | --- |
SEQ_NO
|
3 | String | --- |
LOC_CD
|
5 | String | --- |
PWDNO
|
5 | String | --- |
OLDPWD
|
5 | String | --- |
DOCKCD
|
3 | Number | --- |
NDCCODE
|
10 | String | --- |
CNGDST
|
5 | String | --- |
COMM_CD1
|
2 | String | --- |
COMM_CD2
|
2 | String | --- |
COMM_CD3
|
2 | String | --- |
COMM_CD4
|
2 | String | --- |
REMARK1
|
240 | String | --- |
REMARK2
|
240 | String | --- |
REMARK3
|
240 | String | --- |
DATUM
|
4 | String | --- |
DEPTH1
|
2 | String | --- |
DEPTH1A
|
2 | String | --- |
DEPTH2
|
2 | String | --- |
DEPTH2A
|
2 | String | --- |
DEPTH3
|
2 | String | --- |
DEPTH3A
|
2 | String | --- |
TBIRTH1
|
5 | String | --- |
TBIRTH2
|
5 | String | --- |
TBIRTH3
|
5 | String | --- |
YEAR
|
4 | String | --- |
MAPNO
|
3 | String | --- |
FNAME
|
50 | String | --- |
LNAME
|
50 | String | --- |
PHONE
|
43 | String | --- |
FAX
|
12 | String | --- |
STFIPS
|
2 | String | --- |
VERSION
|
2 | String | --- |
DESCRIPT
|
50 | String | --- |
FGDLAQDATE
|
8 | Date | --- |
SHAPE
|
4 | Geometry | --- |
AUTOID
|
4 | Integer | --- |
FEATURE ATTRIBUTE TABLES CODES AND VALUES:
Item | Item Description | |
OBJECTID |
Internal feature number. |
|
ID |
Unique Identifier |
|
LONGITUDE |
The longitude of the point expressed as a signed real number. This value is in decimal degrees with negative values indicating West longitude and positive values indicating East longitude. |
|
LATITUDE |
The latitude of the point expressed as a signed real number. This value is in decimal degrees with negative values indicating South latitude and positive values indicating North latitude. |
|
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 |
|
COUNTY_FIP |
County FIPS Code |
|
TOWN |
Town in which wharf is located |
|
STATE |
State in which wharf is located |
|
WTRWY |
Waterway on which wharf is located |
|
PORT |
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 |
|
LONGDEC |
Wharf location longitude: Decimal |
|
OPERTOR1 |
Operator of wharf |
|
OWNER |
Owner of wharf |
|
PURPOSE |
Purpose for which wharf is used, including commodities handled and/or services performed |
|
RWYCONN |
Railway connections servicing wharf |
|
PORTSER |
Port Series Report Number (One of 57, Hard Copy) |
|
SEQ_NO |
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 |
|
COMM_CD1 |
Commodity code for first commodity handled at wharf |
|
COMM_CD2 |
Commodity code for second commodity handled at wharf |
|
COMM_CD3 |
Commodity code for third commodity handled at wharf |
|
COMM_CD4 |
Commodity code for fourth commodity handled at wharf |
|
REMARK1 |
Remarks, including description of wharf - related storage facilities and their operators |
|
REMARK2 |
Remarks, including description of wharf - related storage facilities and their operators |
|
REMARK3 |
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 |
|
TBIRTH1 |
Berthing distance of wharf's first operational element being described |
|
TBIRTH2 |
Berthing distance of wharf's second operational element being described |
|
TBIRTH3 |
Berthing distance of wharf's third operational element being described |
|
YEAR |
Year of last survey |
|
MAPNO |
Port series report map no. |
|
FNAME |
First name of contact person |
|
LNAME |
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 |
Date Geoplan acquired data |
|
SHAPE |
Feature geometry. |
|
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. |
|
The Ports database is a geographic database of the US Army Corps of Engineers Ports in and around the United States, for analytical studies of waterway performance, for compiling commodity flow statistics, and for mapping purposes. The data was created to serve as base information for use in GIS systems for a variety of planning and analytical purposes. |
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 |
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 |
National Transportation Atlas Database (NTAD): http://www.bts.gov/ http://www.bts.gov/help/national_transportation_atlas_database.html |
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 (RITA/BTS) USACE 400 7th Street, SW Room 4117 Washington, DC 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