Layer: Interchanges

View In: Map Viewer

Name: Interchanges_v2

Display Field: LogicalName

Type: Feature Layer

Geometry Type: esriGeometryPolygon

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

Copyright Text: North Carolina Department of Transportation, Transportation Safety Unit; NCDIT-Transportation, GIS Unit. Support and maintenance of the spatial database where this data resides is handled by the North Carolina Department of Transportation Traffic Safety Unit.

Min. Scale: 0

Max. Scale: 0

Default Visibility: true

Max Record Count: 2000

Supported query Formats: JSON, geoJSON, PBF

Use Standardized Queries: True

Extent:

Drawing Info:

{"renderer":{"type":"simple","symbol":{"type":"esriSFS","style":"esriSFSSolid","color":[191,217,242,255],"outline":null}},"scaleSymbols":true,"transparency":38,"labelingInfo":null}
HasZ: false

HasM: false

Has Attachments: false

Has Geometry Properties: true

HTML Popup Type: esriServerHTMLPopupTypeAsHTMLText

Object ID Field: OBJECTID

Unique ID Field:

Global ID Field:

Type ID Field:

Fields:

OBJECTID (type: esriFieldTypeOID, alias: OBJECTID, SQL Type: sqlTypeOther, length: 0, nullable: false, editable: false)
InterchangeID (type: esriFieldTypeString, alias: InterchangeID, SQL Type: sqlTypeOther, length: 20, nullable: true, editable: true)
LogicalName (type: esriFieldTypeString, alias: LogicalName, SQL Type: sqlTypeOther, length: 150, nullable: true, editable: true)
InterchangeType (type: esriFieldTypeString, alias: InterchangeType, SQL Type: sqlTypeOther, length: 100, nullable: true, editable: true, Coded Values: [Diamond: Diamond], [Partial cloverleaf: Partial cloverleaf], [Full cloverleaf: Full cloverleaf], ... 15 more ...)
County (type: esriFieldTypeString, alias: County, SQL Type: sqlTypeOther, length: 30, nullable: true, editable: true)
MunicipalBoundary (type: esriFieldTypeString, alias: MunicipalBoundary, SQL Type: sqlTypeOther, length: 3, nullable: true, editable: true)
SmoothUrbanBoundary (type: esriFieldTypeString, alias: SmoothUrbanBoundary, SQL Type: sqlTypeOther, length: 3, nullable: true, editable: true)
ManualGeom (type: esriFieldTypeString, alias: ManualGeom, SQL Type: sqlTypeOther, length: 3, nullable: true, editable: true)
LastEdited (type: esriFieldTypeString, alias: LastEdited, SQL Type: sqlTypeOther, length: 50, nullable: true, editable: true)
EditedBy (type: esriFieldTypeString, alias: EditedBy, SQL Type: sqlTypeOther, length: 50, nullable: true, editable: true)
Notes (type: esriFieldTypeString, alias: Notes, SQL Type: sqlTypeOther, length: 150, nullable: true, editable: true)
InterchangeSubtype (type: esriFieldTypeString, alias: InterchangeSubtype, SQL Type: sqlTypeOther, length: 100, nullable: true, editable: true)
SapCountyCode (type: esriFieldTypeInteger, alias: SapCountyCode, SQL Type: sqlTypeOther, nullable: true, editable: true)
Shape__Area (type: esriFieldTypeDouble, alias: Shape__Area, SQL Type: sqlTypeDouble, nullable: true, editable: false)
Shape__Length (type: esriFieldTypeDouble, alias: Shape__Length, SQL Type: sqlTypeDouble, nullable: true, editable: false)

Templates:

Is Data Versioned: false

Has Contingent Values: false

Supports Rollback On Failure Parameter: true

Last Edit Date: 1/19/2026 3:38:30 PM

Schema Last Edit Date: 1/19/2026 3:38:30 PM

Data Last Edit Date: 1/19/2026 3:12:58 PM

Supported Operations: Query Query Pivot Query Top Features Query Analytic Query Bins Generate Renderer Validate SQL Get Estimates ConvertFormat

Layer: Interchanges_v2 (ID:46)