Exchange Requirement: Delineator
Name
Delineator
Identifier
er_delineator
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 delineator information including identification, spatial location (alignment-based and coordinate-based), type classification, and installation properties necessary for roadway visibility and driver guidance.
General Description
Delineators are retroreflective devices mounted along roadway edges to enhance visibility and guide drivers, particularly during nighttime or adverse weather conditions. This exchange requirement captures both the geometric definition and the specification properties necessary for design coordination, inventory management, and maintenance planning. The information model supports referencing delineators to highway alignments using stationing and offset data, as well as absolute positioning using state plane coordinates, GPS coordinates, and LRS data.
Information Description
The information exchanged through this requirement includes the following parts:
- Identification
- Alignment Data Linear
- State Plane Coordinates Linear
- LRS Data Linear
- GPS Coordinates Linear
- Delineator Features
- Delineator Layout
- Pay Item Information
Information Requirements
Preconditions
Before exchanging delineator information, the following information must be available: Alignment and corridor geometry must be established (see Exchange Requirement: Horizontal Alignment, Exchange Requirement: Corridor). Project coordinate system must be defined. Applicable delineator standards (MUTCD) and spacing requirements 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 Delineator element for database management, field verification, and asset tracking.
Concept: Assign Unique Identifiers
- Purpose: Establish unique identification for each Delineator 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 Linear
- Purpose: Reference the Delineator location to the project alignment and corridor system using stationing and offset measurements.
Concept: Reference to Alignment System
- Purpose: Establish the relationship between Delineator elements and the roadway alignment/corridor framework.
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 Begin | Station of linear location - begin (Type: REAL, Units: Stationing, Cardinality: R) |
| Station Offset Begin | Offset of linear location - begin (Type: REAL, Units: Feet, Cardinality: R) |
| Station End | Station of linear location - end (Type: REAL, Units: Stationing, Cardinality: R) |
| Station Offset End | Offset of linear location - end (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 Linear
- Purpose: Provide absolute positioning using state plane coordinate system for survey control and GIS integration.
Concept: Absolute Coordinate Positioning
- Purpose: Define Delineator location using state plane coordinates independent of alignment references.
Provide a table with the set of information requirements for each concept. Extend the table as needed.
| Idea | Explanation |
|---|---|
| Northing Begin | The “Y” values of coordinates represented on a plane coordinate system - Begin (Linear) (Type: REAL, Units: Feet, Cardinality: R) |
| Easting Begin | The “X” values of coordinates represented on a plane coordinate system - Begin (Linear) (Type: REAL, Units: Feet, Cardinality: R) |
| Northing End | The “Y” values of coordinates represented on a plane coordinate system - End (Linear) (Type: REAL, Units: Feet, Cardinality: R) |
| Easting End | The “X” values of coordinates represented on a plane coordinate system - End (Linear) (Type: REAL, Units: Feet, Cardinality: R) |
Part: LRS Data Linear
- Purpose: Support integration with Linear Reference Systems (LRS) for asset management and maintenance operations.
Concept: LRS Integration
- Purpose: Enable referencing of Delineator assets within agency LRS databases.
Provide a table with the set of information requirements for each concept. Extend the table as needed.
| Idea | Explanation |
|---|---|
| Postmile Begin | Mile post of point location - begin (Type: REAL, Units: Mile, Cardinality: O) |
| LRS Offset Begin | Linear Reference System offset of point location - begin (Type: REAL, Units: Feet, Cardinality: O) |
| Postmile End | Mile post of point location - end (Type: REAL, Units: Mile, Cardinality: O) |
| LRS Offset End | Linear Reference System offset of point location - end (Type: REAL, Units: Feet, Cardinality: O) |
Part: GPS Coordinates Linear
- Purpose: Provide GPS-based location data for field verification and mobile data collection.
Concept: GPS Positioning
- Purpose: Support field crews with GPS coordinates for location verification.
Provide a table with the set of information requirements for each concept. Extend the table as needed.
| Idea | Explanation |
|---|---|
| Latitude Begin | Latitude of linear location - begin (Type: REAL, Cardinality: O) |
| Longitude Begin | Longitude of point location - begin (Type: REAL, Cardinality: O) |
| Latitude End | Latitude of linear location - end (Type: REAL, Cardinality: O) |
| Longitude End | Longitude of point location - end (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: Delineator Features
- Purpose: Define the type, color, retroreflectivity, and installation properties of delineators for roadway visibility and driver guidance.
Concept: Delineator Specification
- Purpose: Specify delineator characteristics to ensure compliance with MUTCD standards and visibility requirements.
Provide a table with the set of information requirements for each concept. Extend the table as needed.
| Idea | Explanation |
|---|---|
| Delineator Classification | Classification of Delineator including Flexible Post or Metal Post (Type: STRING, Cardinality: R) |
Part: Delineator Layout
- Purpose: Describe the purpose of the Delineator Layout part
Concept: Delineator Layout Information
- Purpose: Describe the purpose of capturing Delineator Layout information
Provide a table with the set of information requirements for each concept. Extend the table as needed.
| Idea | Explanation |
|---|---|
| Delineator Height | The minimum vertical distance from the base of the delineator post to its top, ensuring adequate visibility and compliance with roadway design standards. (Type: REAL, Units: Feet, Cardinality: R) |
| Delineator Post Spacing | Typical spacing of the delineator posts (Type: REAL, Units: Feet, 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 Delineator construction for quantity tracking and contractor payment.
Provide a table with the set of information requirements for each concept. Extend the table as needed.
No information requirements defined for this concept.