The map shows the volume of daily traffic over each road segment in Utah, and a measure of safety for those road segments. The map demonstrates the use of smart mapping on two key attributes in a traffic safety database: daily traffic volume, and Safety Index. "The Safety Index offers a statewide comparison of UDOT roadways, taking into account the different traffic patterns and volumes experienced in urban and rural areas. The Safety Index is a combination of four, equally weighted safety analysis sub-scores: Crash Rate Score, Severe Crash Rate Score, Crashes per Mile Score, Severe Crashes per Mile Score. The Safety Index is reported on a 0 to 10 scale, with 10 representing the worst conditions. The data reflect crashes from 2011 through 2013. For more information please see the Data Assessment Form. To download this data please visit UDOT's Open Data Site." -- Utah Department of TransportationThe Safety Index represents factors that transportation experts consider when prioritizing changes to the roads.The original map was the inspiration for this map. See its full explanation here.

The main source of the crash data is owned and maintained by the Virginia Department of Motor Vehicle (DMV). DMV’s Traffic Records Electronic Data System (TREDS) is a state-of-the-art data system maintained by the DMV Highway Safety Office (HSO) that automates and centralizes all crash data in Virginia. Per data sharing use agreement with DMV, VDOT publishes the non-privileged crash data through Virginia Roads data portal. In providing this data, VDOT assumes no responsibility for the accuracy and completeness of the data. In the process of recording and compiling the data, some deletions and/or omissions of data may occur and VDOT is not responsible for any such occurrences. The most recent data contained in this dataset is preliminary and subject to change.

Please be advised that, under Title 23 United State Code – Section 407, this crash information cannot be used in discovery or as evidence in a Federal or State court proceeding or considered for other purposes in any action for damages against VDOT or the State of Virginia arising from any occurrence at the location identified.

All users shall comply with and be subject to all applicable laws and regulations, whether federal or state, in connection with any of the receipt and use of DMV data including, but not limited to, (1) the Federal Drivers Privacy Protection Act (18 U.S.C. § 2721 et seq.), (2) the Government Data Collection and Dissemination Practices Act (Va. Code § 2.2-3800 et seq.), (3) the Virginia Computer Crimes Act (Va. Code § 18.2-152.1 et seq.), (4) the provisions of Va. Code §§ 46.2-208 and 58.1-3, and (5) any successor rules, regulations, or guidelines adopted by DMV with regard to disclosure or dissemination of any information obtained from DMV records or files.

This file contains reported cases of impacts between on-track equipment and any user of a public or private highway-rail intersection. National files from 1975 through the current year are available for download. In addition, individual files by State are available for the years 1991 through the current year.

Please note that 2024 data are incomplete and will be updated as additional records become available. Data are complete through 12/31/2023. Fatal and serious injury crashes are not “accidents” and are preventable. The City of Tempe is committed to reducing the number of fatal and serious injury crashes to zero. This data page provides details about the performance measure related to High Severity Traffic Crashes, as well as access to the data sets and any supplemental data. The Engineering and Transportation Department uses this data to improve safety in Tempe.This data includes vehicle/vehicle, vehicle/bicycle, and vehicle/pedestrian crashes in Tempe. The data also includes the type of crash and _location. This layer is used in the related Vision Zero story map, web maps, and operations dashboard. Time ZonesPlease note that data is stored in Arizona time, which is UTC-07:00 (7 hours behind UTC) and does not adjust for daylight saving (as Arizona does not partake in daylight saving). The data is intended to be viewed in Arizona time. Data downloaded as a CSV may appear in UTC time and, in some rare circumstances and locations, may display online in UTC or local time zones. As a reference to check data, the record with incident number 2579417 should appear as Jan. 10, 2012, 9:04 AM.Please note that 2024 data are incomplete and will be updated as additional records become available. Data are complete through 12/31/2023.This page provides data for the High Severity Traffic Crashes performance measure. The performance measure page is available at 1.08 High Severity Traffic CrashesAdditional InformationSource: Arizona Department of Transportation (ADOT)Contact (author): Shelly SeylerContact (author) E-Mail: Shelly_Seyler@tempe.govContact (maintainer): Julian DresangContact (maintainer) E-Mail: Julian_Dresang@tempe.govData Source Type: CSV files and Excel spreadsheets can be downloaded from the ADOT websitePreparation Method: Data is sorted to remove license plate numbers and other sensitive informationPublish Frequency: semi-annuallyPublish Method: ManualData Dictionary

This dataset includes all Motor Vehicle Collision (MVC) occurrences by their occurrence date and related offences. The MVC categories include property damage (PD) collisions, Fail to Remain (FTR) collisions, injury collisions and fatalities. This data is provided at the occurrence level, therefore multiple offences and/or victims can be associated with each record. Traffic Collisions DashboardDownload DocumentationIn this dataset, a collision is defined as the contact resulting from the motion of a motor vehicle or streetcar or its load, which produces property damage, injury or death. The term collision indicates that the initial point of contact involved at least one motor vehicle or streetcar.Definitions:Fatal Collisions occur when an individual’s injuries from a MVC result in a fatality within 30 days. Please note this category excludes:(i) Occurrences on private property(ii) Occurrences related to sudden death prior to collision (suicide or medical episode)(iii) Occurrences where the individual has died more than 30 days after the collisionPersonal Injury Collisions occur when an individual involved in a MVC suffers personal injuries. Fail to Remain Collisions occur when an individual involved in a MVC fails to stop and provide their information at the scene of a collision.Property Damage Collisions occur when an individual’s property has been damaged in a MVC or the value of damages is less than $2,000 for all involved parties.This data does not include occurrences that have been deemed unfounded. The definition of unfounded according to Statistics Canada is: “It has been determined through police investigation that the offence reported did not occur, nor was it attempted” (Statistics Canada, 2020).**** Statistics Canada. 2020. Uniform Crime Reporting Manual. Surveys and Statistical Programs. Canadian Centre for Justice Statistics.

"This file contains reported cases of collisions, derailments, fires, explosions, acts of God, or other events involving the operation of railroad on-track equipment and involving damages exceeding the reporting threshold for the year reported. National files from 1975 through the current year are available for download. In addition, individual files by State are available for the years 1991 through the current year.

NOTE: This map utilizes crash data from the Washington Department of Transportation (WSDOT); data is updated weekly, however, due to processing time required, final reporting statistics are generally provided 4-5 months after incident occurrence (i.e. final crash reporting for February will be reflected in June, etc.).

The High Crash Network includes Portland’s most dangerous streets and intersections for people driving, walking, and bicycling. This dataset delineates the streets which are among the top 20 crash streets for motor vehicles, for pedestrians and for bicyclists. Many streets are high crash streets for multiple transportation modes. Together, they form a network of 30 high crash streets.--Additional Information: Category: Transportation - Plan Purpose: To delineate streets with a high occurrence of traffic crashes. Update frequency: As needed-- Metadata Link: https://www.portlandmaps.com/metadata/index.cfm?&action=DisplayLayer&LayerID=61189

The State of Michigan’s criteria for a crash is a motor vehicle that was in transport and on the roadway, that resulted in death, injury, or property damage of $1,000 or more. Traffic crashes in this dataset are derived from SEMCOG’s Open Data Portal. Each row in the dataset represents a traffic crash that includes data about when and where the crash occurred, road conditions, number of individuals involved in the crash, and various factors that apply to the crash (Train, Bus, Deer, etc.). Also included is the number of injuries and fatalities that are associated with the crash.

• Road traffic accidents in recent years - information on the time, vehicles involved, type of accident, weather and light conditions and location of the accident - Animation function illustrates the daily course of individual accidents by hours - Map as street view or as aerial view

The State Traffic Safety Information (STSI) portal is part of the larger Fatality Analysis Reporting System (FARS) Encyclopedia. STSI provides state-by-state traffic safety profiles, including: crash data, lives saved/savable, legislation, economic costs, grant funding, alcohol related crash data, performance measures, and geographic maps of crash data.

This dataset shows the position of vehicular crash incidents in Queensland. This includes fatalities, injuries and vehicular damage. The point of truth for this dataset is the Queensland government open data website at, https://data.qld.gov.au/dataset/crash-data-from-queensland-roads

Crashes on the roadway blocks network of Washington, DC maintained by the District Department of Transportation (DDOT). In addition to locations, a related table consisting of crash details is available for each crash. This table provides some anonymized information about each of the persons involved in the crash (linked by CRASHID). These crash data are derived from the Metropolitan Police Department's (MPD) crash data management system (COBALT) and represent DDOT's attempt to summarize some of the most requested elements of the crash data. Further, DDOT has attempted to enhance this summary by locating each crash location along the DDOT roadway block line, providing a number of location references for each crash. In the event that location data is missing or incomplete for a crash, it is unable to be published within this dataset. Location points with some basic summary statistics,The DC ward the crash occurredSummary totals for: injuries (minor, major, fatal) by type (pedestrian, bicycle, car), mode of travel involved (pedestrian, bicycle, car), impaired participants (pedestrian, bicyclist, car passengers)If speeding was involvedNearest intersecting street nameDistance from nearest intersectionCardinal direction from the intersectionRead more at https://ddotwiki.atlassian.net/wiki/spaces/GIS0225/pages/2053603429/Crash+Data. Questions on the contents of these layers should be emailed to Metropolitan Police Department or the DDOT Traffic Safety Division. Questions regarding the Open Data DC can be sent to @OpenDataDC

The provided crash data comes directly from the standard DMV-349 Crash Form completed by the initial officer at the scene of a crash. Only completed crash reports will be mapped in this data. The coordinates for the crash reports are entered manually by the officer and may be subject to error. Therefore, only crashes with coordinates in Raleigh will be shown on the map. Instructions for filtering data are available on the Open Data blog. Follow this link to access the NC DOT DMV-349 Instruction Manual for code descriptions and definitions.https://connect.ncdot.gov/business/DMV/DMV%20Documents/DMV-349%20Instructional%20Manual.pdfTerms of UseThe Raleigh Police Department does not guarantee the accuracy of the information contained herein. While all attempts are made to ensure the correctness and suitability of information under our control and to correct any errors brought to our attention, no representation or guarantee can be made as to the correctness or suitability of the information that is presented, referenced, or implied. Data is provided by initial reports received and processed by the Raleigh Police Department. Data may be amended or corrected by the Raleigh Police Department at any time to reflect changes in the investigation, nature, or accuracy of the initial report and the Raleigh Police Department is not responsible for any error or omission, or for the use of or the results obtained from the use of this information. Misuse of the data may subject a party to criminal prosecution for false advertising under NC GS § 14-117. The Raleigh Police Department may, at its discretion, discontinue or modify this service at any time without notice.

Road traffic injuries in Hauts-de-Seine * * * Every road traffic accident known to the police is the subject of a Body Accident Analysis Bulletin (BAAC) which describes the characteristics and location of the accident, the vehicles and users involved. The National Interministerial Observatory of Road Safety (ONISR) compiles the bulletins from the police and gendarmerie services and constitutes the national register of road traffic injuries, then makes it accessible. In Hauts-de-Seine, the Departmental Road Safety Observatory (ODSR) managed by the Regional and Interdepartmental Directorate for Equipment and Development of Ile-de-France (DRIEA) administers local data and ensures, in particular, the completeness of the file. It transmits them to the technical services of the Departmental Council, which consolidates them by carrying out geolocation and accident mapping. Thus, each year, the Departmental Council publishes the departmental figures from the national register of road traffic injuries. It proposes a geolocation and carries out a mapping city by city. Strategic data in the fight against road safety in order to locate accident sites and implement awareness radars. Related data Hauts-de-seine.fr Statistics and maps of accidentology in Hauts-de-Seine published annually by the Department securite-routiere.gouv.fr National Interministerial Road Safety Observatory (ONISR) data.gouv.fr Database of personal road traffic accidents

Contains locations and information about every crash incident reported to the police in Allegheny County from 2004 to 2024. Fields include injury severity, fatalities, information about the vehicles involved, location information, and factors that may have contributed to the crash. Data is provided by PennDOT and is subject to PennDOT's data privacy restrictions, which are noted in the metadata information section below.

Point representation of traffic collisions which have occurred within the road right‐of‐way. Collisions are mapped according to the Motor Vehicle Collision Report. In some cases, insufficient information may result in spatial accuracy errors.The dataset was created to support the Road Safety Plan initiative, details available on Halifax.ca. The dataset only contains HRP/RCMP closed ROW collision incidents that were completed electronically.Halifax Regional Police & the Halifax Regional Municipality provides this information in good faith but provides no warranty, nor accepts any liability arising from any incorrect, incomplete or misleading information or its improper use. Metadata

This dataset captures detailed statistics about road accidents in Glasgow from 2014 to 2021. The data relate to the location, built environment and level of injury for each accident, along with numbers of casualties and vehicles involved. The statistics relate only to personal injury accidents on public roads that are reported to the police, and subsequently recorded, using the STATS19 accident reporting form. Data are released via the UK Department for Transport and can be found at the UK Government Data portal data.gov.uk.

Overview:

Information on location and characteristics of crashes in Queensland for all reported Road Traffic Crashes occurred from 1 January 2001 to 30 June 2024.

Fatal, Hospitalisation, Medical treatment and Minor injury:

This dataset contains information on crashes reported to the police which resulted from the movement of at least 1 road vehicle on a road or road related area. Crashes listed in this resource have occurred on a public road and meet one of the following criteria:

• a person is killed or injured, or
• at least 1 vehicle was towed away, or
• the value of the property damage meets the appropriate criteria listed below.

Property damage:

1. $2500 or more damage to property other than vehicles (after 1 December 1999)
2. $2500 or more damage to vehicle and/or other property (after 1 December 1991 and before 1 December 1999)
3. value of property damage is greater than $1000 (before December 1991).

Please note:

• This data has been extracted from the Queensland Road Crash Database.
• Information held in the Road Crash Database on events occurring within the last 12 months is considered preliminary as investigations into crashes can take up to 1 year to finalise.
• Property damage only crashes ceased to be reported/recorded by Queensland Police Service after 31 December 2010.
• These crash location coordinates reference the current Australian geodetic datum is GDA2020 (previously it was GDA94).

Accuracy: The City of Ottawa provides this information in good faith but provides no warranty, nor accepts any liability arising from any incorrect, incomplete, or misleading information or its improper use.Collision Data Accuracy: Each reportable collision occurring on public roadways is sent to the City of Ottawa and is validated at least once. Approximately 50% of the records are validated once again by a senior staff. Additionally, many queries are run on the database looking for errors.X & Y Accuracy: Collisions are pinned according to information provided by the officer on the Motor Vehicle Collision Report. In some cases, insufficient information was provided, and the collision location is an estimate.Update Frequency: MonthlyAttributes:DateTimeLocation (RD1 @ RD2 or RD from RD 1 to RD 2)Location Type (Intersection, non-intersection, at/near private driveway) Classification of collision (non-fatal, fatal, property damage only)Initial impact type (Angle, turning movement, rear-end…)Road surface condition (Ice, wet, dry snow...)Environment (Clear, rain, snow…)Light (daylight, dawn, dusk…)Traffic control (stop, traffic signal, no control…)Number of VehiclesNumber of PedestriansNumber of BicyclesNumber of MotorcyclesMax Injury (Highest injury level in the collisions)Number of InjuriesNumber of Minimal Injuries (Person did not go to hospital when leaving the scene of the collision)Number of Minor Injuries (Person went to hospital and was treated in the emergency room, but not admitted)Number of Major Injuries (Person admitted to hospital. Includes person admitted for observation. This could be either life threatening or non-life threatening)Number of Fatal Injuries (Person killed immediately or within 30 days of the motor vehicle collision)X and Y Coordinate (MTM Zone 9, NAD83)Latitude and longitude (WGS1984)Contact: Transportation Data Collection & Analytics