20241113 21005000 1.0 FALSE ev_HPMSSample 212169.334717 2372883.827271 363807.854919 1467588.919678 1 002 Projected GCS_North_American_1983 Linear Unit: Foot_US (0.304801) NAD_1983_Kansas_LCC_ftUS <ProjectedCoordinateSystem xsi:type='typens:ProjectedCoordinateSystem' xmlns:xsi='http://www.w3.org/2001/XMLSchema-instance' xmlns:xs='http://www.w3.org/2001/XMLSchema' xmlns:typens='http://www.esri.com/schemas/ArcGIS/3.5.0'><WKT>PROJCS["NAD_1983_Kansas_LCC_ftUS",GEOGCS["GCS_North_American_1983",DATUM["D_North_American_1983",SPHEROID["GRS_1980",6378137.0,298.257222101]],PRIMEM["Greenwich",0.0],UNIT["Degree",0.0174532925199433]],PROJECTION["Lambert_Conformal_Conic"],PARAMETER["False_Easting",1312333.3333],PARAMETER["False_Northing",0.0],PARAMETER["Central_Meridian",-98.25],PARAMETER["Standard_Parallel_1",37.5],PARAMETER["Standard_Parallel_2",39.5],PARAMETER["Latitude_Of_Origin",36.0],UNIT["Foot_US",0.3048006096012192],AUTHORITY["EPSG",6923]]</WKT><XOrigin>-120729000</XOrigin><YOrigin>-94795000</YOrigin><XYScale>3048.0060960152887</XYScale><ZOrigin>-100000</ZOrigin><ZScale>10000</ZScale><MOrigin>-100000</MOrigin><MScale>16093472.173863573</MScale><XYTolerance>0.003280833333333</XYTolerance><ZTolerance>0.001</ZTolerance><MTolerance>6.2136994900000004e-07</MTolerance><HighPrecision>true</HighPrecision><WKID>6923</WKID><LatestWKID>6923</LatestWKID></ProjectedCoordinateSystem> 20260124 21125400 20260124 21125400 ISO19139 150000000 5000 ev_HPMSSample Feature Class 0 OBJECTID OBJECTID OID 4 10 0 Internal feature number. Esri Sequential unique whole numbers that are automatically generated. EventID EventID String 38 0 0 The unique ID for each event record. KDOT RouteID RouteID String 16 0 0 Unique ID of the route. KDOT FromMeasure FromMeasure Double 8 38 8 The measure on the route where the beginning of the event is located. KDOT ToMeasure ToMeasure Double 8 38 8 The measure on the route where the end of the event is located. KDOT HPMSSampleID HPMSSampleID String 12 0 0 The HPMS sample number assigned to the sample. KDOT HPMSSampleDescription HPMSSampleDescription String 200 0 0 Additional information for State use (formerly referred to as the “State Control Field”). KDOT HPMSAtGradeOther HPMSAtGradeOther SmallInteger 2 5 0 Code for the number of at-grade intersections in the inventory direction where traffic is not controlled by either a signal or a stop sign; is controlled by other types of signage; or some other device. This field satisfies MIRE data element 78. KDOT HPMSNumberSignals HPMSNumberSignals SmallInteger 2 5 0 The number of at-grade intersections with a signal controlling traffic on the inventory route within the segment. A signal that cycles through red, yellow, and green for all or a portion of the day should be counted as a signalized intersection. This field satisfies MIRE data element 76. KDOT HPMSPctGreenTime HPMSPctGreenTime SmallInteger 2 5 0 The percent of green time allocated for throughtraffic at intersections. KDOT HPMSPctPassSight HPMSPctPassSight SmallInteger 2 5 0 The percent of a Sample Panel section meeting the sight distance requirement for passing. This field satisfies MIRE data element 105. KDOT HPMSStopSignCount HPMSStopSignCount SmallInteger 2 5 0 The number of at-grade intersections with a stop sign controlling traffic on the inventory route within the segment. This field satisfies MIRE data element 77. KDOT HPMSSignalType HPMSSignalType String 3 0 0 The predominant type of signal system on a sample section. KDOT HPMSPeakParking HPMSPeakParking SmallInteger 2 5 0 Specific information about the presence of parking during the peak period. KDOT InventoryStartDate InventoryStartDate Date 8 0 0 HPMSTurnLanesL HPMSTurnLanesL SmallInteger 2 5 0 HPMSTurnLanesR HPMSTurnLanesR SmallInteger 2 5 0 LRSFromDate LRSFromDate Date 8 0 0 The date that the event becomes active on the route. KDOT LRSToDate LRSToDate Date 8 0 0 The date that the event is retired on the route. KDOT CreatedUser CreatedUser String 20 0 0 The names of users who created features or records. KDOT LastEditedUser LastEditedUser String 20 0 0 The names of users who last edited features or records. KDOT CreatedDate CreatedDate Date 8 0 0 The dates features or records were created. KDOT LastEditedDate LastEditedDate Date 8 0 0 The dates features or records were last edited. KDOT SourceCIT SourceCIT String 20 0 0 Authoritative source providing event record. KDOT LocError LocError String 100 0 0 The location error for the event. KDOT GlobalID GlobalID GlobalID 38 0 0 KDOTUseOnly KDOTUseOnly String 5 0 0 SHAPE Shape Geometry 8 0 0 Feature geometry. Esri Coordinates defining the features. Shape.STLength() Shape.STLength() Double 0 0 0 dataset Kyle Gonterwitz Kansas Department of Transportation Civil Engineer 700 SW Harrison Topeka KS 66603 kyle.gonterwitz@ks.gov US 785-296-3566 Kyle Gonterwitz 20260124 Enterprise Geodatabase Feature Class 10.6.1 ArcGIS Rest Services 10.6.1 Esri ArcGIS 13.5.0.56755 Highway Performance Monitoring System (HPMS) Sample 2017-12-31T00:00:00 1 -102.175386 -94.465792 40.029686 36.937030 0.000000 0.000100 Kyle Gonterwitz Kansas Department of Transportation Civil Engineer 700 SW Harrison Topeka KS 66603 kyle.gonterwitz@ks.gov US 785-296-3566 State Highway System RouteID with Prefix codes in 1, 2, 3 route networks and event features current all Urban Classified System RouteID with Prefix codes 5 route networks and event features current all Ramps RouteID with Prefix codes 4 OR TravelWayOperations = Ramp code route networks and ev_TravelWayOperations event feature current all 23 USC 409 <DIV STYLE="text-align:Left;"><DIV><DIV>23 USC 409</DIV></DIV></DIV> HPMS, Safety Analyst, ISHDM, MIRE 2.0, KDOT Transportation Planning ENTER SPECIFICS KDOT KDOT KHUB Highway Performance Monitoring System HPMS Sample <DIV STYLE="text-align:Left;"><DIV><DIV>Behaviors<UL><LI>Activity / Rules</LI><LI>CalibrateRoute - Stay Put</LI><LI>ReverseRoute - Stay Put</LI><LI>RetireRoute - Snap</LI><LI>ExtendRoute - Stay Put</LI><LI>ReassignRoute - Snap</LI><LI>RealignRoute - Stay Put</LI><LI>RealignOverlap - Snap</LI><LI>CartoRealignRoute - Honor Route Measure</LI></UL>From 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.<UL><LI>0 - Not Applicable </LI><LI>1 - Parking allowed one side </LI><LI>2 - Parking allowed both sides </LI><LI>3 - No parking allowed or none available </LI></UL>(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: <UL><LI>1 - No Base</LI><LI>2 - Aggregate; </LI><LI>3 - Asphalt or Cement Stabilized with Granular subbase</LI><LI>4 - Asphalt or Cement Stabilized with Granular subbase</LI><LI>5 - Hot Mix AC (bituminous)</LI><LI>6 - Lean Concrete</LI><LI>7 - Stabilized Open-graded Permeable</LI><LI>8 - Fractured PCC</LI></UL>(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. <UL><LI>1 - Flexible</LI><LI>2 - Rigid</LI></UL>(HPMT) - MATERIAL -- IIT_MATERIAL The material codes ***three pages of codes in PDF***(HPMT) - SURFACE TYPE -- IIT_NUM_ATTRIB16 <UL><LI>0 - Invalid</LI><LI>1 - Unpaved</LI><LI>2 - Conventional Asphalt Concrete (Bituminous) </LI><LI>3 - Jointed Plain Concrete Pavement (JPCP) </LI><LI>4 - Jointed Reinforced Concrete Pavement (JRCP) </LI><LI>5 - Continuously Reinforced Concrete Pavement (CRCP) </LI><LI>6 - AC (Bituminous) Overlay over Existing AC (Bituminous) Pavement </LI><LI>7 - AC (Bituminous) Overlay over Existing Jointed Concrete Pavement </LI><LI>8 - AC (Bituminous) Overlay over Existing CRCP </LI><LI>9 - Unbonded Jointed Concrete Overlay on PCC Pavements </LI><LI>10 - Bonded PCC Overlay on PCC Pavement </LI><LI>11 - Other (includes whitetopping) </LI></UL>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.<UL><LI>Code 1 - No Base</LI><LI>Code 2 - Aggregate </LI><LI>Code 3 - Asphalt or Cement Stabilized</LI><LI>Code 4 - Asphalt or Cement Stabilized with Granular subbase</LI><LI>Code 5 - Hot Mix AC (bituminous)</LI><LI>Code 6 - Lean Concrete</LI><LI>Code 7 - Stabilized Open-graded Permeable</LI><LI>Code 8 - Fractured PCC</LI></UL>(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 <UL><LI>0 - Invalid</LI><LI>1 - Unpaved</LI><LI>2 - Conventional Asphalt Concrete (Bituminous) </LI><LI>3 - Jointed Plain Concrete Pavement (JPCP) </LI><LI>4 - Jointed Reinforced Concrete Pavement (JRCP) </LI><LI>5 - Continuously Reinforced Concrete Pavement (CRCP) </LI><LI>6 - AC (Bituminous) Overlay over Existing AC (Bituminous) Pavement </LI><LI>7 - AC (Bituminous) Overlay over Existing Jointed Concrete Pavement </LI><LI>8 - AC (Bituminous) Overlay over Existing CRCP </LI><LI>9 - Unbonded Jointed Concrete Overlay on PCC Pavements </LI><LI>10 - Bonded PCC Overlay on PCC Pavement </LI><LI>11 - Other (includes whitetopping) </LI></UL>(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.</DIV></DIV></DIV> 0 EPSG 8.5.2(10.3.1) Simple FALSE 0 TRUE TRUE