Description: BehaviorsActivity / RulesCalibrateRoute - Stay PutReverseRoute - Stay PutRetireRoute - SnapExtendRoute - Stay PutReassignRoute - SnapRealignRoute - Stay PutRealignOverlap - SnapCartoRealignRoute - Honor Route MeasureFrom CANSYS Metadata Master ReportHPMS - (HPMS) This item contains the HPMS sample ID (up to 4-digits in CANSYS) which should be unique for the whole road network within the state but it’s not. The 12-digit HPMS ID is unique through the state. The Sample_ID reported in HPMS is twelve digits (12-digit ID is computed in HPMS extract function consisting of county number, 4-digit sample number, and 4 zeros for state system: (UAB number, 4-digit sample number, and 4 zeros for NUSYS) must be unique for the whole state. The sample should be a homogeneous panel for the five data items: AADT number of through lanes, urban code, type of facility (one-way / two-way), and functional classification. Even though not required by HPMS we take divided / undivided change and county line as splitting agents for HPMS samples. The HPMS item also stores the HPMS peak parking data. There are other historic attributes (not currently used) that came over from mainframe.History:Before reassessment in 2010 the sample breaks were County Code, Urban Code, NAAQS Code (Kansas does not have), Functional System, NHS STRAHNET, Type of Facility, AADT Volume Group as defined in HPMS 2000, and Manual Number of Through Lanes. The main differences IS that after reassessment the volume groups changed and AADT count has become a splitting agent for samples. In mainframe HPMS inventory item stored other HPMS data items valid for the length of HPMS sample length (such as intersection parameters). In CANSYS the only additional data item that is maintained is peak parking in addition to sample ID.(HPMS) - Critical Parking -- IIT_CHR_ATTRIB30 If parking is allowed during peak hours this attribute is coded.0 - Not Applicable 1 - Parking allowed one side 2 - Parking allowed both sides 3 - No parking allowed or none available (HPMS) - HPMS Sample Id -- IIT_NUM_ATTRIB21 This item contains HPMS sample ID (up to 4 digit) which is unique for a given county route (for state system) or unique within urban boundary for NUSYS.HPMT - (HPMS Material Type Reference) HPMS material type reference this item is used as a reference for surface and base type when creating the HPPA item. This is a non-located item.(HPMT) - BASE TYPE -- IIT_NUM_ATTRIB17 Derived base type based on the material: 1 - No Base2 - Aggregate; 3 - Asphalt or Cement Stabilized with Granular subbase4 - Asphalt or Cement Stabilized with Granular subbase5 - Hot Mix AC (bituminous)6 - Lean Concrete7 - Stabilized Open-graded Permeable8 - Fractured PCC(HPMT) - FLEXIBLE RIGID FLAG -- IIT_NUM_ATTRIB18 Flexible rigid flag - identifies whether the material type is flexible or rigid, which controls the flow of how surface and base type are calculated. 1 - Flexible2 - Rigid(HPMT) - MATERIAL -- IIT_MATERIAL The material codes ***three pages of codes in PDF***(HPMT) - SURFACE TYPE -- IIT_NUM_ATTRIB16 0 - Invalid1 - Unpaved2 - Conventional Asphalt Concrete (Bituminous) 3 - Jointed Plain Concrete Pavement (JPCP) 4 - Jointed Reinforced Concrete Pavement (JRCP) 5 - Continuously Reinforced Concrete Pavement (CRCP) 6 - AC (Bituminous) Overlay over Existing AC (Bituminous) Pavement 7 - AC (Bituminous) Overlay over Existing Jointed Concrete Pavement 8 - AC (Bituminous) Overlay over Existing CRCP 9 - Unbonded Jointed Concrete Overlay on PCC Pavements 10 - Bonded PCC Overlay on PCC Pavement 11 - Other (includes whitetopping) HPPA - (HPMS Pavement Attributes) HPPA is a decode / calculation of data in LYRS. HPPA was created to be used in HPMS using the definition of surface type, base type etc. from HPMS. There are decodes of the HPPAS surface types for EPFS and PMS. See documentation in version control.History:With the HPMS reassessment 2010+ FHWA came up with a new set of surface pavement classifications. HPPA was created to code the new surface types. CANSYS decided to decode the existing material types into the required surface types.(HPPA) - HPMS_BASE_THICKNESS -- IIT_NUM_ATTRIB23 Sum thickness (LYRS - IIT_Length – Depth) of all layers below surface layer, regardless of base type -- the thickness of the base pavement. Base includes everything between subgrade and surface course. If there are several types of base report the total thickness of all base layers.(HPPA) - HPMS_BASE_TYPE -- IIT_NUM_ATTRIB22 Base is everything between sub-grade and surface course. If you have several types of base use the code that best describes the layer immediately below the surface layer.Code 1 - No BaseCode 2 - Aggregate Code 3 - Asphalt or Cement StabilizedCode 4 - Asphalt or Cement Stabilized with Granular subbaseCode 5 - Hot Mix AC (bituminous)Code 6 - Lean ConcreteCode 7 - Stabilized Open-graded PermeableCode 8 - Fractured PCC(HPPA) - HPMS_LAST_OVERLAY_THICKNESS -- IIT_NUM_ATTRIB19 Thickness (LYRS - IIT_Length – Depth) of surface layer (topmost nonzero layer) -- thickness of the most recent pavement overlay. An overlay is more than 0.5 inch. (HPPA) - HPMS_SURFACE_TYPE -- IIT_NUM_ATTRIB16 0 - Invalid1 - Unpaved2 - Conventional Asphalt Concrete (Bituminous) 3 - Jointed Plain Concrete Pavement (JPCP) 4 - Jointed Reinforced Concrete Pavement (JRCP) 5 - Continuously Reinforced Concrete Pavement (CRCP) 6 - AC (Bituminous) Overlay over Existing AC (Bituminous) Pavement 7 - AC (Bituminous) Overlay over Existing Jointed Concrete Pavement 8 - AC (Bituminous) Overlay over Existing CRCP 9 - Unbonded Jointed Concrete Overlay on PCC Pavements 10 - Bonded PCC Overlay on PCC Pavement 11 - Other (includes whitetopping) (HPPA) - HPMS_THICKNESS_FLEXIBLE -- IIT_NUM_ATTRIB21 HPMS_Thickness_Rigid – Sum Thickness (LYRS - IIT_Length – Depth) of all rigid layers (including surface layer) as defined by material type in HPMT. Thickness of rigid pavement. The thickness should reflect the last improvement on the section. When an improvement is made consider all new or redesigned base and pavement materials when determining the appropriate value. Reporting should be consistent with IRI inventory direction and lane. Definitions: refer to the table of codes in data item 49 (surface type) Posite pavements.(HPPA) - HPMS_YEAR_LAST_CONST -- IIT_NUM_ATTRIB18 Mjg (LYRS - IIT_Material – Material_Type) year (or if no MJG, then bottom layer) -- the year in which the roadway was constructed or reconstructed. Reconstruction is the replacement of the existing pavement structure with an equivalent or increased structure. Although recycled materials may be used in the new pavement structure reconstruction usually requires the complete removal and replacement of at least the old pavement surface and often also the base. (HPPA) - HPMS_YEAR_LAST_IMPROV -- IIT_NUM_ATTRIB17 Surface layer year – (LYRS - IIT_Xtra_Date_1 – Layer_Date) -- the year in which the roadway surface was last improved. 0.5 inch or more of compacted pavement material must be put in place for it to be considered a surface improvement.