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.

The AADT shapefile is a station point shapefile of Annual Average Daily Traffic (AADT) estimates. This data includes the data submitted to FHWA for Highway Performance Monitoring System (HPMS) AADT data reporting for 2019. Data is reported for AADT on all highways with a Functional Classification (FC) above Local. A full coverage is provided for these routes where AADT segmentation is based on network configuration, travel patterns, and land use. The extent of highway this AADT represents has not been determined. An AADT is an Annual Average Daily Traffic volume for all lanes in both directions passing a point on the highway system. It represents the average of all days during the year with typical traffic conditions. An AADT estimate is generated using procedures that comply with the standards specified in the Traffic Monitoring Guide published by the Federal Highway Administration. There are over 44,000 AADT stations that provide traffic data history from 2002 to 2019. With more than 44,000 Portable Traffic Count (PTC) Stations located throughout North Carolina, Traffic Survey has adopted the following data collection schedule: Interstate route volumes are collected on an annual basis; US and NC route volumes are also collected on an annual basis with the exception of stations that fall within the off cycle urban areas. (See urban area cycle below.) Secondary Road (SR) volumes are collected on a biennial cycle with approximately half being counted each year. If a particular secondary road is not available for the most current year, it may be available for the prior year. North Carolina's eighteen largest urban areas are counted on a biennial cycle with 10 urban areas counted during the even years, and 8 urban areas counted during the odd years. The following urban areas are collected during the even year cycle: Asheville, Charlotte, Concord-Kannapolis, Fayetteville, Gastonia, Goldsboro, Greenville, and Jacksonville. The following urban areas are collected during the odd year cycle: Burlington, Chapel Hill, Durham, Greensboro, Hickory, High Point, Raleigh, Rocky Mount, Wilmington, and Winston-Salem. 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 2020 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: Location_ID - 10 digit unique count location identifier, ROUTE: Numbered route identifier, or local name if not State maintained, LOCATION: Description of the Annual Average Daily Traffic station location. AADT_2019: Estimated Annual Average Daily Traffic in vehicles per day for 2019 AADT_2018: Estimated Annual Average Daily Traffic in vehicles per day for 2018 AADT_2017: Estimated Annual Average Daily Traffic in vehicles per day for 2017 AADT_2016: Estimated Annual Average Daily Traffic in vehicles per day for 2016 AADT_2015: Estimated Annual Average Daily Traffic in vehicles per day for 2015 AADT_2014: Estimated Annual Average Daily Traffic in vehicles per day for 2014 AADT_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) 707-0936. 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.

The AADT file is a station point location of Annual Average Daily Traffic (AADT) estimates. This includes the data submitted to FHWA for Highway Performance Monitoring System (HPMS) AADT reporting for 2021. Data are reported for AADT on all highways with a Functional Classification (FC) above Local. A full coverage is provided for these routes where AADT segmentation is based on network configuration, travel patterns, and land use. The extent of highway this AADT represents has not been determined. An AADT is an Annual Average Daily Traffic volume for all lanes in both directions passing a point on the highway system. It represents the average of all days during the year with typical traffic conditions. An AADT estimate is generated using procedures that comply with the standards specified in the Traffic Monitoring Guide published by the Federal Highway Administration. There are over 44,000 AADT stations that provide traffic data history from 2002 to the current year. With these collection locations, Traffic Survey has adopted the following data collection schedule: Interstate route volumes are collected on an annual basis; US and NC route volumes are also collected on an annual basis except for stations that fall within the off-cycle urban areas. (See urban area cycle below.) Secondary Road (SR) volumes are collected on a biennial cycle with approximately half being counted each year. If a particular secondary road is not available for the most current year, it may be available for the prior year. North Carolina's eighteen largest urban areas are counted on a biennial cycle with 10 urban areas counted during the even years, and 8 urban areas counted during the odd years. The following urban areas are collected during the even year cycle: Asheville, Charlotte, Concord-Kannapolis, Fayetteville, Gastonia, Goldsboro, Greenville, and Jacksonville. The following urban areas are collected during the odd year cycle: Burlington, Chapel Hill, Durham, Greensboro, Hickory, High Point, Raleigh, Rocky Mount, Wilmington, and Winston-Salem. Data in this file derives from NCDOT Roads & Highways, Quarter 1 publication of the current calendar year. The referencing provided is based on the 2022 Quarter1publication 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 Location_ID - 10-digit unique count location identifier, ROUTE: Numbered route identifier, or local name if not State maintained, LOCATION: Description of the Annual Average Daily Traffic station location. AADT 2021: Estimated Annual Average Daily Traffic in vehicles per day for 2021 AADT_2018: Estimated Annual Average Daily Traffic in vehicles per day for 2018 AADT_2017: Estimated Annual Average Daily Traffic in vehicles per day for 2017 AADT_2016: Estimated Annual Average Daily Traffic in vehicles per day for 2016 AADT_2015: Estimated Annual Average Daily Traffic in vehicles per day for 2015 AADT_2014: Estimated Annual Average Daily Traffic in vehicles per day for 2014 AADT_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. Except for 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) 707-0936. Disclaimer related to the spatial accuracy of this file: This data cannot be construed to be a legal document.

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

(From NCDOT) An AADT is an Annual Average Daily Traffic volume for all lanes in both directions passing a point on the highway system. It represents the average of all days during the year with typical traffic conditions. An AADT estimate is generated using procedures that comply with the standards specified in the Traffic Monitoring Guide published by the Federal Highway Administration. Source: http://www.ncdot.gov/doh/preconstruct/tpb/traffic_survey/

The data is provided by the North Carolina Department of Transportation. It is based on current crash data in the North Carolina Crash Database as reported by the NC State Highway Patrol and municipalities throughout the state. There is a lag in processing crash data, particularly data from municipalities that submit crash reports using paper forms. As a result, the dataset here is preliminary and may represent an undercount of the true crash totals. From the NC DOT: The data are intended to provide the public with a general overview of traffic safety trends, should not be used for planning purposes, and are not considered authoritative. Data presented herein may differ slightly from NCDOT published data due to differences in reporting and update frequencies. The intent of presenting these data is to provide insights and trends for general informational purposes only, and they are not intended as official authoritative data. The raw data is provided directly to our research team as a .csv file containing the county-level aggregated number of traffic crashes each day. The data is updated monthly, and contains the number of crashes of different severity types, including fatal, incapacitating injury, nonincapacitating injury, possible injury, no injury, and unknown injuries.

The Traffic Segment Event file contains Annual Average Daily Traffic (AADT) and Vehicle Class (VC) estimates. This resource represents the approved annual submission to the FHWA, Highway Performance Monitoring System (HPMS) reporting for calendar year 2021. We report AADT on all highways functionally classified (FC) above Local. A full coverage is provided for routes where AADT segmentation is based on network configuration, travel patterns, and land use. Where divided highways occur, the AADT total for both directions is referenced on the inventory direction. Data is provided for ramps also. The ramp data does not cover all ramp segments, but all major traffic flows at interchanges are reported. Some maintained traffic segments require multiple records due to route ID changes at the county boundary in the linear referencing system (LRS). Traffic statistics for these segments are the same on each side of the county boundary but are maintained in this format to preserve the different location referencing data. Over 31,000 reference records (labeled “MAINT” in the SOURCE field) are required to provide event data for all maintained AADT segments. Supplemental AADT are provided on the routes that are Functionally Classified LOCAL. These roadways are not reported in the maintenance table described above for HPMS reporting. A reference is generated through a spatial join between the monitoring station point and the LRS Milepoint upon which it falls. The extent of highway this AADT represents has not been determined. This process captures the AADT for Local routes into the published table without requiring a comprehensive maintenance process. The AADT on Local routes may extend beyond the arc used to report it. The user must exercise their judgment in determining the extent of highway for an AADT in this case. There are over 16,000 records that are supplemental using this method, one record for each station captured. Vehicle Class data is provided for those segments where vehicle class data was collected. Truck volume data is collected at stations and the volumes are annualized. Annualized truck percentages for Single Unit (SU) and Multi Unit (MU) trucks are generated from this data. These truck percentages are applied to the 2021 AADT estimates to generate 2021 truck volume estimates. The truck percentage and volume estimates are provided in the shapefile. The VC coverage includes the National Highway System (NHS) and the NC Truck Network. VC data is not collected on routes not part of these systems and truck statistics are not provided on these segments. The referencing provided is based on the 2022 Quarter 1 publication of the NCDOT Linear Referencing System (LRS) maintained by the NCDIT GIS Unit. This is the official 2021 data set reported for HPMS routes, is the basis for the highway mileage reports, and is used to estimate vehicle miles of travel (VMT) for 2021. Differences in the Milepoints and references may be found when using other quarterly publications with this data set.

The NCDOT Functional Class map service represents state maintained roads with functional classification assignments. This data is updated quarterly; usually February, May, August, November. As stated by the United States Federal Highway Administration, functional classification is the process by which streets and highways are grouped into classes, or systems, according to the character of service they are intended to provide. Basic to this process is the recognition that individual roads and streets do not serve travel independently in any major way. Rather, most travel involves movement through a network of roads. It becomes necessary then to determine how this travel can be channelized within the network in a logical and efficient manner. Functional classification defines the nature of this channelization process by defining the part that any particular road or street should play in serving the flow of trips through a highway network. There are three main functional classes as defined by the United States Federal Highway Administration: arterial, collector, and local. Arterial roads generally provide the fastest method of travel and typically have low accessibility from neighboring roads. They are usually designed with long-distance travel in mind and are not as common as the other two functional classes of roads. Collector roads are the second most common and are used as a connection between local roads and arterial roads. They provide a balance between access and mobility. Local roads are the most common roads by far, but are also the slowest for travel. They are designed specifically to have high accessibility and to connect to collector and arterial roads, and are typically not used for through traffic. The owner of this data is the NCDOT Transportation Planning Division.@@ (Wednesday, April 06, 2022)

The Traffic Segment Event file contains Annual Average Daily Traffic (AADT) and Vehicle Class (VC) estimates. This resource represents the approved annual submission to the FHWA, Highway Performance Monitoring System (HPMS) reporting for calendar year 2021. We report AADT on all highways functionally classified (FC) above Local. A full coverage is provided for routes where AADT segmentation is based on network configuration, travel patterns, and land use. Where divided highways occur, the AADT total for both directions is referenced on the inventory direction. Data is provided for ramps also. The ramp data does not cover all ramp segments, but all major traffic flows at interchanges are reported. Some maintained traffic segments require multiple records due to route ID changes at the county boundary in the linear referencing system (LRS). Traffic statistics for these segments are the same on each side of the county boundary but are maintained in this format to preserve the different location referencing data. Over 31,000 reference records (labeled “MAINT” in the SOURCE field) are required to provide event data for all maintained AADT segments. Supplemental AADT are provided on the routes that are Functionally Classified LOCAL. These roadways are not reported in the maintenance table described above for HPMS reporting. A reference is generated through a spatial join between the monitoring station point and the LRS Milepoint upon which it falls. The extent of highway this AADT represents has not been determined. This process captures the AADT for Local routes into the published table without requiring a comprehensive maintenance process. The AADT on Local routes may extend beyond the arc used to report it. The user must exercise their judgment in determining the extent of highway for an AADT in this case. There are over 16,000 records that are supplemental using this method, one record for each station captured. Vehicle Class data is provided for those segments where vehicle class data was collected. Truck volume data is collected at stations and the volumes are annualized. Annualized truck percentages for Single Unit (SU) and Multi Unit (MU) trucks are generated from this data. These truck percentages are applied to the 2021 AADT estimates to generate 2021 truck volume estimates. The truck percentage and volume estimates are provided in the shapefile. The VC coverage includes the National Highway System (NHS) and the NC Truck Network. VC data is not collected on routes not part of these systems and truck statistics are not provided on these segments. The referencing provided is based on the 2022 Quarter 1 publication of the NCDOT Linear Referencing System (LRS) maintained by the NCDIT GIS Unit. This is the official 2021 data set reported for HPMS routes, is the basis for the highway mileage reports, and is used to estimate vehicle miles of travel (VMT) for 2021. Differences in the Milepoints and references may be found when using other quarterly publications with this data set.

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 data set maps the locations of crashes involving bicyclists 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).

Data available for use in making maps and products related to Hurricane Florence.Esri is supporting organizations that are responding to hurricane/cyclone disasters with software, data, imagery, project services, and technical support. If you are in need of software or support, complete the Request Assistance form. All requests should be justified in the message section of the form and are subject to approval.

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.

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

Bike and Pedestrian crash data for Chatham, Durham, and Orange County. The data collected is from January 2007 to December 2014 and was obtained from the NCDOT Traffic Engineering Accidental Analysis System (TEAAS).

Bike and Pedestrian crash data for Chatham, Durham, and Orange County. The data collected is from January 2007 to December 2014 and was obtained from the NCDOT Traffic Engineering Accidental Analysis System (TEAAS).