FLORIDA GEOGRAPHIC DATA LIBRARY DOCUMENTATION

TITLE: PUBLIC TRANSIT ROUTES IN FLORIDA - 2019

Geodataset Name:       TRRTS_2019
Geodataset Type:       SHAPEFILE
Geodataset Feature:    Polyline
Feature Count:         3348
GENERAL DESCRIPTION:
This dataset contains Florida's public transit routes. This data represents a snapshot of transit offerrings from when the data was made available by the source, for current information please contact the source agency. This dataset does not include many local community buses, shuttles, and trolleys.
DATA SOURCE(S):                    Florida Transit Information System
SCALE OF ORIGINAL SOURCE MAPS:     Unknown
GEODATASET EXTENT:                 State of Florida
PUBLICATION DATE: 20190820 TIME PERIOD OF CONTENT: 201906 DOWNLOAD LINK: http://www.fgdl.org/metadataexplorer/explorer.jsp

FEATURE ATTRIBUTE TABLES:

Datafile Name: TRRTS_2019.DBF
ITEM NAME WIDTH TYPE
OBJECTID
4 OID
Shape
4 Geometry
COUNTY
35 String
ROUTE
20 String
NAME
100 String
ROUTE_DESC
125 String
RT_TYPE
35 String
SRC_NAME
50 String
SRC_FILE
25 String
SRC_DATE
36 Date
URL
175 String
DESCRIPT
100 String
FGDLAQDATE
36 Date
AUTOID
4 Integer
SHAPE.LEN
0 Double

FEATURE ATTRIBUTE TABLES CODES AND VALUES:

Item
Item Description
OBJECTID Internal feature number.

Shape Feature geometry.

COUNTY County or counties where routes are located .

ROUTE Contains the short name of a route. This is a short, abstract identifier like 32, 100X, or Green that riders use to identify a route, but which doesn't give any indication of what places the route serves.

NAME Contains the full name of a route. This name is generally more descriptive than the name from the route field and often includes the route's destination or stop.

ROUTE_DESC Describes a route.

RT_TYPE Route type. Describes the type of transportation used on a route. The following are valid values for this field.
Tram, streetcar, or light rail = Used for any light rail or street-level system within a metropolitan area.

Subway or metro = Used for any underground rail system within a metropolitan area.

Rail = Used for intercity or long-distance travel.

Bus = Used for short- and long-distance bus routes.

Ferry = Used for short and long distance boat service.

Cable car = Used for street level cable cars where the cable runs beneath the car.

Gondola or suspended cable car = Typically used for aerial cable cars where the car is suspended from the cable.

Funicular = Used for any rail system that moves on steep inclines with a cable traction system.


SRC_NAME The name of the transit system as listed on the Florida Transit Data Exchange downloads page.

SRC_FILE The type of source file used to create the data.
Geodatabase = Geodatabase

GTFS = The General Transit Feed Specification (GTFS) is a data specification that allows public transit agencies to publish their transit data in a format that can be consumed by a wide variety of software applications.

Shapefile = Shapefile


SRC_DATE The date listed by the source in the downloaded file name.

URL URL to information on route. If no specific route page exists link to main transit page.

DESCRIPT Concatenation of ROUTE and NAME fields. If no data exists for a record "NO DESCRIPT AVAILABLE."

FGDLAQDATE FGDL added field based on date downloaded.

AUTOID Unique ID added by GeoPlan

SHAPE.LEN Length in meters


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.

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

NONE

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:
Florida Transit Information System:
http://www.ftis.org/index.html

Florida Transit Data Exchange:
http://www.ftis.org/Posts.aspx

General Transit Feed Specification:
https://gtfs.org/

DATA LINEAGE SUMMARY:
GeoPlan downloaded the various inputs to this dataset in August of 2019 
from the Florida Transit Data Exchange (http://www.ftis.org/Posts.aspx).
The data was received in various formats including individual shapefiles, 
geodatabases and GTFS (General Transit Feed Specification) by county. 
When more than one format was available the GTFS file was used as it was 
the most consistently available format across all counties. The field SRC_FILE 
was added to the final product noting what type of source file was used from
each county.

All GTFS files were converted to shapefile using the GTFS shapes to features 
conversion tool in ArcGIS Pro. All shapefiles created from GTFS were in the 
WGS 1984 projection. The new shapefiles were projected to NAD83 HARN 
using the WGS_1984_(ITRF00)_To_NAD_1983 + NAD_1983_To_HARN_Florida 
transformation.

Any data received as a geodatabase was exported to shapefile and projected from
NAD_1983_HARN_StatePlane_Florida_East_FIPS_0901_Feet (Broward),
NAD_1983_HARN_StatePlane_Florida_West_FIPS_0902_Feet (Citrus),
NAD_1983_StatePlane_Florida_West_FIPS_0902_Feet (Hernando),
NAD_1983_StatePlane_Florida_East_FIPS_0901_Feet (Indian River), to NAD83 HARN 
Shapefiles were projected from GCS_WGS_1984 (Volusia) to NAD83 HARN. 

Some geodatabases and shapefiles were received with individual files for each route.
In these cases the features were merged and if there was no unique information for route
segments the routes were dissolved. 

- Added COUNTY field based on county where route is located.
- Added field NAME based on most appropriate name field provided.
- Added SRC_NAME field based on the name of the transit system
  as listed on the Florida Transit Data Exchange downloads page.
- Added SRC_FILE field based on the type of source file used to create the data.
- Added SRC_DATE field based on the date listed by the source in the downloaded file name.
- Added DESCRIPT field based on concatenation of ROUTE and NAME fields.
- Added FGDLAQDATE based on date downloaded from Florida Transit Data Exchange.
- Upcased all fields except for URL.
- For source file names see citation information.
Process Date: 201908

Dataset copied. Process Date: 20191115
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:
Florida Transit Information System
FTIS
10555 W. Flagler Street
Miami, FL
33174
305-348-3116

http://www.ftis.org/Posts.aspx gana@fiu.edu Albert Gan

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