ArcGIS REST Services Directory Login
Home > services > Transportation > HPMS_Sample (FeatureServer) > HPMS Sample > iteminfo API Reference
JSON

ItemInfo

Item Information

snippet: HPMS, Safety Analyst, ISHDM, MIRE 2.0, KDOT Transportation Planning ENTER SPECIFICS
summary: HPMS, Safety Analyst, ISHDM, MIRE 2.0, KDOT Transportation Planning ENTER SPECIFICS
accessInformation: KDOT
thumbnail:
maxScale: 5000
typeKeywords: []
description: <DIV STYLE="text-align:Left;"><DIV><DIV><P><SPAN STYLE="font-weight:bold;">Behaviors</SPAN></P><UL><LI><P><SPAN>Activity / Rules</SPAN></P></LI><LI><P><SPAN>CalibrateRoute - Stay Put</SPAN></P></LI><LI><P><SPAN>ReverseRoute - Stay Put</SPAN></P></LI><LI><P><SPAN>RetireRoute - Snap</SPAN></P></LI><LI><P><SPAN>ExtendRoute - Stay Put</SPAN></P></LI><LI><P><SPAN>ReassignRoute - Snap</SPAN></P></LI><LI><P><SPAN>RealignRoute - Stay Put</SPAN></P></LI><LI><P><SPAN>RealignOverlap - Snap</SPAN></P></LI><LI><P><SPAN>CartoRealignRoute - Honor Route Measure</SPAN></P></LI></UL><P><SPAN /></P><P><SPAN STYLE="font-weight:bold;">From CANSYS Metadata Master Report</SPAN></P><P><SPAN /></P><P><SPAN STYLE="font-weight:bold;">HPMS - (HPMS) </SPAN></P><P STYLE="margin:0 0 0 0;"><SPAN><SPAN>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.</SPAN></SPAN></P><P><SPAN STYLE="font-style:italic;">History:</SPAN></P><P STYLE="margin:0 0 0 0;"><SPAN>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.</SPAN></P><P><SPAN STYLE="font-weight:bold;">(HPMS) - Critical Parking -- IIT_CHR_ATTRIB30 </SPAN></P><P><SPAN>If parking is allowed during peak hours this attribute is coded.</SPAN></P><UL><LI><P><SPAN>0 - Not Applicable </SPAN></P></LI><LI><P><SPAN>1 - Parking allowed one side </SPAN></P></LI><LI><P><SPAN>2 - Parking allowed both sides </SPAN></P></LI><LI><P><SPAN>3 - No parking allowed or none available </SPAN></P></LI></UL><P><SPAN STYLE="font-weight:bold;">(HPMS) - HPMS Sample Id -- IIT_NUM_ATTRIB21 </SPAN></P><P><SPAN>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.</SPAN></P><P><SPAN STYLE="font-weight:bold;">HPMT - (HPMS Material Type Reference) </SPAN></P><P><SPAN>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.</SPAN></P><P><SPAN STYLE="font-weight:bold;">(HPMT) - BASE TYPE -- IIT_NUM_ATTRIB17 </SPAN></P><P><SPAN>Derived base type based on the material: </SPAN></P><UL><LI><P><SPAN>1 - No Base</SPAN></P></LI><LI><P><SPAN>2 - Aggregate; </SPAN></P></LI><LI><P><SPAN>3 - Asphalt or Cement Stabilized with Granular subbase</SPAN></P></LI><LI><P><SPAN>4 - Asphalt or Cement Stabilized with Granular subbase</SPAN></P></LI><LI><P><SPAN>5 - Hot Mix AC (bituminous)</SPAN></P></LI><LI><P><SPAN>6 - Lean Concrete</SPAN></P></LI><LI><P><SPAN>7 - Stabilized Open-graded Permeable</SPAN></P></LI><LI><P><SPAN>8 - Fractured PCC</SPAN></P></LI></UL><P><SPAN STYLE="font-weight:bold;">(HPMT) - FLEXIBLE RIGID FLAG -- IIT_NUM_ATTRIB18 </SPAN></P><P><SPAN>Flexible rigid flag - identifies whether the material type is flexible or rigid, which controls the flow of how surface and base type are calculated. </SPAN></P><UL><LI><P><SPAN>1 - Flexible</SPAN></P></LI><LI><P><SPAN>2 - Rigid</SPAN></P></LI></UL><P><SPAN STYLE="font-weight:bold;">(HPMT) - MATERIAL -- IIT_MATERIAL </SPAN></P><P><SPAN>The material codes </SPAN></P><P><SPAN STYLE="font-style:italic;font-weight:bold;">***three pages of codes in PDF***</SPAN></P><P><SPAN STYLE="font-weight:bold;">(HPMT) - SURFACE TYPE -- IIT_NUM_ATTRIB16 </SPAN></P><UL><LI><P><SPAN>0 - Invalid</SPAN></P></LI><LI><P><SPAN>1 - Unpaved</SPAN></P></LI><LI><P><SPAN>2 - Conventional Asphalt Concrete (Bituminous) </SPAN></P></LI><LI><P><SPAN>3 - Jointed Plain Concrete Pavement (JPCP) </SPAN></P></LI><LI><P><SPAN>4 - Jointed Reinforced Concrete Pavement (JRCP) </SPAN></P></LI><LI><P><SPAN>5 - Continuously Reinforced Concrete Pavement (CRCP) </SPAN></P></LI><LI><P><SPAN>6 - AC (Bituminous) Overlay over Existing AC (Bituminous) Pavement </SPAN></P></LI><LI><P><SPAN>7 - AC (Bituminous) Overlay over Existing Jointed Concrete Pavement </SPAN></P></LI><LI><P><SPAN>8 - AC (Bituminous) Overlay over Existing CRCP </SPAN></P></LI><LI><P><SPAN>9 - Unbonded Jointed Concrete Overlay on PCC Pavements </SPAN></P></LI><LI><P><SPAN>10 - Bonded PCC Overlay on PCC Pavement </SPAN></P></LI><LI><P><SPAN>11 - Other (includes whitetopping) </SPAN></P></LI></UL><P><SPAN STYLE="font-weight:bold;">HPPA - (HPMS Pavement Attributes) </SPAN></P><P><SPAN>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.</SPAN></P><P><SPAN>History:</SPAN></P><P><SPAN>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.</SPAN></P><P><SPAN STYLE="font-weight:bold;">(HPPA) - HPMS_BASE_THICKNESS -- IIT_NUM_ATTRIB23 </SPAN></P><P><SPAN>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.</SPAN></P><P><SPAN STYLE="font-weight:bold;">(HPPA) - HPMS_BASE_TYPE -- IIT_NUM_ATTRIB22 </SPAN></P><P><SPAN>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.</SPAN></P><UL><LI><P><SPAN>Code 1 - No Base</SPAN></P></LI><LI><P><SPAN>Code 2 - Aggregate </SPAN></P></LI><LI><P><SPAN>Code 3 - Asphalt or Cement Stabilized</SPAN></P></LI><LI><P><SPAN>Code 4 - Asphalt or Cement Stabilized with Granular subbase</SPAN></P></LI><LI><P><SPAN>Code 5 - Hot Mix AC (bituminous)</SPAN></P></LI><LI><P><SPAN>Code 6 - Lean Concrete</SPAN></P></LI><LI><P><SPAN>Code 7 - Stabilized Open-graded Permeable</SPAN></P></LI><LI><P><SPAN>Code 8 - Fractured PCC</SPAN></P></LI></UL><P><SPAN STYLE="font-weight:bold;">(HPPA) - HPMS_LAST_OVERLAY_THICKNESS -- IIT_NUM_ATTRIB19 </SPAN></P><P><SPAN>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. </SPAN></P><P><SPAN STYLE="font-weight:bold;">(HPPA) - HPMS_SURFACE_TYPE -- IIT_NUM_ATTRIB16 </SPAN></P><UL><LI><P><SPAN>0 - Invalid</SPAN></P></LI><LI><P><SPAN>1 - Unpaved</SPAN></P></LI><LI><P><SPAN>2 - Conventional Asphalt Concrete (Bituminous) </SPAN></P></LI><LI><P><SPAN>3 - Jointed Plain Concrete Pavement (JPCP) </SPAN></P></LI><LI><P><SPAN>4 - Jointed Reinforced Concrete Pavement (JRCP) </SPAN></P></LI><LI><P><SPAN>5 - Continuously Reinforced Concrete Pavement (CRCP) </SPAN></P></LI><LI><P><SPAN>6 - AC (Bituminous) Overlay over Existing AC (Bituminous) Pavement </SPAN></P></LI><LI><P><SPAN>7 - AC (Bituminous) Overlay over Existing Jointed Concrete Pavement </SPAN></P></LI><LI><P><SPAN>8 - AC (Bituminous) Overlay over Existing CRCP </SPAN></P></LI><LI><P><SPAN>9 - Unbonded Jointed Concrete Overlay on PCC Pavements </SPAN></P></LI><LI><P><SPAN>10 - Bonded PCC Overlay on PCC Pavement </SPAN></P></LI><LI><P><SPAN>11 - Other (includes whitetopping) </SPAN></P></LI></UL><P><SPAN STYLE="font-weight:bold;">(HPPA) - HPMS_THICKNESS_FLEXIBLE -- IIT_NUM_ATTRIB21 </SPAN></P><P><SPAN>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.</SPAN></P><P><SPAN STYLE="font-weight:bold;">(HPPA) - HPMS_YEAR_LAST_CONST -- IIT_NUM_ATTRIB18 </SPAN></P><P><SPAN>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. </SPAN></P><P><SPAN STYLE="font-weight:bold;">(HPPA) - HPMS_YEAR_LAST_IMPROV -- IIT_NUM_ATTRIB17 </SPAN></P><P><SPAN>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.</SPAN></P></DIV></DIV></DIV>
licenseInfo: <DIV STYLE="text-align:Left;"><DIV><DIV><P><SPAN>23 USC 409</SPAN></P></DIV></DIV></DIV>
catalogPath:
title: Highway Performance Monitoring System (HPMS) Sample
type:
url:
tags: ["KDOT","KHUB","Highway","Performance","Monitoring","System","HPMS","Sample"]
culture: en-US
portalUrl:
name:
guid:
minScale: 150000000
spatialReference: