1. HIGHWAY PERFORMANCE MONITORING SYSTEM A state and national data system consisting primarily of: Roadway inventory Traffic data Pavement data The complete listing of data catalogs with all of the data items is available in the FHWA’s HPMS Field Manual: http://www.fhwa.dot.gov/policyinformation/hpms/fieldmanual/

3. TRAFFIC DATA SOUGHT This form appears as it was since 2012 There have been no changes ‘From’ and ‘To’ locations should run from W-E and S-N

4. TRAFFIC DATA SOUGHT It is rare to find traffic volumes broken out by the 13 FHWA vehicle classes. But provide this wherever it is available.

5. Passenger Vehicles Single-Unit Trucks Combination-Unit Trucks These are negligible

6. TRAFFIC DATA SOUGHT ADT For two-way facilities, provide the bi-directional ADT. For one-way roadways, provide the directional ADT. Section Identification Current Traffic Data Forecast Traffic either of these Street Name From LocationTo LocationADTAADT Month and Year of Traffic Count (MM/YYYY) Peak Hour VolumeK FactorD Factor Future ADT (or AADT) Year of Future ADT (or AADT) AADT AADT is the average daily traffic value that represents all days of the reporting year. AADT reflects application of day of week, seasonal, and 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.

7. TRAFFIC DATA SOUGHT Month and Year of Traffic Count: MM/YYYY Enter 'est' if the ADT or AADT is estimated and not count based Section Identification Current Traffic Data Forecast Traffic either of these Street Name From LocationTo LocationADTAADT Month and Year of Traffic Count (MM/YYYY) Peak Hour VolumeK FactorD Factor Future ADT (or AADT) Year of Future ADT (or AADT)

8. TRAFFIC DATA SOUGHT Peak Hour Volume = The 24-hour peak Section Identification Current Traffic Data Forecast Traffic either of these Street Name From LocationTo LocationADTAADT Month and Year of Traffic Count (MM/YYYY) Peak Hour VolumeK FactorD Factor Future ADT (or AADT) Year of Future ADT (or AADT) K-Factor K30 if it is available. This is not common. Code the K-Factor to the 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.

9. TRAFFIC DATA SOUGHT D-Factor The 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 Traffic either of these Street Name From LocationTo LocationADTAADT Month and Year of Traffic Count (MM/YYYY) Peak Hour VolumeK FactorD Factor Future ADT (or AADT) Year of Future ADT (or AADT)

10. 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 Traffic either of these Street Name From LocationTo LocationADTAADT Month and Year of Traffic Count (MM/YYYY) Peak Hour VolumeK FactorD Factor Future ADT (or AADT) Year of Future ADT (or AADT)

11. ARE THERE 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 you have them

12. State Highway Traffic Data Traffic and Vehicle Data Systems Unit http://www.dot.ca.gov/hq/traffops/saferesr/trafdata/index.htm Caltrans traffic counts are summarized annually into three reports: Traffic Volumes Annual Average Daily Truck Traffic Ramp Volumes These may be downloaded from this site (PDF or Excel Files).

13. Pavement Data Sought ‘From’ and ‘To’ locations should run from W-E and S-N

14. Pavement Data Sought IRI and pavement distress data (rutting, faulting, cracking) is often not available from the cites and the counties. Some locations, primarily the principal arterials, have had this information collected under contract.

15. Current Pavement Data Section Identification STREET_NAMEFROMTO Section Length (mi) PCI SURFACE TYPE BASE_TYPE Pavement Condition Index (PCI), a composite index used to assess maintenance and 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).

16. Current Pavement Data Section Identification STREET_NAMEFROMTO Section Length (mi) PCI SURFACE TYPEBASE_TYPE CodeDescription 1Unpaved 2Bituminous 3JPCP – Jointed Plain Concrete Pavement 4JRCP – Jointed Reinforced Concrete Pavement 5CRCP – Continuously Reinforced Concrete Pavement 6Asphalt-Concrete (AC) Overlay over Existing AC Pavement 7AC Overlay over Existing Jointed Concrete Pavement 8AC (Bituminous Overlay over Existing CRCP) 9Unbonded Jointed Concrete Overlay on PCC Pavement 10Bonded PCC Overlay on PCC Pavement 11Other (includes “ whitetopping ” ) SURFACE TYPE

17. Current Pavement Data Section Identification STREET_NAMEFROMTO Section Length (mi) PCI SURFACE TYPEBASE_TYPE BASE TYPE CodeDescriptionDefinition 1No BaseSurface layer is placed directly on subgrade without a base 2AggregateNon-stabilized granular, consisting of either crushed stone, gravel, recycled asphalt, or concrete 3Asphalt or Cement StabilizedAggregate base treated with either asphalt or Portland cement 5Hot Mix AC (Bituminous)Either a new hot-mix asphalt (HMA) layer placed as the base layer or the HMA surface of an old flexible pavement 6Lean ConcreteA Portland cement concrete mixture made with relatively low cement content (typically about 3 sacks/yd) 7Stabilized Open-graded Permeable Open-graded aggregate treated with either asphalt or Portland cement for stability 8Fractured PCCRubberized or crack-and-sealed PCC pavement

18. Pavement History Data Section Identification Pavement History Data STREET_NAMEFROMTO 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.

19. 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_NAMEFROMTO Section Length (mi) THICKNESS RIGID (inches) THICKNESS FLEXIBLE (inches) BASE THICKNESS (inches)

20. ANY QUESTIONS? THIS IS WHAT IS NEEDED FOR PAVEMENT DATA o PCI o SURFACE TYPE o BASE TYPE o PAVEMENT HISTORY DATA o ELEMENTS OF STRUCTURAL SECTION

21. Data files for traffic or pavement data should be sent via email to: hpms@scag.ca.gov

22. 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)”

23. What is LRS? Spatial referencing method, in which locations of features are described in terms of measurement along a linear element, from defined starting point. LRS is suitable for management data related to: Roads Railways Oil and gas transmission pipeline LRS = Route (Base Geometry) + Event Table

24. What is LRS? ROUTES Pavement Quality Legal Speed Limit Call box location GoodPoor 25 mph 35 mph 25 mph 50 mph Event Table (Attribution Information)

25. All Road Network of Linear Referenced Data (ARNOLD) Why All Roads? 1.Geospatial data for transportation is a key data theme within the National Spatial Data Infrastructure 2. All roads datasets are needed by the Federal government, the States, and many of the local agencies to support planning and management infrastructure. 3.Meeting the business needs of these functions: Certified Public Miles Fiscal Management Information System (FMIS) Fatal and Serious Injury Crashes Freight Performance Measures for Safety Performance Measures for Pavement

26. Caltrans’ Efforts in meeting the ARNOLD requirements: 2013 – SACOG Pilot Project Contract 2015 – Development of a Statewide LRS for All Local Roads Contract 2016 – Network Clean up and Validation Statewide LRS project is scheduled for completion in April 2016 All Road Network of Linear Referenced Data (ARNOLD)

27. Challenges we are facing: TIGERLINE: unclean, missing geometry, include non- public roads Discrepancy on public road maintained mileage (For instance: LA county – 2013 PRD: 21,858 miles Statewide LRS: 25,615 miles) All Road Network of Linear Referenced Data (ARNOLD)

28. Support needed from local jurisdiction: Provide us your street centerline shape file with public, non-public streets, and ownership information Review and provide feedback on LRS Route Layer that Caltrans will provide for your agency. All Road Network of Linear Referenced Data (ARNOLD)

29. All Road Network of Linear Referenced Data (ARNOLD) ARNOLD Reference Manual: http://www.fhwa.dot.gov/policyinformation/hpms/docum ents/arnold_reference_manual_2014.pdf Questions?

30. The maintained public road mileage Caltrans has spent much time and resources attempting to define the extent of the public road systems This has to do with miles and lane-miles of public roads So what is a public road?

31. A Public Road 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)] … must be … passable by four-wheel standard passenger cars, and open to the general public for use without restrictive gates, prohibitive signs, or regulation... [23 CFR 460.2(c)]

32. A Public Road A public road is any road or street: –owned by a public authority AND –maintained by a public authority AND –open to public travel

33. Open to public travel? The term “open to public travel” has been interpreted by the Federal Highway Administration (FHWA) to mean that the road is 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. Any road closed by gates, barriers, or regulations to year round use or restricted to use by agency personnel only should not be considered as meeting the definition of public road.

34. Public roads are functionally classified

35. The bifurcation of the functional classification codes was eliminated in 2010. There is no distinction between urban and rural.

36. This presentation is available at the HPMS web site: http://www.dot.ca.gov/hq/tsip/hpms/index.php and at the SCAG web site: http://www.scag.ca.gov/programs/Pages/HighwayMaintenance.aspx Past data submissions can be requested from SCAG staff: Email: hpms@scag.ca.govhpms@scag.ca.gov