Description: WHAT: This dataset contains point locations of public electric vehicle charging stations across the State of Colorado. Each point represents a single publicly accessible EV charging location with attributes including connector type, fuel/charger type, accessibility hours, and contact phone number. The dataset reflects current conditions as of the most recent monthly pull and is statewide in extent — coverage is not limited to Grand Junction or Mesa County. Private charging stations (residential chargers, workplace-only chargers not open to the public) are excluded from the source dataset and therefore from this layer.SOURCE & METHODOLOGY: Source records originate from the U.S. Department of Energy's Alternative Fuels Data Center (AFDC), specifically its Alternative Fueling Station Locator (https://afdc.energy.gov/stations). A scheduled Python script pulls the latest station records for Colorado, along with their latitude and longitude coordinates, and loads them into the City's SDE as point features. The City of Grand Junction does not add or edit stations directly — all content originates with the AFDC. The dataset was first added to the City's web map by the GIS Division in 2020. No City-side QA is performed between monthly pulls; the AFDC is treated as the authoritative source.KEY ATTRIBUTES: CONN_TYPE identifies the connector type available at each station (e.g., J1772, CCS, CHAdeMO, Tesla), which determines vehicle compatibility. FUEL_TYPE identifies the charger type (Level 1, Level 2, DC Fast). ACC_TIME describes the station's public accessibility hours. PHONE provides a contact phone number for the station. STN prefix on field names refers to "station." Additional fields include URL (station website), EV pricing information, and EV_DC_FAST_COUNT (the number of DC fast chargers at the station); these three are only partially populated across the layer because they depend on what each station operator has reported to the AFDC.UPDATE CYCLE: Updated once a month on the first of the month via an automated Python script. The AFDC is the update trigger — the City's script simply pulls the current AFDC state for Colorado each month. No manual updates are performed. KNOWN LIMITATIONS: This dataset reflects publicly accessible charging stations only, as reported to the AFDC. Private residential chargers, restricted-access workplace chargers not open to the public, and any station operator who has not registered with the AFDC will not appear in the layer. Data currency depends on both the AFDC's data collection cadence and the City's monthly refresh — a station that opens or closes mid-month will not appear in the City's copy until the next scheduled pull. Positional accuracy is inherited from the latitude and longitude coordinates provided by the AFDC and has not been independently verified by the City. Several attributes (URL, EV pricing, EV_DC_FAST_COUNT) are only partially populated because they depend on voluntary reporting by station operators; absence of a value does not mean the attribute doesn't apply. The layer covers the entire state of Colorado, not just Grand Junction or Mesa County — users doing local analysis should filter accordingly.CONTACT: City of Grand Junction GIS Division. For data questions or to report errors in the City's copy, email gis@gjcity.org. For questions about the underlying station data itself, to report inaccuracies at specific stations, or to explore the source data directly, users should consult the U.S. Department of Energy's Alternative Fuels Data Center at https://afdc.energy.gov/stations.
Service Item Id: 19408163c97c4152b7c95ed854e26e1b
Copyright Text: Source data: U.S. Department of Energy, Alternative Fuels Data Center (AFDC), Alternative Fueling Station Locator. Pulled monthly, geocoded, and maintained by the City of Grand Junction GIS Division for use by the Community Development Department's Sustainability Council.
Color: [0, 0, 0, 255] Background Color: N/A Outline Color: N/A Vertical Alignment: bottom Horizontal Alignment: left Right to Left: false Angle: 0 XOffset: 0 YOffset: 0 Size: 10 Font Family: Tahoma Font Style: normal Font Weight: normal Font Decoration: none
Min. Scale: 10000.0 Max. Scale: 0.0
Feature Draw Order:
N/A
Advanced Query Capabilities:
Supports Statistics: true
Supports OrderBy: true
Supports Distinct: true
Supports Pagination: true
Supports Result Pagination Token: false
Supports TrueCurve: true
Supports Returning Query Extent: true
Supports Query With Distance: true
Supports Sql Expression: true
Supports Query With ResultType: true
Supports Returning Geometry Centroid: false
Supports Binning LOD: false
Supports Query With LOD Spatial Reference: false
Supports Percentile Statistics: true
Supports Having Clause: true
Supports Count Distinct: true
Supports Time Relation: true
Supports Sql Format: false
Supports Query Analytic: true
Supports Query With Cache Hint: false
Supports Query With Current User: true
Supports Query With Result Type: true
HasZ: false
HasM: false
Has Attachments: false
Has Last Edit Time: false
HTML Popup Type: esriServerHTMLPopupTypeAsHTMLText
Color: [0, 0, 0, 255] Background Color: N/A Outline Color: N/A Vertical Alignment: bottom Horizontal Alignment: left Right to Left: false Angle: 0 XOffset: 0 YOffset: 0 Size: 10 Font Family: Tahoma Font Style: normal Font Weight: normal Font Decoration: none
Min. Scale: 10000.0 Max. Scale: 0.0
Feature Draw Order:
N/A
Advanced Query Capabilities:
Supports Statistics: true
Supports OrderBy: true
Supports Distinct: true
Supports Pagination: true
Supports Result Pagination Token: false
Supports TrueCurve: true
Supports Returning Query Extent: true
Supports Query With Distance: true
Supports Sql Expression: true
Supports Query With ResultType: true
Supports Returning Geometry Centroid: false
Supports Binning LOD: false
Supports Query With LOD Spatial Reference: false
Supports Percentile Statistics: true
Supports Having Clause: true
Supports Count Distinct: true
Supports Time Relation: true
Supports Sql Format: false
Supports Query Analytic: true
Supports Query With Cache Hint: false
Supports Query With Current User: true
Supports Query With Result Type: true
HasZ: false
HasM: false
Has Attachments: false
Has Last Edit Time: false
HTML Popup Type: esriServerHTMLPopupTypeAsHTMLText
Description: WHAT: This dataset contains line features representing trails managed by the Bureau of Land Management (BLM) across the State of Colorado, along with trails managed by Mesa County and the Old Spanish Trail. The layer is a filtered subset of the broader BLM trails dataset, queried by managing unit to show only BLM, Mesa County, and Old Spanish Trail records. Coverage is statewide — not limited to Grand Junction or Mesa County — and reflects conditions as of the City's 2023 refresh.SOURCE & METHODOLOGY: Source records originate from the Bureau of Land Management's Geospatial Business Platform Open Data Portal. The City of Grand Junction GIS Division first added the dataset to the City's database in 2003 and has periodically refreshed it from the BLM source. Records are entered manually into the SDE and filtered by managing unit to include only BLM trails, Mesa County trails, and the Old Spanish Trail. The City does not create or edit trail geometry — the BLM is the authoritative source. No City-side QA process is performed between refreshes.KEY ATTRIBUTES: MANAGING_U identifies the managing unit responsible for each trail segment (used as the filter for this layer). ROUTE_NAME identifies the trail by name. SURFACE indicates the trail surface type (e.g., dirt, gravel, paved). MILES records the trail segment's distance in miles. Many other fields in the schema are inherited from the BLM source; some are empty, and some of the important fields are only partially populated depending on what the BLM has documented for each trail.UPDATE CYCLE: Historically updated on a yearly cycle by the GIS Division, though no update is currently scheduled. Last updated in 2023. Any future update would pull the current BLM state and re-apply the managing-unit filter.KNOWN LIMITATIONS: This dataset is a filtered subset of the BLM's Colorado-wide trails data and reflects only trails whose managing unit is the BLM, Mesa County, or the Old Spanish Trail. Trails managed by other agencies (National Forest Service, National Park Service, Colorado Parks and Wildlife, private landowners, or municipal parks) are not included and require separate datasets. Positional accuracy is inherited from the BLM source and is intended for visual representation rather than survey-grade or navigational use — users should not rely on this data for wayfinding, backcountry navigation, or legal boundary determination. The City's copy has not been updated since 2023, so trails opened, rerouted, closed, or reclassified since then will not be reflected until the layer is refreshed. Many attribute fields are empty or partially populated based on what the BLM has documented; absence of a value should not be interpreted as meaningful information about the trail. The layer is statewide in extent — users doing local analysis should filter to Mesa County or Grand Junction as appropriate.CONTACT: City of Grand Junction GIS Division. For data questions or to report errors in the City's copy, email gis@gjcity.org. For authoritative trail data, corrections to trail geometry or attributes, or questions about trail status and access, users should consult the Bureau of Land Management directly.
Service Item Id: 19408163c97c4152b7c95ed854e26e1b
Copyright Text: Source data: U.S. Bureau of Land Management (BLM), Geospatial Business Platform Open Data Portal. Filtered to BLM-managed trails, Mesa County-managed trails, and the Old Spanish Trail; maintained by the City of Grand Junction GIS Division.
Color: [0, 0, 0, 255] Background Color: N/A Outline Color: N/A Vertical Alignment: bottom Horizontal Alignment: left Right to Left: false Angle: 0 XOffset: 0 YOffset: 0 Size: 10 Font Family: Tahoma Font Style: normal Font Weight: normal Font Decoration: none
Min. Scale: 20000.0 Max. Scale: 0.0
Feature Draw Order:
N/A
Advanced Query Capabilities:
Supports Statistics: true
Supports OrderBy: true
Supports Distinct: true
Supports Pagination: true
Supports Result Pagination Token: false
Supports TrueCurve: true
Supports Returning Query Extent: true
Supports Query With Distance: true
Supports Sql Expression: true
Supports Query With ResultType: true
Supports Returning Geometry Centroid: false
Supports Binning LOD: false
Supports Query With LOD Spatial Reference: false
Supports Percentile Statistics: true
Supports Having Clause: true
Supports Count Distinct: true
Supports Time Relation: true
Supports Sql Format: false
Supports Query Analytic: true
Supports Query With Cache Hint: false
Supports Query With Current User: true
Supports Query With Result Type: true
HasZ: false
HasM: false
Has Attachments: false
Has Last Edit Time: false
HTML Popup Type: esriServerHTMLPopupTypeAsHTMLText
Color: [0, 0, 0, 255] Background Color: N/A Outline Color: N/A Vertical Alignment: bottom Horizontal Alignment: left Right to Left: false Angle: 0 XOffset: 0 YOffset: 0 Size: 10 Font Family: Tahoma Font Style: normal Font Weight: normal Font Decoration: none
Min. Scale: 20000.0 Max. Scale: 0.0
Feature Draw Order:
N/A
Advanced Query Capabilities:
Supports Statistics: true
Supports OrderBy: true
Supports Distinct: true
Supports Pagination: true
Supports Result Pagination Token: false
Supports TrueCurve: true
Supports Returning Query Extent: true
Supports Query With Distance: true
Supports Sql Expression: true
Supports Query With ResultType: true
Supports Returning Geometry Centroid: false
Supports Binning LOD: false
Supports Query With LOD Spatial Reference: false
Supports Percentile Statistics: true
Supports Having Clause: true
Supports Count Distinct: true
Supports Time Relation: true
Supports Sql Format: false
Supports Query Analytic: true
Supports Query With Cache Hint: false
Supports Query With Current User: true
Supports Query With Result Type: true
HasZ: false
HasM: false
Has Attachments: false
Has Last Edit Time: false
HTML Popup Type: esriServerHTMLPopupTypeAsHTMLText
Description: The layer was developed historically for use in emergency response. Each segment represents a street centerline and has information about name, and emergency response information as well. The dataset is also used for network modeling purposes.
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.
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.
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.
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.
Description: WHAT: This dataset contains line features representing bicycle corridor priorities within the City of Grand Junction, produced as part of the Bicycle and Pedestrian Plan. Each line segment represents a candidate corridor for bicycle infrastructure investment along the city's main arterials and collectors, carrying a priority rank and a recommended facility type. Coverage is citywide, limited to main arterials and collectors — the layer does not represent every street eligible for bicycle infrastructure and is not a facilities inventory of existing bike lanes. The layer reflects a 2022 snapshot of analysis and priorities and has not been updated since.SOURCE & METHODOLOGY: The dataset was created in 2023 by a third-party consultant hired by the City of Grand Junction Community Development Mobility Division. The consultant analyzed Grand Junction's active transportation corridors and produced priority rankings and facility-type recommendations based on factors including proximity to schools, presence of stop signs and traffic signals, proximity to grocery stores, and other trip-attraction and safety inputs. The consultant applied its own internal QA process before delivery. The GIS Division and the Community Development Mobility team subsequently reviewed the delivered shapefile and edited it to fit the City's SDE schema before publication.KEY ATTRIBUTES: FULL_NAME identifies the corridor, typically by the street name it follows. PRIORITY carries the priority ranking with values of high, medium, or low, indicating the relative importance of maintenance or construction for each segment. FACILITYRE contains the recommended facility type for each segment, with coded values including BL (bike lane), BBL (buffered bike lane), PBL (protected bike lane), CT (cycle track), T (trail), and NB (neighborhood path). Several count fields carry the underlying inputs the consultant used to derive priority scores, including counts of schools, stop signs, stop lights, and grocery stores along or near each segment.UPDATE CYCLE: Not on a recurring update cycle. The dataset is a 2023 point-in-time analysis and has not been updated since original delivery. Any future updates would be triggered by request and performed by the GIS Division, but no updates are currently scheduled.KNOWN LIMITATIONS: This dataset represents 2023 conditions and 2023 analysis; changes in the street network, land use, or trip-generating attractions since 2023 are not reflected in the priority rankings or facility recommendations. The layer covers main arterials and collectors only and should not be interpreted as a comprehensive review of every street where bicycle infrastructure could be considered. Priority rankings and facility-type recommendations reflect the consultant's analytical framework at the time of the study and are advisory — they do not represent adopted City policy or committed investment. This is a planning-input layer, not an inventory of existing bicycle infrastructure; a segment marked with a facility type recommendation does not mean that facility currently exists there. Positional accuracy is inherited from the street centerlines the corridors were digitized against. Users should confirm current conditions and policy direction with the Community Development department before relying on this data for programming or investment decisions.CONTACT: City of Grand Junction GIS Division. For data questions or to report errors, email gis@gjcity.org. Questions about the underlying analysis, the consultant's methodology, or current City direction on bicycle infrastructure investment should be directed to the Community Development department.
Service Item Id: 19408163c97c4152b7c95ed854e26e1b
Copyright Text: Source data: Third-party consultant hired by the City of Grand Junction Community Development Mobility Division in 2023. Reviewed, edited for SDE compatibility, and maintained by the City of Grand Junction GIS Division in coordination with the Community Development Mobility team.
Description: WHAT: This dataset contains line features representing sidewalk priorities within the City of Grand Junction, produced as part of the Bicycle and Pedestrian Plan. Each line segment represents either an existing sidewalk along a city road or a proposed sidewalk location identified by the consultant, along with a priority ranking indicating the relative importance of construction or repair. Coverage is citywide. The layer reflects a 2023 snapshot and has not been updated since.SOURCE & METHODOLOGY: The dataset was created in 2023 by a third-party consultant hired by the City of Grand Junction Community Development Mobility Division. The consultant applied its own internal QA process before delivery. The GIS Division received the completed shapefile from the consultant and manually entered it into the City's SDE; both the GIS Division and the Community Development Department reviewed the data before publication.KEY ATTRIBUTES: FULL_NAME identifies the road the sidewalk segment follows. ROAD provides the road name reference. CLASS identifies the road classification for the segment. SIDEWALK designates the status or type of sidewalk (existing, proposed, or type category). PRIORITY carries the priority ranking with values of high, medium, or low, indicating the relative importance of construction or repair for each segment. TYPE provides additional categorization of the segment. Users should rely on these six fields as the primary attributes of the layer.UPDATE CYCLE: Not on a recurring update cycle. The dataset is a 2023 point-in-time analysis and has not been updated since original delivery. Any future updates would be triggered by request and performed by the GIS Division, but no updates are currently scheduled.KNOWN LIMITATIONS: This dataset represents 2023 conditions and 2023 analysis; changes in the sidewalk network, street network, or land use since 2023 are not reflected in the priority rankings or proposed sidewalk locations. Priority rankings reflect the consultant's analytical framework at the time of the study and are advisory — they do not represent adopted City policy or committed investment. This is a planning-input layer, not a comprehensive inventory of existing sidewalks; a segment identified as "proposed" does not mean construction has been authorized, and a segment identified as "existing" reflects 2023 conditions rather than current conditions. Positional accuracy is inherited from the street centerlines the sidewalk segments were digitized against. Users should confirm current conditions and policy direction with the Community Development department before relying on this data for programming or investment decisions.CONTACT: City of Grand Junction GIS Division. For data questions or to report errors, email gis@gjcity.org. Questions about the underlying analysis, the consultant's methodology, or current City direction on sidewalk infrastructure investment should be directed to the Community Development department.
Service Item Id: 19408163c97c4152b7c95ed854e26e1b
Copyright Text: Source data: Third-party consultant hired by the City of Grand Junction Community Development Mobility Division in 2023. Reviewed, edited for SDE compatibility, and maintained by the City of Grand Junction GIS Division in coordination with the Community Development Department.
Description: WHAT: This dataset contains line features representing sidewalk priorities within the City of Grand Junction, produced as part of the Bicycle and Pedestrian Plan. Each line segment represents either an existing sidewalk along a city road or a proposed sidewalk location identified by the consultant, along with a priority ranking indicating the relative importance of construction or repair. Coverage is citywide. The layer reflects a 2023 snapshot and has not been updated since.SOURCE & METHODOLOGY: The dataset was created in 2023 by a third-party consultant hired by the City of Grand Junction Community Development Mobility Division. The consultant applied its own internal QA process before delivery. The GIS Division received the completed shapefile from the consultant and manually entered it into the City's SDE; both the GIS Division and the Community Development Department reviewed the data before publication.KEY ATTRIBUTES: FULL_NAME identifies the road the sidewalk segment follows. ROAD provides the road name reference. CLASS identifies the road classification for the segment. SIDEWALK designates the status or type of sidewalk (existing, proposed, or type category). PRIORITY carries the priority ranking with values of high, medium, or low, indicating the relative importance of construction or repair for each segment. TYPE provides additional categorization of the segment. Users should rely on these six fields as the primary attributes of the layer.UPDATE CYCLE: Not on a recurring update cycle. The dataset is a 2023 point-in-time analysis and has not been updated since original delivery. Any future updates would be triggered by request and performed by the GIS Division, but no updates are currently scheduled.KNOWN LIMITATIONS: This dataset represents 2023 conditions and 2023 analysis; changes in the sidewalk network, street network, or land use since 2023 are not reflected in the priority rankings or proposed sidewalk locations. Priority rankings reflect the consultant's analytical framework at the time of the study and are advisory — they do not represent adopted City policy or committed investment. This is a planning-input layer, not a comprehensive inventory of existing sidewalks; a segment identified as "proposed" does not mean construction has been authorized, and a segment identified as "existing" reflects 2023 conditions rather than current conditions. Positional accuracy is inherited from the street centerlines the sidewalk segments were digitized against. Users should confirm current conditions and policy direction with the Community Development department before relying on this data for programming or investment decisions.CONTACT: City of Grand Junction GIS Division. For data questions or to report errors, email gis@gjcity.org. Questions about the underlying analysis, the consultant's methodology, or current City direction on sidewalk infrastructure investment should be directed to the Community Development department.
Service Item Id: 19408163c97c4152b7c95ed854e26e1b
Copyright Text: Source data: Third-party consultant hired by the City of Grand Junction Community Development Mobility Division in 2023. Reviewed, edited for SDE compatibility, and maintained by the City of Grand Junction GIS Division in coordination with the Community Development Department.
Description: The street segments are typically drawn between intersections and form the network of streets primarily within the City Limits. The streets within the city limits are streets that are maintained by the City and part of the maintenance schedule for general maintenance.
Description: The street segments are typically drawn between intersections and form the network of streets primarily within the City Limits. The streets within the city limits are streets that are maintained by the City and part of the maintenance schedule for general maintenance.
Description: WHAT: This dataset contains point locations of public facilities that serve the Grand Junction community, including schools, fire stations, police stations, hospitals, arts and entertainment centers, parking areas, and other civic and public-use sites. Coverage spans Mesa County and the City of Grand Junction. The dataset represents current conditions and is intended as a general-purpose reference layer used both internally and on public-facing City maps, where certain categories (such as bridges and trailheads) may be filtered out depending on the map's audience.SOURCE & METHODOLOGY: Records originate from City government information and from each facility's publicly available information, including address, facility type, and website URLs. New entries are added through manual data entry by the GIS Division. Created by the GIS Division in approximately 2005. Before a new facility is added to the published map, its existence is verified internally with City staff and the GIS Division gathers all relevant attribute information.KEY ATTRIBUTES: FACILITY_N holds the facility name. TYPE identifies the category of facility (school, fire station, hospital, etc.). URL links to the facility's website where available. Other fields exist in the schema but are less central to typical use.UPDATE CYCLE: Updated as needed when a new public facility is built, acquired, or otherwise brought into service. There is no fixed schedule; updates are event-driven and performed by the GIS Division. Last updated March 2026.KNOWN LIMITATIONS: Positional accuracy is not survey-grade — points are digitized from aerial imagery and should be treated as building- or property-level locations rather than precise coordinates. Facilities located outside the City of Grand Junction, in the wider county, may be less accurately positioned than those within city limits, where the GIS Division has more direct familiarity. The URL field is not populated for every facility; some facilities do not have a known public web presence. The dataset reflects facilities the GIS Division is aware of and has verified — a newly opened facility may not appear until staff are notified and verification is complete.CONTACT: City of Grand Junction GIS Division. For data questions or to report errors, email gis@gjcity.org.
Service Item Id: 19408163c97c4152b7c95ed854e26e1b
Copyright Text: Compiled and maintained by the City of Grand Junction GIS Division, drawing on City government records and publicly available facility information.
Description: The utility grid is used in naming many features stored in the asset management database. Each grid section measures 1/4 mile north to south and 1/2 mile east to west.
Color: [0, 0, 0, 255] Background Color: N/A Outline Color: N/A Vertical Alignment: bottom Horizontal Alignment: left Right to Left: false Angle: 0 XOffset: 0 YOffset: 0 Size: 14 Font Family: Arial Font Style: normal Font Weight: normal Font Decoration: none
Min. Scale: 0.0 Max. Scale: 0.0
Feature Draw Order:
N/A
Advanced Query Capabilities:
Supports Statistics: true
Supports OrderBy: true
Supports Distinct: true
Supports Pagination: true
Supports Result Pagination Token: false
Supports TrueCurve: true
Supports Returning Query Extent: true
Supports Query With Distance: true
Supports Sql Expression: true
Supports Query With ResultType: true
Supports Returning Geometry Centroid: false
Supports Binning LOD: false
Supports Query With LOD Spatial Reference: false
Supports Percentile Statistics: true
Supports Having Clause: true
Supports Count Distinct: true
Supports Time Relation: true
Supports Sql Format: false
Supports Query Analytic: true
Supports Query With Cache Hint: false
Supports Query With Current User: true
Supports Query With Result Type: true
Color: [0, 0, 0, 255] Background Color: N/A Outline Color: N/A Vertical Alignment: bottom Horizontal Alignment: left Right to Left: false Angle: 0 XOffset: 0 YOffset: 0 Size: 14 Font Family: Arial Font Style: normal Font Weight: normal Font Decoration: none
Min. Scale: 0.0 Max. Scale: 0.0
Feature Draw Order:
N/A
Advanced Query Capabilities:
Supports Statistics: true
Supports OrderBy: true
Supports Distinct: true
Supports Pagination: true
Supports Result Pagination Token: false
Supports TrueCurve: true
Supports Returning Query Extent: true
Supports Query With Distance: true
Supports Sql Expression: true
Supports Query With ResultType: true
Supports Returning Geometry Centroid: false
Supports Binning LOD: false
Supports Query With LOD Spatial Reference: false
Supports Percentile Statistics: true
Supports Having Clause: true
Supports Count Distinct: true
Supports Time Relation: true
Supports Sql Format: false
Supports Query Analytic: true
Supports Query With Cache Hint: false
Supports Query With Current User: true
Supports Query With Result Type: true
Color: [0, 0, 0, 255] Background Color: N/A Outline Color: N/A Vertical Alignment: bottom Horizontal Alignment: left Right to Left: false Angle: 0 XOffset: 0 YOffset: 0 Size: 14 Font Family: Arial Font Style: normal Font Weight: normal Font Decoration: none
Min. Scale: 0.0 Max. Scale: 0.0
Feature Draw Order:
N/A
Advanced Query Capabilities:
Supports Statistics: true
Supports OrderBy: true
Supports Distinct: true
Supports Pagination: true
Supports Result Pagination Token: false
Supports TrueCurve: true
Supports Returning Query Extent: true
Supports Query With Distance: true
Supports Sql Expression: true
Supports Query With ResultType: true
Supports Returning Geometry Centroid: false
Supports Binning LOD: false
Supports Query With LOD Spatial Reference: false
Supports Percentile Statistics: true
Supports Having Clause: true
Supports Count Distinct: true
Supports Time Relation: true
Supports Sql Format: false
Supports Query Analytic: true
Supports Query With Cache Hint: false
Supports Query With Current User: true
Supports Query With Result Type: true
Color: [0, 0, 0, 255] Background Color: N/A Outline Color: N/A Vertical Alignment: bottom Horizontal Alignment: left Right to Left: false Angle: 0 XOffset: 0 YOffset: 0 Size: 14 Font Family: Arial Font Style: normal Font Weight: normal Font Decoration: none
Min. Scale: 0.0 Max. Scale: 0.0
Feature Draw Order:
N/A
Advanced Query Capabilities:
Supports Statistics: true
Supports OrderBy: true
Supports Distinct: true
Supports Pagination: true
Supports Result Pagination Token: false
Supports TrueCurve: true
Supports Returning Query Extent: true
Supports Query With Distance: true
Supports Sql Expression: true
Supports Query With ResultType: true
Supports Returning Geometry Centroid: false
Supports Binning LOD: false
Supports Query With LOD Spatial Reference: false
Supports Percentile Statistics: true
Supports Having Clause: true
Supports Count Distinct: true
Supports Time Relation: true
Supports Sql Format: false
Supports Query Analytic: true
Supports Query With Cache Hint: false
Supports Query With Current User: true
Supports Query With Result Type: true
Color: [0, 0, 0, 255] Background Color: N/A Outline Color: N/A Vertical Alignment: bottom Horizontal Alignment: left Right to Left: false Angle: 0 XOffset: 0 YOffset: 0 Size: 14 Font Family: Arial Font Style: normal Font Weight: normal Font Decoration: none
Min. Scale: 0.0 Max. Scale: 0.0
Feature Draw Order:
N/A
Advanced Query Capabilities:
Supports Statistics: true
Supports OrderBy: true
Supports Distinct: true
Supports Pagination: true
Supports Result Pagination Token: false
Supports TrueCurve: true
Supports Returning Query Extent: true
Supports Query With Distance: true
Supports Sql Expression: true
Supports Query With ResultType: true
Supports Returning Geometry Centroid: false
Supports Binning LOD: false
Supports Query With LOD Spatial Reference: false
Supports Percentile Statistics: true
Supports Having Clause: true
Supports Count Distinct: true
Supports Time Relation: true
Supports Sql Format: false
Supports Query Analytic: true
Supports Query With Cache Hint: false
Supports Query With Current User: true
Supports Query With Result Type: true
Description: The Mesa County Transportation Planning Region and the Grand Valley Metropolitan Planning Organization are transportation policy-making organizations led by the GVRTC. The MPO planning mandates used for transportation planning in the urban area is loosely defined as Grand Junction, Fruita, Palisade, and the urban portions of unincorporated Mesa County. The TPR planning boundary covers all of Mesa County.