Geodataset Name:       FDOT_CRASH_COUNTS
Geodataset Type:       SHAPEFILE
Geodataset Feature:    Polyline
Feature Count:         39222

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

PUBLICATION DATE:                  201006
TIME PERIOD OF CONTENT:            20100503
DOWNLOAD LINK:                     http://www.fgdl.org/metadataexplorer/explorer.jsp

FEATURE ATTRIBUTE TABLES:

Datafile Name: FDOT_CRASH_COUNTS

FEATURE ATTRIBUTE TABLES CODES AND VALUES:

Item	Item Description
OBJECTID	Internal feature number.
Shape	Feature geometry.
RDWYID	A unique 8-character identification number assigned to a roadway or section of a roadway on State Highway System for which information is maintained in the Department's Roadway Characteristics Inventory (RCI).
STATERD	Lowest-numbered State Road number for the identified segment of roadway.
CRRATECD	2-digit code identifies the type of roadway: urban/suburban/rural, number of lanes, divided/undivided/, median type.
BEGMP	The mile-point along the inventoried roadway at which the analyzed segment starts.
ENDMP	The mile-point along the inventoried roadway at which the analyzed segment ends.
ACTUALRATE	The number of crashes per Million Vehicle Miles (MVM) that have occurred on the identified roadway segment during the calendar years spanned by the analysis.
DIST_AVG_R	The average number of crashes per Million Vehicle Miles (MVM) that have occurred on roadway segments of the same type within the same managing district during the calendar years spanned by the analysis.
CRASH_COUN	The total number of crashes that have occurred on the identified roadway segment within the year-span of the analysis.
FATAL_COUN	The total number of fatalities due to crashes that have occurred on the identified roadway segment within the year-span of the analysis.
INJURY_COU	The total number of injuries due to crashes that have occurred on the identified roadway segment within the year-span of the analysis.
PDO_COUNT	The total number of non-injury crashes that were reported on long-form crash reports that have occurred on the identified roadway segment within the year-span of the analysis.
AADT	The Annual Average Daily Traffic along the identified roadway segment, accumulated and averaged across the year-span of the analysis.
CONF_PCT	The percent confidence that the crash rate for the analyzed segment is higher than average for segments of the same type within the managing district over the same time-span. 50% is not-confident. Safety Office considers segments with confidence greater than 90 percent to be "high crash" segments.
STATE_AVG_	The average number of crashes per Million Vehicle Miles (MVM) that have occurred on roadway segments of the same type within the state during the calendar years spanned by the analysis.
MVM_calc	The total Millions of Vehicle Miles traveled on the identified roadway segment for the entire year-span of the analysis.
DESCRIPT	GeoPlan added field based on STATERD
FGDLAQDATE	Date GeoPlan acquired data from source.
AUTOID	Unique ID added by GeoPlan
SFTY_RATIO	Safety ratio, calculated by the following formula: ACTUALRATE / STATE_AVG
SFTY_NUM	Number representing safety ratio. There are 3 valid values: 1 = Safety ratio greater than 1 2 = Can't calculate saftey ratio because state average = 0 3 = Safety ratio less than 1
SHAPE.LEN	Length in meters

USER NOTES:

All data for this dataset are logically consistent.

This dataset is complete as of date of production.

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

The FDOT GIS Basemap Routes feature class provides spatial information on Florida Basemap Routes, as well attribute information compatible with the Roadway Characteristics Inventory (RCI) database. Furthermore, the spatial data also contains measures (m-values) that can be used for event mapping. The crash rate analysis data is intended for use in targeting safety improvements.

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

This product has been compiled from the most accurate source data from the Florida Department of Transportation's (FDOT) Transportation Statistics Office and the FDOT Safety Office's Crash Analysis Reporting (CAR) database for the 2004-2008 crash rate analyses. However, this product is for reference purposes only and is not to be construed as a legal document or survey instrument. Any reliance on the information contained herein is at the user's own risk. The Florida Department of Transportation assumes no responsibility for any use of the information contained herein or any loss resulting therefrom.

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 dataset was created using ESRI event mapping. The route system is the Transportation Statistics' basemap routes. The event source is an oracle table that is created with the following query: select * from roadway The conversion of these events into a shapefile includes specifying the shapefile geometry should contain measure values (M-values) which means that this dataset may be used as a route source for subsequent event mapping of tabular data that contains a roadway identifier and milepost information that complies with the Florida Department of Transportation's Roadway Characteristics Inventory (RCI) milepost logic. Process Date: 20100503 Benjamin.Jacobs@dot.state.fl.us, a consultant from FDOT Safety Office used GIS techniques to join crash data to the RCI basemap roads data. Process Date: 201005 GeoPlan received data in shapefile format from Benjamin.Jacobs@dot.state.fl.us in May 2010. When received the data was in UTM. The shapefile was projected to Albers HPGN. The following qaqc procedures were performed: -Added SFTY_RATIO and SFTY_NUM fields -Upcased -Added DESCRIPT based on STATERD -Added FGDLAQDATE based on date data was received from source -Changed name from 2008_5yrCrashRates_withDistrict&StateAvgs to FDOT_CRASH_COUNTS Process Date: 20100601 Data imported to ArcSDE and exported as a shapefile. Process Date: 20100602

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, Safety Office
FDOT
605 Suwannee Street, MS 53
Tallahassee, Florida
32399-0450
(850) 245-1515


http://www.dot.state.fl.us/safety/
benjamin.jacobs@dot.state.fl.us
GIS Section Manager

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