This data represents sinks in the Roaring Fork watershed to be used in a web map showing connected wetland and deepwater habitat features from the National Wetlands Inventory (NWI) dataset and various hydrographic features from the National Hydrography Dataset (NHD). A connectivity model was used to determine isolation/connectivity using a 0, 5, & 10 meter buffer of features. The general model process steps include:NWI was used as input data (other data can be added as input e.g. NHD) to determine "seed" jurisdictional waters. Currently, “seed” jurisdictional waters was defined as all Estuarine, Lacustrine, Tidal Riverine, Lower Perennial Riverine, and Upper Perennial Riverine NWI features.Select all NWI features in the study area that are "potential connectors". Currently, “potential connectors” were defined by excluding NWI features that had drier water regimes (temporarily flooded [A], continuously saturated [B], Continuously Saturated [D] and Seasonally Flooded/Saturated [E] and all Palustrine Farmed [Pf] features). Select all the "potential connectors" that intersect the "seed" data with the customized buffer distance. Continue iterations of step 3 by using the output (“seed” + intersecting “potential connectors”) as the “seed”. Iterations repeat until the count of selected NWI features does not increase.Select all NWI features (including non-connector wetlands) that intersect the final output of step 4. All selected features are exported as "Connected NWI Features...".Invert the selection and export remaining features as "Isolated NWI Features..."

This data represents isolated flowlines in the Roaring Fork watershed to be used in a web map showing connected wetland and deepwater habitat features from the National Wetlands Inventory (NWI) dataset and various hydrographic features from the National Hydrography Dataset (NHD). A connectivity model was used to determine isolation/connectivity using a 0, 5, & 10 meter buffer of features. The general model process steps include:NWI was used as input data (other data can be added as input e.g. NHD) to determine "seed" jurisdictional waters. Currently, “seed” jurisdictional waters was defined as all Estuarine, Lacustrine, Tidal Riverine, Lower Perennial Riverine, and Upper Perennial Riverine NWI features.Select all NWI features in the study area that are "potential connectors". Currently, “potential connectors” were defined by excluding NWI features that had drier water regimes (temporarily flooded [A], continuously saturated [B], Continuously Saturated [D] and Seasonally Flooded/Saturated [E] and all Palustrine Farmed [Pf] features). Select all the "potential connectors" that intersect the "seed" data with the customized buffer distance. Continue iterations of step 3 by using the output (“seed” + intersecting “potential connectors”) as the “seed”. Iterations repeat until the count of selected NWI features does not increase.Select all NWI features (including non-connector wetlands) that intersect the final output of step 4. All selected features are exported as "Connected NWI Features...".Invert the selection and export remaining features as "Isolated NWI Features..."

This data represents connected wetland and deepwater habitat features from the National Wetlands Inventory (NWI) dataset. A connectivity model was used to determine isolation/connectivity using a 0, 5, & 10 meter buffer of features. The general model process steps include:NWI was used as input data (other data can be added as input e.g. NHD) to determine "seed" jurisdictional waters. Currently, “seed” jurisdictional waters was defined as all Estuarine, Lacustrine, Tidal Riverine, Lower Perennial Riverine, and Upper Perennial Riverine NWI features.Select all NWI features in the study area that are "potential connectors". Currently, “potential connectors” were defined by excluding NWI features that had drier water regimes (temporarily flooded [A], continuously saturated [B], Continuously Saturated [D] and Seasonally Flooded/Saturated [E] and all Palustrine Farmed [Pf] features). Select all the "potential connectors" that intersect the "seed" data with the customized buffer distance. Continue iterations of step 3 by using the output (“seed” + intersecting “potential connectors”) as the “seed”. Iterations repeat until the count of selected NWI features does not increase.Select all NWI features (including non-connector wetlands) that intersect the final output of step 4. All selected features are exported as "Connected NWI Features...".Invert the selection and export remaining features as "Isolated NWI Features..."

This data represents the boundary of the Roaring Fork watershed, to be used in a web map showing connected wetland and deepwater habitat features from the National Wetlands Inventory (NWI) dataset and various hydrographic features from the National Hydrography Dataset (NHD). A connectivity model was used to determine isolation/connectivity using a 0, 5, & 10 meter buffer of features. The general model process steps include:NWI was used as input data (other data can be added as input e.g. NHD) to determine "seed" jurisdictional waters. Currently, “seed” jurisdictional waters was defined as all Estuarine, Lacustrine, Tidal Riverine, Lower Perennial Riverine, and Upper Perennial Riverine NWI features.Select all NWI features in the study area that are "potential connectors". Currently, “potential connectors” were defined by excluding NWI features that had drier water regimes (temporarily flooded [A], continuously saturated [B], Continuously Saturated [D] and Seasonally Flooded/Saturated [E] and all Palustrine Farmed [Pf] features). Select all the "potential connectors" that intersect the "seed" data with the customized buffer distance. Continue iterations of step 3 by using the output (“seed” + intersecting “potential connectors”) as the “seed”. Iterations repeat until the count of selected NWI features does not increase.Select all NWI features (including non-connector wetlands) that intersect the final output of step 4. All selected features are exported as "Connected NWI Features...".Invert the selection and export remaining features as "Isolated NWI Features..."

River Reach Habitat Quality (RFC 2008)

This layer was digitized in 2015 for the HRS Board using data from the 2008 State of the Watershed Report. This layer shows the quality of habitat surveyed by Delia Malone on selected reaches in the Roaring Fork Watershed. This data is intended as a reference for future research and planning, site specific conditions may vary. Strahler Steam Order numbers are also given for each river reach.

River Watch Sites

This layer was digitized in 2015 for the HRS Board using data from the Roaring Fork Conservancy. The layer shows River Watch sites where the RFC and partner organizations monitor stream health indicators. Active sites are marked with an “x” in the popup. To access the data please visit http://cpw.state.co.us/aboutus/Pages/RW-DataSheets.aspx and search for the river and monitoring site of interest. For more information about the program and additional summery data please contact the RFC www.roaringfork.org

Surface Water Realtime (USGS, CDSS)

This layer shows realtime telemetry gauges maintained by the United States Geological Survey and the Colorado Decision Support System. Click on the icon and then click on “more info” to link to the gauge website. This layer can be used to monitor stream flows and diversion tunnel flows (cfs). Please see the USGS and CDSS websites for more information.

Parcel Boundary (Pitkin County GIS 2015)

This layer identifies property boundaries in Pitkin County. The Parcel geometry is created by reading legal descriptions through Plats, Surveys, Deeds, and CAD drawing files. Approximately 15% of land in Pitkin County is privately held, which is represented in this layer. Federal lands are shown in the Forest Lands layer. Please see http://www.pitkincounty.com/458/GIS-Mapping for more information.

Recreation Easement (Pitkin County GIS 2015)

This layer contains recreation easements throughout Pitkin County with attributes that include the easement type, common name and establishment information. Please see http://www.pitkincounty.com/458/GIS-Mapping or Pitkin County Open Spaces and Trails for more information.

Federal Land Boundary (Pitkin County GIS 2015)The parcel layer and Forest (or Federal Land) layer are independently maintained layers. The Forest layer included lands owned by U.S. Forest Service (USFS), Bureau of Land Management (BLM), and the State of Colorado (State of CO). Approximately 85% of the land area in Pitkin County is Federal Land. Please see http://www.pitkincounty.com/458/GIS-Mapping for more information.SNOTEL Sites From NRCSThese files are updated daily around 7:30 am and 12:30 Pacific Time with midnight summaries of the previous day's data. The symbols are color-coded by the current snow water equivalent as a percent of the 1981-2010 normal on this date. Clicking on a symbol will reveal additional information, including a photo of the site, more real-time data, and links to charts and additional reports. Please visit http://www.wcc.nrcs.usda.gov/snotel/ for more information.

This data represents sinks in the Roaring Fork watershed to be used in a web map showing connected wetland and deepwater habitat features from the National Wetlands Inventory (NWI) dataset and various hydrographic features from the National Hydrography Dataset (NHD). A connectivity model was used to determine isolation/connectivity using a 0, 5, & 10 meter buffer of features. The general model process steps include:NWI was used as input data (other data can be added as input e.g. NHD) to determine "seed" jurisdictional waters. Currently, “seed” jurisdictional waters was defined as all Estuarine, Lacustrine, Tidal Riverine, Lower Perennial Riverine, and Upper Perennial Riverine NWI features.Select all NWI features in the study area that are "potential connectors". Currently, “potential connectors” were defined by excluding NWI features that had drier water regimes (temporarily flooded [A], continuously saturated [B], Continuously Saturated [D] and Seasonally Flooded/Saturated [E] and all Palustrine Farmed [Pf] features). Select all the "potential connectors" that intersect the "seed" data with the customized buffer distance. Continue iterations of step 3 by using the output (“seed” + intersecting “potential connectors”) as the “seed”. Iterations repeat until the count of selected NWI features does not increase.Select all NWI features (including non-connector wetlands) that intersect the final output of step 4. All selected features are exported as "Connected NWI Features...".Invert the selection and export remaining features as "Isolated NWI Features..."

This scene is used as the City of Aspen 3D Basemap derived from 2016 and 2020 Lidar data. Displays realistic buildings and trees in the mountain town of Aspen, Colorado. Aspen is located in a remote area of the Rocky Mountains at an elevation just below 8,000 feet. Surrounded by the White River National Forest along the Roaring Fork River, Aspen is a popular destination for year-round outdoor recreation. For more interactive maps from the City of Aspen, visit Map Aspen, the City of Aspen's open data site.

Layer displays the areas of the 100 year floodplains of the Roaring Fork River, Castle Creek, Maroon Creek, and Hunter Creek.

This layer includes the subbasin and drainage names for the Roaring Fork watershed.

This layer includes the basin and drainage names for the Roaring Fork watershed.

Contact the local municipality for the official town boundary.This layer is a composite of City and Town boundaries in the Roaring Fork watershed. This includes Aspen, Snowmass Village, Basalt, Carbondale, and Marble.Download CAD (.dwg) files here.