highway performance monitoring system … · [23 u.s.c. 101(a)] oto be open to public travel, a...
TRANSCRIPT
State of CaliforniaDepartment of Transportation
Division of Research, Innovation & System Information
HIGHWAY PERFORMANCEMONITORING SYSTEM
(HPMS)
1
What is HPMS?HPMS is a national highway information system that includes data on the extent, condition, performance, use, and operating characteristics of the Nation's highways.
Details can be found on this website:
https://www.fhwa.dot.gov/policyinformation/hpms.cfm
-------------------------------------------------------------------------------------------------------------------------------------------------------
Caltrans is required to:
1) Submit HPMS required dataset to FHWA by June 15th (April 15th ).2) Submit CA Public Road Mileage Certification by June 1st .
3
HPMS- What to submit?
1) Seventy (70) data items on all “Public Roads”Full Extent, Sample Panels or Summary.(HPMS Field Manual)
2) Linear Reference System (LRS) Network links HPMS sections data by Route ID.
4
Public Road
o A public road is any road or street owned and maintained by a public authority and open to public travel. [23 U.S.C. 101(a)]
o To be open to public travel, a road section must be available, except during scheduled periods, extreme weather, or emergency conditions, passable by four-wheel standard passenger cars, and open to the general public for use without restrictive gates, prohibitive signs, or regulation other than restrictions based on size, weight, or class of registration. [23 CFR 460.2(c)]
5
Full Extent: Data reported for the full extent of the system (e.g. section level for AADT). (Federal-Aid Eligible: Urban FC1-6; Rural FC1-5)
Sample Panel: Data reported for HPMS sample panel sections (see diagram on next slide).
Summary: Data reported in aggregate form (e.g. Total VMT on Rural FC 6 & 7).
6
7
SCAG 2County Urban Rural Urban Rural Urban Rural Urban Rural Urban Rural UrbanIMPERIAL 92.06 38.34 32.21 54.97 380.74 98.15 516.82 7.96 2,025.14 307.16 3,553.53 LOS ANGELES 0.24 10.00 1,719.32 55.25 2,699.58 525.76 2,345.81 290.92 9.50 369.45 12,949.17 20,975.02 ORANGE 0.35 627.91 685.29 4.10 375.75 21.62 4,426.60 6,141.60 RIVERSIDE 170.17 53.15 639.30 359.59 984.89 105.64 4.51 1,116.17 5,309.37 8,742.78 SAN BERNARDINO 0.30 4.20 277.62 20.12 908.89 866.18 932.60 86.45 10.14 2,130.95 5,311.23 10,548.69 VENTURA 0.64 0.06 143.20 2.00 233.06 101.03 239.54 38.38 0.07 256.21 1,665.61 2,679.80 Grand Total 1.53 106.32 2,976.56 162.72 5,221.10 2,237.40 4,976.74 1,038.21 32.17 5,919.54 29,969.14 52,641.43
Total= 15,714.54
Grand Total
Functional Class3 4 5 6 7
Full Extent for (non-state owned public roads) SCAG region is 15,714.54 miles [e.g. AADT]
County: NHSIMPERIAL 126.85 LOS ANGELES 1,713.10 ORANGE 594.10 RIVERSIDE 195.19 SAN BERNARDINO 300.85 VENTURA 146.83 Total NHS 3,076.91
[e.g. IRI, Surface Type, Rutting, Faulting, Cracking Percent]
All Road Network of Linear Referenced Data(ARNOLD)
In 2012, FHWA expanded the HPMS reporting requirement for State DOTs to submit all public roads in a Linear Referencing System (LRS).
This requirement is referred to as the “All Road Network of Linear Referenced Data (ARNOLD)”
Challenge: LRS match Certified Mileage
14
Support needed from local jurisdictions: o Provide us your street centerline shapefiles on
public roads with ownership information.
o Review & provide feedback on LRS Route Layer that Caltrans has/will provide for your agency.
All Road Network of Linear Referenced Data(ARNOLD)
Update on LRS “Clean Up” project:
http://www.dot.ca.gov/hq/tsip/hpms/hpmslibrary/hpmsdocs/All_Roads_Fact_Sheet_Jan_2018.pdf
15
HPMS current challenges?Update/maintain local data:To coordinate with 482 cities + 58 counties + 18 MPOs to maintain and update the network data, traffic data, pavement data and shapefiles.
Update/maintain current (Caltrans) All-Roads network:To continue clean up our All Roads LRS network to reflect current ownership, geometry, public roads and mileage.
16
17
What is MIRE?MAP-21 and FAST Act required States to have in place a safety data system under the Highway Safety Improvement Program (HSIP). The system must have the capabilities to perform analyses to support the strategic, data-driven, and performance-based goals in the Strategic Highway Safety Plan (SHSP) and the HSIP. These capabilities include: (1) types of roadways covered, (2) types of data included, (3) geolocation of safety data to a common highway basemap, (4) analysis and evaluation capabilities, and (5) the subset of Model Inventory of Roadway Elements (MIRE) to
be collected.
Subset = Fundamental Data Elements (FDE)To be collected within 10 years until 2026
18
The required FDEs are categorized by roadway functional classification and surface type:
Table 1: Non-Local Paved Roads (FC 1 - 6)
Table 2: Local Paved Roads (FC 7)
Table 3: Unpaved Roads (FC 1 – 7)
o ADT (or AADT)
o Peak Hour Volume (or K-Factor)
o D-Factor
o Truck Percentages
o Forecast Traffic21
TRAFFIC DATA SOUGHT
This form appears as it was since 2012There have been no changes
‘From’ and ‘To’ locations can be either landmark descriptions or lat/long information.
Traffic data is preferable in shapefile format.
22
TRAFFIC DATA SOUGHT
ADTFor two-way facilities, provide the bi-directional ADT.For one-way roadways, provide the directional ADT.
Section Identification Current Traffic Data Forecast Trafficeither of these either of these
Street Name From Location To Location ADT AADT
Month and Year of
Traffic Count (MM/YYYY)
Peak Hour Volume K Factor D Factor
Future ADT (or AADT)
Year of Future ADT (or AADT)
AADTAADT is the average daily traffic value that represents all days of the reporting year. AADT reflects application of day of week, seasonal, & axle correction factors. No other adjustment factors are necessary.
48-hour counts are preferred but shorter duration, such as 24-hour counts, are acceptable if these are the latest available. Lacking a traffic count, the AADT may be estimated from a traffic flow diagram, or by other means.
ADT or AADT may be entered. It is not necessary to supply both. 24
TRAFFIC DATA SOUGHT
Month and Year of Traffic Count: MM/YYYY
Enter 'est' if the ADT or AADT is estimated & not count based
Section Identification Current Traffic Data Forecast Trafficeither of these either of these
Street Name From Location To Location ADT AADT
Month and Year of
Traffic Count (MM/YYYY)
Peak Hour Volume K Factor D Factor
Future ADT (or AADT)
Year of Future ADT (or AADT)
25
TRAFFIC DATA SOUGHT
Peak Hour Volume = The 24-hour peak
Section Identification Current Traffic Data Forecast Trafficeither of these either of these
Street Name From Location To Location ADT AADT
Month and Year of
Traffic Count (MM/YYYY)
Peak Hour Volume K Factor D Factor
Future ADT (or AADT)
Year of Future ADT (or AADT)
K-FactorK30 if it is available. This is not common.
Code the K-Factor to nearest whole percent. Don’t use decimals.
Either Peak Hour Volume or K-Factor may be entered.It is not necessary to supply both of these.
26
TRAFFIC DATA SOUGHT
D-FactorThe percent of the peak hour volume flowing in the peak direction.
This is normally 50-75% (100% for one-way facilities).
It cannot be less than 50% since it is defined by the peak direction.
Section Identification Current Traffic Data Forecast Trafficeither of these either of these
Street Name From Location To Location ADT AADT
Month and Year of
Traffic Count (MM/YYYY)
Peak Hour Volume K Factor D Factor
Future ADT (or AADT)
Year of Future ADT (or AADT)
27
TRAFFIC DATA SOUGHT
Future ADT (or AADT)This is typically greater than the current traffic volume but not more than 4 times the current traffic volume. Please provide an explanation wherever if it is outside that range.
Year of Future ADT (or AADT)Ideally, this would be 20 years hence. It should not be less than 18 years out but whatever model year is being predicted that is closest to the 20 year target will suffice.
Section Identification Current Traffic Data Forecast Trafficeither of these either of these
Street Name From Location To Location ADT AADT
Month and Year of
Traffic Count (MM/YYYY)
Peak Hour Volume K Factor D Factor
Future ADT (or AADT)
Year of Future ADT (or AADT)
28
ANY QUESTIONS?
THIS IS WHAT IS NEEDED FOR TRAFFIC DATA
o ADT (or AADT)
o Peak Hour Volume (or K-Factor)
o D-Factor (Directional Split)
o Forecast Traffic
o Truck Percentages (if available)
29
Pavement Data Sought
IRI & pavement distress data (rutting, faulting, cracking) is often not available from cites & counties
Some locations, primarily principal arterials, have had this information collected under contract
31
Current Pavement DataSection Identification
STREET_NAME FROM TO Section Length (mi)
PCI SURFACE TYPE BASE_TYPE
Pavement Condition Index (PCI), a composite index used to assess maintenance & rehabilitation strategies. It should be reported wherever it has been measured according to this spec:ASTM D 6433 (2007): “Standard Practice for Roads and Parking Lots Pavement Condition Index Surveys”
Though the state does not report PCI directly to the FHWA, there is a conversion to Present Serviceability Rating (PSR).
32
Current Pavement DataSection Identification
STREET_NAME FROM TO Section Length (mi)
PCI SURFACE TYPE BASE_TYPE
Code Description
1 Unpaved 2 Bituminous 3 JPCP – Jointed Plain Concrete Pavement 4 JRCP – Jointed Reinforced Concrete Pavement 5 CRCP – Continuously Reinforced Concrete Pavement 6 Asphalt-Concrete (AC) Overlay over Existing AC Pavement 7 AC Overlay over Existing Jointed Concrete Pavement 8 AC (Bituminous Overlay over Existing CRCP) 9 Unbonded Jointed Concrete Overlay on PCC Pavement
10 Bonded PCC Overlay on PCC Pavement 11 Other (includes “whitetopping”)
SURFACE TYPE
33
Pavement History DataSection Identification Pavement History Data
STREET_NAME FROM TO Section Length
(mi)
YEAR_LAST_ IMPROVEMENT
YEAR_LAST_ CONSTRUCTION
LAST_ OVERLAY_ THICKNESS
(inches)
YEAR_LAST_ IMPROVEMENT:The year in which the roadway surface was last improved.
YEAR_LAST_ CONSTRUCTION:The year in which the roadway was constructed or reconstructed.
LAST_ OVERLAY_ THICKNESS:Thickness of the most recent pavement overlay to the nearest 0.5 inch.
34
Elements of Structural Section
THICKNESS_RIGID:Thickness of rigid pavement to the nearest 0.5 inch.
THICKNESS_FLEXIBLE:Thickness of flexible pavement to the nearest 0.5 inch.
BASE THICKNESS:The thickness of the base pavement to the nearest inch.
Section Identification Elements of Structural Section
STREET_NAME FROM TO Section Length (mi)
THICKNESS RIGID(inches)
THICKNESS FLEXIBLE(inches)
BASE THICKNESS(inches)
35