{"id" : "55ffeceadf72467bbe1ebcb4f03d52a0", 
  "name" : "Interchanges_v2", 
  "owner" : "TRAFFICSAFETY.NCDOT.GOV", 
  "guid" : "", 
  "title" : "NC Traffic Safety Interchange Inventory v2 (2026)", 
  "type" : "Feature Service", 
  "typeKeywords" : [
    "ArcGIS Server", 
    "Data", 
    "Feature Access", 
    "Feature Service", 
    "Metadata", 
    "Service", 
    "Singlelayer", 
    "Hosted Service"
  ], 
  "description" : "\u003cdiv style='text-align:Left;'\u003e\u003cdiv\u003e\u003cdiv\u003e\u003cp style='margin:0;'\u003e\u003cspan\u003eThe NC Traffic Safety Interchange Inventory dataset is a statewide polygon GIS data layer where each polygon represents the area containing the interchange facility. For this dataset, interchanges were defined as a grade-separated junction of two or more roads where at least one road is fully access controlled and movements between roads are accomplished through straight and loop ramps. The polygon for each interchange encompasses the broad area of roadway where traffic interactions are reasonably related to the interchange, including all ramps, ramp intersections with cross streets, merging and diverging areas, acceleration and deceleration lanes, and portions of the mainline freeway that are within the general boundaries of the interchange. Each interchange was classified into a general design category, such as diamond or partial cloverleaf.\u003c/span\u003e\u003c/p\u003e\u003cp style='margin:0;'\u003e \u003c/p\u003e\u003cp style='margin:0;'\u003e\u003cspan\u003eThis interchange inventory includes all interchanges in North Carolina, regardless of road ownership. This interchange inventory was developed to be used primarily in Traffic Safety analysis, though other users within NCDOT as well as external users may find this dataset useful. However, all users should be aware that this dataset was constructed to be suitable for the goals of planning level crash analysis and safety screening. As such, the level of detail and accuracy may not be appropriate for more detailed analysis. For example, the borders of each interchange polygon were drawn in a manner that would ensure that a safety analysis would identify geolocated crashes within the boundary that may be related to the interchange. Further detailed safety analysis and examination of crash reports would follow this high-level identification. To allow for inaccuracies in crash geolocation or data errors, the boundaries of the interchange polygons typically encompass an area much wider than the actual paved roadway. Since the boundaries are only intended to be used in selecting crashes, the edges are roughly drawn and are not intended to convey any detailed information about the environmental, economic, auditory, or other effects of the interchange. The interchange polygons are not intended to indicate anything about the data reporting requirements of the Highway Performance Monitoring System. At locations where interchange ramps intersected with surface streets, the boundaries were drawn to encompass approximately 250 feet around the ramp intersection. This distance was used as a general parameter of an “intersection influence” area for crashes, though a detailed analysis would be needed to determine which crashes would actually be logically linked to the ramp intersection.\u003c/span\u003e\u003c/p\u003e\u003cp style='margin:0;'\u003e \u003c/p\u003e\u003cp\u003e\u003cspan\u003eBelow is the list and description of the attribute fields provided in the interchange inventory.\u003c/span\u003e\u003c/p\u003e\u003cul\u003e\u003cli\u003e\u003cspan\u003eInterchangeID.    Unique alphanumeric identifier for each interchange polygon.    Sequentially numbered in the format of: “TSUINTCXXXXX”\u003c/span\u003e\u003c/li\u003e\u003cli\u003e\u003cspan\u003eLogicalName.    Descriptive name of the interchange (e.g., I-277 at US 74/NC 27/Independence Ave | Exit 2B).    Combination of the routes that converge at the interchange, in the format of: [main freeway name] at [route number] / [local name of street] | Exit [exit number]\u003c/span\u003e\u003c/li\u003e\u003cli\u003e\u003cspan\u003eInterchangeType.    General category of interchange design type. \u003c/span\u003e\u003c/li\u003e\u003cli\u003e\u003cspan\u003eCounty.    County location of intersection. If an interchange crosses a county boundary, both counties are included.    County name\u003c/span\u003e\u003c/li\u003e\u003cli\u003e\u003cspan\u003eMunicipalBoundary.    Indicates if Interchange polygon intersects with a municipal boundary polygon feature.    Yes, No\u003c/span\u003e\u003c/li\u003e\u003cli\u003e\u003cspan\u003eSmoothUrbanBoundary.    Indicates if Interchange polygon intersects with a Smoothed Urban Boundaries polygon feature    Yes, No\u003c/span\u003e\u003c/li\u003e\u003cli\u003e\u003cspan\u003eManualGeom.    Indicates if the interchange polygon was modified manually following the initial feature creation by the automated process.    Yes, No\u003c/span\u003e\u003c/li\u003e\u003cli\u003e\u003cspan\u003eLastEdited.    Date of last edit to feature    Date\u003c/span\u003e\u003c/li\u003e\u003cli\u003e\u003cspan\u003eEditedBy.    User who made the last edit to feature    User name\u003c/span\u003e\u003c/li\u003e\u003cli\u003e\u003cspan\u003eNotes.    Descriptive notes regarding changes to the feature    Descriptive text\u003c/span\u003e\u003c/li\u003e\u003cli\u003e\u003cspan\u003eInterchangeSubType.    Additional categorization for certain interchange types    Descriptive text\u003c/span\u003e\u003c/li\u003e\u003cli\u003e\u003cspan\u003eSapCountyCode.    County number    Numeric\u003c/span\u003e\u003cbr /\u003e \u003c/li\u003e\u003c/ul\u003e\u003cp\u003ePlease contact Daniel Carter, NCDOT Traffic Safety Unit at \u003ca href='mailto:dlcarter4@ncdot.gov' rel='nofollow ugc'\u003edlcarter4@ncdot.gov\u003c/a\u003e with any questions.\u003c/p\u003e\u003c/div\u003e\u003c/div\u003e\u003c/div\u003e", 
  "tags" : [
    "Polygon", 
    "North Carolina", 
    "NCDOT", 
    "Location", 
    "Interchange", 
    "Traffic Safety Unit", 
    "Roads", 
    "Highways", 
    "Transportation", 
    "Safety", 
    "Screening", 
    "Analysis"
  ], 
  "snippet" : "Inventory of interchanges in North Carolina, developed for traffic safety analysis. This dataset is version 2, developed and published in January 2026.", 
  "thumbnail" : "thumbnail/thumbnail.JPEG", 
  "extent" : [-83.539351, 33.892426, 
    -76.291615, 36.546218
  ], "categorites" : null, 
  "spatialReference" : "102719", 
  "url" : "https://services.arcgis.com/NuWFvHYDMVmmxMeM/arcgis/rest/services/Interchanges_v2/FeatureServer", 
  "culture" : "en-us", 
  "licenseInfo" : "\u003cDIV STYLE=\"text-align:Left;\"\u003e\u003cDIV\u003e\u003cDIV\u003e\u003cDIV STYLE=\"font-size:12pt\"\u003e\u003cP STYLE=\"margin:0 0 0 0;\"\u003e\u003cSPAN\u003eThis interchange inventory was developed to be used primarily in Traffic Safety analysis, though other users within NCDOT as well as external users may find this dataset useful. However, all users should be aware that this dataset was constructed to be suitable for the goals of planning level crash analysis and safety screening. As such, the level of detail and accuracy may not be appropriate for more detailed analysis. For example, the borders of each interchange polygon were drawn in a manner that would ensure that a safety analysis would identify crashes within the boundary that may be related to the interchange. Further detailed safety analysis and examination of crash reports would follow this high-level identification. To allow for inaccuracies in crash geolocation or data errors, the boundaries of the interchange polygons typically encompass an area much wider than the actual paved roadway. Since the boundaries are only intended to be used in selecting crashes, the edges are roughly drawn and are not intended to convey any detailed information about the environmental, economic, auditory, or other effects of the interchange. At locations where interchange ramps intersected with surface streets, the boundaries were drawn to encompass approximately 250 feet around the ramp intersection. This distance was used as a general parameter of an “intersection influence” area for crashes, though a detailed analysis would be needed to determine which crashes would actually be logically linked to the ramp intersection.\u003c/SPAN\u003e\u003c/P\u003e\u003cP STYLE=\"margin:0 0 0 0;\"\u003e\u003cSPAN /\u003e\u003c/P\u003e\u003cP STYLE=\"margin:0 0 0 0;\"\u003e\u003cSPAN\u003eThe 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 the data, and relative and positional accuracy of the data. This data cannot be construed to be a legal document. Primary sources from which this data was compiled must be consulted for verification of information contained in this data. This dataset does not replace locally verified data.\u003c/SPAN\u003e\u003c/P\u003e\u003c/DIV\u003e\u003c/DIV\u003e\u003c/DIV\u003e\u003c/DIV\u003e", 
  "accessInformation" : "North Carolina Department of Transportation, Transportation Safety Unit; NCDIT-Transportation, GIS Unit.\nContact Daniel Carter, dlcarter4@ncdot.gov with any questions.\nSupport and maintenance of the spatial database where this data resides is handled by the North Carolina Department of Transportation Traffic Safety Unit.", 
  "properties" : "", 
  "access" : "public", 
  "size" : 5349376
}