Exchange Requirement: Traffic Island
Name
Traffic Island
Identifier
er_traffic-island
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 traffic island information including identification, spatial location (alignment-based and coordinate-based), island type classification (raised or painted), dimensions, surface treatment, and functional properties necessary for traffic channelization and pedestrian refuge design.
General Description
Traffic islands provide traffic channelization, pedestrian refuge, and visual separation at intersections and along roadway corridors. This exchange requirement captures both the geometric definition and the classification properties necessary for design coordination, safety analysis, and construction documentation. The information model supports two primary island types: raised islands (constructed with curb and fill material) and painted islands (marked only with pavement markings). Raised islands may incorporate landscaping, lighting, or signage, while painted islands provide lower-cost channelization where physical separation is not required.
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
- Traffic Island Layout
- Reinforcement
- Pay Item Information
Information Requirements
Preconditions
Before exchanging traffic island 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. Intersection or corridor channelization design must be developed. Applicable geometric design standards for island dimensions and offsets must be identified. MUTCD requirements for pavement marking and signing must be referenced.
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 Traffic Island element for database management, field verification, and asset tracking.
Concept: Assign Unique Identifiers
- Purpose: Establish unique identification for each Traffic Island 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) |
| 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 Traffic Island location to the project alignment and corridor system using stationing and offset measurements.
Concept: Reference to Alignment System
- Purpose: Establish the relationship between Traffic Island 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) |
| 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 Traffic Island 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) |
| 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 Traffic Island 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) |
| 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) |
| 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: Traffic Island Layout
- Purpose: Describe the purpose of the Traffic Island Layout part
Concept: Traffic Island Layout Information
- Purpose: Describe the purpose of capturing Traffic Island Layout information
Provide a table with the set of information requirements for each concept. Extend the table as needed.
| Idea | Explanation |
|---|---|
| Total Traffic Island Width | The horizontal distance between the inside edges of travel of the opposing directions, measured perpendicular to the roadway centerline. This dimension includes any curb, gutter, or shoulder within the traffic island and is used to determine available space for landscaping, barriers, or turn lanes. (Type: REAL, Units: Feet, Cardinality: R) |
| Total Traffic Island Width | The horizontal distance between the inside edges of travel of the opposing directions, measured perpendicular to the roadway centerline. This dimension includes any curb, gutter, or shoulder within the traffic island and is used to determine available space for landscaping, barriers, or turn lanes. (Type: REAL, Units: Feet, Cardinality: R) |
Part: Reinforcement
- Purpose: Describe the purpose of the Reinforcement part
Concept: Reinforcement Information
- Purpose: Describe the purpose of capturing Reinforcement information
Provide a table with the set of information requirements for each concept. Extend the table as needed.
| Idea | Explanation |
|---|---|
| Reinforcement | The indication of whether an object includes reinforcement. (Type: BOOLEAN, Cardinality: O) |
| Reinforcement | The indication of whether an object includes reinforcement. (Type: BOOLEAN, Cardinality: O) |
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 Traffic Island 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) |
| 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) |