데이터셋 상세
미국
Vision Zero Safety
,
데이터 정보
연관 데이터
Vision Zero Dashboard
공공데이터포털
,
District of Columbia Vision Zero Traffic Fatalities and Injury Crashes
공공데이터포털
The Fatal and Injury Crashes Dashboard can be used by the public to locate crashes that result in an injury or fatality. Adjust the Mode, Severity and Date filters to refine the results in the map. All charts will update to reflect the collisions in current map extent. Data are available from 2017-present. Data are updated every Friday.
Vision Zero DC
공공데이터포털
Vision Zero is a safe systems approach to reducing injuries and deaths on our roadways, looking at how our entire transportation system can create a safe environment for travel. The District Government has an all-hands-on-deck approach, with five key agencies involved, and another 25 agencies with some role to play - safe users, safe streets, safe vehicles, safe speeds, post crash care.,
A Vision for Safer Roads
공공데이터포털
,,
VZV Vision Zero View Data
공공데이터포털
Data that that populates the Vision Zero View map, which can be found at www.nycvzv.info Vision Zero is the City's goal for ending traffic deaths and injuries. The Vision Zero action plan can be found at http://www.nyc.gov/html/visionzero/pdf/nyc-vision-zero-action-plan.pdf Crash data is obtained from the Traffic Accident Management System (TAMS), which is maintained by the New York City Police Department (NYPD). Only crashes with valid geographic information are mapped. All midblock crashes are mapped to the nearest intersection. Injuries and fatalities are grouped by intersection and summarized by month and year. This data is queried and aggregated on a monthly basis and is current as of the query date. Current year data is January to the end of the latest full month. All mappable crash data is represented on the simplified NYC street model. Crashes occurring at complex intersections with multiple roadways are mapped onto a single point. Injury and fatality crashes occurring on highways are excluded from this data. Please note that this data is preliminary and may contain errors, accordingly, the data on this site is for informational purposes only. Although all attempts to provide the most accurate information are made, errors may be present and any person who relies upon this data does so at their own risk.
Crashes in DC
공공데이터포털
,
Traffic Crashes - Vision Zero Chicago Traffic Fatalities
공공데이터포털
Traffic fatalities within the City of Chicago that are included in Vision Zero Chicago (VZC) statistics. Vision Zero is Chicago’s commitment to eliminating fatalities and serious injuries from traffic crashes. The VZC Traffic Fatality List is compiled by the Chicago Department of Transportation (CDOT) after monthly reviews of fatal traffic crash information provided by Chicago Police Department’s Major Accident Investigation Unit (MAIU). CDOT uses a standardized process – sometimes differing from other sources and everyday use of the term -- to determine whether a death is a “traffic fatality.” Therefore, the traffic fatalities included in this list may differ from the fatal crashes reported in the full Traffic Crashes dataset (https://data.cityofchicago.org/d/85ca-t3if). Official traffic crash data are published by the Illinois Department of Transportation (IDOT) on an annual basis. This VZC Traffic Fatality List is updated monthly. Once IDOT publishes its crash data for a year, this dataset is edited to reflect IDOT’s findings. VZC Traffic Fatalities can be linked with other traffic crash datasets using the “Person_ID” field. State of Illinois considers a “traffic fatality” as any death caused by a traffic crash involving a motor vehicle, within 30 days of the crash. Fatalities that meet this definition are included in this VZC Traffic Fatality List unless excluded by any criteria below. There may be records in this dataset that do not appear as fatalities in the other datasets. The following criteria exclude a death from being considered a "traffic fatality," and are derived from Federal and State reporting standards. 1. The Medical Examiner determined that the primary cause of the fatality was not the traffic crash, including: a. The fatality was reported as a suicide based on a police investigation. b. The fatality was reported as a homicide in which the "party at fault" intentionally inflicted serious bodily harm that caused the victim's death. c. The fatality was caused directly and exclusively by a medical condition or the fatality was not attributable to road user movement on a public roadway. (Note: If a person driving suffers a medical emergency and consequently hits and kills another road user, the other road user is included, although the driver suffering a medical emergency is excluded.) 2. The crash did not occur within a trafficway. 3. The crash involved a train or other such mode of transport within the rail dedicated right-of-way. 4. The fatality was on a roadway not under Chicago Police Department jurisdiction, including: a. The fatality was occurred on an expressway. The City of Chicago does not have oversight on the expressway system. However, a fatality on expressway ramps occurring within the City jurisdiction will be counted in VZC Traffic Fatality List. b. The fatality occurred outside City limits. Crashes on streets along the City boundary may be assigned to another jurisdiction after the investigation if it is determined that the crash started or substantially occurred on the side of the street that is outside the City limits. Jurisdiction of streets along the City boundary are split between City and neighboring jurisdictions along the street centerline. 5. The fatality is not a person (e.g., an animal). Change 12/7/2023: We have removed the RD_NO (Chicago Police Department report number) for privacy reasons.
Crash Reporting - Non-Motorists Data
공공데이터포털
This dataset provides information on non-motorists (pedestrians and cyclists) involved in traffic collisions occurring on county and local roadways.The reports details of all traffic collisions occurring on county and local roadways within Montgomery County, as collected via the Automated Crash Reporting System (ACRS) of the Maryland State Police, and reported by the Montgomery County Police, Gaithersburg Police, Rockville Police, or the Maryland-National Capital Park Police. This dataset shows each collision data recorded and the non-motorists involved. Please note that these collision reports are based on preliminary information supplied to the Police Department by the reporting parties. Therefore, the collision data available on this web page may reflect: -Information not yet verified by further investigation -Information that may include verified and unverified collision data -Preliminary collision classifications may be changed at a later date based upon further investigation -Information may include mechanical or human error This dataset can be joined with the other 2 Crash Reporting datasets (see URLs below) by the State Report Number. * Crash Reporting - Incidents Data at https://data.montgomerycountymd.gov/Public-Safety/Crash-Reporting-Incidents-Data/bhju-22kf * Crash Reporting - Drivers Data at https://data.montgomerycountymd.gov/Public-Safety/Crash-Reporting-Drivers-Data/mmzv-x632 Update Frequency : Weekly
Parking Violations Issued in January 2010
공공데이터포털
,
Parking Violations Issued in October 2010
공공데이터포털
,