FLORIDA GEOGRAPHIC DATA LIBRARY DOCUMENTATION

TITLE: INTERMODAL TERMINAL FACILITIES - 2004

Geodataset Name:       FCTF_MAR04
Geodataset Type:       SHAPEFILE
Geodataset Feature:    Point
Feature Count:         157
GENERAL DESCRIPTION:
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.
DATA SOURCE(S):                    National Transportation Research Center, Oak Ridge National Laboratory, Center for Transportation Analysis
SCALE OF ORIGINAL SOURCE MAPS:     N/A
GEODATASET EXTENT:                 State of Florida
PUBLICATION DATE: 20040315 TIME PERIOD OF CONTENT: Begin Date: 1998 End Date: 20040315 DOWNLOAD LINK: http://www.fgdl.org/metadataexplorer/explorer.jsp

FEATURE ATTRIBUTE TABLES:

Datafile Name: FCTF_MAR04.DBF
ITEM NAME WIDTH TYPE
OBJECTID
4 OID
Shape
4 Geometry
AJID
10 String
JLON
8 Double
JLAT
8 Double
NAME
30 String
STATUS
1 String
SOURCE
4 String
CARGO1
3 String
CARGO2
3 String
CARGO3
3 String
CARGO4
3 String
CARGO5
3 String
CARGO6
3 String
MODE1
3 String
MODE2
3 String
MODE3
3 String
MODE4
3 String
RR1
4 String
RR2
4 String
CITY
40 String
ZIPCODE
4 Integer
COUNTY
35 String
USNG_FL_1K
10 String
DESCRIPT
30 String
FGDLAQDATE
36 Date
AUTOID
4 Integer

FEATURE ATTRIBUTE TABLES CODES AND VALUES:

Item
Item Description
OBJECTID Internal feature number.

Shape Feature geometry.

AJID Terminal Identification Number.

JLON Longitude

JLAT Latitude

NAME Intermodal Terminal's Facility Name.

STATUS The Status of the Facility.
O = Open

C = Closed

W = Warehouse


SOURCE Source of the original information.

CARGO1 Indicates the first type of cargo that is involved in the transfer.
100 = CONTAINERIZED CARGO: cargo shipped in various international and domestic containers and cargo shipped intermodally in highway trailers.

210 = FOOD PRODUCTS

220 = LUMBER & WOOD: e.g., logs; lumber; mahogany; plywood; pulpwood; timber; and wood posts, poles, and piling.

230 = METAL PRODUCTS: e.g., iron and steel bars, beams, coils, pipe sections, plates, sheets, slabs, & tubes; aluminum and other non-ferrous metal products.

240 = MACHINERY: e.g., engines & turbines, farm machinery, construction & earth moving equipment, industry machinery, electric power generators, military equipment, & other heavy equipment.

250 = MOTOR VEHICLES: automobiles, buses, trucks, vans.

260 = PULP & PAPER PRODUCTS: e.g., fiberboard, paperboard, or pulpboard; linerboard; newsprint; paper rolls; recycled or waste paper; wallboard; & wood pulp.

280 = LIVESTOCK

290 = OTHER BREAKBULK CARGO: appliances, auto parts, cotton, electronics, rubber products, and other non-containerized goods not elsewhere classified.

310 = COAL

320 = GRAIN: barley, corn, oats, rice, rye, sorghum, soybeans, wheat.

330 = METALLIC ORES & BULK METALS: misc. ferrous & non-ferrous ores, ferroalloys, pig iron, scrap metal.

350 = CEMENT and/or Fertilizers

391 = CHEMICALS: e.g., fertilizers, plastic granules & pellets, resin powders, synthetic fibers.

392 = DRY EDIBLES: e.g., alfalfa pellets, citrus pellets, feeds, flour, meal, peanuts, raw sugar, seeds, starches.

393 = BULK MINE: Sand & Gravel, Salt.

410 = CRUDE OIL

420 = PETROLEUM PRODUCTS

491 = CHEMICALS (also 440)

492 = LIQUID EDIBLES (also 450)


CARGO2 Indicates the second type of cargo that is involved in the transfer. See CARGO1 for value definitions.

CARGO3 Indicates the third type of cargo that is involved in the transfer. See CARGO1 for value definitions.

CARGO4 Indicates the fourth type of cargo that is involved in the transfer. See CARGO1 for value definitions.

CARGO5 Indicates the fifth type of cargo that is involved in the transfer. See CARGO1 for value definitions.

CARGO6 Indicates the sixth type of cargo that is involved in the transfer. See CARGO1 for value definitions.

MODE1 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).

MODE2 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).

MODE3 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).

MODE4 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).

RR1 Association of American Railroads (AAR) reporting mark of the primary rail carrier involved in the intermodal connection.

RR2 Association of American Railroads (AAR) reporting mark of the secondary rail carrier involved in the intermodal connection.

CITY The city in which the Intermodal Terminal Facility is located.

ZIPCODE The zip code in which the Intermodal Terminal Facility is located.

COUNTY The county in which the Intermodal Terminal Facility is located.

USNG_FL_1K 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

DESCRIPT Based on the Field NAME.

FGDLAQDATE The date FGDL acquired the data from the Source.

AUTOID Unique ID added by GeoPlan


USER NOTES:
This data is provided 'as is'. GeoPlan relied on the integrity
of the original data layer's topology
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.
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

The data was created to serve as base information for use in GIS systems 
for a variety of planning and analytical purposes.

This data is provided 'as is' and its horizontal positional accuracy
has not been verified by GeoPlan

This data is provided 'as is' and its vertical positional accuracy
has not been verified by GeoPlan

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.

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:
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 LINEAGE SUMMARY:
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.
Process Date: 1998

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. Process Date: 20040315
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. Process Date: 20090518
Data imported to ArcSDE and exported as a shapefile. Process Date: 20090608
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:
National Transportation Research Center, ORNL, CTA
NTRC / ORNL / CTA
2360 Cherahala Boulevard
Knoxville, TN
37932
(865) 946-1352

http://www-cta.ornl.gov/transnet/MOpage.html petersonbe@ornl.gov Bruce Peterson

FGDL CONTACT:
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