ArcGIS REST Services Directory Login
Home > services > CityMaps > Transportation_Map_External (MapServer) > Colorado Riverfront Trail API Reference
JSON

Layer: Colorado Riverfront Trail (ID: 240)

Parent Layer: Active Transportation Corridors

Name: Colorado Riverfront Trail

Display Field: TRAIL_NAME

Type: Feature Layer

Geometry Type: esriGeometryPolyline

Description: WHAT: This dataset contains line features representing the major active transportation corridors identified in the Grand Junction Active Transportation Plan, a component of the broader Grand Junction Circulation Plan. Corridors are drawn along streets, canals, and drainage ways, and are intended to provide critical, safe, continuous, and convenient connections for bicyclists and pedestrians. Coverage is citywide within the urban development boundary. The dataset reflects the current adopted corridor network. Corridors depicted in this layer are shown for planning purposes only — they guide future infrastructure, right-of-way, and easement decisions. Not all corridors are currently open to public use, and future routes along canals, ditches, and drainage corridors would be constructed in cooperation with the property owners and other parties holding use or easement rights along those alignments.SOURCE & METHODOLOGY: The corridor network originates from the Grand Junction Circulation Plan, reviewed by the Planning Commission on May 22, 2018, and adopted by the City Council through Ordinance 4808 on June 18, 2018. Source data is developed by the City of Grand Junction and Mesa County Planning Divisions, the Planning Commission, and City Council through the ordinance process. Line geometry is derived from the City's streets layer where corridors follow roads, and digitized from aerial imagery where corridors follow canals, drainage ways, or other non-road alignments. Changes are entered manually by the GIS Division after a City ordinance authorizing the change is passed; the ordinance process itself serves as the review and approval mechanism.KEY ATTRIBUTES: TYPE identifies the corridor category — canal corridor, road corridor, drainage way, or riverfront trail. STATUS indicates whether a corridor is existing or proposed; note that "proposed" corridors have been approved through the ordinance adoption but may not yet have been developed or opened to public use, so "proposed" should not be read as "not yet authorized." STATUS_2 provides additional detail on the type of non-motorized facility along or within a corridor, such as whether it consists of sidewalks along a road, easements along canals or drainage ways, or connections across private property. TRAIL_NAME contains the corridor's name, typically derived from the road corridor it parallels. COMMENTS provides free-text detail, including whether a trail is on both sides of a road, whether the road already exists, and other alignment-specific context.UPDATE CYCLE: Updated when a City ordinance modifies the corridor network. Updates are event-driven rather than scheduled and are performed by the GIS Division after ordinance passage. Last updated November 15, 2024. There is no scheduled next update; the layer will be revised whenever a subsequent ordinance changes the adopted corridors.KNOWN LIMITATIONS: This is a planning-purposes layer, not a facilities-inventory layer. Corridors shown on this map are not necessarily open, constructed, or accessible to the public — the STATUS field distinguishes existing from proposed alignments, but even some existing alignments may run across property where public access has not yet been secured. Future routes along canals, ditches, and drainage corridors depend on cooperation with property owners and holders of use or easement rights and are not guaranteed to be built as depicted. Positional accuracy varies with source: alignments derived from the streets layer inherit that layer's accuracy, while alignments digitized from aerial imagery are at aerial-photo accuracy. The COMMENTS and STATUS_2 fields are only partially populated across the layer, so absence of a value should not be read as meaningful information. This layer should not be used to determine public access rights, easement rights, or property boundaries.CONTACT: City of Grand Junction GIS Division. For data questions or to report errors, email gis@gjcity.org. Questions about the corridor network itself or the underlying Circulation Plan should be directed to the City's Planning Division.

Service Item Id: 19408163c97c4152b7c95ed854e26e1b

Copyright Text: Source data: Grand Junction Circulation Plan, adopted by City of Grand Junction Ordinance 4808 on June 18, 2018, following review by the Planning Commission on May 22, 2018. Corridor network developed by the City of Grand Junction Planning Division and Mesa County Planning Division in coordination with the Planning Commission and City Council. Digitized and maintained by the City of Grand Junction GIS Division.

Default Visibility: true

Max Result Window: N/A

Max Record Count: 2000

Standard Max Record Count No Geometry: 32000

Max Record Count Factor: 1

Standard MaxRecord Count: 8000

Tile Max Record Count: 4000

MaxSelectionCount: 2000

Supported Query Formats: JSON, geoJSON, PBF

Min Scale: 0.0

Max Scale: 0.0

Effective Min Scale: 250000

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: false

HasM: false

Has Attachments: false

Has Last Edit Time: false

HTML Popup Type: esriServerHTMLPopupTypeAsHTMLText

Type ID Field: N/A

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

  Iteminfo   Thumbnail   Metadata