With more than 44,000 Portable Traffic Count (PTC) Stations located throughout North Carolina, Traffic Survey has adopted a collection schedule. Please see our website: https://www.ncdot.gov/projects/trafficsurvey/for further details. The data in this file was digitized referencing the available NCDOT Linear Referencing System (LRS) and is not the result of using GPS equipment in the field, nor latitude and longitude coordinates. The referencing provided is based on the 2015 Quarter 1 publication of the NCDOT Linear Referencing System (LRS). Some differences will be found when using different quarterly publications with this data set. The data provided is seasonally factored to an estimate of an annual average of daily traffic. The statistics provided are: CVRG_VLM_I: Traffic Survey's seven digit unique station identifier COUNTY: County NameROUTE: Numbered route identifier, or local name if not State maintainedLOCATION: Description of the Annual Average Daily Traffic station location AADT_2015: Estimated Annual Average Daily Traffic in vehicles per day for 2015AADT_2014: Estimated Annual Average Daily Traffic in vehicles per day for 2014AADT_2013: Estimated Annual Average Daily Traffic in vehicles per day for 2013 AADT_2012: Estimated Annual Average Daily Traffic in vehicles per day for 2012 AADT_2011: Estimated Annual Average Daily Traffic in vehicles per day for 2011 AADT_2010: Estimated Annual Average Daily Traffic in vehicles per day for 2010 AADT_2009: Estimated Annual Average Daily Traffic in vehicles per day for 2009 AADT_2008: Estimated Annual Average Daily Traffic in vehicles per day for 2008 AADT_2007: Estimated Annual Average Daily Traffic in vehicles per day for 2007 AADT_2006: Estimated Annual Average Daily Traffic in vehicles per day for 2006 AADT_2005: Estimated Annual Average Daily Traffic in vehicles per day for 2005 AADT_2004: Estimated Annual Average Daily Traffic in vehicles per day for 2004 AADT_2003: Estimated Annual Average Daily Traffic in vehicles per day for 2003 AADT_2002: Estimated Annual Average Daily Traffic in vehicles per day for 2002 Note: A value of zero in the AADT field indicates no available AADT data for that year. Please note the following: Not ALL roads have PTC stations located on them. With the exception of Interstate, NC and US routes, NCDOT County Maps refer to roads using a four digit Secondary Road Number, not a road’s local name. If additional information is needed, or an issue with the data is identified, please contact the Traffic Survey Group at 919 814-5116. Disclaimer related to the spatial accuracy of this file: Data in this file was digitized referencing the available NCDOT GIS Data Layer, LRS Arcs Shapefile Format from Quarter 1 release and is not the result of using GPS equipment in the field.North Carolina Department of Transportation shall not be held liable for any errors in this data. This includes errors of omission, commission, errors concerning the content of data, and relative positional accuracy of the data. This data cannot be construed to be a legal document.

This study investigated whether the North Carolina State Highway Patrol (NCSHP) practiced racial profiling. The NCSHP provided data on all vehicular stops (Parts 1 and 2), written warnings (Part 3), and citations (Part 4) its officers issued in 2000. This included data on what the stops or tickets were for, the race, sex, and age of the driver, and the make, model, and year of the car being driven. Data on accidents in 2000 (Part 5), also obtained from the NCSHP, were used to examine whether there were racial disparities in unsafe driving practices. These data included information about what caused the accident and the race, sex, and age of the driver. The NCSHP also supplied data on all officers who worked for the NCSHP in 2000 (Part 6), including their race, age, and rank. The data in Part 6 can be linked to the data in Parts 3 and 4. In addition, two surveys of North Carolina drivers were conducted to gather information on reported typical driving behaviors that may influence the probability of being stopped, and to gather information about stops conducted by law enforcement agencies across the state. One was conducted using a sample of North Carolina drivers who had recently renewed their licenses (Part 7), and the other used a sample of North Carolina drivers who were ticketed for speeding between June 1, 1999, and June 1, 2000 (Part 8).

This dataset provides information about 2007 Annual Average Daily Traffic (AADT) Volume Estimates by Section of Route in North Carolina

This dataset provides information about 2015 Annual Average Daily Traffic (AADT) Volume Estimates by Section of Route in North Carolina

This dataset provides information about 2014 Annual Average Daily Traffic (AADT) Volume Estimates by Section of Route in North Carolina

Charlotte-Mecklenburg Police Department (CMPD) is committed to deploying traffic officers to areas where we experience high crime and victimization. Our focus is also in the geographical areas where concerns are reported by community members. We as a police department have a responsibility to those communities, to address their concerns and take appropriate enforcement action in an effort to keep their neighborhoods safe. Additionally, we are not only reacting to crime but proactively engaging in strategies that are intended to prevent criminal activity from occurring by placing officers in areas with a greater statistical history of crime. Under North Carolina state law (G.S. 143B-902-903), the CMPD as well as other law enforcement agencies in the state are required to collect information on all traffic stops, the reason for the stop, and the type of enforcement action taken. Information on the driver’s sex, race, ethnicity, and age is collected, compiled, and reported to the NC De

Context:

On a typical day in the United States, police officers make more than 50,000 traffic stops. The Stanford Open Policing Project team is gathering, analyzing, and releasing records from millions of traffic stops by law enforcement agencies across the country. Their goal is to help researchers, journalists, and policymakers investigate and improve interactions between police and the public.

If you'd like to see data regarding other states, please go to https://www.kaggle.com/stanford-open-policing.

Content:

This dataset includes 1.6 gb of stop data from North Carolina, covering all of 2010 onwards. Please see the data readme for the full details of the available fields.

Acknowledgements:

This dataset was kindly made available by the Stanford Open Policing Project. If you use it for a research publication, please cite their working paper: E. Pierson, C. Simoiu, J. Overgoor, S. Corbett-Davies, V. Ramachandran, C. Phillips, S. Goel. (2017) “A large-scale analysis of racial disparities in police stops across the United States”.

Inspiration:

• How predictable are the stop rates? Are there times and places that reliably generate stops?
• Concerns have been raised about jurisdictions using civil forfeiture as a funding mechanism rather than to properly fight drug trafficking. Can you identify any jurisdictions that may be exhibiting this behavior?

Police-recorded crash data has improved over time, but still fails to report all aspects of crashes that are important to developing a full understanding of crash mechanisms, injury burdens, pre-crash conditions, and ultimately total health and cost outcomes. Traditionally, safety and injury analysis has occurred in siloed fields, with road safety researchers relying predominately on police-recorded crash reports, and public health researchers relying on hospitalization records. Depending on the context of the study and the database used, findings vary. This is the case for the micro-level (e.g., injury severity of an individual) to the macro-level (e.g., injury rate) scale. This project begins to map disparate data sets to inform questions surrounding crashes. The data-mapping process will aim to build linkages between police-crash datasets and other datasets (i.e., incident-oriented data, spatial data, emerging datasets) and scale it up to larger geographic areas. Efforts to augment crash data are not new. A notable health-oriented example which sought to link health and police records was the Crash Outcome Data Evaluation System (CODES). Although this federal program ended in 2013, some states, including California, North Carolina, and Tennessee, have continued this effort. Added data and analytics resulted in a more “complete picture” of crashes and injuries. This complete picture enables researchers to improve their modeling, assist policy makers, and contribute to visualization that helps tell compelling safety stories that guide safety improvements.

This service provides lines representing designated secondary routes in North Carolina where truck traffic with axle weights exceeding 13,000 pounds is prohibited by ordinance. These roads are shown as symbolized centerlines aligned to NCDOT’s route network. The Posted Route attribute value is the ordinance number; any value present indicates that the segment is part of the Posted Route system. Roads are posted to avoid damage to the roadway. As roads are improved and strengthened, they may be removed from this list.More information about North Carolina's Posted Roads can be found here:https://connect.ncdot.gov/resources/Asset-Management/Pages/Posted-Roads.aspxDetailed information regarding NCDOT ordinances, including truck restrictions, can be found here:https://connect.ncdot.gov/resources/safety/Pages/Safety-Ordinances.aspxA Posted and Restricted Roads lookup system can be accessed at this link:https://apps.ncdot.gov/PRR/RoadSearch.aspxMetadataThe metadata for the contained layer of the NCDOT Posted Roads Service is available through the following link:Posted RoutesPoint of Contact North Carolina Department of Information Technology -Transportation, GIS UnitGIS Data and Services ConsultantContact information:gishelp@ncdot.govCentury Center – Building B1020 Birch Ridge DriveRaleigh, NC 27610Hours of service: 9:00am - 5:00pm Monday – FridayContact instructions: Please send an email with any issues, questions, or comments regarding the Posted Roads data. If it is an immediate need, please indicate as such in the subject line in an email.NCDOT GIS Unit GO! NC Product TeamLastUpdated: 2024-11-11 00:00:00

CMPD conducts an average of 120,000 traffic stops per year. Under North Carolina state law (G.S. 143B-902-903), the CMPD as well as other law enforcement agencies in the state are required to collect information on all traffic stops, the reason for the stop, and the type of enforcement action taken. Information on the driver’s sex, race, ethnicity, and age is collected, compiled, and reported to the NC Department of Justice. Information on whether the driver or passenger(s) were searched is also collected. For more information, please visit http://charlottenc.gov/CMPD/Pages/Resources/OpenData_Source.aspx

CMPD is committed to deploying traffic officers to areas where we experience high crime and victimization. Our focus is also in the geographical areas where concerns are reported by community members. We as a police department have a responsibility to those communities, to address their concerns and take appropriate enforcement action in an effort to keep their neighborhoods safe. Additionally, we are not only reacting to crime but proactively engaging in strategies that are intended to prevent criminal activity from occurring by placing officers in areas with a greater statistical history of crime.

This service provides lines representing posted speed limits along centerlines of North Carolina state-maintained roads. This data comes from traffic ordinances governing speed limit; where there is no ordinance, the speed limit is 35 within municipalities and 55 outside. The N.C. Department of Transportation sets the speed limit for all state-maintained roads, including access-controlled highways, which are highways with medians that require drivers to enter or exit only at interchanges with bridges, inside the town or city limits. For other state-maintained roads within the municipal limits, NCDOT and the town or city must concur before changing the speed limit. Roads are designed for a specific speed. NCDOT may review the speed limit for various reasons, such as part of a study to improve highway safety, or for proposed new developments. Citizens and local officials may also request NCDOT to conduct a speed zone study to determine whether a road has the appropriate speed limits and signage.The department considers several factors when adjusting the speed limit, such as:Alignment of the roadwayTypes of development along the roadwayThe density, or number, of driveways on a corridorHow far one can see the roadCrash historyVarious speed dataOne of the most common types of speed data NCDOT uses is based on the speed at or below which 85 percent of drivers are traveling. NCDOT uses the 85th percentile to help avoid posting speed limits that are artificially low, which can become difficult to enforce. In the absence of strict enforcement, most people drive at the speed they are comfortable with, regardless of the speed limit.MetadataThe metadata for the contained layer of the NCDOT Speed Limit Service is available through the following link:Speed LimitPoint of Contact North Carolina Department of Information Technology -Transportation, GIS UnitGIS Data and Services ConsultantContact information:gishelp@ncdot.govCentury Center – Building B1020 Birch Ridge DriveRaleigh, NC 27610Hours of service: 9:00am - 5:00pm Monday – FridayContact instructions: Please send an email with any issues, questions, or comments regarding the Speed Limit data. If it is an immediate need, please indicate as such in the subject line in an email.NCDOT GIS Unit GO! NC Product TeamLastUpdated: 2024-01-01 00:00:00

The dataset includes the crash and incident data used for the North Carolina case study in this study. It also includes the congestion scan plot obtained from RITIS for the case study corridor.

Feature layer of Streets.

This web map service provides points and lines representing current Traveler Information Management System (TIMS) Incidents provided by the NCDOT Traffic Systems Operations Unit. This service is used in the Select Tropical/Severe Weather & NCDOT Incident Information Dashboard application.NCDOT’s Traffic Systems Operations Unit provides a web site (https://drivenc.gov) displaying incidents that affect or will affect travel on roads maintained by NCDOT. This service was created to make the data provided by TIMS and maintained by the Traffic Systems Operations Unit (TSO) of NCDOT available for use in Esri products as seamlessly as possible. The service is a repackaging of a JSON data feed from TSO. This data is updated every 5 minutes based on the web services provided by TIMS. A script consumes the feed from TIMS and repopulates the data with the most current information.The TIMS Incidents data indicate the expected impact on traffic using three colored categories of severity: Low, Medium, High.Low Impact - GreenUS/NC routes: on/near roadway but no lanes are affected.Incident on a single or multi-lane facility where there is minimal disruption to the flow of traffic and where incident clearance time is 30 minutes or less:Disabled vehiclesRoadway debrisCrash involving property damage onlyIncidents that fall under the "Fender Bender" lawMedium Impact - OrangeInterstates: on/near roadway but no lanes are affected (e.g., on the shoulder/median).US/NC routes: less than half of available lanes are affected.Incident on a single or multi-lane facility where there is full road closure in one or both directions and expected roadway clearance time is 90 minutes OR incident clearance time is less than 2 hours:Overturned passenger vehicleMultivehicle crashCrash involving injuryCommercial vehicle/tractor trailer crash (NOT overturned)All incidents where Congestion or a Reported Incident is used as the incident type unless otherwise directed.High Impact - OrangeInterstates: One or more lanes effected.US/NC routes half or more of the available lanes are affected.Incident on a multi-lane facility where there is full road closure in one or both directions and expected roadway clearance time is 2 or more hours or incident clearance time is 4 or more hours:Overturned tractor trailerFull road closure in one direction on a multilane facilityFatal or life-threatening injury crashesHazardous materialsStructural damage that compromises further safe use of roadwayMetadataThe metadata for the contained layers of the NCDOT TIMS Incidents Service is available through the following links:NCDOT Division BoundariesCounty BoundaryNCDOT Route ArcsPoint of Contact North Carolina Department of Information Technology -Transportation, GIS UnitGIS Data and Services ConsultantContact information:gishelp@ncdot.govCentury Center – Building B1020 Birch Ridge DriveRaleigh, NC 27610Hours of service: 9:00am - 5:00pm Monday – FridayContact instructions: Please send an email with any issues, questions, or comments regarding the TIMS Incidents data. If it is an immediate need, please indicate as such in the subject line in an email.NCDOT GIS Unit GO! NC Product Team

Traffic accident, injury, fatality, and highway mileage data for North Carolina and counties.

Traffic signal location list for the town of Chapel Hill. This data set includes light cycle information as well as as intersection information.

The Town of Chapel Hill traffic signal system project upgraded the existing 14-year-old system of about 115 signals in Chapel Hill and Carrboro. The $5 million project, funded by the Town of Chapel Hill and American Recovery and Reinvestment Act funds, began in 2010 and was completed in the summer of 2012.

The project’s key elements are:
• pedestrian countdown displays at locations with existing pedestrian signals
• replacement/upgrade of existing cabinets and controllers
• new traffic signal phasing at selected locations
• emergency vehicle preemption at selected locations
• bicycle activated loops at selected locations.
• fiber optic communication cable infrastructure
• closed-circuit television (CCTV) equipment at selected locations
• new system detectors

The signal system project was coupled with an effort to install fiber optic communications cable linking Town of Chapel Hill administrative, service and recreation facilities. The fiber optic part of the project installed about 30 miles of municipal fiber optic cable connecting 15 Town facilities. The cable routing and capacity design included considerations for future needs such as connectivity for schools. The project will provide high speed data communications to facilitate voice, data and video services for Town facilities.

The project also included the installation of a new Traffic Management Center (TMC), located in the Public Works Department at 6850 Millhouse Road. The TMC receives feeds from closed circuit television cameras trained on major arteries, allowing operations staff to track traffic conditions at key locations in the community. The TMC is equipped with eight monitors to view the traffic flow through 16 different intersections that are equipped with traffic cameras. The Town of Chapel Hill does not archive or retain any of the images from the traffic cameras. Similar systems have been installed in municipalities across NC and the United States. Benefits of these systems include enhanced roadway safety, decreased traffic congestion during special events and rush hour, faster programming for real-time adjustments to traffic signals, reduced travel time, and improved air quality.

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 | |:-------------------------|:----------...

This dataset provides information about 2009 Annual Average Daily Traffic (AADT) Volume Estimates by Section of Route in North Carolina

This data set maps the locations of crashes involving pedestrians in the Chapel Hill Region of North Carolina.

The data comes from police-reported bicycle-motor vehicle and pedestrian-motor vehicle collisions that occurred on the public roadway network, public vehicular areas and private properties (if reported) from January 2007 through December 2013. Users are able to click and view information specific to each crash. Information for each crash includes: County, City, Crash Date, Crash Day, Crash Group, Crash Location, Crash Time, Crash Severity, Bike/Pedestrian Age Group, Bike/Pedestrian Alcohol Detected, Bike Direction, Bike/Pedestrian Injury, Bike/Pedestrian Position, Bike/Pedestrian Race, Bike/Pedestrian Sex, Ambulance Response, Driver Age Group, Driver Estimated Speed, Speed Limit, Driver Alcohol Detected, Driver Injury, Driver Race, Driver Sex, Driver Vehicle Type, Hit and Run, Development, Light Condition, Locality, Number of Lanes, Road Characteristics/Class/Condition/Configuration, Road Defects/Features, Traffic Control, Crash Type, and/or Weather. Crash identification numbers have been removed from the data for protection of privacy. Crash records were obtained NCDOT’s Traffic Engineering Accident Analysis System (TEAAS).

This feature layer spatially represents DriveNC//NCDOT’s TIMS incident data feed by Road Condition. The TIMS Incidents data contains the general location of and details about incidents that affect or will affect travel on roads maintained by the North Carolina Department of Transportation.This hosted feature layer view is intended for public viewing.NCDOT TIMS Incidents Points - Contains a point reference for all incidents, point and line.NCDOT TIMS Incidents Lines - Lines representing linear incidents. Generally, only select incidents types and road closed conditions will be represented as lines. A point feature will represent the same incident.This data includes all incidents including those recorded on concurrent routes. To remove these from the data, filter where "CreatedFromConcurrent = False".The data is provided through an automated routine that pulls data from the TIMS geojson feed every 5 minutes. Note that the data may disappear for a few moments while being refreshed.The feature layer contains all incidents; current and future. To only view current incidents in your web map, create a filter using the "StartDate" field. For example, filter by Start Date "in the last" 6 years. Note: DateTime fields are in UTC (as indicated in the field name). Text fields contain data/time values in Eastern Time.

Attributes/Fields:

Attribute/Field 


Description/Comments

Id

Unique Id of the Incident

Location

General description of the incident location.

Road

The road on which the incident occurred.

CommonName

Common name of the road on which the incident occurred or will occur

Direction

Direction of traffic impacted. Values include: North South East West All Inner Out

RouteType

Type of Route. Values include: Interstate US Route NC Route Secondary Road

RouteSuffix

Route Suffix. Values include: Alternate Business Bypass Connector Express Truck Toll

RouteId

NCDOT route id

City

Name of the nearest city to the incident.

CountyId

County number in which the incident occurred. Values from 1 to 100, where Alamance is 1 and Yancey is 100.

CountyName

Name of the county in which the incident occurred.

Division

Division number

EventId

Id of the Event designation. If the field is blank, the incident is not associated with an event.

EventName

Name of the Event designation. If the field is blank, the incident is not associated with an event.

Reason

Additional information about the incident.

IncidentType

Type of incident. Values include: Emergency Road Work Construction Night Time Construction Weekend Construction Maintenance Night Time Maintenance Road Obstruction Vehicle Crash Disabled Vehicle Congestion Signal Problem Weather Event Fog Fire Special Event Other Reported Incident

Severity

Severity of the incident. Values include: 1 = Low Impact 2 = Medium Impact 3 – High Impact

Condition

Road condition caused by the incident. Congestion Lane Closed Lane Shift Lanes Closed Lanes Narrowed Moving Closure Permanent Road Closure Ramp Closed Rest Area Closed Road Closed Road Impassable Shoulder Closed Lane Narrowed Ramp Lane Closed Ramp Lane Narrowed Road Closed with Detour

Detour

The detour or alternate route instructions

LanesClosed

The total number of lanes closed due to the incident

LanesTotal

The total number of lanes affected by the incident

DriveNCLink

Link to the DriveNC web page for the incident

StartDateUTC

Incident start date/time in UTC. AGOL automatically adjust date/time to the local time zone. Calculate the time when used outside of AGOL. To calculate EST subtract 5 hours. To calculate EDT subtract 4 hours.

EndDateUTC

Incident end date/time in UTC. AGOL automatically adjust date/time to the local time zone. Calculate the time when used outside of AGOL. To calculate subtract 5 hours. To calculate EDT subtract 4 hours.

LastUpdateDateUTC

Last update date/time in UTC. AGOL automatically adjust date/time to the local time zone. Calculate the time when used outside of AGOL. To calculate subtract 5 hours. To calculate EDT subtract 4 hours

TIMCCreationDateUTC

TIMS Creation date/time in UTC. Calculate the time when used outside of AGOL. To calculate EST subtract 5 hours.To calculate EDT subtract 4 hours

StartDateET

Incident Start Date in ET (EDT or EST).This is a text field suitable for display. Use the UTC fields for filtering on time.

StartTimeET

Incident Start Time in ET (EDT or EST). This is a text field suitable for display. Use the UTC fields for filtering on time.

EndDateET

Incident End Date in ET (EDT or EST). This is a text field suitable for display. Use the UTC fields for filtering on time.

EndTimeET

Incident End Time in ET (EDT or EST). This is a text field suitable for display. Use the UTC fields for filtering on time.

LastUpdateDateET

Last Update Date in ET (EDT or EST). This is a text field suitable for display. Use the UTC fields for filtering on time.

LastUpdateTimeET

Last Update Time in ET (EDT or EST). This is a text field suitable for display. Use the UTC fields for filtering on time.

TIMSCreationDateET

TIMS Creation Date in ET (EDT or EST). This is a text field suitable for display. Use the UTC fields for filtering on time.

TIMSCreationTimeET

TIMS Creation Time in ET (EDT or EST). This is a text field suitable for display. Use the UTC fields for filtering on time.

Latitude

Latitude

Longitude

Longitude

Note: Details about the incident are available through the NCDOT TIMS site. You can link directly to the incident details by combining https://tims.ncdot.gov/TIMS/IncidentDetail.aspx?id= and the TimsId/Incident ID. Note: The Last Modified and Created dates apply to this item entry in GO!NC/ArcGIS Online and may not reflect the actual dates of the data or map service itself.