Exchange Requirement: Pedestrian Ramps
Name
Pedestrian Ramps
Identifier
er_pedestrian-ramps
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 pedestrian ramp information including identification, spatial location (alignment-based and coordinate-based), slope characteristics, width, surface treatment, and ADA compliance parameters necessary for accessible design.
General Description
Pedestrian ramps provide accessible transitions between different elevation levels, primarily at curb interfaces with crosswalks and pedestrian facilities. This exchange requirement captures both the geometric definition and the ADA compliance properties necessary for design coordination, accessibility verification, and construction documentation. The information model supports referencing pedestrian ramps to highway alignments using stationing and offset data, as well as absolute positioning using state plane coordinates, GPS coordinates, and LRS data. Compliance with ADA standards for slope, cross-slope, landing areas, and detectable warnings is critical.
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
- Pedestrian Ramp Features
- Joint
- Pedestrian Ramp Layout
- Reinforcement
- Pay Item Information
Information Requirements
Preconditions
Before exchanging pedestrian ramp information, the following information must be available: Alignment and corridor geometry must be established (see Exchange Requirement: Horizontal Alignment, Exchange Requirement: Pedestrian Travelway). Project coordinate system must be defined. Curb and gutter locations must be defined (see Exchange Requirement: Curb and Gutter). ADA design criteria including maximum slopes and landing 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 Pedestrian Ramps element for database management, field verification, and asset tracking.
Concept: Assign Unique Identifiers
- Purpose: Establish unique identification for each Pedestrian Ramps 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 Pedestrian Ramps location to the project alignment and corridor system using stationing and offset measurements.
Concept: Reference to Alignment System
- Purpose: Establish the relationship between Pedestrian Ramps 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 Pedestrian Ramps 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 Pedestrian Ramps 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: Pedestrian Ramp Features
- Purpose: Define pedestrian ramp slope, width, surface treatment, landing dimensions, and ADA compliance parameters for accessible design.
Concept: Pedestrian Ramp ADA Compliance
- Purpose: Specify ramp geometry and features to ensure compliance with ADA accessibility standards.
Provide a table with the set of information requirements for each concept. Extend the table as needed.
| Idea | Explanation |
|---|---|
| Ramp Type | The categorization based on the design and function of the inclines, such as perpendicular, parallel, and blended transitions. (Type: STRING, Cardinality: R) |
| Detectable Warning Strip | A standardized surface feature built in or applied to pedestrian circulation paths and other pedestrian facilities to warn of hazards. (Type: BOOLEAN, Cardinality: R) |
| Landing | An area at the top or bottom of a ramp with cross slopes that adhere to current ADA standards, situated outside the travel way. (Type: BOOLEAN, Cardinality: R) |
Part: Joint
- Purpose: Describe the purpose of the Joint part
Concept: Joint Information
- Purpose: Describe the purpose of capturing Joint information
Provide a table with the set of information requirements for each concept. Extend the table as needed.
| Idea | Explanation |
|---|---|
| Joint Type | The classification of joints formed where two sections of pavement or structural material meet, based on their shape, size, and functional purpose. Common types include contraction joints, expansion joints, and construction joints, which help control cracking and accommodate movement. (Type: STRING, Cardinality: O) |
| Maximum Joint Interval | The greatest permissible spacing between consecutive pavement joints, as specified by design standards, to control cracking and accommodate material movement. (Type: REAL, Units: Feet, Cardinality: O) |
Part: Pedestrian Ramp Layout
- Purpose: Describe the purpose of the Pedestrian Ramp Layout part
Concept: Pedestrian Ramp Layout Information
- Purpose: Describe the purpose of capturing Pedestrian Ramp Layout information
Provide a table with the set of information requirements for each concept. Extend the table as needed.
| Idea | Explanation |
|---|---|
| Length of Ramp | The total distance from the beginning to the end of the inclined surface. (Type: REAL, Units: Feet, Cardinality: R) |
| Opening Width | The horizontal measurement of the object along the perpendicular face. (Type: REAL, Units: Inches, Cardinality: R) |
| Detectable Strip Length | The perpendicular measurement of the textured panel along the path of travel. (Type: REAL, Units: Inches, Cardinality: O) |
| Landing Length | The perpendicular measurement of the flat section at the top or bottom of a ramp. (Type: REAL, Units: Inches, Cardinality: O) |
| Landing Width | The horizontal measurement of the flat section at the top or bottom of a ramp. (Type: REAL, Units: Inches, Cardinality: O) |
| Edge of Pavement Elevations at Opening | The vertical measurement of the roadway surface at the beginning of the ramp. (Type: REAL, Units: Feet, Cardinality: R) |
| Elevations at Tiein Points | The vertical measurement of the sidewalk surface at the joint of the proposed ramp. (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) |
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 Pedestrian Ramps 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) |