{ "currentVersion": 10.81, "cimVersion": "2.6.0", "id": 2, "name": "Yes - Interstate in Wichita/KC (SG, BU, SU, JO, WY, LV Counties), Interstate in MPO and AADT > 30,000 vpd OR AADT > 10,000 vpd with 30% truck (HC) and Class A (Interstate) or Class B (U.S./State important corridors) routes OR urban principal arterials", "type": "Feature Layer", "description": "BehaviorsActivity / RulesCalibrateRoute - Stay PutReverseRoute - Stay PutRetireRoute - SnapExtendRoute - Stay PutReassignRoute - SnapRealignRoute - Stay PutRealignOverlap - SnapCartoRealignRoute - Honor Route MeasureFrom CANSYS Metadata Master Report:SWZ - (Significant Work Zones) All federal-aid interstate projects within a Transportation Management Area (TMA) that occupy a location for more than three days with either intermittent or continuous lane closures are considered significant. In addition, a significant project is one that alone or in combination with other concurrent projects nearby is anticipated to cause sustained work zone impacts that are greater than what is considered tolerable based on engineering judgment. This data set supports the KDOT policy (local copy of pdf here) - \\\\gisdata\\khub\\documentation\\UsersDocumentation\\BusinessProcess\\SignificantWorkZone\\KANSAS_WORK_ZONE_ SAFETY_AND_MOBILITY_POLICY_MASTER.pdfpublic link at https://www.ksdot.org/Assets/wwwksdotorg/PDF_Files/KANSAS%20WORK%20ZONE%20SAFETY%20AND%20MOBILITY%20POLICY%20MASTER.pdfThe division of transportation planning is responsible for providing traffic volumes, hourly traffic counts, and populating and maintaining a lane closure chart that illustrates lane requirements on an hourly basis for routes that meet the criteria for significant projects. The division of transportation planning will also be responsible for the following items: identifying mobility impacts of significant projects at both corridor and network levels. Identifying the combined impacts of concurrent projects that are located near each other when requested. Estimating work zone delays in work zones with a computer analysis software when requested. The traffic safety and technology (ITS) unit will assist with any its deployment.History:New data item in 2008(SWZ) - Significant Work Zone Code -- IIT_CHR_ATTRIB26 Code used to determine the status of the work zone. Code 1 - YES (work zone is significant) Code 2 - TBD (work zone may be significant, needs manual determination as needed).(SWZ) - SWZ Source Code -- IIT_CHR_ATTRIB27 Code used to record the method used to identify the significant work zone. Code 1 - District engineer discretion (this record was selected by the discretion of the district engineer.)Code 2 - Criteria met within TMA or MPO. (this record was selected by automated process within CANSYS database)****************Information stored below for lack of better place / keeping format****************HPMS Field ManualHPMS Field ManualHPMS Field ManualHPMS Field ManualFacility_Type (Facility Type) Description: The operational characteristic of the roadway. Use:For determining public road mileage, for investment requirements modeling to calculate capacity and estimate roadway deficiencies and improvement needs, in the cost allocation pavement model, and in the national highway database; for the querying and analysis of data (e.g., transportation performance management (TPM) metrics, Federal-aid project information, etc.) by facility type. Extent:All Public highways including ramps located within grade-separated interchanges as identified in 23 U.S.C 101.a(27).Functional SystemNHS: Rural = FE+R; Urban = FE+RIH: Rural = FE+R; Urban = FE+ROFE: Rural = FE+R; Urban = FE+ROPA: Rural = FE+R; Urban = FE+RMiA: Rural = FE+R; Urban = FE+RMaC: Rural = FE+R; Urban = FE+RMiC: Rural = FE+R; Urban = FE+RLocal: Rural = FE+R; Urban = FE+RFE+R = Full Extent & RampsCode & Description1 - One-Way Roadway - Roadway that operates with traffic moving in a single direction during non-peak period hours.2 - Two-Way Roadway - Roadway that operates with traffic moving in both directions during non-peak period hours.4 - Ramp - Non-mainline junction or connector facility contained within a grade-separated interchange.5 - Non Mainline - All non-mainline facilities excluding ramps. 6 - Non Inventory - Direction Individual road/roads of a multi-road facility that is/are not used for determining the primary length for the facility.7 - Planned/Unbuilt - Planned roadway that has yet to be constructed. Item 8: HOV_Type (Managed Lane Operations Type) Description:The type of managed lane operations (e.g., HOV, HOT, ETL, etc.). Use:For administrative, legislative, analytical, and national highway database purposes. Extent:All sections where managed lane operations exist. This shall correspond with the information reported for Data Item 9 (Managed Lanes). Functional SystemNHS: Rural = FE**; Urban = FE**IH: Rural = FE**; Urban = FE**OFE: Rural = FE**; Urban = FE**OPA: Rural = FE**; Urban = FE**MiA: Rural = FE**; Urban = FE**MaC: Rural = FE**; Urban = FE** MiC: Rural = ; Urban = FE**Local: Rural = ; Urban = FE**= Full Extent wherever data item is applicableCodes & Descriptions1 - Full-time Managed Lanes Section has 24-hour exclusive managed lanes (e.g., HOV use only; no other use permitted). 2 - Part-time Managed Lanes Normal through lanes used for exclusive managed lanes during specified time periods. 3 - Part-time Managed Lanes Shoulder/Parking lanes used for exclusive managed lanes during specified time periods. Item 9: HOV_Lanes (Managed Lanes) Description: Maximum number of lanes in both directions designated for managed lane operations. Use: For administrative, legislative, analytical, and national highway database purposes. Extent: All Sections where managed lanes exist. This should correspond with the information reported for Data Item 8 (Managed Lane Operations Type). Functional SystemNHS: Rural = FE**; Urban = FE**IH: Rural = FE**; Urban = FE**OFE: Rural = FE**; Urban = FE**OPA: Rural = FE**; Urban = FE**MiA: Rural = FE**; Urban = FE**MaC: Rural = FE**; Urban = FE** MiC: Rural = ; Urban = FE**Local: Rural = ; Urban = FE**= Full Extent wherever data item is applicableItem 10: Peak_Lanes (Peak Lanes) Description:The number of lanes in the peak direction of flow during the peak period. Use:For investment requirements modeling to calculate capacity, and in congestion analyses, including estimates of delay. Also used in the Highway Capacity Manual (HCM)-based capacity calculation procedure.Extent:All Sample Panel sections, optional for all other sections beyond the limits of the Sample Panel. Functional SystemNHS: Rural = SP; Urban = SPIH: Rural = SP; Urban = SPOFE: Rural = SP; Urban = SPOPA: Rural = SP; Urban = SPMiA: Rural = SP; Urban = SPMaC: Rural = SP; Urban = SPMiC: Rural = ; Urban = SPLocal: Rural = ; Urban = FE = Full ExtentSP = Sample Panel SectionsItem 11: Counter_Peak_Lanes (Counter-Peak Lanes) Description:The number of lanes in the counter-peak direction of flow during the peak period. Use:For investment requirements modeling to calculate capacity, and in congestion analyses, including estimates of delay. It is used in the Highway Capacity Manual (HCM)-based capacity calculation procedure.Extent:All Sample Panel sections, optional for all other sections beyond the limits of the Sample Panel. Functional SystemNHS: Rural = SP; Urban = SPIH: Rural = SP; Urban = SPOFE: Rural = SP; Urban = SPOPA: Rural = SP; Urban = SPMiA: Rural = SP; Urban = SPMaC: Rural = SP; Urban = SPMiC: Rural = ; Urban = SPLocal: Rural = ; Urban = SP = Sample Panel SectionsItem 15: Toll_Charged (Toll Charged) Description:Identifies sections that are toll facilities regardless of whether or not a toll is charged.Use:For administrative, legislative, analytical, and national highway database purposes. Extent:All roadways that are toll facilities, whether public or privately-owned / operated. Functional SystemNHS: Rural = FE**; Urban = FE**IH: Rural = FE**; Urban = FE**OFE: Rural = FE**; Urban = FE**OPA: Rural = FE**; Urban = FE**MiA: Rural = FE**; Urban = FE**MaC: Rural = FE**; Urban = FE**MiC: Rural = FE**; Urban = FE**Local: Rural = FE**; Urban = FE**FE** = Full Extent wherever data item is applicable Code & Description 1 - Toll charged in one direction only. 2 - Toll charged in both directions. 3 - No toll charged Item 16: Toll_Type (Toll Type) Description:Indicates the presence of special tolls (i.e., High Occupancy Toll (HOT) lane(s) or other managed lanes).Use:For administrative, legislative, analytical, and national highway database purposes. Extent:All roadways where special tolls exist. Functional System NHS: Rural = FE**; Urban = FE**IH: Rural = FE**; Urban = FE**OFE: Rural = FE**; Urban = FE**OPA: Rural = FE**; Urban = FE**MiA: Rural = FE**; Urban = FE**MaC: Rural = FE**; Urban = FE**MiC: Rural = FE**; Urban = FE**Local: Rural = FE**; Urban = FE**FE** = Full Extent wherever data item is applicable Code & Description 1 This section has toll lanes but no special tolls (e.g., HOT lanes). 2 This section has HOT lanes. 3 This section has other special tolls.Item 29: Signal_Type (Signal Type) Description:The predominant type of signal system on a sample section. Use:For the investment requirements modeling process to calculate capacity and estimate delay. Extent:All Sample Panel sections located in urban areas; optional for all other urban sections beyond the limits of the Sample Panel and rural Sample Panel sections.Functional SystemNHS: Rural = SP*; Urban = SPIH: Rural = SP*; Urban = SPOFE: Rural = SP*; Urban = SPOPA: Rural = SP*; Urban = SPMiA: Rural = SP*; Urban = SPMaC: Rural = SP*; Urban = SPMiC: Rural = ; Urban = SPLocal: Rural = ; Urban = SP = Sample Panel Sections SP* = Sample Panel Sections (optional) Codes & Descriptions1 Uncoordinated Fixed Time (may include pre-programmed changes for peak or other time periods). 2 Uncoordinated Traffic Actuated. 3 Coordinated Progressive (coordinated signals through several intersections). 4 Coordinated Real-time Adaptive 5 No signal systems exist. Item 30: Pct_Green_Time (Percent Green Time) Description:The percent of green time allocated for through-traffic at intersections. Use:For investment requirements modeling to calculate capacity and in congestion analyses. Extent:All Sample Panel sections located in urban areas; optional for all other urban sections beyond the limits of the Sample Panel and rural Sample Panel sections.Functional SystemNHS: Rural = SP*; Urban = SPIH: Rural = SP*; Urban = SPOFE: Rural = SP*; Urban = SPOPA: Rural = SP*; Urban = SPMiA: Rural = SP*; Urban = SPMaC: Rural = SP*; Urban = SPMiC: Rural = ; Urban = SPLocal: Rural = ; Urban = SP = Sample Panel Sections SP* = Sample Panel Sections (optional)Item 31: Number_Signals (Number of Signalized Intersections) Description:A count of at-grade intersections where traffic signals are present. Use:For investment requirements modeling to calculate capacity and estimate delay. Extent:All Sample Panel sections, optional for all other sections beyond the limits of the Sample Panel. Functional SystemNHS: Rural = SP; Urban = SPIH: Rural = SP; Urban = SPOFE: Rural = SP; Urban = SPOPA: Rural = SP; Urban = SPMiA: Rural = SP; Urban = SPMaC: Rural = SP; Urban = SPMiC: Rural = ; Urban = SPLocal: Rural = ; Urban = SP = Sample Panel SectionsItem 32: Stop_Signs (Number of Stop Sign-Controlled Intersections) Description:A count of at-grade intersections where stop signs are present. Use:For investment requirements modeling to calculate capacity and estimate delay. Extent:All Sample Panel sections, optional for all other sections beyond the limits of the Sample Panel. Functional SystemNHS: Rural = SP; Urban = SPIH: Rural = SP; Urban = SPOFE: Rural = SP; Urban = SPOPA: Rural = SP; Urban = SPMiA: Rural = SP; Urban = SPMaC: Rural = SP; Urban = SPMiC: Rural = ; Urban = SPLocal: Rural = ; Urban = SP = Sample Panel SectionsItem 33: At_Grade_Other (Number of Intersections, Type \u2013 Other) Description:A count of at-grade intersections, where full sequence traffic signal or stop sign traffic control devices are not present, in the inventory direction.Use:For investment requirements modeling to calculate capacity and estimate delay. Extent:All Sample Panel sections, optional for all other sections beyond the limits of the Sample Panel. Functional SystemNHS: Rural = SP; Urban = SPIH: Rural = SP; Urban = SPOFE: Rural = SP; Urban = SPOPA: Rural = SP; Urban = SPMiA: Rural = SP; Urban = SPMaC: Rural = SP; Urban = SPMiC: Rural = ; Urban = SPLocal: Rural = ; Urban = SP = Sample Panel SectionsItem 34: Lane_Width (Lane Width) Description:The measure of existing lane width. Use:For investment requirements modeling to calculate capacity, estimate needed improvements, and compute a safety index, for cost allocation pavement models. Extent:All Sample Panel sections, optional for all other sections beyond the limits of the Sample Panel. Functional SystemNHS: Rural = SP; Urban = SPIH: Rural = SP; Urban = SPOFE: Rural = SP; Urban = SPOPA: Rural = SP; Urban = SPMiA: Rural = SP; Urban = SPMaC: Rural = SP; Urban = SPMiC: Rural = ; Urban = SPLocal: Rural = ; Urban = SP = Sample Panel SectionsItem 42: Widening_Potential (Widening Potential) Description: The number of through lanes that could be potentially added. Use: For investment requirements modeling to estimate needed capacity improvements Extent: All Sample Panel sections, optional for all other sections beyond the limits of the Sample Panel. Functional SystemNHS: Rural = SP; Urban = SPIH: Rural = SP; Urban = SPOFE: Rural = SP; Urban = SPOPA: Rural = SP; Urban = SPMiA: Rural = SP; Urban = SPMaC: Rural = SP; Urban = SPMiC: Rural = ; Urban = SPLocal: Rural = ; Urban = SP = Sample Panel SectionsItem 43: Curves_A through Curves_F (Curve Classification) Description:Curve classification data. Use:For investment requirements modeling to calculate horizontal alignment adequacy and estimate running speed and operating costs. Extent: All paved principal arterial and rural minor arterial Sample Panel sections; optional for all other sections beyond the limits of the Sample Panel.Functional SystemNHS: Rural = ; Urban = IH: Rural = SP; Urban = SPOFE: Rural = SP; Urban = SPOPA: Rural = SP; Urban = SPMiA: Rural = SP; Urban = MaC: Rural = ; Urban = MiC: Rural = ; Urban = Local: Rural = ; Urban = SP = Sample Panel SectionsCurve Classification & DegreesA - Under 3.5 degrees (i.e., 0.061 radians) B - 3.5 \u2013 5.4 degrees (i.e., 0.061 \u2013 0.094 radians) C - 5.5 \u2013 8.4 degrees (i.e., 0.096 \u2013 0.147 radians) D - 8.5 \u2013 13.9 degrees (i.e., 0.148 \u2013 0.243 radians) E - 14.0 \u2013 27.9 degrees (i.e., 0.244 \u2013 0.487 radians) F - 28 degrees (i.e., 0.489 radians) or more Item 46: Pct_Pass_Sight (Percent Passing Sight Distance) Description:The percent of a Sample Panel section meeting the sight distance requirement for passing. Use:For investment requirements modeling to calculate capacity and estimate running speed and for truck size and weight analysis purposes.Extent:All rural, paved two-lane Sample Panel sections; optional for all other rural sections beyond the limits of the Sample Panel.Functional SystemNHS: Rural = SP; Urban = IH: Rural = SP; Urban = OFE: Rural = SP; Urban = OPA: Rural = SP; Urban = MiA: Rural = SP; Urban = MaC: Rural = SP; Urban = MiC: Rural = ; Urban = Local: Rural = ; Urban = SP = Sample Panel SectionsItem 47: IRI (International Roughness Index) Description: IRI is the road roughness index most commonly used worldwide for evaluating and managing road systems. Road roughness is the primary indicator of the utility of a highway network to road users. IRI is defined as a statistic used to estimate the amount of roughness in a measured longitudinal profile.Use: For investment requirements modeling to estimate pavement deterioration, section deficiencies, and necessary improvements, in cost allocation studies, in pavement condition trends, and for other analysis purposes including NHS performance. Also, for performance measure calculation for pavement condition on the NHS.Extent: All NHS and principal arterial sections, and rural minor arterial Sample Panel sections; optional for urban minor arterial, major collector, and minor collector Sample Panel sections and rural major collector Sample Panel sections.Functional SystemNHS: Rural = FE; Urban = FEIH: Rural = FE; Urban = FEOFE: Rural = FE; Urban = FEOPA: Rural = FE; Urban = FEMiA: Rural = SP; Urban = SP*MaC: Rural = SP*; Urban = SP*MiC: Rural = ; Urban = SP*Local: Rural = ; Urban = FE = Full ExtentSP = Sample Panel SectionsSP* = Sample Panel Sections (optional)Code / DescriptionA - Construction \u2013 Roadway was under construction B - Closure \u2013 Roadway was closed to traffic C - Disaster \u2013 Roadway was located in an area declared as a disaster zone D - Deterioration \u2013 Roadway is too deteriorated to measure and is already designated as \u201cPoor\u201dItem 48: PSR (Present Serviceability Rating) Description:Present Serviceability Rating (PSR) for pavement condition. Use:For investment requirements modeling to estimate pavement deterioration, section deficiencies, and needed improvements, in cost allocation studies, in pavement condition trends, and for other analysis purposes including NHS performance. Also, for performance measure calculation for pavement condition on the NHS. Extent:NHS, urban minor arterial, major collector, and minor collector Sample Panel sections and rural major collector Sample Panel sections where IRI is not reported. Functional SystemNHS: Rural = FE*; Urban = FE*IH: Rural = FE*; Urban = FE*OFE: Rural = ; Urban = OPA: Rural = ; Urban = MiA: Rural = ; Urban = SP*MaC: Rural = SP*; Urban = SP*MiC: Rural = ; Urban = SP*Local: Rural = ; Urban = Code / DescriptionA - Posted speed limit is less than 40 mph PSR / Description4.0 \u2013 5.0 Only new (or nearly new) superior pavements are likely to be smooth enough and distress free (sufficiently free of cracks and patches) to qualify for this category. Most pavements constructed or resurfaced during the data year would normally be rated in this category. 3.0 \u2013 4.0 Pavements in this category, although not quite as smooth as those described above, give a first class ride and exhibit few, if any, visible signs of surface deterioration. Flexible pavements may be beginning to show evidence of rutting and fine random cracks. Rigid pavements may be beginning to show evidence of slight surface deterioration, such as minor cracks and spalling. 2.0 \u2013 3.0 The riding qualities of pavements in this category are noticeably inferior to those of new pavements, and may be barely tolerable for high-speed traffic. Surface defects of flexible pavements may include rutting, map cracking, and extensive patching. Rigid pavements in this group may have a few joint failures, faulting and/or cracking, and some pumping. 1.0 \u2013 2.0 Pavements in this category have deteriorated to such an Extent that they affect the speed of free-flow traffic. Flexible pavement may have large potholes and deep cracks. Distress includes raveling, cracking, rutting and occurs over 50 percent of the surface. Rigid pavement distress includes joint spalling, patching, cracking, scaling, and may include pumping and faulting. 0.1 \u2013 1.0 Pavements in this category are in an extremely deteriorated condition. The facility is passable only at reduced speeds, and with considerable ride discomfort. Large potholes and deep cracks exist. Distress occurs over 75 percent or more of the surface. Item 49: Surface_Type (Surface Type) Description:Surface type on a given section. Use:For investment requirements modeling to estimate pavement deterioration and loading history, for the cost allocation pavement model, for the national highway database, and pavement condition performance metric rating determination. Extent:All NHS and Sample Panel sections, optional for all other sections beyond the limits of the Sample Panel.Functional SystemNHS: Rural = FE; Urban = FEIH: Rural = FE; Urban = FEOFE: Rural = SP; Urban = SPOPA: Rural = SP; Urban = SPMiA: Rural = SP; Urban = SPMaC: Rural = SP; Urban = SPMiC: Rural = ; Urban = SPLocal: Rural = ; Urban = FE = Full ExtentSP = Sample Panel SectionsCode / Description / Pavement Group1 - Unpaved - N/A2 - Bituminous - Asphalt Pavement3 - JPCP \u2013 Jointed Plain Concrete Pavement (includes whitetopping) - Jointed Concrete Pavement4 - JRCP \u2013 Jointed Reinforced Concrete Pavement (includes whitetopping) - Jointed Concrete Pavement5 - CRCP \u2013 Continuously Reinforced Concrete Pavement - CRCP6 - Asphalt-Concrete (AC) Overlay over Existing AC Pavement - Asphalt Pavement7 - AC Overlay over Existing Jointed Concrete Pavement - Asphalt Pavement8 - AC (Bituminous Overlay over Existing CRCP) - Asphalt Pavement9 - Unbonded Jointed Concrete Overlay on PCC Pavement - Jointed Concrete Pavement10 - Bonded PCC Overlay on PCC Pavement - Jointed Concrete Pavement11 - Other (e.g., plank, brick, cobblestone, etc.) - N/AData Item Requirements by Surface Type1 - UnpavedIRI - N/APSR - N/A Rutting - N/AFaulting - N/A Cracking % - N/A Thickness (Rigid) - N/A Thickness - N/A 2 - BituminousIRI - in/miPSR - 0.1-5.0Rutting - 0.01\u201d Faulting - N/A Cracking % - Fatigue % areaThickness (Rigid) - N/AThickness (Flexible) - 0.5\u201d3 - JPCPIRI - in/miPSR - 0.1-5.0Rutting - N/A Faulting - 0.01\u201d Cracking % - % cracked slabsThickness (Rigid) - 0.5\u201dThickness (Flexible) - 0.5\u201d include for white-topping only4 - JRPCIRI - in/miPSR - 0.1-5.0Rutting - N/A Faulting - 0.01\u201d Cracking % - % cracked slabsThickness (Rigid) - 0.5\u201dThickness (Flexible) - 0.5\u201d include for white-topping only5 - CRCPIRI - in/miPSR - 0.1-5.0Rutting - N/A Faulting - N/A Cracking % - Punchout/long./patch % area Thickness (Rigid)- 0.5\u201dThickness (Flexible) - N/A6 - Composite (AC / AC)IRI - in/miPSR - 0.1-5.0Rutting - 0.01\u201d Faulting - N/A Cracking % - Fatigue % areaThickness (Rigid) - N/AThickness (Flexible) - 0.5\u201d7 - Composite (AC / JCP)IRI - in/miPSR - 0.1-5.0Rutting - 0.01\u201d Faulting - N/A Cracking % - Fatigue % areaThickness (Rigid) - 0.5\u201dThickness (Flexible) - 0.5\u201d 8 - Composite (Bituminous / CRCP)IRI - in/miPSR - 0.1-5.0Rutting - 0.01\u201d Faulting - N/A Cracking % - Fatigue % areaThickness (Rigid) - 0.5\u201dThickness (Flexible) - 0.5\u201d 9 - Composite (Unbonded JC / PCC)IRI - in/miPSR - 0.1-5.0Rutting - N/A Faulting - 0.01\u201d Cracking % - % cracked slabsThickness (Rigid) - 0.5\u201dThickness (Flexible) - N/A10 - Composite (Bonded JC / PCC)IRI - in/miPSR - 0.1-5.0Rutting - N/A Faulting - 0.01\u201d Cracking % - % cracked slabsThickness (Rigid) - 0.5\u201dThickness (Flexible) - N/A11 - Other (e.g., brick)IRI - in/miPSR - 0.1-5.0Rutting - N/A Faulting - N/A Cracking % - N/A Percent - N/A Thickness (Rigid) - N/A Thickness (Flexible) - N/A Item 50: Rutting (Rutting) Description:Average depth of rutting. A rut is defined as longitudinal surface depressions in the asphalt pavement derived from measurements of a profile transverse to the path of travel on a highway lane. It may have associated transverse displacement. Asphalt pavement (Item 49 codes \u20182\u2019, \u20186\u2019, \u20187\u2019, and \u20188\u2019) is defined as pavements where the top-most surface is constructed with asphalt materials. Use:For pavement modeling purposes and pavement condition performance metric rating. Extent:All NHS and Sample Panel sections, optional for all other sections beyond the limits of the Sample Panel.Functional SystemNHS: Rural = FE; Urban = FEIH: Rural = FE; Urban = FEOFE: Rural = SP; Urban = SPOPA: Rural = SP; Urban = SPMiA: Rural = SP; Urban = SPMaC: Rural = SP; Urban = SPMiC: Rural = ; Urban = SPLocal: Rural = ; Urban = FE = Full ExtentSP = Sample Panel SectionsCode / DescriptionA - Construction \u2013 Roadway was under construction B - Closure \u2013 Roadway was closed to traffic C - Disaster \u2013 Roadway was located in an area declared as a disaster zone D - Deterioration \u2013 Roadway is too deteriorated to measure and is already designated as \u201cPoor\u201dItem 51: Faulting (Faulting) Description:Faulting is defined as a vertical misalignment of pavement joints in Portland Cement Concrete Pavements (Jointed Concrete Pavement). Jointed Concrete Pavements is defined as pavements where the top-most surface is constructed of Portland cement concrete with joints (Item 49 codes \u20183\u2019, \u20184\u2019, \u20189\u2019, \u201810\u2019, and \u201811\u2019). It may be constructed of either reinforced or unreinforced (plain) concrete.Use:For pavement modeling purposes and pavement condition performance metric rating. Extent:All NHS and Sample Panel sections, optional for all other sections beyond the limits of the Sample Panel. Functional SystemNHS: Rural = FE; Urban = FEIH: Rural = FE; Urban = FEOFE: Rural = SP; Urban = SPOPA: Rural = SP; Urban = SPMiA: Rural = SP; Urban = SPMaC: Rural = SP; Urban = SPMiC: Rural = ; Urban = SPLocal: Rural = ; Urban = FE = Full ExtentSP = Sample Panel SectionsCode / DescriptionA - Construction \u2013 Roadway was under construction B - Closure \u2013 Roadway was closed to traffic C - Disaster \u2013 Roadway was located in an area declared as a disaster zone D - Deterioration \u2013 Roadway is too deteriorated to measure and is already designated as \u201cPoor\u201dItem 52: Cracking_Percent (Cracking Percent) Description:Cracking is defined as a fissure or discontinuity of the pavement surface not necessarily extending through the entire thickness of the pavement . Cracking Percent is defined as the percentage of pavement surface exhibiting cracking as follows:For Asphalt pavements (Item 49 codes \u20182\u2019, \u20186\u2019, \u20187\u2019, and \u20188\u2019), Cracking Percent is the percentage of the total area exhibiting visible fatigue type cracking for all severity levels in the wheelpath in each section. For Jointed Concrete Pavements (Item 49 codes \u20183\u2019, \u20184\u2019, \u20189\u2019, \u201810\u2019, and \u201811\u2019), Cracking Percent is the percentage of slabs within the section that exhibit transverse cracking. Partial slabs shall contribute to the section that contains the majority of the slab length. For CRCP (Item 49 code \u20185\u2019), the Cracking Percent is the percentage of the area of the section exhibiting longitudinal cracking, punchouts, and/or patching. Transverse cracking shall not be considered in the Cracking_Percent for CRCP.Use:For pavement modeling purposes and pavement condition performance metric rating. Extent:All NHS and Sample Panel sections; optional for all other sections beyond the limits of the Sample Panel. Functional SystemNHS: Rural = FE; Urban = FEIH: Rural = FE; Urban = FEOFE: Rural = SP; Urban = SPOPA: Rural = SP; Urban = SPMiA: Rural = SP; Urban = SPMaC: Rural = SP; Urban = SPMiC: Rural = ; Urban = SPLocal: Rural = ; Urban = FE = Full ExtentSP = Sample Panel SectionsCode Description A - Construction \u2013 Roadway was under construction B - Closure \u2013 Roadway was closed to traffic C - Disaster \u2013 Roadway was located in an area declared as a disaster zone D - Deterioration \u2013 Roadway is too deteriorated to measure and is already designated as \u201cPoor\u201dItem 54: Year_Last_Improv (Year of Last Improvement) Description:The year in which the roadway surface was last improved. Use:For the cost allocation pavement model. Extent:All paved Sample Panel sections; optional for all other sections beyond the limits of the Sample Panel. Functional SystemNHS: Rural = SP; Urban = SPIH: Rural = SP; Urban = SPOFE: Rural = SP; Urban = SPOPA: Rural = SP; Urban = SPMiA: Rural = SP; Urban = SPMaC: Rural = SP; Urban = SPMiC: Rural = ; Urban = SPLocal: Rural = ; Urban = SP = Sample Panel SectionsItem 55: Year_Last_Construction (Year of Last Construction) Description:The year in which the roadway was constructed or reconstructed. Use:For pavement modeling purposes. Extent:All paved Sample Panel sections; optional for all other sections beyond the limits of the Sample Panel. Functional SystemNHS: Rural = SP; Urban = SPIH: Rural = SP; Urban = SPOFE: Rural = SP; Urban = SPOPA: Rural = SP; Urban = SPMiA: Rural = SP; Urban = SPMaC: Rural = SP; Urban = SPMiC: Rural = ; Urban = SPLocal: Rural = ; Urban = SP = Sample Panel SectionsItem 56: Last_Overlay_Thickness (Last Overlay Thickness) Description:Thickness of the most recent pavement overlay. Use:For pavement modeling purposes. Extent: All paved Sample Panel sections; optional for all other sections beyond the limits of the Sample Panel. Functional SystemNHS: Rural = SP; Urban = SPIH: Rural = SP; Urban = SPOFE: Rural = SP; Urban = SPOPA: Rural = SP; Urban = SPMiA: Rural = SP; Urban = SPMaC: Rural = SP; Urban = SPMiC: Rural = ; Urban = SPLocal: Rural = ; Urban = SP = Sample Panel SectionsItem 57: Thickness_Rigid (Thickness Rigid) Description: Thickness of rigid pavement. Use: For investment requirements modeling to estimate pavement deterioration and loading history and in the cost allocation pavement model. Extent: All paved Sample Panel sections; optional for all other sections beyond the limits of the Sample Panel.Functional SystemNHS: Rural = SP; Urban = SPIH: Rural = SP; Urban = SPOFE: Rural = SP; Urban = SPOPA: Rural = SP; Urban = SPMiA: Rural = SP; Urban = SPMaC: Rural = SP; Urban = SPMiC: Rural = ; Urban = SPLocal: Rural = ; Urban = SP = Sample Panel SectionsItem 58: Thickness_Flexible (Thickness Flexible) Description:Thickness of the flexible pavement. Use:For investment requirements modeling to estimate pavement deterioration and loading history and in the cost allocation pavement model. Extent: All paved Sample Panel sections; optional for all other sections beyond the limits of the Sample Panel. Functional SystemNHS: Rural = SP; Urban = SPIH: Rural = SP; Urban = SPOFE: Rural = SP; Urban = SPOPA: Rural = SP; Urban = SPMiA: Rural = SP; Urban = SPMaC: Rural = SP; Urban = SPMiC: Rural = ; Urban = SPLocal: Rural = ; Urban = SP = Sample Panel SectionsItem 59: Base_Type (Base Type) Description: The base pavement type. Use: For pavement modeling purposes. Extent: All paved Sample Panel sections; optional for all other sections beyond the limits of the Sample Panel. Functional SystemNHS: Rural = SP; Urban = SPIH: Rural = SP; Urban = SPOFE: Rural = SP; Urban = SPOPA: Rural = SP; Urban = SPMiA: Rural = SP; Urban = SPMaC: Rural = SP; Urban = SPMiC: Rural = ; Urban = SPLocal: Rural = ; Urban = SP = Sample Panel SectionsCode / Description1 - No Base - Surface layer is placed directly on subgrade without a base 2 - Aggregate - Non-stabilized granular, consisting of either crushed stone, gravel, recycled asphalt or concrete 3 - Asphalt or Cement Stabilized - Aggregate base treated with either asphalt or Portland cement 5 - Hot 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 6 - Lean Concrete - A Portland cement concrete mixture made with relatively low cement content (typically about 3 sacks/yd.) 7 - Stabilized Open-graded Permeable - Open-graded aggregate treated with either asphalt or Portland cement for stability 8 - Fractured PCC - Rubblized or crack-and-seated PCC pavement Item 60: Base_Thickness (Base Thickness) Description: The thickness of the base pavement. Use: For pavement modeling purposes. Extent: All paved Sample Panel sections; optional for all other sections beyond limits of the Sample Panel.Functional SystemNHS: Rural = SP; Urban = SPIH: Rural = SP; Urban = SPOFE: Rural = SP; Urban = SPOPA: Rural = SP; Urban = SPMiA: Rural = SP; Urban = SPMaC: Rural = SP; Urban = SPMiC: Rural = ; Urban = SPLocal: Rural = ; Urban = SP = Sample Panel SectionsItem 61: Climate_Zone (Climate Zone) Description: Climate zone as defined by the 4 LTPP climate zone descriptions. Use: For cost allocation pavement model purposes. Extent: All paved Sample Panel sections; optional for all other sections beyond the limits of the Sample Panel. Functional SystemNHS: Rural = SP; Urban = SPIH: Rural = SP; Urban = SPOFE: Rural = SP; Urban = SPOPA: Rural = SP; Urban = SPMiA: Rural = SP; Urban = SPMaC: Rural = SP; Urban = SPMiC: Rural = ; Urban = SPLocal: Rural = ; Urban = SP = Sample Panel SectionsCode / Description1 - Wet-Freeze 2 - Wet-Non-freeze 3 - Dry-Freeze 4 - Dry-Non-freezeItem 62: Soil_Type (Soil Type) Description: Soil type as defined by AASHTO soil classes. Use: For pavement modeling purposes. Extent: All paved Sample Panel sections; optional for all other sections beyond the limits of the Sample Panel. Functional SystemNHS: Rural = SP; Urban = SPIH: Rural = SP; Urban = SPOFE: Rural = SP; Urban = SPOPA: Rural = SP; Urban = SPMiA: Rural = SP; Urban = SPMaC: Rural = SP; Urban = SPMiC: Rural = ; Urban = SPLocal: Rural = ; Urban = SP = Sample Panel SectionsCode / Description1 - Granular (35% or less passing the 0.075 mm sieve) (AASHTO Soil Class A0 through A-3) 2 - Fine (Silt-Clay) Materials (>35% passing the 0.075 mm sieve) (AASHTO Soil Class A-4 through A-7) Item 66: Truck (National Truck Network) Description: Roadway section that is a component of the National Truck Network (NN) as defined by 23 CFR 658. Use: For analysis and mapping of NN information. Extent: All roadways that are designated NN routes. Functional SystemIH: Rural = FE**; Urban = FE**OFE: Rural = FE**; Urban = FE**OPA: Rural = FE**; Urban = FE**MiA: Rural = FE**; Urban = FE**MaC: Rural = FE**; Urban = FE**MiC: Rural = FE**; Urban = FE**Local: Rural = FE**; Urban = FE**FE** = Full Extent wherever data item is applicableCode / Description1 Section is on the National Network (NN) 2 Other State-designated truck route (optional) Item 67: Future_Facility (Future National Highway System) Description: An unbuilt roadway (or section) of the National Highway System (NHS), including intermodal connectors. Use: For analysis and mapping of future NHS information. Extent: All roadways that are designated future NHS routes. Functional SystemIH: Rural = FE**; Urban = FE**OFE: Rural = FE**; Urban = FE**OPA: Rural = FE**; Urban = FE**MiA: Rural = FE**; Urban = FE**MaC: Rural = FE**; Urban = FE**MiC: Rural = FE**; Urban = FE**Local: Rural = FE**; Urban = FE**FE** = Full Extent wherever data item is applicableCode / Description1 Un-built NHS section Item 70: Dir_Through_Lanes (Directional Through Lanes) Description: The number of lanes designated for through-traffic, for a given direction of travel on a divided highway section. Use: For querying and analysis of pavement performance metrics for Transportation Performance Management (TPM) purposes. Extent: All divided Interstate highway sections, where pavement distresses have been reported independently for the inventory and non-inventory directions of travel. Functional SystemNHS: Rural = ; Urban = IH: Rural = FE*; Urban = FE*OFE: Rural = ; Urban = OPA: Rural = ; Urban = MiA: Rural = ; Urban = MaC: Rural = ; Urban = MiC: Rural = ; Urban = Local: Rural = ; Urban = FE* = Full Extent (*See \u2018NOTE\u2019 below)*NOTE: This data item is only required to be reported when pavement distresses and other related data items (e.g., IRI, Surface Type, Rutting, etc.) have been reported independently for the inventory and non-inventory directions of travel associated with divided highway sections (see Chapter 2 - Sec. 2.7, Chapter. 3 - Sec. 3.3 (\u201cMetadata\u201d discussion), and Sec. 4.3 discussion for additional information).Cansys Metadata Master ReportCansys Metadata Master ReportCansys Metadata Master ReportCansys Metadata Master ReportCansys Metadata Master ReportCansys Metadata Master ReportCPMS - (WinCPMS projects) This item captures project information from the construction project management system. No data is entered by gad unit it is copied directly from CPMSHistory:WinCPMS was implemented in 2009 with interface to CANSYS data. Intention was to capture project data in CANSYS so the LRS locations of these projects could be maintained on CANSYS dynamic network and roadway geometry could be provided to WinCPMS as well. Cost benefit analysis may be performed when location on current network is maintained as well. CANSYS in turn uses this project information to determine what construction projects will be performed in a given year and where network realignments may take place that will require CANSYS network maintenance. The historical data prior to implementation of the WinCPMS system was loaded with locations that existed in older mainframe CPMS. Those route milepost locations were not necessarily accurate because they were never updated when a network realignment occurred. Some clean-up was done but locations prior to 2009 may not be accurate. They also will not have accurate effective dates and cannot be used in an as-at query.CTY - (City Number) CTY is a reference asset item. It is not located on the network. CTY contains detail data about each city. When a CTY name or number is created or modified the following reference tables need modified to match: Hig_Codes (CANSYS_Cities) - HIG codes should only have incorporated cities -- Inv_Attri_Lookup (Ct City_Nbr) - Inv_Attri_Lookup should only have incorporated cities -- Str_Attr_Lookup (RRCIT) - RRCIT should only contain incorporated cities with a GSA code -- Str_Attr_Lookup (RRFCI) - RRFCI should contain all cities that have a GSA code only (CTY) - CENSUS_POP -- IIT_NUM_ATTRIB108 Census population received every 10 years (CTY) - CENSUS_YEAR -- IIT_NUM_ATTRIB109 The year of the latest census data loaded (CTY) - City Name -- IIT_CHR_ATTRIB26 The name of the city being referenced. There are duplicate city names located in separate counties throughout the state. These will be unincorporated.(CTY) - City Number -- IIT_PRIMARY_KEY The unique identification number for the city being referenced. The gad unit assigns the unique identification number to the cities.(CTY) - County -- IIT_NUM_ATTRIB100 The main county where the city is located. (CTY) - County 2 -- IIT_NUM_ATTRIB101 There are cities located in multiple counties. On the state system, the counties will be adjoining, and the city overlaps into more counties. On the NUSYS system there are cities that are actually located in non-adjoining counties. County 2 is the second county where a city is located.(CTY) - County 3 -- IIT_NUM_ATTRIB102 There are cities located in multiple counties. On the state system, the counties will be adjoining, and the city overlaps into more counties. On the NUSYS system there are cities that are actually located in non-adjoining counties. County 3 is the third county where a city is located.History:When the CTY asset item was created, there were no cities located in more than three Counties. If that changes, there will need to be another attribute added to address county 4.(CTY) - FARS City Number -- IIT_NUM_ATTRIB107 Unique identifier for a city as assigned by fatal accident reporting system (FARS). (CTY) - Fips City ID -- IIT_NUM_ATTRIB105 Unique identifier for federal city number as assigned by federal information processing standards (fips). (CTY) - Incorporated City -- IIT_CHR_ATTRIB28 This attribute indicates if the city is incorporated, unincorporated or a defense entity. Code I - Incorporated cityCode U - Unincorporated cityCode D - Sefense feature(CTY) - Population -- IIT_NUM_ATTRIB106 This is referred to as the secretary of state population. It is the population as reported annually by Kansas secretary of state. This is updated annually from a data set downloaded from the secretary of state website. The file is usually ready for use around July.(CTY) - SOS_CITY_NAME -- IIT_CHR_ATTRIB29 City name received from the secretary of state. The primary use for this column is for loading new records received from secretary of state. (CTY) - Sub City -- IIT_NUM_ATTRIB104 Sub city is the parent city of the city being referenced. For example: city 520 - Olathe has a sub city value of 390 - Kansas City. The domain ct city_nbr contains all city numbers and names. If a new city is added to CTY, the domain needs to be modified to match.(Long List in separate document)DESH - (Designated Highway) Designated highway name as assigned by the legislature. This item will be maintained by cartography between the end of legislature and the beginning of network maintenance. History:Initial load, January 2013 DLDL - (Dynamic Location Descriptions w LINTs) Dynamic location descriptions w LINTS DLDS generation package was ran using lint instead of INTR DLDS - (Dynamic Location Descriptions) Dynamic location descriptions. Point items used to create descriptions based on desired criteria. Descriptions are created at point locations for each occurrence of type. A function is used to extract description based on a specific location. This will use the primary route name. History is to be retained. The asset items used to create point items are city, UAB, INTR. Network items used to create point items are divided/undivided, CRND, SRND.(DLDS) - Description Text -- IIT_CHR_ATTRIB66 Detailed text description of the location from designated description types. This description is generated when the DLDS load is ran. (DLDS) - Description Type -- IIT_CHR_ATTRIB26 CITY - City Line CNTY - County Line CNYB - Begin County Line Names CNYE - End County Line Names D_UN - Divided Undivided INTR - Intersection LINT - Location Intersection NINTR - Off State Intersection ROUTE - Route Begin/End SINTR - On State Intersection STATE - State Limit STRP - State Reference Post UAB - Urban Area Boundary DWRA -- Foreign Table: DWRA_FOREIGN_TBL - (Data Warehouse RPAC summary) DWRA is a summary of the RPAC item with each action concatenated into a string that can be reported through Data Warehouse. This item was created for the Data Warehouse geometric. This item is needed due to there being multiple action items at the same location and that merge query has a limitation on the number of fields that can be used in a single query and the roadway geometric merge query is at its maximum number. So, it was decided to concatenate the RPAC attribute items together into one field, thus the need for DWRA.(DWRA) - DOWEL ACTION -- DOWEL_ACTION Summarization of the dowel action performed: concatenation of action, date and width. Example: dowel|01-Jan-1999|0| (DWRA) - INTOL ACTION -- INTOL_ACTION Summarization of the intol action performed: concatenation of action, date and width. Example: intol|01-Jan-1999|0|. (DWRA) - JOINT ACTION -- JOINT_ACTION Summarization of the joint action performed: concatenation of action, date and width. Example: joint|01-Jan-1999|0| EBNB -- Foreign Table: V_NM_EBNB - (HPMS SECT) This item is for internal use to capture the segmentation of network used for annual HPMS reporting. The attribution is element information from the nm_elements table. There are specific NUSYS routes specified in the code. FHWA - (FHWA Systems) Federal highway administration id numbers Elsit will find out what other states are doing. Further discussion. Update: Alan has prepared document (per Steve Foust\u2019s recommendation) that we include al state highways as truck routes and send to Chris & Dennis for comments. 12/21/10 (FHWA) - FHWA PRIMARY ID -- IIT_CHR_ATTRIB26 S not updated but it is supposed to be maintained as it was when FHWA primary ids were assigned. See domain fh FHWA_pri_id for all valid entries.***Large List of values in separate document***FRNT - (Frontage Roads) FRNT is data that was used to plan the need for frontage roads. See history for validity of data. History:FRNT is data that was collected in the 1970s and 80s by field survey teams. At this time FRNT was used as part of a capacity formula to plan future road programs in the cities. The data is old and is not presently used. We have made some minor attempt to maintain the data when it is evident on plans. (FRNT) - Frontage Road Type -- IIT_CHR_ATTRIB26 Frontage road status and projected need.0 - N.A. - Not applicable 1 - EXISTS - Frontage road exists 2 - NEED/FLOW - Frontage road needed to achieve free flow during peak 3 - NEED/DESTROY - Frontage road needed but would destroy existing 4 - NOT NEEDED - Frontage road not needed. GPGR - (GPS Grades) This item contains grade data collected by materials and research. They provided GPS grade data segmented in 1/10-mile segments that have been averaged for all years collected. This represents data received in year 2009. The data is less accurate on roadways where grade improvements had been done, as the process doesn\u2019t throw out data prior to grade improvement in the averaging process.History:Only used where grad does not exist. Grad data supersedes GPGR data. (GPGR) - GRADIENT -- IIT_NUM_ATTRIB16 GPS grade data segmented in 1/10-mile segments that have been averaged for all years collected. INTR - (Intersections) At grade or grade separated intersection of two or more roadways. Have to be able to move from one route to another within a reasonable distance (half mile is reasonable (example: K4 and HWY 40)). Each intersection has only one Intersection ID. Each route passing through the intersection has the Intersection ID located at one time. One intersection id shared by all routes passing through. A state to state intersection should have at least two locations. A state to non-state would only have one location on an undivided route. A state to non-state would have at least two locations for a divided route. This is a very deep subject, there are always exceptions to the rules. Consideration has to be made for intersections with multiple legs, etc.History:There are older intersections with separate nodes these need to be cleaned up in the future. Ruby has explained that the same datum node should be used between state and NUSYS. This would make truck routing easier in the future.(INTR) - % Peak Green Time -- IIT_NUM_ATTRIB20 The percent of green time allocated for through-traffic at intersections (INTR) - Cartography Node ID -- IIT_NUM_ATTRIB17 This ID is being used to identify which intersections are marked for deletion in NUSYS. History:Lots of work has been done to identify duplicate intersections where one needs to be removed. A value of 0 was retained in The cart node id to identify the records needing removed. (INTR) - Intersection Control -- IIT_NUM_ATTRIB25 The type of control on the intersection. If the intersection control is unknown leave the value null. Code 0 - N/A, Rural Section Code 1 - Signal, Uncoordinated Fixed TimeCode 2 - Signal, Traffic ActuatedCode 3 - Signal, Progressive (Coordinated Signal Through Several Intersections)Code 4 - Stop SignCode 5 -- Other or No ControlCode 6 - RoundaboutCode 7 - Interchange(INTR) - Intersection Desc -- IIT_CHR_ATTRIB56 Enter the friendly name of the road for each leg on the intersection in clockwise direction beginning with the north leg. When coding the intersections use the back slash \"\\\" as the leg separator and the front slash \"/\" as the separator between rider routes. Rider routes should be listed in hierarchical order. Ex: u50/k7\\e 12th st\\u50/k7\\w 12th St. Please see the naming document.History:Originally the route description did not include all legs at an intersection, but it is an on-going process to get all those included. (INTR) - Intersection ID -- IIT_PRIMARY_KEY Number that identifies the intersection. This is no longer being auto calculated with a specific sequence of numbers. If no ID is specified, the NE_ID of the inventory item will be set as the ID.History:In the past a -1 was used in the intersection_id so the system would assign the next available Number but that practice has been discontinued. There will be some cases where the primary keys of intrs will be the same primary keys for other inventory types. This is not the way the system was originally designed but it does not cause a major problem.(INTR) - Intersection Name -- IIT_CHR_ATTRIB26 Enter the 3-digit city number (county number for state system) one-character route prefix and the remaining seven digits for each leg on the intersection in clockwise direction beginning with the north leg. Ex: 040c0021000\\040l0000000\\040c0021000\\003k0000700(INTR) - Left Turn Lane -- IIT_NUM_ATTRIB18 The presence of left turn lanes at an intersection. In cases where we have a t-intersection and there is no road to the left use option 0.code 0 - N/A, Rural Section, not permitted, or no intersections exist on section.code 1 - Turns Permitted, Mult. exclusive turning lanes exist. No throughcode 2 - Turns Permitted, cont. exclusive turn lane. (chicken ln) no throughcode 3 - Turns Permitted, single exclusive turn lanecode 4 - Turns Permitted, no exclusive turn lanecode 5 - No Turn permitted during peak period. (INTR) - Number of Legs -- IIT_NUM_ATTRIB22 Number of roads in all directions at an intersection. (INTR) - On State/Non-State -- IIT_CHR_ATTRIB27 Identifies with the intersection is state or non-state. Code N - Non-Dtate (any leg is non-state)Code S - State (INTR) - Project Number INTR -- IIT_CHR_ATTRIB29 Roundabouts only (INTR) - Right Turn Lane -- IIT_NUM_ATTRIB19 The presence of right turn lanes at an intersection. In cases where we have a t-intersection and there is no road to the left use option 0.0 - N/A, rural section, not permitted, or no intersections exist on section. 1 - Turns permitted, mult. exclusive turning lanes exist. No through 2 - Turns permitted, cont. exclusive turn lane. (Chicken Ln) No through. 3 - Turns Permitted, single exclusive turn lane. 4 - Turns permitted, no exclusive turn lane. 5 - No turn permitted during peak period. (INTR) - Roundabout KARS ID -- IIT_CHR_ATTRIB30 Roundabouts only (INTR) - TFO Indicator -- IIT_CHR_ATTRIB28 Indicates if the intersection is used as a segment break for AADT data load and resides in the TFO asset item.N - No, Value not supplied by TFO Y - Yes, Value supplied by TFO LAND - (Land Uses) Land use describes the land on either side of the roadway traveled. \"inside/outside\" is \"left/right\" on undivided facilities. On divided facilities inside is coded type 11 or other. Cross sectional position is used for landLUIN - land use insideLUOL - land use outside leftLUOR - land use outside rightLUOR should always exist, LUOL should always exist for undivided facilities and never for divided, and LUIN should always exist on divided facilities and never for undivided.(LAND) - LAND USE CODE -- IIT_CHR_ATTRIB55 Type of land use1 - GRASSLAND - Grassland 2 - CULT UPLAND - Cultivated Upland 3 - CULT BOTTOM - Cultivated bottomland 4 - IRRIGATED - Irrigated 5 - MINERAL DEV - Mineral Development. Oil, gas, etc. 6 - CBD - Central business district. 7 - OBD - Outlying business district. 8 - RESIDENTIAL - Residential. 9 - INDUSTRIAL - Industrial 10 - PUBLIC - Public, Park, game reserve, etc. 11 - OTHER - Land use that is not defined. (LYRS) - Accuracy -- IIT_CLASS Layers are created by schemes. This attribute is standard in exor. Not used by CANSYS.D - DefiniteG - GuessS - Sure(LYRS) - Depth -- IIT_LENGTH The thickness in millimeters of the layer History:From about 2000 - 2007 most plans and 402s were specified in MM. (LYRS) - Layer -- IIT_NO_OF_UNITS 1 - Layer 12 - Layer 23 - Layer 34 - Layer 45 - Layer 56 - Layer 67 - Layer 78 - Layer 89 - Layer 910 - Layer 1011 - Layer 1112 - Layer 1213 - Layer 1314 - Layer 1415 - Layer 14History:Prior to 2003 layers were numbered from bottom to top. Oldest on the bottom was number 1 ****(RC MATERIAL LIST IN SEPERATE PDF)*****MASA - (Maintenance Area/Sub Area) More (see history) the KDOT geographic area / sub-area a route is located within. This data is meant to retain the area/sub area of the responsible party for the network. This will not always coincide with the physical location of the area/subarea. History:In some rare instances a roadway is actually within one district/area/sub-area but administered/maintained by another. At first area and sub-area were coded as flexible attributes of the element. Since about 2007 MASA is the correct data. **The element flexible attributes for area and subarea need to be removed so masa is the official area subarea location** NONA - (Non-Attainment Area) Non-attainment area - EPA defined non-attainment area (see comments column): no data is present on state or NUSYS. We do not have any ea defined non-attainment area yet. This appears to be created for HPMS-NAAQS -non-attainment area. As of 2010, FHWA has not assigned any non-attainment areas for KS.NAAQS area boundaries\u2014the polygon shapes dataset representing the EPA-defined non-attainment and maintenance areas for each state.History:This shape dataset will be maintained by FHWA. From HPMS field manual ---the definition of a maintenance area is any geographic region of the US previously designated as non-attainment pursuant to the clean air act (CAA) amendments of 1990 and subsequently re-designated to attainment subject to the requirement to develop a maintenance plan under sect 175a of the CAA, as amended. The national HPMS database is used for tracking travel for air quality assurance purposes in non-attainment and maintenance areas as required by EPA under the 1990 CAA (sect 187) and the transportation conformity rule, 40 CFR parts 51 and 93. More specifically, the database is used primarily for establishing regional transportation-related emissions for transportation conformity purposes. Estimated travel based on these data is used for the calibration and validation of base-year network travel models when required for non-attainment or maintenance areas. PMID - (Pavement Management ID) This is a unique ID between state segs in CANSYS and the Pavement Management Database. Unique ID Number assigned by Bureau of Materials and Research, PMS section. This num is used to identify roadway segs, by county, route, milepost and lane. This num is included in data dumps sent from PMS for loading into CANSYS. After network MAINT each year these nums will need to be updated in the CANSYS app before the data extract can be sent to PMS.these segs are intended to be 1 mile long. The format desc from PMS: PMS seg.id.no. PMS segment ID number. Each of the segments in the network has a unique ID number. It contains county number, route class letter, route num, route suffix num, segment integer log points (mileposts), and lane number.co.the number (1-105) of the county the PMS seg is in. Route letters are I, U and K. Route num is the assigned number of the route. History:Materials and research do not use the same LRS key identification as the rest of KDOT. This allows for a relationship between CANSYS and PMS.(PMID) - PMS_ID -- IIT_NUM_ATTRIB16 Unique number used to map CANSYS location to PMS location. PSRE - (PSR EQUIVALENT) PSRE equivalent is a conversion of PAVC rideability value for fun classes 16 and 17. This is to be used for NUSYS only, to report PSR. The PSRE will be pulled if there is no IRI value for the sample. (PSRE) - PAVC_DATE -- IIT_DATE_ATTRIB86 Last modified date of the PAVC record for which the PSRE value was determined. (PSRE) - PSR_EQUIVALENT -- IIT_NUM_ATTRIB100 Conversion of PAVC rideability code SECT -- Foreign Table: V_NM_SECT - (FT Inv for \"NETWORK SECTIONS\") Sect is a foreign table asset based on the view v_nm_sect. State route data is in this asset. This asset is used primarily in the creation of merge queries to allow for reference to the element data. To create the v_nm_sect view, goto >network manager >reference data >network types query back sect, press create foreign table inv button. Check the replace inv type box and press proceed. Note: the customized columns in the view will disappear when the view is recreated through the CANSYS application. Currently, (11-2011) the customized columns are: substr (ne_unique, 1, 3) county, Substr (ne_unique, 4, 1) prefix, Substr (ne_unique, 4, 8) state_route, Ne_sub_class exor_sub_class --new trc 5/27/2008SSF - (Soil Support Factor) Per email from Rick Miller, soil support factor is no longer used, and item can be end dated. Soil support factor is split into three categories low, medium and high to reflect the density of the soil in the area. Soil support factor is split into three categories low, medium and high to reflect the density of the soil in the area. History:Imported from old mainframe database (SSF) - FACTOR -- IIT_CHR_ATTRIB26 Soil support factor is split into three categories low, medium and high to reflect the density of the soil in the area. Data_source: the surface deployment and distribution command transportation engineering agency (SDDCTEA) is the DOD designated agent for public highway matters, including STRAHNET and STRAHNET connectors. The SDDCTEA identified STRAHNET and the connector routes in coordination with the federal highway administration (FHWA), the state transportation departments, the military services and installations, and the ports. (SSYS) - Special System Type -- IIT_CHR_ATTRIB26-- Ended (1/1/2013) Special systems: Code 1 - add int - addition to the interstate system (23 USC 139(c)).Code 2 - add int -84 - addition to the interstate system (23 USC 139(a)) before 3/9/84.Code 3 - add int +84 - addition to the interstate system (23 USC 139(a)) after 3/8/84.Code 4 - fut int - future addition to the interstate system (23 USC 139 (b)).Code 8 - STRAHNET - strategic highway network (STRAHNET)Code 11 - ADH - Appalachian development highwayCode 13 - IRRB - Indian reservation roads and bridgesCode 15 - NFHS - national forest highway systemCode 16 - NFDRT - national forest development roads and trailsCode 18 - NPSP - national park service parkwayCode 19 - NPRT - national park roads and trailsCode 20 - PPR - priority primary routeSTNM - (Street Name) The name of the street that is associated with the route. Currently NUSYS only - the name of the street that is associated with the route. History:In the old mainframe system, street name was limited to twelve alpha/numeric characters but during the conversion to NUSYS, the length was extended to fifty. When entering street names in the old system, street names were not followed by the abbreviation \"st\" except where absolutely necessary to avoid confusion.(STNM) - STREET NAME -- IIT_CHR_ATTRIB26 The name of the street that is associated with the route. STP - (State Transportation Plan Classes) KDOT route classification system: in an effort to better manage and address the diversity of the Kansas state highway system, KDOT has developed a route classification system based on daily traffic, route continuity, access to major cities, trip length and route spacing. The system is divided into five classification levels A through E routes. Section 5.1-definition: http://KDOTweb.ksdot.org/KDOTorg/burdesign/manuals/manuals.htm ; http://www.ksdot.org/burtransplan/maps/GISmaps/routeclass.pdf; (Links above don't work) maps, http://www.ksdot.org/burtransplan/maps/GISmapst.asp (STP) - STP CLASS TYPE -- IIT_CHR_ATTRIB26 STP Class Type: A - Those routes designated as the interstate system (the interstate system, including the Kansas turnpike. Its primary function is to serve interstate travel)B - The most important corridors of statewide and interstate travel. (Routes that serve as the most important statewide and interstate corridors for travel. The routes serve distinct trip movements since they are widely spaced throughout the state. On major sections of the routes traffic volumes are relatively constant. A significant number of out-of-state vehicles use class B routes, and trips on the routes are typically very long)C - Part of the statewide arterial system and is integrated with A and B. (Class C - defined as arterials, these routes are closely integrated with class A and B routes in service to all parts of the state. Major locations that are not on A or B routes are connected by a C route. Average trip lengths are typically long.)D - Routes serving a combined role of inter-county movement. (Class D - these routes provide access to arterials and serve small urban areas not on a class A, B, or C route. The routes are important for inter county movement); E - Stubs and routes whose service is limited to local service. (Class E routes are frequently used on a daily basis, sometimes several times a day, to connect rural residents with other routes or to provide access to small towns in the area.) TOLL - (Toll Roadways) In the beginning all toll roads were privately owned by the Turnpike Authority. The Turnpike Authority was responsible for collecting the toll charges when public funds were used to construct a roadway. Currently, a secretarial agreement (between Secretary of KDOT and the Secretary of KTA), made the Kansas Turnpike a part of the Kansas Highway System. An interstate roadway is defined as a roadway which is part of the unites states interstate roadway system. Toll is not used in the calculating of mileage and travel.(TOLL) - TOLL ROADWAY TYPE -- IIT_CHR_ATTRIB26 1 - NON/TOLL - Not a toll roadway. 2 - TOLL - Toll roadway 3 - AGRMNT - Interstate toll segment under Secretarial Agreement. 4 - AGRMNT FREE - Interstate toll segment under Secretarial Agreement 5 - AGRMNT MAINT - Toll segment under Secretarial Agreement, Contract UAB - (Urban Area Boundary) UAB asset type stores length and location where a route crosses an urban area boundary. Outside of urban area is stored as 999 and inside urban area stores the UAB number pertaining to the urban area you are in. History:Currently, UAB changes are derived from strip map. With the abolishment of the strip map a new process will need to be determined to collect UAB changes. UABS are reviewed every 10 years to coincide with the taking of the census. The assistant bureau chief of the bureau of transportation planning is responsible for working with the cities and the FHWA division office in getting updates to the UABS approved. Updated UAB shapefiles are provided by GIS.(UAB) - FIPS Urban Area Code -- IIT_NUM_ATTRIB100 The federal information processing standard (FIPS) code used to identify the urban area boundary for which data is being reported. 2012 urban areas are: Topeka (134), St. Joseph (179), Kansas City (19), Lawrence (328), Wichita (62), not urban area (999).? Should this population column be removed and use only the population in the UABR item does the y2000 population need to be retained UABR should contain the population and thus the population doesn\u2019t need to be in UAB? The population number for that urban area boundary. This population number is copied from other classified routes from within the same urban area boundary.History:***this column should be removed and the FIPS code should refer to UABR item. Code is used For UABS that are outside the city limits (rural) but inside the specified UAB. Currently UAB changes are derived from strip map. With the abolishment of the strip map a new process will need to be determined to collect UAB changes. UABS are reviewed every 10 years to coincide with the taking of the census. The assistant bureau chief of the bureau of transportation planning is responsible for working with the cities and the FHWA division office in getting updates to the UABS approved. Updated UAB shapefiles are provided by GIS. (UAB) - Primary City Code -- IIT_CHR_ATTRIB27 City code number found in atlas this code is used for the primary city code that is outside the city limits (rural) but inside the specified UAB.city code number found in atlas and in the primary_city_code. Primary city code_num is for the city number unless city is a subcity within a major city then primary city code is the major city number (example. UAB will contain city number 390 for Olathe (city number 520)) the CTY item contains the reference between city number and if a subcity of a larger city (example. Primary_city_code will contain 520 for Olathe and 390 for sub_city).(UAB) - Primary_City_Code_Num -- IIT_NUM_ATTRIB17 City code number found in atlas and in the primary_city_code. Primary city code_num is for the city number unless city is a subcity within a major city then primary city code is the major city number (example. UAB will contain city number 390 for Olathe (city number 520)) the CTY item contains the reference between city number and if a subcity of a larger city (example. Primary_city_code will contain 520 for Olathe and 390 for sub_city)(UAB) - Urban Area Population -- IIT_NUM_ATTRIB16 ? Should this population column be removed and use only the population in the UABR item does the y2000 population need to be retained UABR should contain the population and thus the population doesn't need to be in UAB? The population number for that urban area boundary. This population number is copied from other classified routes from within the same urban area boundary. History:****this population column should be removed and use only the population in the UABR Item-does the y2000 population need to be retained -- UABR should contain the population and thus the population doesn\u2019t need to be in UAB? The population number for that urban area boundary. This population number is copied from other classified routes from within the same urban area boundary. (UABL) - Urban Type -- IIT_CHR_ATTRIB26 Hi business - high density of business but not central business district. Lo business - lower density of business than high business and central business. Hi resident - urban residential area with a population >= 2000 persons/sq.km. Lo resident - urbanized residential area with a population < 2000 persons/sq.km. Other - undeveloped land and residential area with < 1 house per acre. UABR - (Urban Area Boundary Reference) A generalized categorization of the urban type based on history. (UABR) - FIPS_URBAN_AREA_CODE -- IIT_NUM_ATTRIB100 Federal information processing standards code used to define an UAB. (UABR) - PRIMARY_CITY_CODE -- IIT_CHR_ATTRIB27 UAB city number (UABR) - URBAN_AREA_POPULATION -- IIT_NUM_ATTRIB16 This is the urban population for a specific UAB. This replaces the population from the UAB asset. This data comes from the decennial census data and will not update until the 2010 census data is released. When the new census data is released, load new records and retain history of the old. Make the start date of the 2010 census - Jan 1, 2010 - to allow for correct processing of the population.History:A new attribute is needed to retain the annual population estimate engineering associate iii (Elsit) receives from the MPO's. This is data received from Kansas City, St. Joseph, Topeka and Wichita.VCUR - (Vertical Curves) This is a historical item and probably needs end dated (VCUR) - LENGTH -- IIT_NUM_ATTRIB16 The length of vertical curve from vertical point of curvature to vertical point of tangency (VCUR) - PCT DIFFERENCE -- IIT_NUM_ATTRIB17 Absolute value of the algebraic difference in gradients (VCUR) - STOP SIGHT DISTANCE -- IIT_NUM_ATTRIB18 Stopping sight distance is the sum of two distances: the distance traversed by the vehicle from the instant the driver sights an object necessitating a stop to the instant the brakes are applied and the distance required to stop the vehicle from the instant brake application begins. ", "geometryType": "esriGeometryPolyline", "sourceSpatialReference": { "wkid": 6923, "latestWkid": 6923, "xyTolerance": 0.003280833333333, "zTolerance": 0.001, "mTolerance": 6.21369949E-7, "falseX": -120729000, "falseY": -94795000, "xyUnits": 3048.0060960152887, "falseZ": -100000, "zUnits": 10000, "falseM": -100000, "mUnits": 1.6093472173863573E7 }, "copyrightText": "KDOT", "parentLayer": null, "subLayers": [], "minScale": 0, "maxScale": 0, "referenceScale": 0.0, "drawingInfo": { "renderer": { "type": "simple", "symbol": { "type": "esriSLS", "style": "esriSLSSolid", "color": [ 56, 168, 0, 255 ], "width": 3 } }, "scaleSymbols": true, "transparency": 0, "labelingInfo": null }, "defaultVisibility": true, "extent": { "xmin": 1519240.3332867175, "ymin": 538265.2542511523, "xmax": 2347933.023338124, "ymax": 1181041.7413327396, "spatialReference": { "wkid": 6923, "latestWkid": 6923, "xyTolerance": 0.003280833333333, "zTolerance": 0.001, "mTolerance": 6.21369949E-7, "falseX": -120729000, "falseY": -94795000, "xyUnits": 3048.0060960121928, "falseZ": -100000, "zUnits": 10000, "falseM": -100000, "mUnits": 10000 } }, "hasAttachments": false, "htmlPopupType": "esriServerHTMLPopupTypeAsHTMLText", "displayField": "EventID", "typeIdField": null, "subtypeFieldName": null, "subtypeField": null, "defaultSubtypeCode": null, "fields": [ { "name": "OBJECTID", "type": "esriFieldTypeOID", "alias": "OBJECTID", "domain": null }, { "name": "Shape", "type": "esriFieldTypeGeometry", "alias": "Shape", "domain": null }, { "name": "Shape.STLength()", "type": "esriFieldTypeDouble", "alias": "Shape_Length", "domain": null }, { "name": "EventID", "type": "esriFieldTypeString", "alias": "EventID", "length": 38, "domain": null }, { "name": "RouteID", "type": "esriFieldTypeString", "alias": "RouteID", "length": 16, "domain": null }, { "name": "FromMeasure", "type": "esriFieldTypeDouble", "alias": "FromMeasure", "domain": null }, { "name": "ToMeasure", "type": "esriFieldTypeDouble", "alias": "ToMeasure", "domain": null }, { "name": "WorkZoneSigCriteria", "type": "esriFieldTypeString", "alias": "WorkZoneSigCriteria", "length": 2, "domain": { "type": "codedValue", "name": "dWorkZoneSigCriteria", "description": "WorkZoneSigCriteriaDesc", "codedValues": [ { "name": "District Engineer Discretion", "code": "1" }, { "name": "Criteria met within TMA or MPO", "code": "2" } ], "mergePolicy": "esriMPTDefaultValue", "splitPolicy": "esriSPTDefaultValue" } }, { "name": "WorkZoneSig", "type": "esriFieldTypeString", "alias": "WorkZoneSig", "length": 3, "domain": { "type": "codedValue", "name": "dWorkZoneSig", "description": "WorkZoneSigDesc", "codedValues": [ { "name": "YES", "code": "1" }, { "name": "TBD", "code": "2" } ], "mergePolicy": "esriMPTDefaultValue", "splitPolicy": "esriSPTDefaultValue" } }, { "name": "WorkZoneType", "type": "esriFieldTypeString", "alias": "WorkZoneType", "length": 20, "domain": null }, { "name": "WorkZoneSource", "type": "esriFieldTypeString", "alias": "WorkZoneSource", "length": 20, "domain": null }, { "name": "WorkZoneID", "type": "esriFieldTypeString", "alias": "WorkZoneID", "length": 20, "domain": null }, { "name": "WorkZoneStatus", "type": "esriFieldTypeString", "alias": "WorkZoneStatus", "length": 20, "domain": null }, { "name": "InventoryStartDate", "type": "esriFieldTypeDate", "alias": "InventoryStartDate", "length": 8, "domain": null }, { "name": "LRSFromDate", "type": "esriFieldTypeDate", "alias": "LRSFromDate", "length": 8, "domain": null }, { "name": "LRSToDate", "type": "esriFieldTypeDate", "alias": "LRSToDate", "length": 8, "domain": null }, { "name": "CreatedUser", "type": "esriFieldTypeString", "alias": "CreatedUser", "length": 20, "domain": null }, { "name": "LastEditedUser", "type": "esriFieldTypeString", "alias": "LastEditedUser", "length": 20, "domain": null }, { "name": "CreatedDate", "type": "esriFieldTypeDate", "alias": "CreatedDate", "length": 8, "domain": null }, { "name": "LastEditedDate", "type": "esriFieldTypeDate", "alias": "LastEditedDate", "length": 8, "domain": null }, { "name": "SourceCIT", "type": "esriFieldTypeString", "alias": "SourceCIT", "length": 20, "domain": { "type": "codedValue", "name": "dSourceCIT", "description": "SourceCITDesc", "codedValues": [ { "name": "Aerial Photography - Unknown Spec", "code": "AP" }, { "name": "Aerial Photography - ASPRS II or higher spec", "code": "AP2" }, { "name": "Aerial Photography - DOQQ imagery", "code": "AP3" }, { "name": "Aerial Photography - USDA FSA NAIP Imagery", "code": "AP4" }, { "name": "Apple Device", "code": "APL" }, { "name": "Assumed", "code": "ASD" }, { "name": "AADT Route Average", "code": "AVG" }, { "name": "URS Curve Application", "code": "C2" }, { "name": "Curve Tool", "code": "C3" }, { "name": "AADT City with Factor Applied", "code": "CITY" }, { "name": "CANSYS II Legacy, Migrated", "code": "CLM" }, { "name": "AADT Portable Counters", "code": "CVRG" }, { "name": "AADT Portable Counters with Factor Applied", "code": "CVRGFCT" }, { "name": "Digital Elevation Model, 10M or equivalent", "code": "DEM" }, { "name": "Derived", "code": "DER" }, { "name": "Design Standards Shoulder Width \\\\CANSYSTEST\\CANSYS\\KDOT\\DOCUMENTATION\\KDOT USER DOCUMENTATION\\METADATA\\STANDARDSHOULDERWIDTHTABLE.PDF", "code": "DSSW" }, { "name": "Design Plan", "code": "DTD" }, { "name": "KDOT Surveyor", "code": "DTS" }, { "name": "Estimated", "code": "Est" }, { "name": "AADT Flowmap", "code": "FLOW" }, { "name": "NAIP 2012", "code": "FS12" }, { "name": "NAIP 2015", "code": "FS15" }, { "name": "GNIS", "code": "GN" }, { "name": "Google", "code": "GOOG" }, { "name": "Other Handheld GPS", "code": "GPS1" }, { "name": "HPMS Data for Migration", "code": "HPMS" }, { "name": "KDOT Data Owner", "code": "KDO" }, { "name": "KDOT Official Notification or Contract", "code": "KOC" }, { "name": "Aerial Imagery", "code": "KP15" }, { "name": "Project Plans", "code": "KPP" }, { "name": "KDOT Notification, Field Verified", "code": "KUC" }, { "name": "LiDAR Derived, High Altitude USGS Spec", "code": "Li" }, { "name": "LiDAR Derived, Low Altitude, Manned, Transportation Spec", "code": "LiM" }, { "name": "LiDAR Derived, Low Altitude, UAS, Transportation Spec", "code": "LiU" }, { "name": "Local Agency Data Steward", "code": "LPA" }, { "name": "AADT Major-Minor Collectors", "code": "MAJMIN" }, { "name": "Unknown", "code": "NA" }, { "name": "No Best Fit Obtained", "code": "NBFO" }, { "name": "NG911 Data Steward", "code": "NG" }, { "name": "Non-State Section, Migrated", "code": "NSSect" }, { "name": "Notified", "code": "NTF" }, { "name": "AADT Non-State Urban", "code": "NUSYS" }, { "name": "Other Video or Photo Source", "code": "PHO" }, { "name": "Project", "code": "PR" }, { "name": "Interchange Ramp for Migration", "code": "RAMP" }, { "name": "AADT Ramp Data", "code": "RAMPS" }, { "name": "Other State Agency Data Steward", "code": "SA" }, { "name": "Samsung Device", "code": "SAM" }, { "name": "Aerial Imagery", "code": "SDX15" }, { "name": "KDOT Videolog", "code": "VL" }, { "name": "PMS videolog http://dtpml004.ksdot.org/npcve/", "code": "VLPMS" }, { "name": "Construction Plans", "code": "Y" } ], "mergePolicy": "esriMPTDefaultValue", "splitPolicy": "esriSPTDefaultValue" } }, { "name": "LocError", "type": "esriFieldTypeString", "alias": "LocError", "length": 100, "domain": null }, { "name": "GlobalID", "type": "esriFieldTypeGlobalID", "alias": "GlobalID", "length": 38, "domain": null } ], "geometryField": { "name": "Shape", "type": "esriFieldTypeGeometry", "alias": "Shape" }, "indexes": [ { "name": "R122_pk", "fields": "OBJECTID", "isAscending": true, "isUnique": true, "description": "" }, { "name": "UUID_122", "fields": "GlobalID", "isAscending": true, "isUnique": true, "description": "" }, { "name": "S109_idx", "fields": "Shape", "isAscending": true, "isUnique": true, "description": "" } ], "subtypes": [], "relationships": [], "canModifyLayer": true, "canScaleSymbols": false, "hasLabels": false, "capabilities": "Query,Map,Data", "maxRecordCount": 2000, "supportsStatistics": true, "supportsExceedsLimitStatistics": true, "supportsAdvancedQueries": true, "hasZ": true, "hasM": true, "supportedQueryFormats": "JSON, geoJSON, PBF", "isDataVersioned": false, "ownershipBasedAccessControlForFeatures": {"allowOthersToQuery": true}, "useStandardizedQueries": true, "advancedQueryCapabilities": { "useStandardizedQueries": true, "supportsStatistics": true, "supportsPercentileStatistics": true, "supportsHavingClause": true, "supportsOrderBy": true, "supportsDistinct": true, "supportsCountDistinct": true, "supportsPagination": true, "supportsTrueCurve": true, "supportsQueryWithDatumTransformation": true, "supportsReturningQueryExtent": true, "supportsQueryWithDistance": true, "supportsSqlExpression": true }, "supportsDatumTransformation": true, "dateFieldsTimeReference": null, "hasMetadata": true, "isDataArchived": false, "archivingInfo": { "supportsQueryWithHistoricMoment": false, "startArchivingMoment": -1 }, "supportsCoordinatesQuantization": true, "supportsDynamicLegends": true, "serviceItemId": "86b0c6b0f7864ecb976cc147c998e02c" }