Geodataset Name:       FDOT_CRASH_COUNTS_2014
Geodataset Type:       SHAPEFILE
Geodataset Feature:    Polyline
Feature Count:         40891

DATA SOURCE(S):                    Florida Department of Transportation, Transportation Statistics Office (TRANSTAT)
SCALE OF ORIGINAL SOURCE MAPS:     24000
GEODATASET EXTENT:                 State of Florida

PUBLICATION DATE:                  2016
TIME PERIOD OF CONTENT:            Begin Date: 2010    End Date: 2014
DOWNLOAD LINK:                     http://www.fgdl.org/metadataexplorer/explorer.jsp

FEATURE ATTRIBUTE TABLES:

Datafile Name: FDOT_CRASH_COUNTS_2014.DBF

FEATURE ATTRIBUTE TABLES CODES AND VALUES:

Item	Item Description
OBJECTID	Internal feature number.
Shape	Feature geometry.
DISTRICT	Two-digit code which identifies the Managing District in which the intersection is located, division is geographic by county except for roadways maintained under the Turnpike Enterprise: 01 - headquarters in Bartow, includes counties Charlotte, Collier, DeSoto, Glades, Hardee, Hendry, Highlands, Lee, Manatee, Okeechobee, Polk, and Sarasota; 02 - headquarters in Lake City, includes counties Alachua, Baker, Bradford, Clay, Columbia, Dixie, Duval, Gilchrist, Hamilton, Lafayette, Levy, Madison, Nassau, Putam, Suwannee, Taylor, and Union; 03 - headquarters in Chipley, includes counties Bay, Calhoun, Escambia, Franklin, Gadsden, Gulf, Holmes, Jackson, Jefferson, Leon, Liberty, Okaloosa, SantaRosa, Wakulla, Walton, and Washington; 04 - headquarters in Fort Lauderdale, includes counties Broward, Indian River, Martin, PalmBeach, and St Lucie; 05 - headquarters in DeLand, includes counties Brevard, Flagler, Lake, Marion, Orange, Osceola, Seminole, Sumter, and Volusia; 06 - headquarters in Miami, includes counties Miami-Dade and Monroe; 07 - headquarters in Tampa, includes counties Citrus, Hernando, Hillsborough, Pasco, and Pinellas; 08 - Turnpike (statewide)
ROADWAY_ID	This eight-digit roadway identification number designates the roadway segment within DOT's linear-reference system (LRS) for state-maintained roadways in the FDOT Roadway Characteristics Inventory (RCI) database. The first two characters are DOT County Code, third through fifth characters are the roadway section number and sixth through eighth characters are the subsection number.
ROUTE_ID	This eight - character field stores the Route Identifier for the roadway segment. It shows the lowest-numbered state route number where more than one route applies.
CATEGORY	This two-digit Crash Rate Category Code gives the dominant roadway type at the point of the intersection for purposes of crash rate performance analysis. It is determined by Safety Office automated processes, based on the RCI number of lanes, rural/urban location, drainage type, and divided/undivided and median type: 01 Urban interstate, 02 Rural interstate, 03 Urban toll road, 04 Rural toll road, 05 Urban other limited access, 06 Rural other limited access, 07 Urban ramp, 08 Rural ramp, 10 Urban 2-3 lanes two-way divided raised median, 11 Urban 2-3 lanes two-way divided painted median, 12 Urban 2-3 lanes two-way undivided, 13 Suburban 2-3 lanes two-way divided raised median, 14 Suburban 2-3 lanes two-way divided painted median, 15 Suburban 2-3 lanes two-way undivided, 16 Rural 2-3 lanes two-way divided raised median, 17 Rural 2-3 lanes two-way divided painted median, 18 Rural 4-5 lanes two-way undivided, 20 Urban 4-5 lanes two-way divided raised median, 21 Urban 4-5 lanes two-way divided painted median, 22 Urban 4-5 lanes two-way undivided, 23 Suburban 4-5 lanes two-way divided raised median, 24 Suburban 4-5 lanes two-way divided painted median, 25 Suburban 4-5 lanes two-way undivided, 26 Rural 4-5 lanes two-way divided raised median, 27 Rural 4-5 lanes two-way divided painted median, 28 Rural 4-5 lanes two-way undivided, 30 Urban 6 or more lanes two-way divided raised median, 31 Urban 6 or more lanes two-way divided painted median, 32 Urban 6 or more lanes two-way undivided, 33 Suburban 6 or more lanes two-way divided raised median, 34 Suburban 6 or more lanes two-way divided painted median, 35 Suburban 6 or more lanes two-way undivided, 36 Rural 6 or more lanes two-way divided raised median, 37 Rural 6 or more lanes two-way divided painted median, 38 Rural 6 or more lanes two-way undivided, 40 Urban one-way, 41 Suburban one-way, 42 Rural one-way, 77 Undefined
BEG_MP	This is the Inventory mile-point for the beginning of the roadway segment. With the Roadway ID forms it the LRS coordinate for the beginning of the segment. It is a measurement in miles from the beginning of the inventory for the Roadway ID to the point at which the analyzed segment begins. It does not correspond to any mile-markers, signs, or county or state lines.
END_MP	This is the Inventory mile-point for the end of the roadway segment. With the Roadway ID forms it the LRS coordinate for the end of the segment. It is a measurement in miles from the beginning of the inventory for the Roadway ID to the point at which the analyzed segment ends. It does not correspond to any mile-markers, signs, or county or state lines.
ACTUAL_RAT	This is the actual crash rate for the segment expressed as crashes per Million Vehicle-Miles (MVM); calculated by dividing the 5-year total crashes by the 5-year accumulated MVM (MVM is Annual Average Daily Traffic times number of days in the year times the length of the segment, accumulated for each of the 5 years and summed).
DISTRICT_A	The District Average is the average crash rate for roadways of the same category on the State Highway System (SHS) within the District. It is calculated in the same way as the actual rate, but accumulated for all segments of the same type within the District.
CRASH_COUN	This is a count of all crashes in the database that have occurred on the segment within the 5-year analysis period.
FATAL_COUN	This is a count of traffic fatalities that have occurred in crashes that have happened on the segment within the 5-year analysis period. It counts only those who have a final Injury Severity code of "5" (fatal (within 30 days)), as coded by the officer who investigated the crash.
INJURY_COU	This is a count of non-fatal injuries that have occurred in crashes that have happened on the segment within the 5-year analysis period. It counts those who have an Injury Severity code of "2" (possible injury), "3" (non-incapacitating injury), or "4" (incapacitating injury) as coded by the officer who reported the crash.
PDO_COUNT	This is a count of property-damage-only (PDO) crashes (i.e. crashes not resulting in any injuries) that have occurred on the segment within the 5-year analysis period.
AADT	Annual Average Daily Traffic is the average number of cars per day that pass along the segment, as averaged over the five years of the analysis.
CONFIDENCE	The Confidence is a percentage that expresses the degree of statistical certainty with which we can say that the actual crash rate for the segment is above the average rate to which it was compared (generally the District average rate); a confidence of 50% or less indicates no certainty.
STATE_AVG	The State Average is the average crash rate for all roadways of the same category on the State Highway System (SHS). It is calculated in the same way as the actual rate, but accumulated for all segments of the same type within the State.
COUNTY_AVG	The County Average is the average crash rate for roadways of the same category on the State Highway System (SHS) within the County. It is calculated in the same way as the actual rate, but accumulated for all segments of the same type within the County.
MVM	Millions of Vehicle-Miles (MVM) is Annual Average Daily Traffic (AADT) times the length of the segment times number of days in the year, accumulated for each of the 5 years and summed.
LOC_ERROR	Undefined by Source
DTPUBLISHE	The date on which shapefile generation was completed.
SFTY_RATIO	Safety ratio, calculated by the following formula: ACTUAL_RAT / STATE_AVG
SFTY_NUM	Number representing safety ratio. There are 3 valid values. 1 = Safety ratio greater than 1 2 = Can't calculate safety ratio because state average = 0 3 = Safety ratio less than 1
AXL	Suggested color coding for safety crash ratio by Imran Ghani 1 = 0.0 - 0.75 - number of crashes is below the average for a similar facility 2 = 0.75 - 0.90 - number of crashes is approaching the average for a similar facility 3 = 0.9 -1.0 - number of crashes is close but below the average for a similar facility 4 = 1.0- 1.10 - number of crashes is close but above the average for a similar facility 5 = >1.10 - number of crashes exceeds the average for a similar facility 0 = Can't calculate safety ratio because state average = 0
DESCRIPT	GeoPlan added field based on ROUTE_ID
FGDLAQDATE	Date GeoPlan acquired data from source
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 Segments file shows mapped roadway segments on the State Highway System (SHS) with their 5-year crash rates as analyzed by the Safety Office s Crash Analysis Reporting (CAR) system.

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

The information contained in this file has been compiled from information collected by the FDOT Safety Office for the purpose of identifying, evaluating, or planning safety enhancements on Florida's roadways. It contains information that is to be used to develop highway safety improvement projects. Access to the information contained in this file, or otherwise originating from the Florida Department of Transportation (FDOT), Safety Office or from the Crash Analysis Reporting (CAR) System is restricted to government agencies and to employees of government agencies working on projects that require access to crash report data. For exceptions, apply to FDOT Safety Office. The information contained in this file, or otherwise originating from the Florida Department of Transportation (FDOT), Safety Office or from the Crash Analysis Reporting (CAR) System shall be used only for those purposes deemed appropriate by the FDOT. See Title 23, United States Code, section 409.

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: DATA LINEAGE SUMMARY:

This data set was received by GeoPlan on November 10th 2016 from the Unified Basemap Repository hosted by the FDOT: https://www3.dot.state.fl.us/unifiedbasemaprepository/ The data was in shapefile format and the following projection: UTM zone 17, NAD 1983. The shapefile was projected to FGDL Albers HPGN using NAD_1983_To_HARN_Florida datum transformation. The following qaqc procedures were performed: -Added SFTY_RATIO based on following equation: ACTUAL_RAT / STATE_AVG -Added SFTY_NUM field. Calculated numbers based on the values from the safety ratio. There are 3 valid values: 1 = Safety ratio greater than 1 2 = Can't calculate safety ratio because state average = 0 3 = Safety ratio less than 1 -Added AXL field. Calculated numbers based on the values from the safety ratio. There are 6 valid values: 0 = Can't calculate safety ratio because state average = 0 1 = 0.0 - 0.75 - number of crashes is below the average for a similar facility 2 = 0.75 - 0.90 - number of crashes is approaching the average for a similar facility 3 = 0.9 -1.0 - number of crashes is close but below the average for a similar facility 4 = 1.0- 1.10 - number of crashes is close but above the average for a similar facility 5 = >1.10 - number of crashes exceeds the average for a similar facility -Added DESCRIPT based on ROUTE_ID -Added FGDLAQDATE based on date data was received from source -Changed name from 2014_5yrCrashRates_withDistrictandStateAvgs.shp to FDOT_CRASH_COUNTS_2014 Process Date: 20161106

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 Department of Transportation, State Safety Office, Crash Records Section
FDOT
Transportation Statistics Office, 605 Suwannee Street, MS 27
Tallahassee, Florida
32399-0450
850-414-3100


http://www.dot.state.fl.us

Shaun Davis

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