ArcGIS REST Services Directory
JSON

Layer: Designated Climbing Access (ID:0)

View In:   Map Viewer

Name: Designated Climbing Access

Display Field: TrailName

Type: Feature Layer

Geometry Type: esriGeometryPolyline

Is View: true

Is Updatable View: true

Source Schema Changes Allowed: true

Sources

Description: This is a subset of the trails data and only includes the designated climbing access trails. Each trail has a unique TrlID, but has been broken up into segments, between junctions. For example, the Mesa trail The unique ID for each trail segment is within the "RID" field, which is unique over time. This means the RID of a trail segment can change over time, for example when a new alignment occurs. Each trail segment has a unique ID, within the "SegmentID" field, that persists over time.All trails are routes and have directionality and measures associated with them. The measures are based on the field measured trail length. Field measured trail length is stored in the "MeasuredFeet" field and GIS trail length is stored in the "shape.length" field. If there was no measured feet calculated it will read -9999. Currently the "Mileage" field is based on GIS trail length and not the field measured length. These data are topologically connected to the Trail Junctions feature class.Trails that are displayed have Display = Yes and the current date falls between DateFrom and Date To.When a segment is replaced, it is not removed. The DateFrom and DateTo are filled in to indicated it has been retired.This FC relates to the trailtblDogRegulations to display detailed dog regulations, based on RID (this is useful for the segments where the regulation changes). General dog regulation information is also included for each entire segement. Maintained in the FC are fields to indicate whether horses and bikes are allowed on each segment. This FC also relates to the trailtblTrailClassDesignedUse and trailtblManagedUse to display detailed trail management objectives, based on RID. There is a relative difficulty rating for each segmentData are primarily managed and edited by the Trails Research coordinator. Starting in 2019, 1/5 of the system is surveyed every year and any changes in alignments are made. Surveys are done using HETAP (High Efficiency Trail Assessment Program). Throughout the year any new trails that open are added once they have been surveyed.

Copyright Text: City of Boulder

Min. Scale: 0

Max. Scale: 0

Default Visibility: true

Max Record Count: 2000

Supported query Formats: JSON, geoJSON, PBF

Use Standardized Queries: True

Extent:

Drawing Info:

HasZ: false

HasM: true

Has Attachments: true

Has Geometry Properties: true

HTML Popup Type: esriServerHTMLPopupTypeAsHTMLText

Object ID Field: OBJECTID

Unique ID Field:

Global ID Field:

Type ID Field: STATUS

Fields:
Types:

Is Data Versioned: false

Has Contingent Values: false

Supports Rollback On Failure Parameter: true

Last Edit Date: 7/30/2026 7:57:55 PM

Schema Last Edit Date: 5/26/2026 1:42:38 PM

Data Last Edit Date: 7/30/2026 7:57:55 PM

Supported Operations:   Query   Query Pivot   Query Top Features   Query Analytic   Query Bins   Query Attachments   Generate Renderer   Validate SQL   Get Estimates   ConvertFormat