This data has been consolidated from Victoria Police reports and Hospital injury information, then validated and enriched to provide a comprehensive and detailed view of road crashes and injuries across Victoria. The data provides users with information about Victorian fatal and injury road crash data based on time, location, conditions, crash type, road user type, and other relevant attributes. Data Currency This information will be updated on a monthly basis but with a 7 month lag in order to provide a comprehensive view of incidents during that time period. Data Structure The CSV data is split across multiple tables with attributes to facilitate joins between the information. This has been captured as part of the supporting documentation in the metadata. The tables and attributes include: - accident (basic accident details, time, severity, location) - person (person based details, age, gender etc) - vehicle (vehicle based data, vehicle type, make etc) - accident_event (sequence of events e.g. left road, rollover, caught fire) - road_surface_cond (whether road was wet, dry, icy etc) - atmospheric_cond (rain, winds etc) - sub_dca (detailed codes describing accident) - accident_node (master location table - NB subset of accident table) - Node Table with Lat/Long references There is also a lite Victoria Road Crash .csv dataset is a single flat file containing a subset of the attributes from the other CSV files. It provides a single set of attributes for each road crash that has occurred within Victoria. Supporting documentation in the metadata will provide further details of the attributes. This used to be a .GeoJSON file however due to feedback from a significant number of Open Data users, this was changed to a .csv file. Disclaimer No claim is made as to the accuracy or currency of the content on this site at any time, there will be instances where attributes relating to a crash are amended over time. This data is provided on the basis that users undertake responsibility for assessing the relevance and accuracy of its content. Data relating to fatal crashes that have occurred recently are provisional and are subject to change or removal. They will have a high level of incompleteness and details will be amended before they are finalised. The Victorian Government and Department of Transport and Planning accept no liability to any person or group for the data or advice (or the use of such data or advice) which is provided or incorporated into it by reference.

Community Maps provides Wisconsin's law enforcement agencies and county Traffic Safety Commissions with a statewide map of all police reported motor vehicle crashes from 2010 to the current year. Fatal crashes are included from 2001. Crashes are updated on a nightly basis using geo-coded locations from the Wisconsin Department of Transportation DT4000 police crash report. The Community Maps system was designed to support and enhance traffic safety planning, resource allocation, and decision support at the local level, in particular through the regular review of crashes at each of the county quarterly TSC meetings.

Community Maps is hosted at the University of Wisconsin-Madison by the Wisconsin Traffic Operations and Safety (TOPS) Laboratory in collaboration with the Wisconsin Department of Transportation (WisDOT) Bureau of Transportation Safety (BOTS).

New: For crash data analysis requests, please email the BOTS Program and Policy Unit at CrashDataAnalysis@dot.wi.gov.

For Community Maps technical support, please email community-maps@topslab.wisc.edu.

To request access to Community Maps Advanced features, please use the WisTransPortal online User Account Request Form.

Additional contact information:

Randy Wiessinger Statewide Law Enforcement Liaison Bureau of Transportation Safety (BOTS) Division of State Patrol, WisDOT Email: rpw@wiessinger.com

Steven T. Parker, Ph.D. Traffic Operations and Safety (TOPS) Laboratory UW-Madison Department of Civil and Environmental Engineering E-mail: sparker@engr.wisc.edu

Traffic accidents in the City and County of Denver. The data is based on the National Incident Based Reporting System (NIBRS). The data is dynamic, which allows for additions, deletions and/or modifications at any time, resulting in more accurate information in the database. Due to continuous data entry, the number of records in subsequent extractions are subject to change. Accident data is updated Monday through Friday.

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 dataset contains crash information from the last five years to the current date. The data is based on the National Incident Based Reporting System (NIBRS). The data is dynamic, allowing for additions, deletions and modifications at any time, resulting in more accurate information in the database. Due to ongoing and continuous data entry, the numbers of records in subsequent extractions are subject to change.About Crash DataThe Cary Police Department strives to make crash data as accurate as possible, but there is no avoiding the introduction of errors into this process, which relies on data furnished by many people and that cannot always be verified. As the data is updated on this site there will be instances of adding new incidents and updating existing data with information gathered through the investigative process.Not surprisingly, crash data becomes more accurate over time, as new crashes are reported and more information comes to light during investigations.This dynamic nature of crash data means that content provided here today will probably differ from content provided a week from now. Likewise, content provided on this site will probably differ somewhat from crime statistics published elsewhere by the Town of Cary, even though they draw from the same database.About Crash LocationsCrash locations reflect the approximate locations of the crash. Certain crashes may not appear on maps if there is insufficient detail to establish a specific, mappable location.

Please note that 2025 data are incomplete and will be updated as additional records become available. Data are complete through 12/31/2024. 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 2025 data are incomplete and will be updated as additional records become available. Data are complete through 12/31/2024.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

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 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 service contains layers that are used in the Weber/Morgan County Pedestrain Safety Story map. It contains location and related information for pedestrian-related crashes occuring during a three-year analysis period (2016-18). The service was developed to assist a Move Utah meeting with Weber and Morgan Counties regarding pedestrian safety. The service also contains heat maps at two different resolutions showing the concentrations of these pedestrian-related crashes. Questions about this service and related maps can be directed to the Active Transportation Manager, Heidi Goedhart.

The I-15 Statewide Tool provides a comprehensive overview of the I-15 corridor across the State of Utah. It helps us understand how well I-15 is performing on important Utah transportation values like mobility, safety, and connectivity. The tool also identifies areas where I-15 should be improved to meet Utah’s needs, and provides standards and guidelines that UDOT and other transportation agencies can use to maintain a consistent I-15 experience throughout the state. This map contains Congestion and Crash data for the I-15 Corridor. Data is sourced from the raw traffic data from Iteris ClearMobility. This intermediate map is not intended to be viewed directly, but through the I-15 Tool.This map is a component of the I-15 Mobility Dashboard and the broader I-15 ToolFor questions on the data, please contact Andrea Moser at AndreaMoser@utah.gov.

The Crash Emphasis Areas Dashboards provides users with the ability to view crash data for specific emphasis areas such as roadway departure or crashes involving young drivers. Currently there are 26 emphasis areas developed. Each can be viewed by clicking within the different tabs on the top horizontal bar. The emphasis area data is visualized using Dashboards for ArcGIS. Emphasis area descriptions are as follows:Fatal Crashes – All crashes where at least one person involved was fatally-injured. These data are based upon only the crash reports. The reports are delayed until the investigation is completed, which, in the case of fatal crashes, can take three to six months at a minimum. Therefore, crash counts for fatal crashes may conflict with other sources because the final crash report had not been filed at the time of the last update.DUI Crashes – Crashes where at least one driver involved is identified as under the influence of Medication, Drugs, or Alcohol at the time of the crash in the accident report.Young Drivers – Crashes where at least one of the drivers involved is between the ages of 15 to 25.Crashes involving Motorcycles – Crashes where at least one of the vehicles involved is a motorcycle.Non-Motorist Crashes – Crash where at least one of the people involved in the crash is either a bicyclist or a pedestrian.Pedestrian-Involved Crashes – Crash where at least one of the people involved in the crash is a pedestrian.Bicyclist-Involved Crashes – Crash where at least one of the people involved in the crash is a bicyclist.Work Zone Crashes – Crashes that were related to the presence of a Work Zone.Crashes involving School Buses – Crashes where at least one vehicle involved is a School Bus.Crashes involving ATVs – Crashes where at least one vehicle involved is an All-Terrain Vehicle (ATV).Roadway Departure Crashes – Crash where at least one driver's action was driving off of the roadway.Intersections Crashes - Crashes that occurred at an intersection or are intersection-related.Railroad Crossing Crashes - Crashes that occurred at a railroad grade crossing.Crashes involving Transit Buses - Crashes where at least one vehicle involved is a Transit Bus.Federal Motor Carrier Safety Administration (FMCSA) Qualifying Crashes - Crashes where at least one vehicle involved is an FMCSA qualifying vehicle and where there was either 1) a fatality, 2) an injury requiring transportation to a medical facility, or 3) disabling damage to one of the vehicles involved.Crashes Involving Motor Coaches – Crashes where at least one vehicle involved is a Motor Coach.Crashes Involving a Wrong Way Vehicle – Crashes where at least one vehicle was listed as traveling on the wrong side of the wrong direction.Crashes Involving Children Required to Use Car Seats – Crashes where at least one passenger involved is a child required to be in a car seat. In Connecticut, children are required to use a car seat until they are aged 7 and heavier than 60 lbs.Crashes Involving Distracted Drivers – Crashes where at least one driver involved in the crash is deemed to be distracted. Crashes With Fixed Objects – Crashes where at least one vehicle involved hits a fixed object as the first harmful event of the crash. Crashes Involving Older Drivers - Crashes where at least one of the drivers involved is 65 years of age or older Crashes Involving Older Drivers and Pedestrians - Crashes where at least one driver and/or one pedestrian involved is 65 years of age or older Crashes Involving Unlicensed Drivers - Crashes where at least one driver involved in the crash is unlicensed. Aggressive Driving Crashes - Crashes where the investigating officer has recorded driver actions that include at least one and up to four of the following behaviors: failed to yield right of way, ran red light, ran stop sign, disregarded other traffic signs, disregarded other road markings, improper passing, following too closely, operating a vehicle in a reckless and aggressive manner and operating a vehicle in an inattentive, careless, negligent, or erratic mannerSpeed Related Crashes - Crashes where the investigating officer has recorded that one or more drivers has been racing, exceeding the posted speed limit or driving too fast for conditions

Pedestrian Crashes, since 2012, which have been reported by the Police or the Public through the AFP Crash Report Form.

Please note: Although crash data is updated on regular bases it will always have a backlog of entries hence it is not a true reflection of the up to date crash locations. Crash locations are only indicative and may not reflect an accurate position of persons involved in an incident. Casualty crashes are occasionally omitted from some maps or crash reports if they are still under investigation.

On Road Cyclist Crashes, since 2012, which have been reported by the Police or the Public through the AFP Crash Report Form. Please note; Although crash data is updated on regular bases it will always have a backlog of entries hence it is not a true reflection of the up to date crash locations. Crash locations are only indicative and may not reflect an accurate position of persons involved in an incident. Casualty crashes are occasionally omitted from some maps or crash reports if they are still under investigation.

Sites of Road Crashes in South Australia.

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.

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 intersection Read 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

Web map of traffic crashes within the Pikes Peak Area Council of Governments (PPACG) region, developed from crash data records compiled by CDOT from police accident reports filed with the state from each jurisdiction in the region. CDOT consolidates the police reports into a single database, removes personal identifying information, and then provides PPACG with an exported table of crash data records. The majority of the crash data records (greater than 99.99%) are mapped by successfully linear referencing or geocoding the records to routes or address information acquired from CDOT, the El Paso-Teller County E911 Authority, and Park County.For more detailed information regarding the information contained, including available attribute fields, extents, and data sources, please examine the descriptions and metadata for each layer.

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.

Lorem ipsum dolor sit amet, consectetur adipiscing elit, sed do eiusmod tempor incididunt ut labore et dolore magna aliqua. Lorem ipsum dolor sit amet consectetur adipiscing elit. Massa enim nec dui nunc. Quis commodo odio aenean sed adipiscing diam donec adipiscing. Nulla pellentesque dignissim enim sit amet venenatis urna. Sit amet volutpat consequat mauris nunc congue nisi vitae. Fames ac turpis egestas maecenas pharetra convallis posuere morbi leo. Morbi tristique senectus et netus et malesuada fames ac turpis. Eget lorem dolor sed viverra ipsum nunc. Id ornare arcu odio ut sem. Morbi leo urna molestie at elementum eu. In metus vulputate eu scelerisque. Lobortis mattis aliquam faucibus purus in massa tempor nec feugiat. Ut sem viverra aliquet eget sit amet tellus cras adipiscing. Lobortis mattis aliquam faucibus purus in massa tempor. Donec massa sapien faucibus et molestie ac feugiat. Et odio pellentesque diam volutpat commodo sed egestas egestas. Pharetra magna ac placerat vestibulum lectus. Fermentum leo vel orci porta non pulvinar neque laoreet suspendisse.PurposeLorem ipsum dolor sit amet, consectetur adipiscing elit, sed do eiusmod tempor incididunt ut labore et dolore magna aliqua.Dataset ClassificationLevel 0 - OpenKnown UsesLorem ipsum dolor sit amet, consectetur adipiscing elit, sed do eiusmod tempor incididunt ut labore et dolore magna aliqua.Known ErrorsLorem ipsum dolor sit amet, consectetur adipiscing elit, sed do eiusmod tempor incididunt ut labore et dolore magna aliqua.Data ContactLorem ipsum dolor sit amet, consectetur adipiscing elit, sed do eiusmod tempor incididunt ut labore et dolore magna aliqua.Update FrequencyLorem ipsum dolor sit amet, consectetur adipiscing elit, sed do eiusmod tempor incididunt ut labore et dolore magna aliqua.

Contains locations and information about every crash incident reported to the police in Allegheny County from 2004 to 2020. 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. The map below shows car crashes in Allegheny County during 2016, with the color indicating whether it was a rear end collision or not.