Exchange Requirement: Intersection
Name
Intersection
Identifier
er_intersection
Change Log
| Date (yyyy-mm-dd) | Action | Author (email) |
|---|---|---|
| 2025-12-09 | Initial draft | AI Generated |
Project Stage
Select the applicable project stage(s); remove rows that do not apply.
| Code | Stage |
|---|---|
| 0 | Portfolio requirements |
| 1 | Conception of need |
| 2 | Outline feasibility |
| 3 | Substantive feasibility |
| 4 | Outline conceptual design |
| 5 | Full conceptual design |
| 6 | Coordinated design and procurement |
| 7 | Production information |
| 8 | Construction |
| 9 | Operation and maintenance |
| 10 | Disposal |
Overview
Provide a textual overview of the exchange requirement under the headings Scope, General Description and Information Description. Keep it non-technical and aimed at an executive audience.
Scope
The scope of this exchange requirement is to enable the exchange of intersection information including identification, point location data (alignment-based and coordinate-based), intersection type classification, control type, and geometric configuration necessary for traffic operations and safety analysis.
General Description
Intersections are critical junction points where two or more roadways meet, requiring coordinated geometric design and traffic control. This exchange requirement captures the location and classification properties necessary for design coordination, traffic signal placement, capacity analysis, and safety evaluation. The information model supports referencing intersections to highway alignments using stationing and offset data as point features, as well as absolute positioning using state plane coordinates, GPS coordinates, and LRS data. Intersection types include signalized, unsignalized, roundabouts, and interchanges.
Information Description
The information exchanged through this requirement includes the following parts:
- Identification
- Alignment Data Point
- State Plane Coordinates Point
- LRS Data Point
- GPS Coordination Point
- Intersection Layout
- Intersection Features
- Pay Item Information
Information Requirements
Preconditions
Before exchanging intersection information, the following information must be available: Alignment and corridor geometry for all intersecting roadways must be established (see Exchange Requirement: Horizontal Alignment, Exchange Requirement: Corridor). Project coordinate system must be defined. Traffic operational data and turning movement counts must be available. Applicable geometric design standards (AASHTO Green Book) and traffic control devices (MUTCD) must be identified.
Parts
A part is a set of information that achieves a specific purpose or function within this exchange requirement (for example: Select Object, Assign To Group, Associate Library Reference). An exchange requirement is expected to consist of many parts.
Repeat the following block for each part.
Part: Identification
- Purpose: Uniquely identify each Intersection element for database management, field verification, and asset tracking.
Concept: Assign Unique Identifiers
- Purpose: Establish unique identification for each Intersection instance to support data management and asset tracking.
Provide a table with the set of information requirements for each concept. Extend the table as needed.
| Idea | Explanation |
|---|---|
| Object ID | Unique ID assigned to each asset in database (Type: STRING, Cardinality: R) |
| Feature ID | Specific point, linear, and surface designation (Type: STRING, Cardinality: O) |
| Feature Description | Specific point, linear, and surface detailed description (Type: STRING, Cardinality: O) |
| Survey Feature Code | Short abbreviation surveyors use in the field to identify and describe physical features and data points encountered (Type: STRING, Cardinality: O) |
Part: Alignment Data Point
- Purpose: Reference the intersection location to the project alignment using stationing and offset measurements as a point feature.
Concept: Point Reference to Alignment
- Purpose: Establish the relationship between intersection point location and the roadway alignment for traffic control design.
Provide a table with the set of information requirements for each concept. Extend the table as needed.
| Idea | Explanation |
|---|---|
| Alignment ID Reference | Alignment ID that is referenced for element layout (Type: STRING, Cardinality: R) |
| Corridor ID Reference | Corridor ID that is referenced for element layout (Type: STRING, Cardinality: R) |
| Station | Station of point location (Type: REAL, Units: Stationing, Cardinality: R) |
| Station Offset | Offset of point location (Type: REAL, Units: Feet, Cardinality: R) |
| Reference Point Location | Placement of point for offset (i.e. gutterline for traffic barrier feature) (Type: STRING, Cardinality: R) |
Part: State Plane Coordinates Point
- Purpose: Provide absolute positioning of intersection location using state plane coordinate system as a point feature.
Concept: Point Coordinate Positioning
- Purpose: Define intersection location using state plane coordinates for GIS integration and signal design.
Provide a table with the set of information requirements for each concept. Extend the table as needed.
| Idea | Explanation |
|---|---|
| Northing | The “Y” values of coordinates represented on a plane coordinate system (Type: REAL, Units: Feet, Cardinality: R) |
| Easting | The “X” values of coordinates represented on a plane coordinate system. (Type: REAL, Units: Feet, Cardinality: R) |
Part: LRS Data Point
- Purpose: Support integration with Linear Reference Systems (LRS) for intersection safety analysis and traffic operations.
Concept: Point LRS Integration
- Purpose: Enable referencing of intersection locations within agency LRS databases as point features.
Provide a table with the set of information requirements for each concept. Extend the table as needed.
| Idea | Explanation |
|---|---|
| Postmile | Mile post of point location (Type: REAL, Units: Mile, Cardinality: O) |
| LRS Offset | Linear Reference System offset of point location (Type: REAL, Units: Feet, Cardinality: O) |
Part: GPS Coordination Point
- Purpose: Provide GPS-based location data for intersection as a point feature for field verification and signal installation.
Concept: Point GPS Positioning
- Purpose: Support field verification of intersection locations using GPS coordinates.
Provide a table with the set of information requirements for each concept. Extend the table as needed.
| Idea | Explanation |
|---|---|
| Latitude | Latitude of point location (Type: REAL, Cardinality: O) |
| Longitude | Longitude of point location (Type: REAL, Cardinality: O) |
| Control Points Benchmarks | Reference points with known coordinates and/or elevations, used to create a consistent horizontal and vertical datums for accurate coordination of highway right of way and private property boundaries and existing features for construction projects. (Type: STRING, Cardinality: O) |
| GPS Notes | Notes referring to GPS location data (Type: STRING, Cardinality: O) |
Part: Intersection Layout
- Purpose: Describe the purpose of the Intersection Layout part
Concept: Intersection Layout Information
- Purpose: Describe the purpose of capturing Intersection Layout information
Provide a table with the set of information requirements for each concept. Extend the table as needed.
| Idea | Explanation |
|---|---|
| Opening Width | The horizontal measurement of the object along the perpendicular face. (Type: REAL, Units: Feet, Cardinality: O) |
| Total Back Width | The horizontal measurement of the object along the perpendicular face on the foreside of the intersection. (Type: REAL, Units: Inches, Cardinality: O) |
| Overall Length from Edge of Pavement | The horizontal measurement of the intersection length from the edge of pavement to edge of pavement. (Type: REAL, Units: Feet, Cardinality: O) |
| Radius | A line segment extending from the center of a circle to the circumference. (Type: REAL, Units: Feet, Cardinality: O) |
| Opening Grade | An inclination angle line of the street to the horizontal plane at the beginning of a segment. (Type: REAL, Units: Unitless, Cardinality: O) |
| Back Grade | An inclination angle line of the street from the current point of inflection to the previous. (Type: REAL, Units: Unitless, Cardinality: O) |
| Grading Plan Included | A detailed proposal that outlines the proposed ground elevations, slopes, and dimensions. (Type: BOOLEAN, Cardinality: O) |
Part: Intersection Features
- Purpose: Define intersection type, control type, geometric configuration, and traffic operational properties for design and safety analysis.
Concept: Intersection Classification and Geometry
- Purpose: Specify intersection characteristics to support capacity analysis, signal design, and safety evaluation.
Provide a table with the set of information requirements for each concept. Extend the table as needed.
| Idea | Explanation |
|---|---|
| Median or Island | The indication of whether the object is intended to be included in the contract documents. (Type: BOOLEAN, Cardinality: R) |
| Curb and Gutter | The indication of whether the object is intended to be included in the contract documents. (Type: BOOLEAN, Cardinality: R) |
Part: Pay Item Information
- Purpose: Provide construction contract administration data for cost estimation and payment processing.
Concept: Contract Pay Items
- Purpose: Define pay items associated with Intersection construction for quantity tracking and contractor payment.
Provide a table with the set of information requirements for each concept. Extend the table as needed.
| Idea | Explanation |
|---|---|
| Pay Item Code | The code used to describe the pay item often associated with construction standards or specifications developed by an owner agency. (Type: STRING, Cardinality: R) |
| Pay Item Description | A description of the pay item code. (Type: STRING, Cardinality: R) |
| Pay Item Unit of Measure | The unit of measure associated with the pay item (LF, CY, LS, etc.). Use the unit abbreviation defined in the associated specification if one exists. (Type: STRING, Cardinality: R) |
| Pay Quantity | Pay Item quantity (Type: STRING, Cardinality: R) |
| Pay Item Note | A note used to further describe the pay item. (Type: STRING, Cardinality: O) |
| Specification URL | The world wide web address associated with the specification or specification section that provides additional information realted to the Pay Item. (Type: STRING, Cardinality: O) |