Geodataset Name:       FDOT_CRASH_2013_FATAL
Geodataset Type:       SPATIAL VIEW
Geodataset Feature:    Point
Feature Count:         2158

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

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

FEATURE ATTRIBUTE TABLES:

Datafile Name: FDOT_CRASH_2013_FATAL

FEATURE ATTRIBUTE TABLES CODES AND VALUES:

Item	Item Description
OBJECTID	Internal feature number.
SHAPE	Feature geometry.
KEYFIELD1	This is the concatenated Calendar Year and Crash Number (13-character text string) that forms unique key correspondence for the crash in the DOT Safety Office database.
CALYEAR	Four-digit year from CrashDate (= Calendar Year). This comes from the crash date on the crash report form.
CRASHNUM	Nine-digit crash report id number within CAR db, unique within calendar year. This comes from the crash report form.
CASENUMBER	Reporting Agency Case Number from the crash report form, as entered by the reporting officer, up to fifteen characters.
AGENCY	One-digit agency type code from the crash report form as entered by the reporting officer. (Source: DHSMV) 1 Florida Highway Patrol (FHP) 2 Sherriff s Office (SO) 3 Police Department (PD) 4 Other
DISTRICT	This two-digit number identifies the Managing District in which the crash occurred, division is geographic by county except for roadways maintained under the Turnpike Enterprise. This information is determined during the Safety Office s crash location processing, stored in the CAR database. (Source: FDOT Safety Office) The codes are: 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, Putnam, Suwannee, Taylor, and Union; 03 Headquarters in Chipley, includes counties Bay, Calhoun, Escambia, Franklin, Gadsden, Gulf, Holmes, Jackson, Jefferson, Leon, Liberty, Okaloosa, Santa Rosa, Wakulla, Walton, and Washington; 04 Headquarters in Fort Lauderdale, includes counties Broward, Indian River, Martin, Palm Beach, 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).
DOTCOUNTY	This two-digit DOT code number identifies the County in which the crash occurred. This information is initially converted from the DHSMV County code on the incoming report data, but may be changed during the Safety Office s crash location processing. (Source: FDOT Safety Office) The County codes are: 01 Charlotte 02 Citrus 03 Collier 04 Desoto 05 Glades 06 Hardee 07 Hendry 08 Hernando 09 Highlands 10 Hillsborough 11 Lake 12 Lee 13 Manatee 14 Pasco 15 Pinellas 16 Polk 17 Sarasota 18 Sumter 26 Alachua 27 Baker 28 Bradford 29 Columbia 30 Dixie 31 Gilchrist 32 Hamilton 33 Lafayette 34 Levy 35 Madison 36 Marion 37 Suwannee 38 Taylor 39 Union 46 Bay 47 Calhoun 48 Escambia 49 Franklin 50 Gadsden 51 Gulf 52 Holmes 53 Jackson 54 Jefferson 55 Leon 56 Liberty 57 Okaloosa 58 Santa Rosa 59 Wakulla 60 Walton 61 Washington 70 Brevard 71 Clay 72 Duval 73 Flagler 74 Nassau 75 Orange 76 Putnam 77 Seminole 78 St Johns 79 Volusia 86 Broward 87 Miami-Dade 88 Indian River 89 Martin 90 Monroe 91 Okeechobee 92 Osceola 93 Palm Beach 94 St Lucie
CRASHDATE	The date on which crash occurred. This comes from the crash report form.
CRASHTIME	The time at which the crash occurred, in military (24 hr) format. This information is initially converted from the incoming report data, but may be changed during the Safety Office s crash location processing.
DAYOFWEEK	A single-digit code for the day of week on which the crash occurred: 1 Monday, 2 Tuesday, etc. This information is initially converted from the incoming report data, but may be changed during the Safety Office s crash location processing.
DHSCNTYCTY	This four-digit code gives the DHSMV county code (first two digits) and city code (second two digits) for the location of the crash, according to the reporting officer. This comes from the crash report form.
TOWNNAME	This text field gives the name of the closest town or city to the location of the crash, according to the reporting officer. This comes from the crash report form.
INTOWNFLAG	This one-character flag field shows "Y" if the reporting officer has indicated that the crash occurred within a city or town, N if the officer has not so indicated. This comes from the crash report form.
ONROADNAME	This 36-character field stores the On Road name entered by officer who reported crash or otherwise shows the name used to finalize the location of the crash on the LRS. This information is initially converted from the incoming report data, but may be changed during the Safety Office s crash location processing.
INROADNAME	This 25-character field stores the nearest intersecting road name or referenced feature description for the location of the crash, as entered by the officer who reported crash or otherwise as used to finalize location of crash on the LRS. This information is initially converted from the incoming report data, but may be changed during the Safety Office s crash location processing.
REFDIST	Distance from reference point that determines crash location, units may be miles or feet, as given in the "REFMEAS" field, reference point may be Intersecting Road (INROADNAME) or may be another feature as identified by the reference node field. This information is determined during the Safety Office s crash location processing.
REFMEAS	Two-character code "FT" (feet) or "MI" (miles) gives units for the REFDIST field. This information is determined during the Safety Office s crash location processing.
REFDIRECT	This single-character code gives approximate direction of REFDIST from referenced intersection or feature to crash location: N north, S south, E east, W west. This information is determined during the Safety Office s crash location processing.
ROADWAYID	This datum is only available for crashes on the SHS; not entered for off-system records
LOCMILEPT	This datum is only available for crashes on the SHS; not entered for off-system records.
LOCNODE	This datum is only available for crashes on the SHS; not entered for off-system records.
SRROUTEID	This datum is only available for crashes that occur on the SHS.
USROUTEID	This datum is only available for crashes that occur on the US Routes within the SHS.
SIDEOFROAD	This information is determined during the Safety Office s crash location processing. It is only populated for crashes on the SHS except for fatal crashes, which have Side of Road and Lane regardless of on-/off-system status. The single-character code indicates the side of the roadway on which the first harmful event or impact of the crash occurred, as coded by the Safety Office staff. (Source: FDOT Safety Office): I Middle of intersection E Off end of maintained roadway at T-shaped intersection L Left (lanes bound in direction of decreasing mile-points) M Median P Parking lot/private property (crashes on private property or in parking lots should not appear in this dataset) R Right (lanes bound in direction of increasing mile-points) S Right-hand (lanes bound in direction of increasing mile-points) side-road, not on the maintained roadway T Left-hand (lanes bound in direction of decreasing mile-points) side-road, not on the maintained roadway U Unknown
CRASHLANE	This information is determined during the Safety Office s crash location processing. It is only populated for crashes on the SHS except for fatal crashes, which have Side of Road and Lane regardless of on-/off-system status. The single-character code indicates the lane of the roadway in which the first harmful event or impact of the crash occurred, as coded by the Safety Office staff, only populated for crashes on the SHS (Source: FDOT Safety Office): 1-9 Number of through-lane (counting from center/median toward each edge of roadway) A Acceleration/merge lane B Tollbooth plaza C Pedestrian in crosswalk E Off end of maintained roadway at T-shaped intersection H Island (median that divides lanes of traffic going the same direction) K Service/access road L Left-turn-only lane M Median/middle N Not applicable P Parking lane (with designated parking spaces) R Right-turn-only lane S Side of roadway/shoulder/off-road/emergency lane T Continuous left-turn lane accessible from both directions U Unknown V Bicycle in a designated bicycle travel lane X On-/off-ramp
ROADCATGRY	This datum is only available for crashes on the SHS. It is not entered for off-system records.
SKIDNUMBER	This datum is only available for crashes on the SHS. It is not entered for off-system records.
SKIDTESTDT	This datum is only available for crashes on the SHS. It is not entered for off-system records.
RCIFEDHWY	All of the RCI data are only available for crashes on the SHS.
RCIFUNCLAS	All of the RCI data are only available for crashes on the SHS.
RCIACC	All of the RCI data are only available for crashes on the SHS.
RCIPLACECD	All of the RCI data are only available for crashes on the SHS.
RCILANDUSE	All of the RCI data are only available for crashes on the SHS.
RCISURFWTH	All of the RCI data are only available for crashes on the SHS.
RCISLDTYP1	All of the RCI data are only available for crashes on the SHS.
RCISLDTYP2	All of the RCI data are only available for crashes on the SHS.
RCISLDTYP3	All of the RCI data are only available for crashes on the SHS.
RCISLDWTH1	All of the RCI data are only available for crashes on the SHS.
RCISLDWTH2	All of the RCI data are only available for crashes on the SHS.
RCISLDWTH3	All of the RCI data are only available for crashes on the SHS.
RCIMEDWDTH	All of the RCI data are only available for crashes on the SHS.
RCIAADT	All of the RCI data are only available for crashes on the SHS.
RCIAVGTFCT	All of the RCI data are only available for crashes on the SHS.
RCIHZDGCRV	All of the RCI data are only available for crashes on the SHS.
RCIMAXSPD	All of the RCI data are only available for crashes on the SHS.
RCITYPPARK	All of the RCI data are only available for crashes on the SHS.
HIGHESTINJ	This information is initially converted from the incoming report data, but may be changed during the Safety Office s crash location processing. The single-digit code indicates highest injury severity that has occurred because of the crash, listed here in order of severity from least to most .
CRSHALCDRG	This information is converted from the incoming report data. The single-digit Alcohol/Drugs Involved code gives cumulative alcohol/drug involvement from the crash, based on each of the drivers and each of the pedestrians involved (Source: FDOT Safety Office): 0 None 1 Alcohol involved 2 Drugs involved 3 Alcohol and drugs involved 4 Undetermined
SITELOCA	SITELOCA: This information is initially converted from the incoming report data, but may be changed during the Safety Office s crash location processing. This is the Site Location code from the crash report form, as entered by the officer or updated by Safety Office staff (Source: DHSMV/FDOT Safety Office): 00 Unknown 01 Not at intersection/rr x-ing/bridge 02 At intersection 03 Influenced by intersection 04 Driveway access 05 Railroad 06 Bridge 07 Entrance ramp 08 Exit ramp 09 Private parking lot 10 Public parking lot 11 Private property 12 Toll booth 13 Public bus stop zone 77 All other (explained in narrative)
LIGHTCOND	LIGHTCOND: This is the Lighting Condition code from the crash report form, as entered by the officer (Source: DHSMV): 01 Daylight 02 Dusk 03 Dawn 04 Dark (street light) 05 Dark (no street light) 88 Unknown
WEATHCOND	WEATHCOND: This is the Weather code from the crash report form, as entered by the officer (Source: DHSMV): 01 Clear 02 Cloudy 03 Rain 04 Fog 77 All other (explained in narrative)
RDSURFCOND	RDSURFCOND: This is the Road Surface Condition code from the crash report form, as entered by the officer (Source: DHSMV): 00 Not coded 01 Dry 02 Wet 03 Slippery 04 Icy 77 All other (explained in narrative)
DIV_UNDIV	This is the Divided/Undivided code from the crash report form, as entered by the officer: 1 divided, 2 undivided. (Source: DHSMV)
TRAFCNTL1	TRAFCNTL1: This is the two-digit Traffic Control code from the crash report form, as entered by the officer, first entry (Source: DHSMV): 00 Not coded 01 No control 02 Special speed zone 03 Speed control sign 04 School zone 05 Traffic signal 06 Stop sign 07 Yield sign 08 Flashing light 09 Railroad signal 10 Officer/guard/flagperson 11 Posted no u-turn 12 No passing zone 77 All other (explained in narrative)
TRAFCNTL2	TRAFCNTL2: This is the two-digit Traffic Control code from the crash report form, as entered by the officer, second entry (Source: DHSMV): 00 Not coded 01 No control 02 Special speed zone 03 Speed control sign 04 School zone 05 Traffic signal 06 Stop sign 07 Yield sign 08 Flashing light 09 Railroad signal 10 Officer/guard/flagperson 11 Posted no u-turn 12 No passing zone 77 All other (explained in narrative)
CNTOFLANES	CNTOFLANES: This is the two-digit count of roadway lanes from the crash report form, as entered by the officer. (Source: DHSMV)
RDSURFTYPE	RDSURFTYPE: This is the two-digit Roadway Surface Type code from the crash report form, as entered by the officer (Source: DHSMV): 00 Not coded 01 Slag/gravel/stone 02 Blacktop 03 Brick/block 04 Concrete 05 Dirt 77 All other (explained in narrative)
ROADCOND1	ROADCOND1: This is the two-digit Road Conditions at Time of Crash code from the crash report form, as entered by the officer, first entry (Source: DHSMV): 01 No defects 02 Obstruction with warning 03 Obstruction without warning 04 Road under repair/construction 05 Loose surface materials 06 Shoulders soft/low/high 07 holes/ruts/unsafe paved edge 08 Standing water 09 worn/polished road surface 77 All other (explained in narrative)
ROADCOND2	ROADCOND2: This two-digit Road Conditions at Time of Crash code from the crash report form, as entered by the officer, first entry (Source: DHSMV): 01 No defects 02 Obstruction with warning 03 Obstruction without warning 04 Road under repair/construction 05 Loose surface materials 06 Shoulders soft/low/high 07 holes/ruts/unsafe paved edge 08 Standing water 09 worn/polished road surface 77 All other (explained in narrative)
VISIBLTY1	VISIBLTY1: This is the two-digit Vision Obstructed code from the crash report form, as entered by the officer, first entry (Source: DHSMV): 01 Vision not obscured 02 Inclement weather 03 parked/stopped vehicle 04 trees/crops/bushes 05 Load on vehicle 06 building/fixed object 07 signs/billboards 08 Fog 09 Smoke 10 Glare 77 All other (explained in narrative)
VISIBLTY2	VISIBLTY2: This is the two-digit Vision Obstructed code from the crash report form, as entered by the officer, second entry (Source: DHSMV): 01 Vision not obscured 02 Inclement weather 03 parked/stopped vehicle 04 trees/crops/bushes 05 Load on vehicle 06 building/fixed object 07 signs/billboards 08 Fog 09 Smoke 10 Glare 77 All other (explained in narrative)
CRSHEVENT1	CRSHEVENT1: This two-digit code gives the First/Subsequent Harmful Event(s), first entry for the first vehicle in the crash, as entered by the reporting officer. (Source: DHSMV) 00 not coded 01 collision with mv in transport (rear end) 02 collision with mv in transport (head on) 03 collision with mv in transport (angle) 04 collision with mv in transport (left turn) 05 collision with mv in transport (right turn) 06 collision with mv in transport (sideswipe) 07 collision with mv in transport (backed into) 08 collision with parked car 09 collision with mv on roadway 10 collision with pedestrian 11 collision with bicycle 12 collision with bicycle in bike lane 13 collision with moped 14 collision with train 15 collision with animal 16 mv hit sign/signpost 17 mv hit utility pole/light pole 18 mv hit guardrail 19 mv hit fence 20 mv hit concrete barrier wall 21 mv hit bridge/pier/abutment/rail 22 mv hit tree/shrubbery 23 collision with construction barricade sign 24 collision with traffic gate 25 collision with crash attenuators 26 collision with fixed object above road 27 mv hit other fixed object 28 collision with moveable object on road 29 mv ran into ditch/culvert 30 ran off road into water 31 overturned 32 occupant fell from vehicle 33 tractor/trailer jackknifed 34 fire 35 explosion 36 downhill runaway 37 cargo loss or shift 38 separation of units 39 median crossover 77 all other (explained in narrative)
CRSHCAUSE1	CRSHCAUSE1: This two-digit code gives the Contributing Causes - Driver/Pedestrian, first entry for the first vehicle in the crash, as entered by the reporting officer. (Source: DHSMV) 00 not coded 01 no improper driving/action 02 careless driving (explained in narrative) 03 failed to yield right-of-way 04 improper backing 05 improper lane change 06 improper turn 07 alcohol (under influence) 08 drugs (under influence) 09 alcohol & drugs (under influence) 10 followed too closely 11 disregarded traffic signal 12 exceeded safe speed limit 13 disregarded stop sign 14 failed to maintain equip./vehicle 15 improper passing 16 drove left of center 17 exceeded stated speed limit 18 obstructing traffic 19 improper load 20 disregarded other traffic control 21 driving wrong side/way 22 fleeing police 23 vehicle modified 24 driver distraction (explained in narrative) 77 all other (explained in narrative)
CNTOFINJ	CNTOFINJ: This information is calculated from the incoming report data. It is a count of all persons injured because of the crash. 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. (Source: FDOT Safety Office)
CNTOFFATL	CNTOFFATL: This information is calculated from the incoming report data. It is a count of all persons who died in the crash or within 30 days of the crash due to injuries received in the crash. 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. (Source: FDOT Safety Office)
CNTOFSVINJ	CNTOFSVINJ: This information is calculated from the incoming report data. It is a count of all persons severely injured because of the crash. It counts only those who have an Injury Severity code of "4" (incapacitating injury), as coded by the officer who reported the crash. (Source: FDOT Safety Office)
CNTOFPEDES	CNTOFPEDES: This information is calculated from the incoming report data. It is a count of all the pedestrians involved in the crash. (Source: FDOT Safety Office)
CNTOFDRVRS	CNTOFDRVRS: This information is calculated from the incoming report data. It is a count of all the drivers involved in the crash. (Source: FDOT Safety Office)
CNTOFCYCLS	CNTOFCYCLS: This information is calculated from the incoming report data. It is a count of all the pedalcyclists involved in the crash. (Source: FDOT Safety Office)
CNTOFVEH	CNTOFVEH: This information is calculated from the incoming report data. It is a count of all the vehicles involved in the crash. (Source: FDOT Safety Office)
CNTOFPERS	CNTOFPERS: This information is calculated from the incoming report data. It is a count of all the persons (drivers, passengers, pedestrians) involved in the crash. (Source: FDOT Safety Office)
CNTNONTFTL	CNTNONTFTL: This information is calculated from the incoming report data. It is a count of all persons involved in the crash who have died, but NOT as a result of the crash. It counts only those who have an Injury Severity code of "6" (nontraffic fatality), as coded by the officer who reported the crash. The relative severity of this injury is considered less than "2" but greater than "1". (Source: FDOT Safety Office)
TOTCRSHDMG	TOTCRSHDMG: This information is calculated from the incoming report data. It is the total amount of vehicle and non-vehicle property damage that has occurred because of the crash, in dollars. (Source: FDOT Safety Office)
TOTVEHDMG	TOTVEHDMG: This information is calculated from the incoming report data. It is the total amount of vehicle damage that has occurred because of the crash, in dollars. (Source: FDOT Safety Office)
TOTOTHRDMG	TOTOTHRDMG: This information is calculated from the incoming report data. It is the total amount of non-vehicle property damage that has occurred because of the crash, in dollars. (Source: FDOT Safety Office)
WORKZONE	WORKZONE: This attribute is a yes/no flag (values Y or N ) that indicates potential work zone involvement for the crash based on the work zone information as entered by the reporting officer. (Source: FDOT Safety Office)
FLAG_CMV	FLAG_CMV: This attribute is a yes/no flag (values Y or N ) that indicates commercial vehicle involvement for the crash based on the vehicle information as entered by the reporting officer. (Source: FDOT Safety Office)
FLAG_INT	FLAG_INT: This attribute is a yes/no flag (values Y or N ) that indicates intersection involvement for the crash based on the crash information as entered by the reporting officer. (Source: FDOT Safety Office)
FL_LANEDEP	FL_LANEDEP: This attribute is a yes/no flag (values Y or N ) that indicates that there was a lane departure event for one or more vehicles involved in the crash based on the event and driver action information as entered by the reporting officer. (Source: FDOT Safety Office)
FL_AGGRSV	FL_AGGRSV: This attribute is a yes/no flag (values Y or N ) that indicates that there was aggressive driving by one or more of the drivers involved in the crash based on the driver action and citation information as entered by the reporting officer. (Source: FDOT Safety Office)
FL_VRU_PED	FL_VRU_PED: This attribute is a yes/no flag (values Y or N ) that indicates that there were one or more pedestrians (Vulnerable Road Users) involved in the crash based on the person information as entered by the reporting officer. (Source: FDOT Safety Office)
FL_VRU_BIK	FL_VRU_BIK: This attribute is a yes/no flag (values Y or N ) that indicates that there were one or more bicyclists (Vulnerable Road Users) involved in the crash based on the person information as entered by the reporting officer. (Source: FDOT Safety Office)
FLELDERPED	FLELDERPED: This attribute is a yes/no flag (values Y or N ) that indicates that there were one or more pedestrians (Vulnerable Road Users) involved in the crash who were age 65 or over at the time of the crash based on the person information as entered by the reporting officer. (Source: FDOT Safety Office)
FLPED5064	FLPED5064: This attribute is a yes/no flag (values Y or N ) that indicates that there were one or more pedestrians (Vulnerable Road Users) involved in the crash who were age 50 to 64 at the time of the crash based on the person information as entered by the reporting officer. (Source: FDOT Safety Office)
FLPED6569	FLPED6569: This attribute is a yes/no flag (values Y or N ) that indicates that there were one or more pedestrians (Vulnerable Road Users) involved in the crash who were age 65 to 69 at the time of the crash based on the person information as entered by the reporting officer. (Source: FDOT Safety Office)
FLPED7074	FLPED7074: This attribute is a yes/no flag (values Y or N ) that indicates that there were one or more pedestrians (Vulnerable Road Users) involved in the crash who were age 70 to 74 at the time of the crash based on the person information as entered by the reporting officer. (Source: FDOT Safety Office)
FLPED7579	FLPED7579: This attribute is a yes/no flag (values Y or N ) that indicates that there were one or more pedestrians (Vulnerable Road Users) involved in the crash who were age 75 to 79 at the time of the crash based on the person information as entered by the reporting officer. (Source: FDOT Safety Office)
FLPED80UP	FLPED80UP: This attribute is a yes/no flag (values Y or N ) that indicates that there were one or more pedestrians (Vulnerable Road Users) involved in the crash who were age 80 or over at the time of the crash based on the person information as entered by the reporting officer. (Source: FDOT Safety Office)
FLMINORPED	FLMINORPED: This attribute is a yes/no flag (values Y or N ) that indicates that there were one or more pedestrians (Vulnerable Road Users) involved in the crash who were under age 18 at the time of the crash based on the person information as entered by the reporting officer. (Source: FDOT Safety Office)
FLELDERBIK	FLELDERBIK: This attribute is a yes/no flag (values Y or N ) that indicates that there were one or more bicyclists (Vulnerable Road Users) involved in the crash who were age 65 or over at the time of the crash based on the person information as entered by the reporting officer. (Source: FDOT Safety Office)
FLBIK5064	FLBIK5064: This attribute is a yes/no flag (values Y or N ) that indicates that there were one or more bicyclists (Vulnerable Road Users) involved in the crash who were age 50 to 64 at the time of the crash based on the person information as entered by the reporting officer. (Source: FDOT Safety Office)
FLBIK6569	FLBIK6569: This attribute is a yes/no flag (values Y or N ) that indicates that there were one or more bicyclists (Vulnerable Road Users) involved in the crash who were age 65 to 69 at the time of the crash based on the person information as entered by the reporting officer. (Source: FDOT Safety Office)
FLBIK7074	FLBIK7074: This attribute is a yes/no flag (values Y or N ) that indicates that there were one or more bicyclists (Vulnerable Road Users) involved in the crash who were age 70 to 74 at the time of the crash based on the person information as entered by the reporting officer. (Source: FDOT Safety Office)
FLBIK7579	FLBIK7579: This attribute is a yes/no flag (values Y or N ) that indicates that there were one or more bicyclists (Vulnerable Road Users) involved in the crash who were age 75 to 79 at the time of the crash based on the person information as entered by the reporting officer. (Source: FDOT Safety Office)
FLBIK80UP	FLBIK80UP: This attribute is a yes/no flag (values Y or N ) that indicates that there were one or more bicyclists (Vulnerable Road Users) involved in the crash who were age 80 or over at the time of the crash based on the person information as entered by the reporting officer. (Source: FDOT Safety Office)
FLMINORBIK	FLMINORBIK: This attribute is a yes/no flag (values Y or N ) that indicates that there were one or more bicyclists (Vulnerable Road Users) involved in the crash who were under age 18 at the time of the crash based on the person information as entered by the reporting officer. (Source: FDOT Safety Office)
FL_VRU_MOT	FL_VRU_MOT: This attribute is a yes/no flag (values Y or N ) that indicates that there were one or more motorcyclists (Vulnerable Road Users) involved in the crash based on the person information as entered by the reporting officer. (Source: FDOT Safety Office)
FLMOT5064	FLMOT5064: This attribute is a yes/no flag (values Y or N ) that indicates that there were one or more motorcyclists (Vulnerable Road Users) involved in the crash who were age 50 to 64 at the time of the crash based on the vehicle and person information as entered by the reporting officer. (Source: FDOT Safety Office
FLMOT6569	FLMOT6569: This attribute is a yes/no flag (values Y or N ) that indicates that there were one or more motorcyclists (Vulnerable Road Users) involved in the crash who were age 65 to 69 at the time of the crash based on the vehicle and person information as entered by the reporting officer. (Source: FDOT Safety Office)
FLMOT7074	FLMOT7074: This attribute is a yes/no flag (values Y or N ) that indicates that there were one or more motorcyclists (Vulnerable Road Users) involved in the crash who were age 70 to 74 at the time of the crash based on the vehicle and person information as entered by the reporting officer. (Source: FDOT Safety Office)
FLMOT7579	FLMOT7579: This attribute is a yes/no flag (values Y or N ) that indicates that there were one or more motorcyclists (Vulnerable Road Users) involved in the crash who were age 75 to 79 at the time of the crash based on the vehicle and person information as entered by the reporting officer. (Source: FDOT Safety Office)
FLMOT80UP	FLMOT80UP: This attribute is a yes/no flag (values Y or N ) that indicates that there were one or more motorcyclists (Vulnerable Road Users) involved in the crash who were age 80 or over at the time of the crash based on the vehicle and person information as entered by the reporting officer. (Source: FDOT Safety Office)
FL_AR_TEEN	FL_AR_TEEN: This attribute is a yes/no flag (values Y or N ) that indicates that there were one or more motor-vehicle drivers involved in the crash who were age 15 to 19 (At-Risk Drivers Teen) at the time of the crash, based on person information as entered by the reporting officer. (Source: FDOT Safety Office)
FL_AR_AG	FL_AR_AG: This attribute is a yes/no flag (values Y or N ) that indicates that there were one or more motor-vehicle drivers involved in the crash who were age 65 or over (At-Risk Drivers Aging Road Users) at the time of the crash, based on person information as entered by the reporting officer. (Source: FDOT Safety Office)
FL_AG5064	FL_AG5064: This attribute is a yes/no flag (values Y or N ) that indicates that there were one or more motor-vehicle drivers involved in the crash who were age 50 to 64 at the time of the crash, based on person information as entered by the reporting officer. (Source: FDOT Safety Office)
FL_AG6569	FL_AG6569: This attribute is a yes/no flag (values Y or N ) that indicates that there were one or more motor-vehicle drivers involved in the crash who were age 65 to 69 (At-Risk Drivers Aging Road Users) at the time of the crash, based on person information as entered by the reporting officer. (Source: FDOT Safety Office)
FL_AG7074	FL_AG7074: This attribute is a yes/no flag (values Y or N ) that indicates that there were one or more motor-vehicle drivers involved in the crash who were age 70 to 74 (At-Risk Drivers Aging Road Users) at the time of the crash, based on person information as entered by the reporting officer. (Source: FDOT Safety Office)
FL_AG7579	FL_AG7579: This attribute is a yes/no flag (values Y or N ) that indicates that there were one or more motor-vehicle drivers involved in the crash who were age 75 to 79 (At-Risk Drivers Aging Road Users) at the time of the crash, based on person information as entered by the reporting officer. (Source: FDOT Safety Office)
FL_AG80UP	FL_AG80UP: This attribute is a yes/no flag (values Y or N ) that indicates that there were one or more motor-vehicle drivers involved in the crash who were age 80 or over (At-Risk Drivers Aging Road Users) at the time of the crash, based on person information as entered by the reporting officer. (Source: FDOT Safety Office)
FLAG_IMP	FLAG_IMP: This attribute is a yes/no flag (values Y or N ) that indicates that one or more drivers involved in the crash were potentially under the influence of alcohol and/or drugs, based on the person information as entered by the reporting officer. (Source: FDOT Safety Office)
FL_IMP_PED	FL_IMP_PED: This attribute is a yes/no flag (values Y or N ) that indicates that one or more pedestrians involved in the crash were potentially under the influence of alcohol and/or drugs, based on the person information as entered by the reporting officer. (Source: FDOT Safety Office)
FLAG_DIST	FLAG_DIST: This attribute is a yes/no flag (values Y or N ) that indicates that one or more drivers involved in the crash were distracted at the time of the crash, based on the driver information as entered by the reporting officer. (Source: FDOT Safety Office)
FLAG_MIN	FLAG_MIN: This attribute is a yes/no flag (values Y or N ) that indicates that there were one or more minors (persons age 1 to 17) involved in the crash, based on the person information as entered by the reporting officer. (Source: FDOT Safety Office)
FLNOBTKID	FLNOBTKID: This attribute is a yes/no flag (values Y or N ) that indicates that the crash involved one or more occupants of one or more seat-belt-equipped vehicles who were between the ages of 1 and 4 and were not restrained at the time of the crash, based on the person information as entered by the reporting officer. (Source: FDOT Safety Office)
FLNOBTMIN	FLNOBTMIN: This attribute is a yes/no flag (values Y or N ) that indicates that the crash involved one or more occupants of one or more seat-belt-equipped vehicles who were between the ages of 5 and 12 and were not restrained at the time of the crash, based on the person information as entered by the reporting officer. (Source: FDOT Safety Office)
FLNOBTTEEN	FLNOBTTEEN: This attribute is a yes/no flag (values Y or N ) that indicates that the crash involved one or more occupants of one or more seat-belt-equipped vehicles who were between the ages of 13 and 17 and were not restrained at the time of the crash, based on the person information as entered by the reporting officer. (Source: FDOT Safety Office)
FL_NOBELT	FL_NOBELT: This attribute is a yes/no flag (values Y or N ) that indicates that the crash involved one or more occupants of one or more seat-belt-equipped vehicles who were not restrained at the time of the crash, based on the person information as entered by the reporting officer. (Source: FDOT Safety Office)
LATITUDE	LATITUDE: This is the latitude (decimal degrees, to 6 places) of the final crash location, as projected on the map in use at the FDOT Safety Office at the time that the data in this file were generated. (Source: FDOT Safety Office)
LONGITUDE	LONGITUDE: This is the longitude (decimal degrees, to 6 places) of the final crash location, as projected on the map in use at the FDOT Safety Office at the time that the data in this file were generated. (Source: FDOT Safety Office)
XCOORDINAT	XCOORDINAT: This gives the X coordinate of the final crash location, as projected on the map in use at the FDOT Safety Office at the time that the data in this file were generated, coordinate system used to determine X/Y is indicated in the CoordSys field. (Source: FDOT Safety Office)
YCOORDINAT	YCOORDINAT: This gives the Y coordinate of the final crash location, as projected on the map in use at the FDOT Safety Office at the time that the data in this file were generated, coordinate system used to determine X/Y is indicated in the CoordSys field. (Source: FDOT Safety Office)
COORDSYS	COORDSYS: This gives the Geographic Coordinate System used to obtain the X/Y coordinates at which the crash is plotted in the GIS environment. (Source: FDOT Safety Office)
MAPSOURCE	MAPSOURCE: This stores the source/provider of the base map information for the line segment on which the crash is located in the GIS environment. (Source: FDOT Safety Office)
MAPVERSION	MAPVERSION: This stores the version information for the base map for the line segment on which the crash is located in the GIS environment. (Source: FDOT Safety Office)
DTPUBLISHE	DTPUBLISHE: The date on which shapefile generation was completed. (Source: FDOT Safety Office)
DTCARXTRCT	DTCARXTRCT: The date on which the crash attribute data for the shapefile were extracted from the FDOT Safety Office s Crash Analysis and Reporting (CAR) database. (Source: FDOT Safety Office)
DTCOORDXTR	DTCOORDXTR: The date on which the geographic coordinates for the crashes were captured or generated. (Source: FDOT Safety Office)
LINESEGID	LINESEGID: This stores the key that corresponds to the basemap information for the line segment on which the crash is located in the GIS environment. It may be blank. (Source: FDOT Safety Office)
SOURCE	Source shapefile OFF = Off system Roadways On = On system Roadways
DESCRIPT	FGDL added fields based on ONROADNAME
FGDLAQDATE	Date acquired by GeoPlan
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.

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.

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, 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 in March 24th, 2015 from the Unified Basemap Repository hosted by the FDOT: https://www3.dot.state.fl.us/unifiedbasemaprepository/ The data was in shapefile format and in the following projections: Off2013.shp - GCS_North_American_1983_HARN On2013.shp - UTM zone 17, NAD 1983 Both shapefiles were projected to FGDL Albers HARN and merged. A SOURCE field was added with two valid values: ON = on-system OFF = off-system. -upcased all records -changed merged layer name to fdot_crash_2013 -added DESCRIPT based on ONROADNAME -add FGDLAQDATE based on date GeoPlan received data from source Process Date: 20150430 the following spatial view command was run: sdetable -o create_view -T FDOT_CRASH_2013_FATAL -t "FDOT_CRASH_2013" -c "*" -w "CNTOFFATL >= 1" Process Date: 20150430

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, Mail Station 53
Tallahassee, FL
32399-0450
(850) 245-1500


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

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