ArcGIS REST Services Directory Login
JSON

Layer: Urban Jurisdiction (ID: 0)

Name: Urban Jurisdiction

Display Field: EventID

Type: Feature Layer

Geometry Type: esriGeometryPolyline

Description: BehaviorsActivity / RulesCalibrateRoute - Stay PutReverseRoute - Stay PutRetireRoute - SnapExtendRoute - Stay PutReassignRoute - SnapRealignRoute - Stay PutRealignOverlap - SnapCartoRealignRoute - Honor Route MeasureFrom HPMS Field ManualUrban_Code (Urban Code) Description: The U.S. Census Urban Area Code. Use: For the querying and analysis of data (e.g., transportation performance management (TPM) metrics, Federal-aid project information, etc.) by the unique identification of a State’s urbanized areas, and generically by small urban or rural areas. 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 & RampsKDT Process of Defining Urban/Rural (Urban Area Boundary)(as described by Bill Hughes, P.E, Bureau of Transportation Planning)According to he HPMS/FunClass guidance we start with the Census urban areas – all urban tracts must be included in the transportation UAB. We also try to include all incorporated areas of the urban city, though an outlying island for the water plant or airport can be ignored if it has no classified roads. From there, we look for transportation assets to use as the UAB boundary. Census tracts give us jagged borders that cross and re-cross roads, as well as depend on ‘city limits’ and other imaginary boundaries that are too hard to find in the field. Where a segment of roadway is crossed by the Census boundary we will extend the UAB along that road to a cross-road, river bridge, railroad crossing, or other fixed asset. In the extreme, we might use a survey corner or extend a road alignment that doesn’t actually have an intersection but those are not ideal. We will also use rivers as they form a natural geographic barrier to urban spread. The ideal border road should be just beyond the commercial development; in keeping with the 5-10 year horizon of Functional Classification, as well as to avoid having equivalent commercial development on opposite sides of the street in distinct Character areas.

Service Item Id: e639e696b67e411e90cc1bebcfd4c9c6

Copyright Text: KDOT

Default Visibility: true

MaxRecordCount: 2000

MaxSelectionCount: 2000

Supported Query Formats: JSON, geoJSON, PBF

Min Scale: 0.0

Max Scale: 0.0

Supports Advanced Queries: true

Supports Statistics: true

Has Labels: false

Can Modify Layer: true

Can Scale Symbols: false

Use Standardized Queries: true

Supports Datum Transformation: true

Extent:
Drawing Info: Feature Draw Order: Advanced Query Capabilities:
HasZ: true

HasM: true

Has Attachments: false

HTML Popup Type: esriServerHTMLPopupTypeAsHTMLText

Type ID Field: null

Fields:
Supported Operations:   Query   Query Attachments   Query Analytic   Generate Renderer   Return Updates

  Iteminfo   Thumbnail   Metadata