Facebook
TwitterWith 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.
Facebook
TwitterThe 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.
Facebook
TwitterTraffic analytics, rankings, and competitive metrics for ncdot.gov as of August 2025
Facebook
Twitter(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/
Facebook
TwitterThe 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.
Facebook
TwitterThe 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.
Facebook
TwitterThis 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
Facebook
TwitterThis 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).
Facebook
TwitterThis 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
Facebook
TwitterBike 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).
Not seeing a result you expected?
Learn how you can add new datasets to our index.
Facebook
TwitterWith 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.