Geodataset Name:       NTRAN_2004
Geodataset Type:       SHAPEFILE
Geodataset Feature:    Polyline
Feature Count:         84

DATA SOURCE(S):                    Federal Transit Administration (FTA), Research and Innovative Technology Administration's Bureau of Transportation Statistics (RITA/BTS)
SCALE OF ORIGINAL SOURCE MAPS:     Unknown
DATE OF AUTOMATION OF SOURCE:      2004
GEODATASET EXTENT:                 State of Florida

FEATURE ATTRIBUTE TABLES:

Datafile Name: NTRAN_2004.DBF

FEATURE ATTRIBUTE TABLES CODES AND VALUES:

Item	Item Description
OBJECTID	Internal feature number.
RECID	Unique feature number.
STFIPS	Two digit State FIPS Code
TR_TYPE	Mode of primary transit system AG = Automated guideway CC = Cable car CR = Commuter Rail FB = Ferry Boat HOV = High-occupancy vehicle lanes HR = Heavy Rail IP = Inclined Plane LR = Light Rail MR = Monorail TL = Logical Network Transfer Link
TR_TYPE2	Mode of secondary concurrent transit system AG = Automated guideway CC = Cable car CR = Commuter Rail FB = Ferry Boat HOV = High-occupancy vehicle lanes HR = Heavy Rail IP = Inclined Plane LR = Light Rail MR = Monorail TL = Logical Network Transfer Link
SYSTEM	Name of Primary Transit System
RTS_SRVD	Name of the route(s) served by Primary System on link (Route names delinated by commas e.g. Blue, Red Lines) in alphabetical order
GRD_ELEV	Code defining the grade/elevation of the link. 1 = At grade 2 = Elevated 3 = Below grade 4 = On structure
DIR	Direction of Travel 1 = One Way - Arcs digitized in direction of travel 2 = Two Way - Travel in both directions
UZA	Urbanized Area Name
UACODE	Primary Urbanized Area 5 Digit Code
NTDID	Transit Agency ID of Primary Transit System
AMTRAK	Denotes presence of Amtrak service on link Y = Link carries Amtrak service N = Link does not carry Amtrak service
BEGSTA	Station RECID number for the beginning of an arc (from-node).
ENDSTA	Station RECID number for the end of an arc (to-node).
STATUS	Current status of the link 1 = Planned 2 = Out of service 3 = Active 4 = Under Construction
SOURCE	Identifies source of original data RITA/BTS = Research and Innovative Technology Administration's Bureau of Transportation Statistics (RITA/BTS) DOT = State Department of Transportation MPO = Metropolitan Planning Organization FTA = Federal Transit Administration (FTA) RTA = Responsible Transit Agency DOQ = Digital Ortho Quarter Quads NTL = Network Transfer Link (Logical arc to link stations) FRA = Federal Railroad Administration (FRA) TGR = TIGER 2000 U.S. Bureau of the Census (BOC)
SHAPE_LENG	No description
Shape_Leng	Length of feature in internal units.
VERSION	Version of the database
DESCRIPT	Based on SYSTEM
SHAPE	Feature geometry.
AUTOID	Unique ID added by GeoPlan
SHAPE.LEN	No description
FGDLAQDATE	Date Geoplan acquired the data

USER NOTES:

This database contains fixed-guideway transit features for agencies identified by RITA/BTS. Additional agencies may be added to complete the coverage as work progresses.

Data were processed for FTA's universe of cities based on the availability of source data from FTA, RITA/BTS, or local transit agencies. At this time, coverage is incomplete for the New York City are due to the lack of availability of local transit data.

GeoPlan relied on the integrity of the attribute information within the original data.

The data provide users with information about the location and type of fixed-guideway transit and terminal facilities primarily for regional cartographic, spatial and network analysis purposes.

Right-of-ways for fixed guideways were developed from GIS data provided by FTA, RITA/BTS and local transit agencies. In most cases, the source data are very accurate and complete. In rare cases where the lines were digitized, DOQQ's for the local area were used as a reference for heads-up digitizing. Station locations were verified using street maps, local DOQQ's and USGS DOQ's which were available via the internet from a variety of publically available data clearinghouses. Data include a SOURCE field that identifies the original source of the data.

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

REFERENCES:

National Transportation Atlas Database (NTAD): http://www.bts.gov/ http://www.bts.gov/help/national_transportation_atlas_database.html

DATA LINEAGE SUMMARY:

Source data were compiled from a number of transit sources. The SOURCE field identifies the original source of the data. The source data were checked for duplicate arcs, connectivity problems such as dangles were corrected. All stations were checked for existence and added when necessary. Nodes were added to the Network at Station locations to facilitate routing . Psuedo Nodes where arcs cross without a station are flagged Status = 9. Process Date: Extraction of spatial and type attributes for waterway features from NA, DLG and TIGER Process Date: 1994 Specification of offshore, coastal and Great Lake network nodes and links on NOAA, followed by direct digitization of specified nodes and links. Process Date: 1995 Merging of inland and offshore waterway networks. A specialized program was written to merge the two networks. In general, Vanderbilt node locations were accepted as authoritative when both data sets had the same elements. This meant moving an Oak Ridge link incident to that node. If the link was classified geographically ocean or Great Lakes, and a Vanderbilt link or chain existed with the same ID and endpoints, the Oak Ridge link was discarded, after transfer of Oak Ridge attributes. If the Oak Ridge link was within 2 km of the new end nodes' location: and 1) if a duplicate Vanderbilt link existed with a higher source code, it replaced the Oak Ridge link, or 2) the Oak Ridge link was moved by a logistic adjustment to the new location. (This causes modest disruption to the preponderance of the shape, yet assured that the angle of approach to the displaced end node location was preserved.) If the link was functionally classed "deep draft" and a duplicate Vanderbilt link had an authoritative source code, the Oak Ridge link was replaced. Otherwise an additional shape point was added at the end to snap to the new node location without disrupting the original link shape. If the link had a Vanderbilt duplicate with the same ID, the Oak Ridge link was so flagged to be manually resolved. The composite network was then cleaned manually, resolving all cases of still remaining duplicate links and deciding case-by-case how to smooth or otherwise accommodate a highly displaced Oak Ridge shape into the Vanderbilt digitized node location, using TIGER shorelines as a background. Process Date: 1994 Heads-up digitizing of WWAY10 to add shape points to inland waterways where straight links still existed. Incorporation of comments from users (Vanderbilt, ORNL, and USACE Waterborne Commerce Statistics Center) of WWAY10 and error correction. Process Date: 1995 Upgrades to link shape and attribute data based on information from US Army Corps of Engineers CWIS projects as published in their digital projects notebook. Includes the addition of new links, removal of unnecessary links/nodes, and splitting of links to more effectively relate the digital waterway network to the physical network as maintained by the Corps of Engineers. Process Date: 1999 GeoPlan, during the QA/QC process included the following aspects: 1.) Clipped the dataset to the State of Florida boundary 2.) Reprojected data to FGDL Albers HPGN 3.) DESCRIPT added to attribute table based on SYSTEM 4.) FGDLAQDATE field added to attribute table 5.) Upcased all character records Process Date: 20060918 Dataset copied. Process Date: Metadata imported. Process Date:

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)
FTA
400 7th Street, SW Room 4117
Washington, District of Columbia
20590
202-366-DATA


http://www.bts.gov/programs/geographic_information_services/
answers@bts.gov
Geospatial Information Program

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