. <\/SPAN><\/P><\/P>
SMCs depicted in dark green were developed using a very high level GIS desktop analysis based on a floodplain-based regression analysis. These are intended to be a starting point for planning purposes only, with refinement occurring through project design in combination with a more detailed science-backed methodology based on current practices.<\/SPAN><\/P><\/P>
SMCs depicted in light green were developed using a field visit confirmed, peer reviewed, detailed analysis of the stream corridor. This may be fulfilled by a Fluvial Hazard Zone study or other scientifically defensible methods.<\/SPAN><\/P><\/P>
SMCs are still under development for streams not showing an associated corridor.<\/SPAN><\/P><\/P>
For more information about stream management corridors and flood hazard zones, visit the <\/SPAN>Colorado Flood Hazard Zone Mapping Program website<\/SPAN><\/A>. <\/SPAN><\/P><\/DIV><\/DIV><\/DIV>",
"mapName": "StreamMgmtCorridorsNew",
"description": "Stream Management Corridors (SMCs) are the general corridors needed to allow a stream to function in a way that replicates natural processes to the extent possible. Stream Management Corridors should be considered when developing a site plan at the earliest stages of land planning or planning for a stream restoration project.This SMC dataset is based on a floodplain-based regression analysis. MHFD staff identified SMCs on both the eastern and western sides of the District\u2019s service area where the previous shear stress-based method (released in 2019) produced unrealistic SMC widths. To improve accuracy, MHFD updated these SMCs using the revised floodplain-based approach. Last updated: 6/21/2025This is the first release of stream management corridors following the regression-based approach and should be used in place of the legacy shear stress based stream management corridors. SMCs depicted in dark green were developed using a very high level GIS desktop analysis based on a floodplain-based regression analysis. These are intended to be a starting point for planning purposes only, with refinement occurring through project design in combination with a more detailed science-backed methodology based on current practices.SMCs depicted in light green were developed using a field visit confirmed, peer reviewed, detailed analysis of the stream corridor. This may be fulfilled by a Fluvial Hazard Zone study or other scientifically defensible methods.SMCs are still under development for streams not showing an associated corridor.For more information about stream management corridors and flood hazard zones, visit the Colorado Flood Hazard Zone Mapping Program website. ",
"copyrightText": "River Works, MHFD",
"supportsDynamicLayers": true,
"layers": [
{
"id": 0,
"name": "Stream Management Corridors",
"parentLayerId": -1,
"defaultVisibility": true,
"subLayerIds": null,
"minScale": 0,
"maxScale": 0,
"type": "Feature Layer",
"geometryType": "esriGeometryPolygon",
"supportsDynamicLegends": true
}
],
"tables": [],
"spatialReference": {
"wkid": 102100,
"latestWkid": 3857,
"xyTolerance": 0.001,
"zTolerance": 0.001,
"mTolerance": 0.001,
"falseX": -20037700,
"falseY": -30241100,
"xyUnits": 10000,
"falseZ": -100000,
"zUnits": 10000,
"falseM": -100000,
"mUnits": 10000
},
"singleFusedMapCache": false,
"initialExtent": {
"xmin": -1.165378301105255E7,
"ymin": 4810399.8611268,
"xmax": -1.161680649513404E7,
"ymax": 4845830.877624214,
"spatialReference": {
"wkid": 102100,
"latestWkid": 3857,
"xyTolerance": 0.001,
"zTolerance": 0.001,
"mTolerance": 0.001,
"falseX": -20037700,
"falseY": -30241100,
"xyUnits": 10000,
"falseZ": -100000,
"zUnits": 10000,
"falseM": -100000,
"mUnits": 10000
}
},
"fullExtent": {
"xmin": -1.172700264608759E7,
"ymin": 4776040.445964806,
"xmax": -1.1625864193652052E7,
"ymax": 4887999.107139121,
"spatialReference": {
"wkid": 102100,
"latestWkid": 3857,
"xyTolerance": 0.001,
"zTolerance": 0.001,
"mTolerance": 0.001,
"falseX": -20037700,
"falseY": -30241100,
"xyUnits": 10000,
"falseZ": -100000,
"zUnits": 10000,
"falseM": -100000,
"mUnits": 10000
}
},
"datesInUnknownTimezone": false,
"minScale": 0,
"maxScale": 0,
"units": "esriMeters",
"supportedImageFormatTypes": "PNG32,PNG24,PNG,JPG,DIB,TIFF,EMF,PS,PDF,GIF,SVG,SVGZ,BMP",
"documentInfo": {
"Title": "StreamManagementCorridors",
"Author": "",
"Comments": "Stream Management Corridors (SMCs) are the general corridors needed to allow a stream to function in a way that replicates natural processes to the extent possible. Stream Management Corridors should be considered when developing a site plan at the earliest stages of land planning or planning for a stream restoration project.This SMC dataset is based on a floodplain-based regression analysis. MHFD staff identified SMCs on both the eastern and western sides of the District\u2019s service area where the previous shear stress-based method (released in 2019) produced unrealistic SMC widths. To improve accuracy, MHFD updated these SMCs using the revised floodplain-based approach. Last updated: 6/21/2025This is the first release of stream management corridors following the regression-based approach and should be used in place of the legacy shear stress based stream management corridors. SMCs depicted in dark green were developed using a very high level GIS desktop analysis based on a floodplain-based regression analysis. These are intended to be a starting point for planning purposes only, with refinement occurring through project design in combination with a more detailed science-backed methodology based on current practices.SMCs depicted in light green were developed using a field visit confirmed, peer reviewed, detailed analysis of the stream corridor. This may be fulfilled by a Fluvial Hazard Zone study or other scientifically defensible methods.SMCs are still under development for streams not showing an associated corridor.For more information about stream management corridors and flood hazard zones, visit the Colorado Flood Hazard Zone Mapping Program website. ",
"Subject": "Stream Management Corridors (SMCs) within the Mile High Flood District (MHFD) Boundary. SMC boundaries are a rough estimate of the space needed for a highly functional stream design and reduced maintenance expense.",
"Category": "",
"Version": "3.2.0",
"AntialiasingMode": "Fast",
"TextAntialiasingMode": "Force",
"Keywords": "smcs,stream management corridors,geomorphology,mhfd"
},
"supportsQueryDomains": true,
"capabilities": "Map,Query,Data",
"supportedQueryFormats": "JSON, geoJSON, PBF",
"exportTilesAllowed": false,
"referenceScale": 0.0,
"datumTransformations": [
{
"geoTransforms": [
{
"wkid": 108363,
"latestWkid": 108363,
"transformForward": true,
"name": "WGS_1984_(ITRF08)_To_NAD_1983_2011"
}
]
},
{
"geoTransforms": [
{
"wkid": 108363,
"latestWkid": 108363,
"transformForward": false,
"name": "WGS_1984_(ITRF08)_To_NAD_1983_2011"
}
]
},
{
"geoTransforms": [
{
"wkid": 108363,
"latestWkid": 108363,
"transformForward": true,
"name": "WGS_1984_(ITRF08)_To_NAD_1983_2011"
}
]
},
{
"geoTransforms": [
{
"wkid": 108363,
"latestWkid": 108363,
"transformForward": false,
"name": "WGS_1984_(ITRF08)_To_NAD_1983_2011"
}
]
}
],
"supportsDatumTransformation": true,
"floorAwareMapProperties": {
"defaultFloorFilterSettings": {"isEnabled": false}
},
"archivingInfo": {"supportsHistoricMoment": false},
"supportsClipping": true,
"supportsSpatialFilter": true,
"supportsTimeRelation": true,
"supportsQueryDataElements": true,
"mapUnits": {"uwkid": 9001},
"maxRecordCount": 2000,
"maxImageHeight": 4096,
"maxImageWidth": 4096,
"supportedExtensions": "FeatureServer",
"resampling": false,
"serviceItemId": "e48a5461e96547b8a0efc28c9a4da905"
}