Appendix H_Roadside Features Inventory Guide.pdf

Appendix H:

Roadside Features Inventory Guide

H-1

1. FEATURE INVENTORY DATA SOURCES

Refer to the following documents for supporting information to describe the RIP features inventory:

• Manual on Uniform Traffic Control Devices (MUTCD) for Streets and Highways, 2009 edition with May 2012 revisions 1 and 2

• Model Inventory of Roadway Elements, (MIRE 2.0). FHWA Safety Program, July 2017

• Appendix I: Sign Inventory Guide

• Appendix J: Database Data Dictionary

2. INVENTORY FEATURES FROM VIDEO/IMAGES

The contractor shall identify and inventory the roadside features listed in Table H-2. The features shall be identified from video/images obtained by the data collection vehicle during the collection of pavement condition data. As a reminder, some sites/roads may be driven for condition more than once, but features would only be inventoried one time throughout NPS Cycle 7. The contractor shall classify each feature according to the attributes listed for each feature type in this Appendix (where applicable). Table H-1 lists the fundamental attributes that are always populated in the database to identify the feature type and location.

Table H-1: Fundamental Attributes of Features Inventory

DATABASE FIELD DESCRIPTION

CYCLE_COLLECTED Cycle of features inventory

INSP_DATE Date video collected

ASSET_TYPE Road or Parking

FEATURE_EVENT Type of Feature

EVENT_DESCRIPTION Description of Feature

FEATURE_GEOMETRY Linear or Point

EVENT_CODE MIRE, MUTCD, or other codes

BEG_MP Begin Milepost

END_MP End Milepost

BEG_LAT Begin Latitude Coordinate (decimal degrees)

BEG_LON Begin Longitude Coordinate (decimal degrees)

END_LAT End Latitude Coordinate (decimal degrees)

END_LON End Longitude Coordinate (decimal degrees)

SIDE Right, Left, N/A

Table H-2: Features to Inventory from Video

Feature Type Feature Geometry

MIRE 2.0

Reference

Description / Attributes Collected

Auxiliary Lane Linear #36, #37 Presence/Type

Bicycle Lanes/Markings

Linear #41, #42 Type, Side, width of bike lane (when bike line is on road)

Boundary Point NPS Park (or Federal Land) Boundary State Boundary EFLHD can provide Boundary GIS

Bridge Linear #109 Structure Number (provided by EFLHD)

Cattle Guard Point Type/Material of Grate

H-2

Feature Geometry

MIRE 2.0

Reference

Description / Attributes Collected

Construction Zone Linear Start/end of construction area – pavement distress ratings may still be attainable in construction settings, however, features inventories may be incomplete within the construction zone.

Crosswalk Point #147 Pedestrian Crossing, Marked/Unmarked

Culvert Point

EFLHD will advise if these will be collected on a per site basis.

Culverts would be marked by onsite staff with flags, paint, or other markers for viewing in video. Study feasibility of bringing past culvert location data into updated features inventory in Cycle 7.

Curb Linear #53, #54 Curb Material

Curb and Gutter Linear #53, #54 Curb and Gutter Material

Curve Superelevation

Point #197 If available

Drop Inlet Point Location

Fire Hydrant Point Location

Gate Point Gate Material, Gate Style

Guard/Guide Rail Linear Barrier Material, Barrier Type, Barrier Post Material Barrier Approach/End Type, Offset from Edge of Pavement.

Include Median Side.

Guard/Guide Wall Linear Barrier Material, Barrier Type, Offset from Edge of Pavement.

Include Median Side.

Intersected Route Point Road or Parking intersected including inventoried route numbering when available. ELFHD can provide historical intersection road logs from Cycle 6

Intersection Type Point #116, #134 Number of legs, traffic control, skew, turn lanes, # of thru lanes

Horizontal Curve Linear #195, #196 Degree or Radius, Length of Curve

Lane Deviation Linear Comment Reason for deviation (i.e. blocked lane, entrance station, etc.)

Lighting Point #102 Light or light poles

Low Water Crossing Linear Surface Type (pavement condition may not be required)

Left Shoulder Linear #48, #49, #50 Surface type (paved/unpaved), Width

Median Linear #55, 56 Presence, Width, Protected Barrier

Mile Marker Point #14 Text of Mile Number on Sign (keep separate from Sign Feature Type)

One-Way Linear #93 EFLHD can provide historical one-way locations

On-street Parking Presence/Type

Linear #100, #101 Parallel Parking, Marked/Unmarked

Overpass Point Name of route or structure intersected

Paved Ditch Linear Material/Surface Type

Pedestrian Beacons Point Type/Location

Pullout/Turnout/Pull Over

Linear Surface type. Used for unofficial parking not in the Parking Inventory

Railroad Crossing Point #118 Railroad Crossing ID Number (on MUTCD I-13 sign if available)

Retaining Wall Linear Type and Offset

Right Shoulder Linear #44, #45 Surface type (paved/unpaved), Width

Turn Lane Linear #135, #136, #141, #140, #142

Right Side/Left Side, type, number, length

Route Start/End Point Typically at MP 0 and end MP (may differ for routes running end-to-end)

Rumble Strip Linear #47, #51, #59, #107, Type (shoulder/edge, centerline, transverse)

H-3

Feature Geometry

MIRE 2.0

Reference

Description / Attributes Collected

#157

Sidewalk Linear #52 Presence, width, surface type, shared-use

Sign Point #79, #80

Sign Type, MUTCD code, Sign Text, facing direction. Use MUTCD and Appendix I for more guidance.

Speed Limit Linear #94 Indicated by signage in primary driving direction.

Speed Limit, Advisory Speed

Surface Type Change

Point Description of change (for example, “ASPHALT TO CONCRETE”, Bridge surface)

Traffic Light Point #78, #121, #122, #123

Signal type

Tunnel Linear Tunnel Structure Number (provided by EFLHD)

EFLHD can provide historical features inventories from previous cycles of collections.

These will have approximate locations of some features, however, may also be outdated.

The contractor shall obtain and record more accurate/updated locations using the latest video collected in order to create a complete inventory.

3. SCOPE OF FEATURE INVENTORY

Inventory all features, excluding the following:

• Temporary or construction-related roadway features.

• Roadway features not associated with the road being collected.

For example: a curb running along an adjacent or intersecting road that is visible in the video would be excluded from the inventory. Another example is a gate that does not cross the road being collected, but crosses an intersecting road, would be excluded from the inventory for that road. However, it may be included if the intersecting road is in the inventory for features collection.

• Features in parking areas adjacent to the road being collected are features of the parking area and must not be inventoried as features of the road. EFLHD will provide locations and GPS of official parking locations. However, features located in pullouts (pullouts are not official parking locations in the inventory) that are adjacent to the road being collected are features of the road and must be inventoried as features of the road.

4. FEATURE MILEPOST AND LATITUDE/LONGITUDE DETERMINATION

Features must be inventoried and reported in the proper milepost sequence in which they occur while traveling in the primary direction of the road collected (same direction as the pavement condition is collected). Features would be identified in the forward-facing and rear-facing cameras on the data collection vehicle.

All “co-located” features must have common milepost and latitude/longitude coordinate for their location. For example, two or more signs mounted on a common signpost.

H-4

Assign to all features the milepost and latitude/longitude coordinates of the primary-direction driving lane, perpendicular to the feature’s location. All mileposts assigned to features must be between the beginning milepost and the ending milepost of the route.

FEATURE GEOMETRY

• POINT features shall be given a single location (milepost and Lat./Long coordinate).

• LINEAR features shall be given two locations (milepost and Lat./Long coordinate), at the feature starting location and the feature ending location.

Refer to table H-3 for locational precision and accuracy

Table H-3: Feature Location Definition

LOCATING FEATURE ASSETS BY MILEPOST AND GPS

ROADWAY VIDEO

Data Element

Location Method

Reporting Precision

Accuracy Location Location Relative to Primary Lane

Milepost Video

Analysis 3 decimals

<= 0.001 mile (5.28 feet)

Milepost perpendicular to point feature;

Milepost perpendicular to linear feature begin point and end point

Left Side, Right Side, or N/A (e.g., N/A=Bridge, Park Boundary, etc.)

GPS

Video

Analysis

Lat/Lon, WGS 84, Decimal Degrees, 6 decimals <= 1 meter

GPS Coordinates of assigned milepost

Identify Asset Relative to Corresponding Milepost

NOTE: number of lanes, lane widths, road widths, shoulder widths aren’t included in

Table H-2 because they are likely already recorded in the pavement condition tables.

Please ensure this information is captured.

5. FEATURE EVENT (TYPE) DETAILS

After contract award EFLHD will work with Contractor to provide comprehensive information for all features, including a data dictionary and domain list for the management of feature attributes.

6. PHOTOGRAPHIC EXAMPLES

After contract award EFLHD will provide Contractor with a photograph guide document showing photographic examples of each feature type.