Dataset: Cary, NC Crash Data

About this Dataset

Cary, NC Crash Data

Injuries, Fatalities, and Contributing Factors

By Town of Cary [source]

About this dataset

The Town of Cary Crash Database contains five years worth of detailed crash data up to the current date. Each incident is mapped based on National Incident-Based Reporting System (NIBRS) criteria, providing greater accuracy and access to all available crashes in the County.

This valuable resource is constantly being updated – every day fresh data is added and older records are subject to change. The locations featured in this dataset reflect approximate points of intersection or impact. In cases when essential detail elements are missing or rendered unmapable, certain crash incidents may not appear on maps within this source.

We invite you to explore how crashes have influenced the Town of Cary over the past five years – from changes in weather conditions and traffic controls to vehicular types, contributing factors, travel zones and more! Whether it's analyzing road design elements or assessing fatality rates – come take a deeper look at what has shaped modern day policies for safe driving today!

More Datasets

For more datasets, click here.

Featured Notebooks

🚨 Your notebook can be here! 🚨!

How to use the dataset

Understanding Data Elements – The first step in using this dataset is understanding what information is included in it. The data elements include location descriptions, road features, character traits of roads and more that are associated with each crash. Additionally, the data provides details about contributing factors, light conditions, weather conditions and more that can be used to understand why certain crashes happen in certain locations or under certain circumstances.

Research Ideas

Analyzing trends in crash locations to better understand where crashes are more likely to occur. For example, using machine learning techniques and geographical mapping tools to identify patterns in the data that could enable prediction of future hotspots of crashes.

Investigating the correlations between roadway characteristics (e.g., surface, configuration and class) and accident severities in order to recommend improvements or additional preventative measures at certain intersections or road segments which may help reduce crash-related fatalities/injuries.

Using data from various contributing factors (e.g., traffic control, weather conditions, work area) as an input for a predictive model for analyzing the risk factors associated with different types of crashes such as head-on collisions, rear-end collisions or side swipe accidents so that safety alerts can be issued for public awareness campaigns during specific times/days/conditions where such incidents have been known to occur more often or have increased severity repercussions than usual (i.e., near schools during school days)

Acknowledgements

If you use this dataset in your research, please credit the original authors.
Data Source

License

License: Open Database License (ODbL) v1.0

You are free to:

Share - copy and redistribute the material in any medium or format.

Adapt - remix, transform, and build upon the material for any purpose, even commercially.

You must:

Give appropriate credit - Provide a link to the license, and indicate if changes were made.

ShareAlike - You must distribute your contributions under the same license as the original.

Keep intact - all notices that refer to this license, including copyright notices.

No Derivatives - If you remix, transform, or build upon the material, you may not distribute the modified material.

No additional restrictions - You may not apply legal terms or technological measures that legally restrict others from doing anything the license permits.

Columns

File: crash-data-3.csv

Column name	Description
type	The type of crash, such as single-vehicle, multi-vehicle, or pedestrian. (String)
features	The features of the crash, such as location, contributing factors, vehicle types, and more. (String)

File: crash-data-1.csv

Column name	Description
location_description	Describes the location of the crash. (Text)
rdfeature	Describes the type of road feature involved in the crash. (Text)
rdcharacter	Describes the character of the road involved in the crash. (Text)
rdclass	Describes the class of the road involved in the crash. (Text)
rdconfigur	Describes the configuration of the road involved in the crash. (Text)
rdsurface	Describes the surface of the road involved in the crash. (Text)
rdcondition	Describes the condition of the road involved in the crash. (Text)
lightcond	Describes the light conditions at the time of the crash. (Text)
weather	Describes the weather conditions at the time of the crash. (Text)
trafcontrl	Describes the traffic control measures taken at the time of the crash. (Text)
lat	Describes the latitude coordinate of the crash. (Numerical)
lon	Describes the longitude coordinate of the crash. (Numerical)
lon2	Describes the second longitude coordinate of the crash. (Numerical)
lat2	Describes the second latitude coordinate of the crash. (Numerical)
tract	Describes the census tract of the crash. (Text)
zone	Describes the zone of the crash. (Text)
fatality	Describes the number of fatalities in the crash. (Numerical)
possblinj	Describes the number of possible injuries in the crash. (Numerical)
numpassengers	Describes the number of passengers in the crash. (Numerical)
numpedestrians	Describes the number of pedestrians in the crash. (Numerical)
contrcir1_desc	Describes the first contributing factor to the crash. (Text)
contrcir2_desc	Describes the second contributing factor to the crash. (Text)
contrcir3_desc	Describes the third contributing factor to the crash. (Text)
contrfact2	Describes the second contributing factor to the crash. (Text)
contributing_factor	Describes the contributing factor to the crash. (Text)
vehicleconcat1	Describes the first vehicle involved in the crash. (Text)

Acknowledgements

If you use this dataset in your research, please credit the original authors.
If you use this dataset in your research, please credit Town of Cary.

Tables

Crash Data 1

@kaggle.thedevastator_cary_nc_crash_data_2015_2022.crash_data_1

167.79 KB
20654 rows
47 columns


CREATE TABLE crash_data_1 (
  "index_tamainid" VARCHAR,
  "location_description" VARCHAR,
  "rdfeature" VARCHAR,
  "rdcharacter" VARCHAR,
  "rdclass" VARCHAR,
  "rdconfigur" VARCHAR,
  "rdsurface" VARCHAR,
  "rdcondition" VARCHAR,
  "lightcond" VARCHAR,
  "weather" VARCHAR,
  "trafcontrl" VARCHAR,
  "lat" VARCHAR,
  "lon" VARCHAR,
  "lon2" VARCHAR,
  "lat2" VARCHAR,
  "tract" VARCHAR,
  "zone" VARCHAR,
  "fatality" VARCHAR,
  "possblinj" VARCHAR,
  "numpassengers" VARCHAR,
  "numpedestrians" VARCHAR,
  "contrcir1_desc" VARCHAR,
  "contrcir2_desc" VARCHAR,
  "contrcir3_desc" VARCHAR,
  "contrcir4_desc" VARCHAR,
  "vehicle1" VARCHAR,
  "vehicle2" VARCHAR,
  "vehicle3" VARCHAR,
  "vehicle4" VARCHAR,
  "vehicle5" VARCHAR,
  "workarea" VARCHAR,
  "records" VARCHAR,
  "ta_date" VARCHAR,
  "ta_time" VARCHAR,
  "crash_date" VARCHAR,
  "geo_location" VARCHAR,
  "year" VARCHAR,
  "fatalities" VARCHAR,
  "injuries" VARCHAR,
  "month" VARCHAR,
  "contrfact1" VARCHAR,
  "contrfact2" VARCHAR,
  "contributing_factor" VARCHAR,
  "vehicleconcat1" VARCHAR,
  "vehicleconcat2" VARCHAR,
  "vehicleconcat3" VARCHAR,
  "vehicle_type" VARCHAR
);

Crash Data 2

@kaggle.thedevastator_cary_nc_crash_data_2015_2022.crash_data_2

10.85 KB
1 row
3 columns


CREATE TABLE crash_data_2 (
  "index" BIGINT,
  "links" VARCHAR,
  "dataset" VARCHAR
);

Crash Data 3

@kaggle.thedevastator_cary_nc_crash_data_2015_2022.crash_data_3

4.79 MB
23482 rows
3 columns


CREATE TABLE crash_data_3 (
  "index" BIGINT,
  "type" VARCHAR,
  "features" VARCHAR
);

Crash Data 4

@kaggle.thedevastator_cary_nc_crash_data_2015_2022.crash_data_4

1.75 MB
23482 rows
48 columns


CREATE TABLE crash_data_4 (
  "index" BIGINT,
  "tamainid" BIGINT,
  "location_description" VARCHAR,
  "rdfeature" VARCHAR,
  "rdcharacter" VARCHAR,
  "rdclass" VARCHAR,
  "rdconfigur" VARCHAR,
  "rdsurface" VARCHAR,
  "rdcondition" VARCHAR,
  "lightcond" VARCHAR,
  "weather" VARCHAR,
  "trafcontrl" VARCHAR,
  "lat" DOUBLE,
  "lon" DOUBLE,
  "lon2" DOUBLE,
  "lat2" DOUBLE,
  "tract" VARCHAR,
  "zone" DOUBLE,
  "fatality" BIGINT,
  "possblinj" BIGINT,
  "numpassengers" DOUBLE,
  "numpedestrians" DOUBLE,
  "contrcir1_desc" VARCHAR,
  "contrcir2_desc" VARCHAR,
  "contrcir3_desc" VARCHAR,
  "contrcir4_desc" VARCHAR,
  "vehicle1" VARCHAR,
  "vehicle2" VARCHAR,
  "vehicle3" VARCHAR,
  "vehicle4" VARCHAR,
  "vehicle5" VARCHAR,
  "workarea" VARCHAR,
  "records" BIGINT,
  "ta_date" TIMESTAMP,
  "ta_time" TIMESTAMP,
  "crash_date" TIMESTAMP,
  "geo_location" VARCHAR,
  "year" BIGINT,
  "fatalities" VARCHAR,
  "injuries" VARCHAR,
  "month" BIGINT,
  "contrfact1" VARCHAR,
  "contrfact2" VARCHAR,
  "contributing_factor" VARCHAR,
  "vehicleconcat1" VARCHAR,
  "vehicleconcat2" VARCHAR,
  "vehicleconcat3" VARCHAR,
  "vehicle_type" VARCHAR
);