Geodataset Name:       FDOT_CRASH_2005_2007
Geodataset Type:       SHAPEFILE
Geodataset Feature:    Point
Feature Count:         779579

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

PUBLICATION DATE:                  20090216
TIME PERIOD OF CONTENT:            Begin Date: 20050101    End Date: 20071231
DOWNLOAD LINK:                     http://www.fgdl.org/metadataexplorer/explorer.jsp

FEATURE ATTRIBUTE TABLES:

Datafile Name: FDOT_CRASH_2005_2007.DBF

FEATURE ATTRIBUTE TABLES CODES AND VALUES:

Item	Item Description
OBJECTID	Internal feature number.
Shape	Feature geometry.
ID	Undefined by Source
CALYEAR	Four-digit year from CrashDate (= Calendar Year)
CRASHNUM	Nine-digit crash report id number within CAR db, unique within calendar year
DISTRICT	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: 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)
DOTCOUNTY	Two-digit code number identifies the County in which the crash occurred: 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 - SantaRosa, 59 - Wakulla, 60 - Walton, 61 - Washington, 70 - Brevard, 71 - Clay, 72 - Duval, 73 - Flagler, 74 - Nassau, 75 - Orange, 76 - Putam, 77 - Seminole, 78 - StJohns, 79 - Volusia, 86 - Broward, 87 - Miami-Dade, 88 - IndianRiver, 89 - Martin, 90 - Monroe, 91 - Okeechobee, 92 - Osceola, 93 - PalmBeach, 94 - StLucie
CRASHDATE	Date on which crash occurred
CRASHTIME	Time at which the crash occurred, in military (24 hr) format
DAYOFWEEK	Single-digit code for day of week on which crash occurred: 1 - Monday, 2 - Tuesday, etc.
DHSCNTYCTY	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
TOWNNAME	Text field gives the closest town or city to the location of the crash, according to the reporting officer
INTOWNFLAG	One-character flag field shows "1" if the reporting officer has indicated that the crash occurred within a city or town, is blank if officer has not so indicated
ONROADNAME	36-character field stores On Road name entered by officer who reported crash or otherwise shows name used to finalize location of crash on the LRS
INROADNAME	25-character field stores the nearest intersecting road name or referenced feature description for the location of the crash, as entered by officer who reported crash or otherwise as used to finalize location of crash on the LRS
REFDIST	Distance from reference point that determines crash location, units may be miles or feet, as given in the "REF_MEAS_C" field, reference point may be Intersecting Road (INTSROAD) or may be another feature as identified by the ACNODESQ field
REFMEAS	Two-character code "FT" (feet) or "MI" (miles) gives units for the REFDIST field
REFDIRECT	Single-character code gives approximate direction of REFDIST from referenced intersection or feature to crash location: N - north, S - south, E - east, W - west
ROADWAYID	Eight-digit roadway identification number, corresponds to DOT's linear-reference system (lrs) for state-maintained roadways, matches RDWYID in RCI, if any; first two characters are DOT County Code
LOCMILEPT	Mile-point at which the crash occurred along the inventoried length of the roadway, only populated for crashes located on the State Highway System (SHS), gives mileage from beginning point of the inventoried length of the roadway as identified by the linear-reference Roadway Id and does NOT necessarily correspond to official mile-marker signs, state or county lines
LOCNODE	Five-digit reference number that identifies feature on the roadway that is closest to the location of the crash on the linear-reference system, only populated for crashes located on the SHS
SRROUTEID	Eight-character field stores Route Identifier for Roadway on which the crash is located, only populated for crashes that occur on the SHS, shows lowest-numbered state route number where more than one route applies
USROUTEID	Seven-character field stores designated US Highway System or Interstate Highway System route for the Roadway on which the crash is located, only populated for crashes on the SHS
SIDEOFROAD	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, only populated for crashes on the SHS: R - right (lanes bound in direction of increasing mile-points), L - left (lanes bound in direction of decreasing mile-points), M - median, I - middle of intersection, E - off end of maintained roadway at T-shaped intersection, 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	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: 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 lande os traffice going the same direction), K - service/access road, L - left-turn-only lane, M - median/middle, 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	Two-digit Crash Rate Category Code, only popluated for crashes on the SHS, gives the roadway type at the point of the crash with reference to number of lanes, rural/urban location and 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
SKIDNUMBER	Friction Number (FN) from skid test for most recent test prior to date of crash, only populated for crashes on the SHS; results 35 and up are "good", 30-34 are marginal
SKIDTESTDT	Date of skid test for results reportd in SKTRESNM (Skid Test Results Number) field, only populated for crashes on the SHS
RCIFEDHWY	Single-digit code gives the Federal-Aid Highway System code for the roadway at the point of the crash, only populated for crashes on the SHS, empty field means no data: 5 - NHS, 6 - STP, 9 - FA none
RCIFUNCLAS	Two-digit code gives the Roadway Functional Class for the roadway at the point of the crash, only populated for crashes on the SHS, empty field means no data: 01 - rural principal arterial interstate, 02 - rural principal aterial other, 06 - rural minor arterial, 07 - rural major collector, 08 - rural minor collector, 09 - rural local, 11 - urban principal arterial interstate, 12 - urban principal arterial expressway, 14 - urban other principal arterial, 16 - urban minor arterial, 17 - urban collector, 19 - urban local
RCIRDACC	Single-digit code gives the Roadway Access Type for the roadway at the point of the crash, only populated for crashes on the SHS, empty field means no data: 1 - full access, 2 - partial access, 3 - no access
RCIPLACECD	Four-digit code identifies the Census Place Code for the location of the crash, too many values to include code translations here, only populated for crashes on the SHS, empty field means no data
RCILANDUSE	Single-digit code identifies the Prevailing Land Use code, if any, for the property along the roadway at the point of the crash, only populated for crashes on the SHS, empty field means no data: 1 - central business district, 2 - high-density business/commercial, 3 - low-density commercial, 4 - high-density residential, 5 - low-density residential, 6 - other
RCISURFWTH	Numeric value gives the total width, in feet, of roadway surface at the point of the crash, only populated for crashes on the SHS, empty field means no data
RCISLDTYP1	Single-digit code identifies the first entry, if any, for the type of shoulder along the roadway at the point of the crash, only populated for crashes on the SHS, empty field means no data: 0 - raised curb, 1 - paved, 2 - paved with warning, 3 - lawn, 4 - gravel/marl, 5 - valley gutter, 6 - curb and gutter, 7 - other, 8 - curb w/ resf
RCISLDTYP2	Single-digit code identifies the second entry, if any, for the type of shoulder along the roadway at the point of the crash, only populated for crashes on the SHS, empty field means no data: 0 - raised curb, 1 - paved, 2 - paved with warning, 3 - lawn, 4 - gravel/marl, 5 - valley gutter, 6 - curb and gutter, 7 - other, 8 - curb w/ resf
RCISLDTYP3	Single-digit code identifies the third entry, if any, for the type of shoulder along the roadway at the point of the crash, only populated for crashes on the SHS, empty field means no data: 0 - raised curb, 1 - paved, 2 - paved with warning, 3 - lawn, 4 - gravel/marl, 5 - valley gutter, 6 - curb and gutter, 7 - other, 8 - curb w/ resf
RCISLDWTH1	Decimal value gives the width, in feet, of the shoulder identified by Shoulder Type 1 for the roadway at the point of the crash, only populated for crashes on the SHS, empty field means no data
RCISLDWTH2	Decimal value gives the width, in feet, of the shoulder identified by Shoulder Type 2 for the roadway at the point of the crash, only populated for crashes on the SHS, empty field means no data
RCISLDWTH3	Decimal value gives the width, in feet, of the shoulder identified by Shoulder Type 3 for the roadway at the point of the crash, only populated for crashes on the SHS, empty field means no data
RCIMEDWDTH	Three-digit value gives the width, in feet, of the median (if any) for the roadway at the point of the crash, only populated for crashes on the SHS, empty field means no median or no data
RCIAADT	Six-digit value gives the average number of vehicles per day that travel along the roadway at the point of the crash, average is of all days in the year, only populated for crashes on the SHS
RCIAVGTFCT	Decimal value gives the annually-averaged percentage of traffic that travels along the roadway at the point of the crash that is heavy trucks, only populated for crashes on the SHS
RCIHZDGCRV	Six-character text string gives the horizontal degree of curve, if any, for the roadway at the point of the crash, only populated for crashes on the SHS, empty field indicates no curve or no data
RCIMAXSPD	Three-digit value gives posted maximum speed limit in Miles per Hour along the roadway at the point of the crash, only populated for crashes on the SHS
RCITYPPARK	Single-digit code identifies the type of parking along the roadway at the point of the crash, only populated for crashes on the SHS, empty field means no data: 0 - highway type, 1 - no parking, 2 - curb both, 3 - angle both, 4 - curb one side, 5 - angle one side, 6 - curb one angle one, 7 - none-curb side, 8 - curb-curb side, 9 - angle-curb side
HIGHESTINJ	Single-digit code indicates highest injury severity that has occurred as a result of the crash, listed here in order of severity from least to most: 0 - not coded, 1 - no injury, 6 - nontraffic fatal, 2 - possible injury, 3 - non-incapacitating injury, 4 - incapacitating injury, 5 - fatality (within 30 days)
CRSHALCDRG	Single-digit Alcohol/Drugs Involved code gives cumulative alcohol/drug involvement from crash based on each of drivers/pedestrians involved: 0 - none, 1 - alcohol involved, 2 - drugs involved, 3 - alcohol and drugs involved, 4 - undetermined
SITELOCA	Site Location code from crash report form, as entered by officer or updated by Safety Office staff: 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	Lighting Condition code from crash report form, as entered by officer: 01 - daylight, 02 - dusk, 03 - dawn, 04 - dark (street light), 05 - dark (no street light), 88 - unknown
WEATHCOND	Weather code from crash report form, as entered by officer: 01 - clear, 02 - cloudy, 03 - rain, 04 - fog, 77 - all other (explained in narrative)
RDSURFCOND	Road Surface Condition code from crash report form, as entered by officer: 00 - not coded, 01 - dry, 02 - wet, 03 - slippery, 04 - icy, 77 - all other (explained in narrative)
DIV_UNDIV	Divided/Undivided code from crash report form, as entered by officer: 1 - divided, 2 - undivided
TRAFCNTL1	Two-digit Traffic Control code from crash report form, as entered by officer, first entry: 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	Two-digit Traffic Control code from crash report form, as entered by officer, second entry: 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	Two-digit count of roadway lanes crash report form, as entered by officer
RDSURFTYPE	Two-digit Roadway Surface Type code from crash report form, as entered by officer: 00 - not coded, 01 - slag/gravel/stone, 02 - blacktop, 03 - brick/block, 04 - concrete, 05 - dirt, 77 - all other (explained in narrative)
ROADCOND1	Two-digit Road Conditions at Time of Crash code from crash report form, as entered by officer, first entry: 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	Two-digit Road Conditions at Time of Crash code from crash report form, as entered by officer, first entry: 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	Two-digit Vision Obstructed code from crash report form, as entered by officer, first entry: 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	Two-digit Vision Obstructed code from crash report form, as entered by officer, second entry: 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)
PHNTM_HTRN	One-digit code indicates involvement of phantom and/or hit-and-run vehicles: 0 - n/a, 1 - phantom, 2 - hit-and-run, 3 - phantom and hit-and-run
CNTOFINJ	Count of all persons injured as a result of the crash, counts only 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
CNTOFFATL	Count of all persons who died in the crash or within 30 days of the crash due to injuries received in the crash, counts only those who have a final Injury Severity code of "5" (fatal (withn 30 days)) as coded by the officer who investigated the crash
CNTOFSVINJ	Count of all persons severely injured as a result of the crash, counts only those who have an Injury Severity code of "4" (incapacitating injury) as coded by the officer who reported the crash
CNTOFPEDES	Count of all pedestrians involved in crash
CNTOFDRVRS	Count of all drivers involved in crash
CNTOFCYCLS	Count of all pedalcyclists involved in crash
CNTOFVEH	Count of all vehicles involved in crash
CNTOFPERS	Count of all persons (drivers, passengers, pedestrians) involved in crash
CNTNONTFTL	Count of all persons involved in the crash who died, but NOT as a result of the crash, counts only those who have an Injury Severity code of "6" (nontraffic fatality) as coded by the officer who reported the crash, relative severity of this injury is considered less than "2" but greater than "1"
TOTCRSHDMG	Total amount of vehicle and non-vehicle property damage that has occurred as a result of the crash, in dollars
TOTVEHDMG	Total amount of vehicle damage that has occurred as a result of the crash, in dollars
TOTOTHRDMG	Total amount of non-vehicle property damage that has occurred as a result of the crash, in dollars
Latitude	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
Longitude	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
XCoordinat	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
YCoordinat	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
CoordSys	Gives the Geographic Coordinate System used to obtain the X/Y coordinates at which the crash is plotted in the GIS environment
MapSource	Stores the source/provider of the base map information for the line segment on which the crash is located in the GIS environment
MapVersion	Stores the version information for the base map for the line segment on which the crash is located in the GIS environment
LineSegId	Stores the key that corresponds to the basemap information for the line segment on which the crash is located in the GIS environment, may be blank
KeyField1	Concatenated Calendar Year and Crash Number (13-character text string) that forms unique key correspondence for the crash in the DOT Safety Office database
SOURCE	The layer was originally two layers for on-system and off-system roads (on0507.shp and off0507.shp). The two layers were merged and a SOURCE field was added ON = source was on0507.shp OFF = source was off0507.shp
DESCRIPT	GeoPlan added item based on ONROADNAME
FGDLAQDATE	Date GeoPlan acquired data from source
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 April 2009 from Benjamin.Jacobs@dot.state.fl.us via the DOT File Transfer Appliance. The data was originally in UTM zone 17, NAD 1983 and was projected to FGDL Albers. The layer was originally two layers for on-system and off-system roads (on0507.shp and off0507.shp). The two layers were merged and a SOURCE field was added. Records from the on-system shapefile received values of "ON" and records from the off-system roads received a value of "OFF". -upcased all records -changed name from on0507.shp and off0507.shp to fdot_crash_2005_2007 -added DESCRIPT based on ONROADNAME -calculated 7 records with no value for DESCRIPT to "NO DESCRIPT AVAILABLE" -add FGDLAQDATE based on date GeoPlan received data from source Process Date: 20090505 Data imported to ArcSDE and exported as a shapefile. Process Date: 20090511

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 St., MS 53
Tallahassee, FL
32399-0450
(850) 245-1500


Contact FDOT Safety Office

Transportation Safety Engineer

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