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

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

This dataset provides information about 2008 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 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

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

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

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

Reason for SelectionThis indicator captures the recreational value and opportunities to connect with nature provided by greenways and trails. Greenways and trails provide many well-established social and economic benefits ranging from improving human health, reducing traffic congestion and air and noise pollution, increasing property values, and generating new jobs and business revenue (ITRE 2018). The locations of greenways and trails are regularly updated through the open-source database OpenStreetMap, while data on condition are regularly updated through the National Land Cover Database (NLCD).Input DataBase Blueprint 2022 extentOpenStreetMap data “roads” layer, accessed 2-27-2023 A line from this dataset is considered a potential greenway/trail if the value in the “fclass” attribute is either bridleway, cycleway, footway, or path. OpenStreetMap® is open data, licensed under the Open Data Commons Open Database License (ODbL) by the OpenStreetMap Foundation (OSMF). Additional credit to OSM contributors. Read more on the OSM copyright page.2019 National Land Cover Database (NLCD): Percent developed imperviousnessSoutheast Blueprint 2023 extentMapping StepsThe greenways and trails indicator score reflects both the natural condition and connected length of the greenway/trail. Note: For more details on the mapping steps, code used to create this layer is available in the Southeast Blueprint Data Download under > 6_Code.Natural conditionNatural condition is based on the amount of impervious surface surrounding the greenway/trail. Since perceptions of a greenway’s “naturalness” are influenced both by the immediate surroundings adjacent to the path, and the greater viewshed, natural condition is calculated by averaging two measurements: local impervious and nearby impervious. Local impervious is defined as the percent impervious surface of the 30 m pixel that intersects the trail. Nearby impervious is defined as the average impervious surface within a 300 m radius circle surrounding the path (note: along a 300 m stretch of trail, we only count the impervious surface within a 45 m buffer on either side of the trail, since pixels nearer the trail have a bigger impact on the greenway/trail experience). The natural classes are defined as follows:3 = Mostly natural: average of local and nearby impervious is ≤1%2 = Partly natural: average of local and nearby impervious is >1 and <10%1 = Developed: average of local and nearby impervious is ≥10%Connected lengthThe connected length of the path is calculated using the entire extent of the potential greenways/trails dataset. A trail is considered connected to another trail if it is within 2 m of the other trail. Length thresholds are defined by typical lengths of three common recreational greenway activities: walking, running, and biking. The 40 km threshold for biking is based on the standard triathlon biking segment of 40 km (~25 mi). Because a 5K is the most common road race distance, the running threshold is set at 5 km (~3.1 mi) (Running USA 2017). The 1.9 km (1.2 mi) walking threshold is based on the average walking trip on a summer day (U.S. DOT 2002). Using the statistics software R, download the OpenStreetMap data for the continental Southeast area. Select all lines from the OpenStreetMap data that have a highway tag of either footway, cycleway, bridleway, or path. These are all considered potential trails. Removed all lines marked as private.Identify lines from the potential trails that are tagged as sidewalks. Assign them a value of 1 in the indicator.Final scoresIf the potential greenway/trail was tagged as a sidewalk in the “other tags” field, it is given a value of 1 to separate sidewalks from what most people think of as a trail or greenway. If a pixel does not intersect a potential greenway/trail but overlaps with a value that is not NoData in the 2019 NLCD impervious surface layer, it is coded with a value of 0. Then clip to the spatial extent of Base Blueprint 2022. As a final step, clip to the spatial extent of Southeast Blueprint 2023.Final indicator valuesIndicator values are assigned as follows:7 = Mostly natural and connected for ≥40 km6 = Mostly natural and connected for 5 to <40 km or partly natural and connected for≥40 km5 = Mostly natural and connected for 1.9 to <5 km, partly natural and connected for 5 to <40 km, or developed and connected for ≥40 km4 = Mostly natural and connected for <1.9 km, partly natural and connected for 1.9 to <5 km, or developed and connected for 5 to <40 km3 = Partly natural and connected for <1.9 km or developed and connected for 1.9 to <5 km2 = Developed and connected for <1.9 km1 = Sidewalk0 = Not identified as trail, sidewalk, or other pathKnown IssuesThis indicator sometimes misclassifies sidewalks as greenways and trails because they are not tagged as a sidewalk in the OpenStreetMap data. This indicator occasionally misclassifies driveways as “sidewalks and other paths” in places where they are not correctly tagged as private in OpenStreetMap. These typically appear as isolated pixels receiving a score of 1 on the indicator. OpenStreetMap does not provide a complete inventory of greenways and trails in the Southeast. Paths that are missing from the source data will be underprioritized in this indicator. For example, some trails are missing within National Wildlife Refuges.This indicator includes trails and sidewalks from OpenStreetMap, which is a crowdsourced dataset. While members of the OpenStreetMap community often verify map features to check for accuracy and completeness, there is the potential for spatial errors (e.g., misrepresenting the path of a greenway) or incorrect tags (e.g., mislabeling a path as a footway that is actually a road for vehicles). However, using a crowdsourced dataset gives on-the-ground experts, Blueprint users, and community members the power to fix errors and add new greenways and trails to improve the accuracy and coverage of this indicator in the future. This indicator sometimes underestimates greenway length when connections route under bridges or along abandoned dirt roads. Some of these issues have been fixed through active testing and improvement, but some likely remain.When calculating nearby impervious for one greenway, if there’s another greenway within 300 m, impervious surface from the different but overlapping greenway buffer area is also used to compute natural condition. This is an unintended issue with the analysis methods. Investigation into potential fixes is ongoing.The indicator doesn’t currently include areas where future greenways are planned.Disclaimer: Comparing with Older Indicator Versions There are numerous problems with using Southeast Blueprint indicators for change analysis. Please consult Blueprint staff if you would like to do this (email hilary_morris@fws.gov).Literature CitedAmerican Planning Association. 2018. Recommendations for Future Enhancements to the Blueprint. [https://secassoutheast.org/pdf/Recommendations-for-Future-Enhancements-to-the-Blueprint-FINAL.pdf]. Institute for Transportation Research and Education (ITRE) & Alta Planning and Design. February 2018. Evaluating the Economic Impact of Shared Use Paths in North Carolina: 2015-2017 Final Report. [https://itre.ncsu.edu/wp-content/uploads/2018/03/NCDOT-2015-44_SUP-Project_Final-Report_optimized.pdf]. OpenStreetMap. Highways. Data extracted through Geofabrik downloads. Accessed February 23, 2022. [https://wiki.openstreetmap.org/wiki/Highways]. Running USA. 23 March 2017. U.S. Road Race Trends. Road race finisher total experiences slight year-over-year decline in 2016. [https://web.archive.org/web/20170404232619/https://www.runningusa.org/2017-us-road-race-trends]. U.S. Geological Survey (USGS). Published June 2021. National Land Cover Database (NLCD) 2019 Land Cover Conterminous United States. Sioux Falls, SD. [https://doi.org/10.5066/P9KZCM54]. U.S. Department of Transportation. National Highway Traffic Safety Administration and the Bureau of Transportation Statistics. 2002. National Survey of Pedestrian & Bicyclist Attitudes and Behaviors: Highlights Report. [https://www.bts.gov/sites/bts.dot.gov/files/docs/browse-statistical-products-and-data/bts-publications/archive/203331/entire-1.pdf]. Yang, Limin, Jin, Suming, Danielson, Patrick, Homer, Collin G., Gass, L., Bender, S.M., Case, Adam, Costello, C., Dewitz, Jon A., Fry, Joyce A., Funk, M., Granneman, Brian J., Liknes, G.C., Rigge, Matthew B., Xian, George. 2018. A new generation of the United States National Land Cover Database—Requirements, research priorities, design, and implementation strategies: ISPRS Journal of Photogrammetry and Remote Sensing, v. 146, p. 108–123. [https://doi.org/10.1016/j.isprsjprs.2018.09.006].

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