INTERMODAL TERMINAL FACILITIES - 2004

Metadata also available as

Metadata:

Identification_Information:
Citation:
Citation_Information:
Originator:
National Transportation Research Center, Oak Ridge National Laboratory, Center for Transportation Analysis
Publication_Date: 20040315
Title: INTERMODAL TERMINAL FACILITIES - 2004
Geospatial_Data_Presentation_Form: vector digital data
Publication_Information:
Publication_Place: Knoxville, TN
Publisher:
National Transportation Research Center, Oak Ridge National Laboratory, Center for Transportation Analysis
Other_Citation_Details: State of Florida
Online_Linkage: <http://www-cta.ornl.gov/transnet/MOpage.html>
Description:
Abstract:
This dataset contains geographic data for trailer-on-flatcar (TOFC) and container-on-flatcar (COFC) highway rail and/or rail-water transfer facilities in the State of Florida. Attribute data specify the intermodal connections at each facility; i.e., the modes involved in the intermodal transfer, the AAR reporting marks of the railroad serving the facility, the type of cargo (always containers/trailers), and the direction of the transfer. This dataset is an update to the 2001 FGDL layer fctf.shp. Please Note: This layer should be used in conjunction with the FGDL layer INTERMODAL.shp which also contains different types of intermodal facilities.
Purpose:
The data was created to serve as base information for use in GIS systems for a variety of planning and analytical purposes.
Supplemental_Information:
CTA Intermodal Terminals Database Overview
The Intermodal Terminals Database (CTA data system MO) is a list of 3100 important transload facilities in the U.S. (157 facilities in Florida) where freight shipments may be transferred between surface modes. It was compiled by David Middendorf in 1998 under the sponsorship of the Bureau of Transportation Statistics, and since that time has only been augmented with new rail-truck TOFC/COFC and auto ramp terminals and to reflect post-Conrail railroad ownership.
By "terminal" is meant a specific facility or site with a single operator, and not an entire port complex, which typically contains several facilities with specialized equipment for transloading different types of cargoes. In general, this terminals set excludes warehouses where goods are stored for a period pending selection of an ultimate destination, even though the warehouse may act as the shipper's consignment agent rather than as receiver of the goods. Also excluded are truck-to-air terminals operated by air freight carriers at airports and truck-to-truck terminals where packages are transferred between local delivery services and line-haul trucks.
The location of each terminal is idealized as a point in the interior of the facility with longitude/latitude coordinates in decimal degrees, datum NAD27. Within the limits of subjective placement, it may be considered to have 100 m geographic accuracy, though many of the terminals represented have docks longer than 100 m, not to mention areal extent.
The formal database is a single ASCII file in Oak Ridge native format, mo43.lmr, which contains a record for each facility and sub-records describing the types of transfers that occur there by cargo type, modes connected, and rail carriers. The fixed format structure of data in the file is explained in notes at the beginning of the file. (Those notes alone may be viewed here at MOnotes.txt.)
All serious users should consult the database documentation which explains the logical structure, coverage, attribute codes, and sources.
An easier-to-use derivative version of the database is also available in ESRI shapefile format. Users are cautioned, however, that it somewhat simplifies the data content of the native format file. The reformat program RHA available in the highway section will also support this data system "M" format.
The above information was taken directly from the following CTA ORNL website: <http://www-cta.ornl.gov/transnet/MOpage.html>
For more information on the INTERMODAL TERMINALS DATABASE: Concepts, Design, Implementation, and Maintenance Please see the following website:
<http://www-cta.ornl.gov/transnet/terminal_doc/index.htm>
Time_Period_of_Content:
Time_Period_Information:
Range_of_Dates/Times:
Beginning_Date: 1998
Ending_Date: 20040315
Currentness_Reference: publication date
Status:
Progress: Complete
Maintenance_and_Update_Frequency: None planned
Spatial_Domain:
Bounding_Coordinates:
West_Bounding_Coordinate: -87.429040
East_Bounding_Coordinate: -79.872251
North_Bounding_Coordinate: 30.983191
South_Bounding_Coordinate: 24.492815
Keywords:
Theme:
Theme_Keyword_Thesaurus: NONE
Theme_Keyword: Terminal
Theme_Keyword: Flatcar
Theme_Keyword: Trailer
Theme_Keyword: TOFC
Theme_Keyword: COFC
Theme_Keyword: Container
Theme_Keyword: Highway
Theme_Keyword: Railroad
Theme_Keyword: Pipeline
Theme_Keyword: Waterway
Theme_Keyword: Air
Theme_Keyword: Transportation
Theme:
Theme_Keyword_Thesaurus: ISO 19115 Topic Category
Theme_Keyword: transportation
Place:
Place_Keyword: Florida
Access_Constraints: NONE
Use_Constraints:
All serious users should consult the database documentation which explains the logical structure, coverage, attribute codes, and sources.
Please Note: Contact was made with Bruce Peterson on 5/21/2009 regarding the update cycle for this layer. During this communication acknowledgement was made by ORNL/CTA that currently there is no maintenance program in existence for this layer. However, information was passed that most of the facilities have lifetimes of several decades, so most of the facilities are still operational. Additionally many rail/truck facilities have minimal capital invested and turnover a lot faster, so there is no doubt that MO is missing a lot after a decade of inattention. Because of this, this layer should be used in conjunction with the FGDL layer INTERMODAL.shp which also contains different types of intermodal facilities.
Point_of_Contact:
Contact_Information:
Contact_Organization_Primary:
Contact_Organization: National Transportation Research Center, ORNL, CTA
Contact_Person: Bruce Peterson
Contact_Address:
Address_Type: mailing address
Address: 2360 Cherahala Boulevard
City: Knoxville
State_or_Province: TN
Postal_Code: 37932
Country: USA
Contact_Voice_Telephone: (865) 946-1352
Contact_Facsimile_Telephone: (865) 946-1314
Contact_Electronic_Mail_Address: petersonbe@ornl.gov
Contact_Instructions:
National Transportation Research Center (NTRC) Oak Ridge National Laboratory (ORNL) Center for Transportation Analysis (CTA)
<http://www-cta.ornl.gov/transnet/Index.html>
Data_Set_Credit:
The Center for Transportation Analysis (CTA) in the Oak Ridge National Laboratory (ORNL)
Native_Data_Set_Environment:
Microsoft Windows XP Version 5.1 (Build 2600) Service Pack 3; ESRI ArcCatalog 9.3.1.1850
Cross_Reference:
Citation_Information:
Other_Citation_Details:
Center for Transportation Analysis Energy Division Oak Ridge National Laboratory INTERMODAL TERMINALS DATABASE: Concepts, Design, Implementation, and Maintenance <http://www-cta.ornl.gov/transnet/terminal_doc/index.htm>
CTA Intermodal Terminals Database <http://www-cta.ornl.gov/transnet/MOpage.html>
CTA Transportation Networks <http://www-cta.ornl.gov/transnet/>
Center for Transportation Analysis <http://cta.ornl.gov/cta/>
Oak Ridge National Laboratory <http://www.ornl.gov/>
Data_Quality_Information:
Attribute_Accuracy:
Attribute_Accuracy_Report:
GeoPlan relied on the integrity of the attribute information within the original data.
Logical_Consistency_Report:
This data is provided 'as is'. GeoPlan relied on the integrity of the original data layer's topology
Completeness_Report:
This data is provided 'as is' by GeoPlan and is complete to our knowledge.
Positional_Accuracy:
Horizontal_Positional_Accuracy:
Horizontal_Positional_Accuracy_Report:
This data is provided 'as is' and its horizontal positional accuracy has not been verified by GeoPlan
Vertical_Positional_Accuracy:
Vertical_Positional_Accuracy_Report:
This data is provided 'as is' and its vertical positional accuracy has not been verified by GeoPlan
Lineage:
Source_Information:
Source_Scale_Denominator: N/A
Type_of_Source_Media: online
Source_Citation_Abbreviation: NTRC / ORNL / CTA
Source_Contribution: Spatial and Attribute Information
Process_Step:
Process_Description:
The Intermodal Terminals Database (CTA data system MO) was compiled by David Middendorf in 1998 under the sponsorship of the Bureau of Transportation Statistics.
The dataset provides location and attribute information for use in national and regional cartographic and network analysis applications. Attribute data were extracted from the IANA 1997 Rail Intermodal Terminal Directory, the Official Railway Guide; the TTX Company Intermodal Directory; World Wide Web home pages of Burlington Northern Santa Fe, Conrail, CSX Transportation, Kansas City Southern, and Norfolk Southern; U.S. Army Corps of Engineers Port Series Reports; Containerization International Yearbook; 1996 AAPA Directory; and various transportation news sources both in print and on the Internet. Attribute data reflect conditions at TOFC/COFC facilities during 1995-96 and are subject to frequent change. Some facilities may be dormant or permanently closed. The database includes TOFC/COFC facilities and marine container terminals with rail connections which were listed the IANA 1997 Rail Intermodal Terminal Directory, the January/February 1997 edition of the Official Railway Guide; the TTX Company Intermodal Directory; the World Wide Web home pages of Burlington Northern Santa Fe Railway, Conrail, CSX Transportation, Kansas City Southern, and Norfolk Southern; U.S. Army Corps of Engineers Port Series Reports; Containerization International Yearbook; 1996 AAPA Directory; and various transportation news sources both in print and on the Internet. The database does not include TOFC/COFC and marine container facilities known to have been closed before or during 1996. However, because of the frequent turnover of this type of facility, some of the terminals included in the database may now be dormant or permanently closed.
The locations of TOFC/COFC facilities were determined using available facility address information and MapExpert, a commercial nationwide digital map database and software package, and recording the longitude/latitude of the approximate center of the facility. Facility locations are not bound to any current or previous highway, railway, or waterway network models.
Source_Used_Citation_Abbreviation: CTA
Process_Date: 1998
Process_Step:
Process_Description:
In general, this file reflects 1998 data as left by David Middendorf, with 2002 updates of TOFC/COFC terminals, and with 2004 post-Conrail railroads updated and new TOFC/COFC terminals.
Source_Used_Citation_Abbreviation: CTA
Process_Date: 20040315
Process_Step:
Process_Description:
The GeoPlan Center downloaded the CTA Intermodal Terminals Database on May 18th, 2009 from the following website:
<http://www-cta.ornl.gov/transnet/MOpage.html>
The data was downloaded as a zipfile. The uncompressed shapefile was originally named moun.shp and it contained 3104 records. The shapefile was defined as decimal degrees, datum NAD27.
Next the shapefile was reprojected to the FGDL NAD83 HARN Albers projection.
Next a selection was made for features falling within the boundary of the State of Florida. This selection set was extracted and named as FCTF_MAR04.shp
Next the attribute table was uppercased.
Next GeoPlan Center added and populated the following fields; -CITY -ZIPCODE -COUNTY -USNG_FL_1K -DESCRIPT -FGDLAQDATE
Please Note: Contact was made with Bruce Peterson on 5/21/2009 regarding the update cycle for this layer. During this communication acknowledgement was made by ORNL/CTA that currently there is no maintenance program in existence for this layer. However, information was passed that most of the facilities have lifetimes of several decades, so most of the facilities are still operational. Additionally many rail/truck facilities have minimal capital invested and turnover a lot faster, so there is no doubt that MO is missing a lot after a decade of inattention. Because of this, this layer should be used in conjunction with the FGDL layer INTERMODAL.shp which also contains different types of intermodal facilities.
Source_Used_Citation_Abbreviation: GeoPlan
Process_Date: 20090518
Process_Step:
Process_Description: Data imported to ArcSDE and exported as a shapefile.
Source_Used_Citation_Abbreviation: GeoPlan
Process_Date: 20090608
Process_Step:
Process_Description: Dataset copied.
Source_Used_Citation_Abbreviation:
Server=delphi.geoplan.ufl.edu; Service=5151; User=etat; Version=SDE.DEFAULT
Process_Date: 20090608
Process_Time: 14320600
Spatial_Data_Organization_Information:
Direct_Spatial_Reference_Method: Vector
Point_and_Vector_Object_Information:
SDTS_Terms_Description:
SDTS_Point_and_Vector_Object_Type: Entity point
Point_and_Vector_Object_Count: 157
Spatial_Reference_Information:
Horizontal_Coordinate_System_Definition:
Planar:
Map_Projection:
Map_Projection_Name: Albers Conical Equal Area
Albers_Conical_Equal_Area:
Standard_Parallel: 24.000000
Standard_Parallel: 31.500000
Longitude_of_Central_Meridian: -84.000000
Latitude_of_Projection_Origin: 24.000000
False_Easting: 400000.000000
False_Northing: 0.000000
Planar_Coordinate_Information:
Planar_Coordinate_Encoding_Method: coordinate pair
Coordinate_Representation:
Abscissa_Resolution: 0.002048
Ordinate_Resolution: 0.002048
Planar_Distance_Units: meters
Geodetic_Model:
Horizontal_Datum_Name: D_North_American_1983_HARN
Ellipsoid_Name: Geodetic Reference System 80
Semi-major_Axis: 6378137.000000
Denominator_of_Flattening_Ratio: 298.257222
Vertical_Coordinate_System_Definition:
Altitude_System_Definition:
Altitude_Resolution: 1.000000
Altitude_Encoding_Method:
Explicit elevation coordinate included with horizontal coordinates
Entity_and_Attribute_Information:
Detailed_Description:
Entity_Type:
Entity_Type_Label: FCTF_MAR04
Entity_Type_Definition: FCTF_MAR04.DBF
Entity_Type_Definition_Source: CTA
Attribute:
Attribute_Label: OBJECTID
Attribute_Definition: Internal feature number.
Attribute_Definition_Source: ESRI
Attribute_Domain_Values:
Unrepresentable_Domain:
Sequential unique whole numbers that are automatically generated.
Attribute:
Attribute_Label: Shape
Attribute_Definition: Feature geometry.
Attribute_Definition_Source: ESRI
Attribute_Domain_Values:
Unrepresentable_Domain: Coordinates defining the features.
Attribute:
Attribute_Label: AJID
Attribute_Definition: Terminal Identification Number.
Attribute_Definition_Source: CTA
Attribute:
Attribute_Label: JLON
Attribute_Definition: Longitude
Attribute_Definition_Source: CTA
Attribute:
Attribute_Label: JLAT
Attribute_Definition: Latitude
Attribute_Definition_Source: CTA
Attribute:
Attribute_Label: NAME
Attribute_Definition: Intermodal Terminal's Facility Name.
Attribute_Definition_Source: CTA
Attribute:
Attribute_Label: STATUS
Attribute_Definition: The Status of the Facility.
Attribute_Definition_Source: CTA
Attribute_Domain_Values:
Enumerated_Domain:
Enumerated_Domain_Value: O
Enumerated_Domain_Value_Definition: Open
Enumerated_Domain_Value_Definition_Source: CTA
Attribute_Domain_Values:
Enumerated_Domain:
Enumerated_Domain_Value: C
Enumerated_Domain_Value_Definition: Closed
Enumerated_Domain_Value_Definition_Source: CTA
Attribute_Domain_Values:
Enumerated_Domain:
Enumerated_Domain_Value: W
Enumerated_Domain_Value_Definition: Warehouse
Enumerated_Domain_Value_Definition_Source: CTA
Attribute:
Attribute_Label: SOURCE
Attribute_Definition: Source of the original information.
Attribute_Definition_Source: CTA
Attribute:
Attribute_Label: CARGO1
Attribute_Definition:
Indicates the first type of cargo that is involved in the transfer.
Attribute_Definition_Source: CTA
Attribute_Domain_Values:
Enumerated_Domain:
Enumerated_Domain_Value: 100
Enumerated_Domain_Value_Definition:
CONTAINERIZED CARGO: cargo shipped in various international and domestic containers and cargo shipped intermodally in highway trailers.
Enumerated_Domain_Value_Definition_Source: CTA
Attribute_Domain_Values:
Enumerated_Domain:
Enumerated_Domain_Value: 210
Enumerated_Domain_Value_Definition: FOOD PRODUCTS
Enumerated_Domain_Value_Definition_Source: CTA
Attribute_Domain_Values:
Enumerated_Domain:
Enumerated_Domain_Value: 220
Enumerated_Domain_Value_Definition:
LUMBER & WOOD: e.g., logs; lumber; mahogany; plywood; pulpwood; timber; and wood posts, poles, and piling.
Enumerated_Domain_Value_Definition_Source: CTA
Attribute_Domain_Values:
Enumerated_Domain:
Enumerated_Domain_Value: 230
Enumerated_Domain_Value_Definition:
METAL PRODUCTS: e.g., iron and steel bars, beams, coils, pipe sections, plates, sheets, slabs, & tubes; aluminum and other non-ferrous metal products.
Enumerated_Domain_Value_Definition_Source: CTA
Attribute_Domain_Values:
Enumerated_Domain:
Enumerated_Domain_Value: 240
Enumerated_Domain_Value_Definition:
MACHINERY: e.g., engines & turbines, farm machinery, construction & earth moving equipment, industry machinery, electric power generators, military equipment, & other heavy equipment.
Enumerated_Domain_Value_Definition_Source: CTA
Attribute_Domain_Values:
Enumerated_Domain:
Enumerated_Domain_Value: 250
Enumerated_Domain_Value_Definition: MOTOR VEHICLES: automobiles, buses, trucks, vans.
Enumerated_Domain_Value_Definition_Source: CTA
Attribute_Domain_Values:
Enumerated_Domain:
Enumerated_Domain_Value: 260
Enumerated_Domain_Value_Definition:
PULP & PAPER PRODUCTS: e.g., fiberboard, paperboard, or pulpboard; linerboard; newsprint; paper rolls; recycled or waste paper; wallboard; & wood pulp.
Enumerated_Domain_Value_Definition_Source: CTA
Attribute_Domain_Values:
Enumerated_Domain:
Enumerated_Domain_Value: 280
Enumerated_Domain_Value_Definition: LIVESTOCK
Enumerated_Domain_Value_Definition_Source: CTA
Attribute_Domain_Values:
Enumerated_Domain:
Enumerated_Domain_Value: 290
Enumerated_Domain_Value_Definition:
OTHER BREAKBULK CARGO: appliances, auto parts, cotton, electronics, rubber products, and other non-containerized goods not elsewhere classified.
Enumerated_Domain_Value_Definition_Source: CTA
Attribute_Domain_Values:
Enumerated_Domain:
Enumerated_Domain_Value: 310
Enumerated_Domain_Value_Definition: COAL
Enumerated_Domain_Value_Definition_Source: CTA
Attribute_Domain_Values:
Enumerated_Domain:
Enumerated_Domain_Value: 320
Enumerated_Domain_Value_Definition: GRAIN: barley, corn, oats, rice, rye, sorghum, soybeans, wheat.
Enumerated_Domain_Value_Definition_Source: CTA
Attribute_Domain_Values:
Enumerated_Domain:
Enumerated_Domain_Value: 330
Enumerated_Domain_Value_Definition:
METALLIC ORES & BULK METALS: misc. ferrous & non-ferrous ores, ferroalloys, pig iron, scrap metal.
Enumerated_Domain_Value_Definition_Source: CTA
Attribute_Domain_Values:
Enumerated_Domain:
Enumerated_Domain_Value: 350
Enumerated_Domain_Value_Definition: CEMENT and/or Fertilizers
Enumerated_Domain_Value_Definition_Source: CTA
Attribute_Domain_Values:
Enumerated_Domain:
Enumerated_Domain_Value: 391
Enumerated_Domain_Value_Definition:
CHEMICALS: e.g., fertilizers, plastic granules & pellets, resin powders, synthetic fibers.
Enumerated_Domain_Value_Definition_Source: CTA
Attribute_Domain_Values:
Enumerated_Domain:
Enumerated_Domain_Value: 392
Enumerated_Domain_Value_Definition:
DRY EDIBLES: e.g., alfalfa pellets, citrus pellets, feeds, flour, meal, peanuts, raw sugar, seeds, starches.
Enumerated_Domain_Value_Definition_Source: CTA
Attribute_Domain_Values:
Enumerated_Domain:
Enumerated_Domain_Value: 393
Enumerated_Domain_Value_Definition: BULK MINE: Sand & Gravel, Salt.
Enumerated_Domain_Value_Definition_Source: CTA
Attribute_Domain_Values:
Enumerated_Domain:
Enumerated_Domain_Value: 410
Enumerated_Domain_Value_Definition: CRUDE OIL
Enumerated_Domain_Value_Definition_Source: CTA
Attribute_Domain_Values:
Enumerated_Domain:
Enumerated_Domain_Value: 420
Enumerated_Domain_Value_Definition: PETROLEUM PRODUCTS
Enumerated_Domain_Value_Definition_Source: CTA
Attribute_Domain_Values:
Enumerated_Domain:
Enumerated_Domain_Value: 491
Enumerated_Domain_Value_Definition: CHEMICALS (also 440)
Enumerated_Domain_Value_Definition_Source: CTA
Attribute_Domain_Values:
Enumerated_Domain:
Enumerated_Domain_Value: 492
Enumerated_Domain_Value_Definition: LIQUID EDIBLES (also 450)
Enumerated_Domain_Value_Definition_Source: CTA
Attribute:
Attribute_Label: CARGO2
Attribute_Definition:
Indicates the second type of cargo that is involved in the transfer. See CARGO1 for value definitions.
Attribute_Definition_Source: CTA
Attribute:
Attribute_Label: CARGO3
Attribute_Definition:
Indicates the third type of cargo that is involved in the transfer. See CARGO1 for value definitions.
Attribute_Definition_Source: CTA
Attribute:
Attribute_Label: CARGO4
Attribute_Definition:
Indicates the fourth type of cargo that is involved in the transfer. See CARGO1 for value definitions.
Attribute_Definition_Source: CTA
Attribute:
Attribute_Label: CARGO5
Attribute_Definition:
Indicates the fifth type of cargo that is involved in the transfer. See CARGO1 for value definitions.
Attribute_Definition_Source: CTA
Attribute:
Attribute_Label: CARGO6
Attribute_Definition:
Indicates the sixth type of cargo that is involved in the transfer. See CARGO1 for value definitions.
Attribute_Definition_Source: CTA
Attribute:
Attribute_Label: MODE1
Attribute_Definition:
The first MODE code for the facility. This code identifying the two modes of transportation involved in the intermodal connection and the direction type of the intermodal transfer between these two modes. MODE TYPES = (A) Air, (H) Highway, (P) Pipeline, (R) Railroad, (W) Waterway. DIRECTION TYPES = (1) A unidirectional transfer bewteen the first mode and the second mode, (2) A bidirectional transfer between the two modes. (EXAMPLE 1: H2W - Highway with a bidirectional transfer to a waterway) (EXAMPLE 2: R1P - Railroad with a unidirectional transfer to a pipeline).
Attribute_Definition_Source: CTA
Attribute:
Attribute_Label: MODE2
Attribute_Definition:
The second MODE code for the facility. This code identifying the two modes of transportation involved in the intermodal connection and the direction type of the intermodal transfer between these two modes. MODE TYPES = (A) Air, (H) Highway, (P) Pipeline, (R) Railroad, (W) Waterway. DIRECTION TYPES = (1) A unidirectional transfer bewteen the first mode and the second mode, (2) A bidirectional transfer between the two modes. (EXAMPLE 1: H2W - Highway with a bidirectional transfer to a waterway) (EXAMPLE 2: R1P - Railroad with a unidirectional transfer to a pipeline).
Attribute_Definition_Source: CTA
Attribute:
Attribute_Label: MODE3
Attribute_Definition:
The third MODE code for the facility. This code identifying the two modes of transportation involved in the intermodal connection and the direction type of the intermodal transfer between these two modes. MODE TYPES = (A) Air, (H) Highway, (P) Pipeline, (R) Railroad, (W) Waterway. DIRECTION TYPES = (1) A unidirectional transfer bewteen the first mode and the second mode, (2) A bidirectional transfer between the two modes. (EXAMPLE 1: H2W - Highway with a bidirectional transfer to a waterway) (EXAMPLE 2: R1P - Railroad with a unidirectional transfer to a pipeline).
Attribute_Definition_Source: CTA
Attribute:
Attribute_Label: MODE4
Attribute_Definition:
The fourth MODE code for the facility. This code identifying the two modes of transportation involved in the intermodal connection and the direction type of the intermodal transfer between these two modes. MODE TYPES = (A) Air, (H) Highway, (P) Pipeline, (R) Railroad, (W) Waterway. DIRECTION TYPES = (1) A unidirectional transfer bewteen the first mode and the second mode, (2) A bidirectional transfer between the two modes. (EXAMPLE 1: H2W - Highway with a bidirectional transfer to a waterway) (EXAMPLE 2: R1P - Railroad with a unidirectional transfer to a pipeline).
Attribute_Definition_Source: CTA
Attribute:
Attribute_Label: RR1
Attribute_Definition:
Association of American Railroads (AAR) reporting mark of the primary rail carrier involved in the intermodal connection.
Attribute_Definition_Source: CTA
Attribute:
Attribute_Label: RR2
Attribute_Definition:
Association of American Railroads (AAR) reporting mark of the secondary rail carrier involved in the intermodal connection.
Attribute_Definition_Source: CTA
Attribute:
Attribute_Label: CITY
Attribute_Definition: The city in which the Intermodal Terminal Facility is located.
Attribute_Definition_Source: GeoPlan
Attribute:
Attribute_Label: ZIPCODE
Attribute_Definition:
The zip code in which the Intermodal Terminal Facility is located.
Attribute_Definition_Source: GeoPlan
Attribute:
Attribute_Label: COUNTY
Attribute_Definition:
The county in which the Intermodal Terminal Facility is located.
Attribute_Definition_Source: GeoPlan
Attribute:
Attribute_Label: USNG_FL_1K
Attribute_Definition:
Facility's 1-kilometer United States National Grid (USNG) address. The USNG is an alpha-numeric reference system based on the UTM coordinate system and is similar to the Military Grid Reference System. Use of the USNG ensures a uniform grid mapping and positional reporting system for search and rescue, emergency planning, response, and recovery. How to Read a United States National Grid (USNG) Spatial Address Website - <http://www.fgdc.gov/usng/how-to-read-usng/index_html>
Attribute_Definition_Source: GeoPlan
Attribute:
Attribute_Label: DESCRIPT
Attribute_Definition: Based on the Field NAME.
Attribute_Definition_Source: GeoPlan
Attribute:
Attribute_Label: FGDLAQDATE
Attribute_Definition: The date FGDL acquired the data from the Source.
Attribute_Definition_Source: GeoPlan
Attribute:
Attribute_Label: AUTOID
Attribute_Definition: Unique ID added by GeoPlan
Attribute_Definition_Source: GeoPlan
Distribution_Information:
Distributor:
Contact_Information:
Contact_Organization_Primary:
Contact_Organization: Florida Geographic Data Library (FGDL)
Contact_Address:
Address_Type: mailing address
Address: 431 Architecture PO Box 115706
City: Gainesville
State_or_Province: Florida
Postal_Code: 32611-5706
Country: United States
Contact_Electronic_Mail_Address: Web site: <http://www.fgdl.org>
Contact_Electronic_Mail_Address: Technical Support: <http://www.fgdl.org/fgdlfeed.html>
Contact_Electronic_Mail_Address: For FGDL Software: <http://www.fgdl.org/software.html>
Contact_Electronic_Mail_Address:
FGDL Frequently Asked Questions: <http://www.fgdl.org/fgdlfaq.html>
Contact_Electronic_Mail_Address: Mailing list for FGDL: <http://www.fgdl.org/fgdl-l.html>
Resource_Description: DOWNLOADABLE DATA
Distribution_Liability:
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>
Standard_Order_Process:
Digital_Form:
Digital_Transfer_Information:
Transfer_Size: 0.004
Technical_Prerequisites:
This data is intended for use with a Geographic Information Systems or Remote Sensing software package.
Metadata_Reference_Information:
Metadata_Date: 20090628
Metadata_Contact:
Contact_Information:
Contact_Organization_Primary:
Contact_Organization: National Transportation Research Center, ORNL, CTA
Contact_Person: Bruce Peterson
Contact_Address:
Address_Type: mailing address
Address: 2360 Cherahala Boulevard
City: Knoxville
State_or_Province: TN
Postal_Code: 37932
Country: USA
Contact_Voice_Telephone: (865) 946-1352
Contact_Electronic_Mail_Address: petersonbe@ornl.gov
Metadata_Standard_Name: FGDC Content Standards for Digital Geospatial Metadata
Metadata_Standard_Version: FGDC-STD-001-1998
Metadata_Time_Convention: local time
Metadata_Extensions:
Online_Linkage: <http://www.esri.com/metadata/esriprof80.html>
Profile_Name: ESRI Metadata Profile
Generated by mp version 2.9.6 on Sun Jun 28 20:16:30 2009