Name: National Hydrography Dataset Plus Version 2.1 Monthly Flow and Velocity
Display Field: GNIS_NAME
Type: Feature Layer
Geometry Type: esriGeometryPolyline
Description: <div style="font-family:"Avenir Next W01", "Avenir Next W00", "Avenir Next", Avenir, "Helvetica Neue", sans-serif; font-size:16px;">The National Hydrography Dataset Plus (NHDplus) maps the<span style="font-family:inherit;"> lakes, ponds, streams, rivers and other surface waters of the United States. Created by the</span> <a href="https://www.epa.gov/waterdata/basic-information" style="color:rgb(0, 97, 155); text-decoration-line:none; font-family:inherit;" target="_blank">US EPA Office of Water</a> and the <a href="https://www.usgs.gov/core-science-systems/ngp/national-hydrography" style="color:rgb(0, 97, 155); text-decoration-line:none; font-family:inherit;" target="_blank">US Geological Survey</a>, the NHDPlus provides mean annual and monthly flow estimates for rivers and streams. Additional attributes provide connections between features facilitating complicated analyses.<br /></div><div style="font-family:"Avenir Next W01", "Avenir Next W00", "Avenir Next", Avenir, "Helvetica Neue", sans-serif; font-size:16px;"><br /></div><div style="font-family:"Avenir Next W01", "Avenir Next W00", "Avenir Next", Avenir, "Helvetica Neue", sans-serif; font-size:16px;">For more information on the NHDPlus dataset see the <a href="https://www.horizon-systems.com/NHDPlus/NHDPlusV2_documentation.php#NHDPlusV2%20User%20Guide" style="color:rgb(0, 97, 155); text-decoration-line:none; font-family:inherit;" target="_blank">NHDPlus v2 User Guide</a>.</div><div style="font-family:"Avenir Next W01", "Avenir Next W00", "Avenir Next", Avenir, "Helvetica Neue", sans-serif; font-size:16px;"><font size="4" style="font-family:inherit;"><br /></font></div><div style="font-family:"Avenir Next W01", "Avenir Next W00", "Avenir Next", Avenir, "Helvetica Neue", sans-serif; font-size:16px;"><font size="4" style="font-family:inherit;">Dataset Summary</font></div><span style="font-family:sans-serif; font-size:20px;"></span><div style="font-family:"Avenir Next W01", "Avenir Next W00", "Avenir Next", Avenir, "Helvetica Neue", sans-serif; font-size:16px;"><font style="font-family:inherit;"><span style="font-family:inherit; font-variant-ligatures:none;"><b>Phenomenon Mapped:</b> Surface waters and related features of the United States and associated territories not including Alaska.</span></font></div><div style="font-family:"Avenir Next W01", "Avenir Next W00", "Avenir Next", Avenir, "Helvetica Neue", sans-serif; font-size:16px;"><font style="font-family:inherit;"><span style="font-family:inherit; font-variant-ligatures:none;"><b>Coordinate System: </b>Web Mercator Auxiliary Sphere </span></font></div><div style="font-family:"Avenir Next W01", "Avenir Next W00", "Avenir Next", Avenir, "Helvetica Neue", sans-serif; font-size:16px;"><font style="font-family:inherit;"><span style="font-family:inherit; font-variant-ligatures:none;"><b>Extent: </b>The United States not including Alaska, Puerto Rico, Guam, US Virgin Islands, Marshall Islands, Northern Marianas Islands, Palau, Federated States of Micronesia, and American Samoa </span></font></div><div style="font-family:"Avenir Next W01", "Avenir Next W00", "Avenir Next", Avenir, "Helvetica Neue", sans-serif; font-size:16px;"><font style="font-family:inherit;"><span style="font-family:inherit; font-variant-ligatures:none;"><b>Visible Scale: </b>Visible at all scales but layer draws best at scales larger than 1:1,000,000</span></font></div><div style="font-family:"Avenir Next W01", "Avenir Next W00", "Avenir Next", Avenir, "Helvetica Neue", sans-serif; font-size:16px;"><font style="font-family:inherit;"><span style="font-family:inherit; font-variant-ligatures:none;"><b>Resolution/Tolerance: </b>1 meter/2 meters </span></font></div><div style="font-family:"Avenir Next W01", "Avenir Next W00", "Avenir Next", Avenir, "Helvetica Neue", sans-serif; font-size:16px;"><font style="font-family:inherit;"><span style="font-family:inherit; font-variant-ligatures:none;"><b>Number of Features: </b>3,035,617 flowlines, 473,936 waterbodies, 16,658 sinks</span></font></div><div style="font-family:"Avenir Next W01", "Avenir Next W00", "Avenir Next", Avenir, "Helvetica Neue", sans-serif; font-size:16px;"><font style="font-family:inherit;"><span style="font-family:inherit; font-variant-ligatures:none;"><b>Feature Request Limit: </b>5,000</span></font></div><div style="font-family:"Avenir Next W01", "Avenir Next W00", "Avenir Next", Avenir, "Helvetica Neue", sans-serif; font-size:16px;"><font style="font-family:inherit;"><span style="font-family:inherit; font-variant-ligatures:none;"><b>Source:</b> </span></font><a href="https://www.epa.gov/waterdata/basic-information" style="color:rgb(0, 97, 155); text-decoration-line:none; font-family:inherit;" target="_blank">EPA</a> and <a href="https://www.usgs.gov/core-science-systems/ngp/national-hydrography" style="color:rgb(0, 97, 155); text-decoration-line:none; font-family:inherit;" target="_blank">USGS</a></div><div style="font-family:"Avenir Next W01", "Avenir Next W00", "Avenir Next", Avenir, "Helvetica Neue", sans-serif; font-size:16px;"><font style="font-family:inherit;"><span style="font-family:inherit; font-variant-ligatures:none;"><b>Publication Date: </b>March 13, 2019</span></font></div><div style="font-family:"Avenir Next W01", "Avenir Next W00", "Avenir Next", Avenir, "Helvetica Neue", sans-serif; font-size:16px;"><font style="font-family:inherit;"><span style="font-family:inherit; font-variant-ligatures:none;"><br /></span></font></div><div style="font-family:"Avenir Next W01", "Avenir Next W00", "Avenir Next", Avenir, "Helvetica Neue", sans-serif; font-size:16px;"><font style="font-family:inherit;"><span style="font-family:inherit; font-variant-ligatures:none;">Prior to publication, the NHDPlus network and non-network flowline feature classes were combined into a single flowline layer. Similarly, the NHDPlus Area and Waterbody feature classes were merged under a single schema.<br /></span></font></div><div style="font-family:"Avenir Next W01", "Avenir Next W00", "Avenir Next", Avenir, "Helvetica Neue", sans-serif; font-size:16px;"><font style="font-family:inherit;"><span style="font-family:inherit; font-variant-ligatures:none;"><br /></span></font></div><div style="font-family:"Avenir Next W01", "Avenir Next W00", "Avenir Next", Avenir, "Helvetica Neue", sans-serif; font-size:16px;"><font style="font-family:inherit;"><span style="font-family:inherit; font-variant-ligatures:none;">Attribute fields were added to the flowline and waterbody layers to simplify symbology and enhance the layer's pop-ups. Fields added include </span></font><font style="font-family:inherit;"><span style="font-family:inherit; font-variant-ligatures:none;">Pop-up Title, </span></font><font style="font-family:inherit;"><span style="font-family:inherit; font-variant-ligatures:none;">Pop-up Subtitle, </span></font><font style="font-family:inherit;"><span style="font-family:inherit; font-variant-ligatures:none;">On or Off Network (flowlines only), </span></font><font style="font-family:inherit;"><span style="font-family:inherit; font-variant-ligatures:none;"><font style="font-family:inherit;"><span style="font-family:inherit;"><font style="font-family:inherit;"><span style="font-family:inherit;"><font style="font-family:inherit;"><span style="font-family:inherit;"><font style="font-family:inherit;"><span style="font-family:inherit;">Esri Symbology (waterbodies only), and </span></font></span></font></span></font></span></font>Feature Code Description. All other attributes are from the original NHDPlus dataset. No data values -9999 and -9998 were converted to Null values for many of the flowline fields.<br /></span></font></div><div style="font-family:"Avenir Next W01", "Avenir Next W00", "Avenir Next", Avenir, "Helvetica Neue", sans-serif; font-size:16px;"><font style="font-family:inherit;"><span style="font-family:inherit; font-variant-ligatures:none;"><br /></span></font></div><div style="font-family:"Avenir Next W01", "Avenir Next W00", "Avenir Next", Avenir, "Helvetica Neue", sans-serif; font-size:16px; margin:0px; padding:0px;"><font size="4" style="font-family:inherit;">What can you do with this Feature Layer?</font></div><div style="font-family:"Avenir Next W01", "Avenir Next W00", "Avenir Next", Avenir, "Helvetica Neue", sans-serif; font-size:16px; margin:0px; padding:0px;"><font size="4" style="font-family:inherit;"><br /></font></div><div align="left" style="font-family:"Avenir Next W01", "Avenir Next W00", "Avenir Next", Avenir, "Helvetica Neue", sans-serif; font-size:16px; margin:0px; padding:0px;">Feature layers work throughout the ArcGIS system. Generally your work flow with feature layers will begin in ArcGIS Online or ArcGIS Pro. Below are just a few of the things you can do with a feature service in Online and Pro.</div><div align="left" style="font-family:"Avenir Next W01", "Avenir Next W00", "Avenir Next", Avenir, "Helvetica Neue", sans-serif; font-size:16px; margin:0px; padding:0px;"><br /></div><div align="left" style="font-family:"Avenir Next W01", "Avenir Next W00", "Avenir Next", Avenir, "Helvetica Neue", sans-serif; font-size:16px; margin:0px; padding:0px;"><b>ArcGIS Online</b></div><div align="left" style="font-family:"Avenir Next W01", "Avenir Next W00", "Avenir Next", Avenir, "Helvetica Neue", sans-serif; font-size:16px; margin:0px; padding:0px; text-align:center;"><ul><li><div align="left" style="font-family:inherit;">Add this layer to a map in the map viewer. The layer is limited to scales of approximately 1:1,000,000 or larger but a <a href="https://www.arcgis.com/home/item.html?id=ae4bd17e348c45a4b12448c1890df725" style="color:rgb(0, 97, 155); text-decoration-line:none; font-family:inherit;" target="_blank">vector tile layer</a> created from the same data can be used at smaller scales to produce a webmap that displays across the full range of scales. The layer or a map containing it can be used in an application.<span style="font-family:inherit; text-align:center;"> </span></div></li></ul><ul><li><div align="left" style="font-family:inherit;"><span style="font-family:inherit; text-align:center;">Change the layer’s transparency and set its visibility range</span></div></li></ul></div><div style="font-family:"Avenir Next W01", "Avenir Next W00", "Avenir Next", Avenir, "Helvetica Neue", sans-serif; font-size:16px; margin:0px; padding:0px; text-align:center;"><ul><li><div align="left" style="font-family:inherit;">Open the layer’s attribute table and make selections. Selections made in the map or table are reflected in the other. Center on selection allows you to zoom to features selected in the map or table and show selected records allows you to view the selected records in the table.</div></li></ul><div style="font-family:inherit; text-align:left;"><ul><li>Apply filters. For example you can set a filter to show larger streams and rivers using the mean annual flow attribute or the stream order attribute.</li></ul></div></div><div style="font-family:"Avenir Next W01", "Avenir Next W00", "Avenir Next", Avenir, "Helvetica Neue", sans-serif; font-size:16px; margin:0px; padding:0px; text-align:center;"><ul><li><div align="left" style="font-family:inherit;">Change the layer’s style and symbology<span style="font-family:inherit; background-color:rgb(255, 255, 0);"><br /></span></div></li></ul></div><ul><li><div align="left" style="font-family:inherit;">Add labels and set their properties</div></li></ul><ul><li><div align="left" style="font-family:inherit;">Customize the pop-up</div></li></ul><ul><li>Use as an input to the ArcGIS Online analysis tools. This layer works well as a reference layer with the trace downstream and watershed tools. The buffer tool can be used to draw protective boundaries around streams and the extract data tool can be used to create copies of portions of the data.<br /></li></ul><div align="left" style="font-family:"Avenir Next W01", "Avenir Next W00", "Avenir Next", Avenir, "Helvetica Neue", sans-serif; font-size:16px; margin:0px; padding:0px;"><b>ArcGIS Pro</b></div><div align="left" style="font-family:"Avenir Next W01", "Avenir Next W00", "Avenir Next", Avenir, "Helvetica Neue", sans-serif; font-size:16px; margin:0px; padding:0px;"><ul><li>Add this layer to a 2d or 3d map.<br /></li></ul></div><ul><li><div align="left" style="font-family:inherit;">Use as an input to geoprocessing. For example, copy features allows you to select then export portions of the data to a new feature class.<br /></div></li></ul><ul><li><div align="left" style="font-family:inherit;">Change the symbology and the attribute field used to symbolize the data</div></li></ul><ul><li><div align="left" style="font-family:inherit;">Open table and make interactive selections with the map</div></li></ul><ul><li><div align="left" style="font-family:inherit;">Modify the pop-ups</div></li></ul><ul><li><div align="left" style="font-family:inherit;">Apply Definition Queries to create sub-sets of the layer</div></li></ul><div align="left" style="font-family:"Avenir Next W01", "Avenir Next W00", "Avenir Next", Avenir, "Helvetica Neue", sans-serif; font-size:16px; margin:0px; padding:0px;">This layer is part of the <a href="https://livingatlas.arcgis.com/" style="color:rgb(0, 94, 149); font-family:inherit;" target="_blank">ArcGIS Living Atlas of the World</a> that provides an easy way to explore the landscape layers and many other beautiful and authoritative maps on hundreds of topics.</div>
AreaSqKM (type: esriFieldTypeSingle, alias: Area in Square Kilometers, SQL Type: sqlTypeOther, nullable: true, editable: true)
TotDASqKM (type: esriFieldTypeSingle, alias: Total Upstream Catchment Area from Downstream End of Flowline in Square Kilometers, SQL Type: sqlTypeOther, nullable: true, editable: true)
DivDASqKM (type: esriFieldTypeSingle, alias: Divergence-Routed Upstream Catchment Area from Downstream End of Flowline in Square Kilometers, SQL Type: sqlTypeOther, nullable: true, editable: true)
SLOPELENKM (type: esriFieldTypeSingle, alias: Feature Length Used to Compute Slope in Kilometers, SQL Type: sqlTypeOther, nullable: true, editable: true)
QA_MA (type: esriFieldTypeSingle, alias: Mean Annual Flow from Runoff in Cubic Feet per Second, SQL Type: sqlTypeOther, nullable: true, editable: true)
VA_MA (type: esriFieldTypeSingle, alias: Mean Annual Velocity for Mean Annual Flow in Feet per Second, SQL Type: sqlTypeOther, nullable: true, editable: true)
QC_MA (type: esriFieldTypeSingle, alias: Mean Annual Flow with Reference Gage Regression in Cubic Feet per Second, SQL Type: sqlTypeOther, nullable: true, editable: true)
VC_MA (type: esriFieldTypeSingle, alias: Mean Annual Velocity for Mean Annual Flow with Reference Gage Regression in Feet per Second, SQL Type: sqlTypeOther, nullable: true, editable: true)
VE_MA (type: esriFieldTypeSingle, alias: Mean Annual Velocity from Gage Adjustment in Feet per Second, SQL Type: sqlTypeOther, nullable: true, editable: true)
QA_01 (type: esriFieldTypeSingle, alias: January Mean Monthly Flow from Runoff in Cubic Feet per Second, SQL Type: sqlTypeOther, nullable: true, editable: true)
VA_01 (type: esriFieldTypeSingle, alias: January Mean Monthly Velocity for Mean Monthly Flow in Feet per Second, SQL Type: sqlTypeOther, nullable: true, editable: true)
QC_01 (type: esriFieldTypeSingle, alias: January Mean Monthly Flow with Reference Gage Regression in Cubic Feet per Second, SQL Type: sqlTypeOther, nullable: true, editable: true)
VC_01 (type: esriFieldTypeSingle, alias: January Mean Monthly Velocity for Mean Monthly Flow with Reference Gage Regression in Feet per Second, SQL Type: sqlTypeOther, nullable: true, editable: true)
QE_01 (type: esriFieldTypeSingle, alias: January Mean Monthly Flow from Gage Adjustment in Cubic Feet per Second, SQL Type: sqlTypeOther, nullable: true, editable: true)
VE_01 (type: esriFieldTypeSingle, alias: January Mean Monthly Velocity from Gage Adjustment in Feet per Second, SQL Type: sqlTypeOther, nullable: true, editable: true)
QA_02 (type: esriFieldTypeSingle, alias: February Mean Monthly Flow from Runoff in Cubic Feet per Second, SQL Type: sqlTypeOther, nullable: true, editable: true)
VA_02 (type: esriFieldTypeSingle, alias: February Mean Monthly Velocity for Mean Monthly Flow in Feet per Second, SQL Type: sqlTypeOther, nullable: true, editable: true)
QC_02 (type: esriFieldTypeSingle, alias: February Mean Monthly Flow with Reference Gage Regression in Cubic Feet per Second, SQL Type: sqlTypeOther, nullable: true, editable: true)
VC_02 (type: esriFieldTypeSingle, alias: February Mean Monthly Velocity for Mean Monthly Flow with Reference Gage Regression in Feet per Second, SQL Type: sqlTypeOther, nullable: true, editable: true)
QE_02 (type: esriFieldTypeSingle, alias: February Mean Monthly Flow from Gage Adjustment in Cubic Feet per Second, SQL Type: sqlTypeOther, nullable: true, editable: true)
VE_02 (type: esriFieldTypeSingle, alias: February Mean Monthly Velocity from Gage Adjustment in Feet per Second, SQL Type: sqlTypeOther, nullable: true, editable: true)
QA_03 (type: esriFieldTypeSingle, alias: March Mean Monthly Flow from Runoff in Cubic Feet per Second, SQL Type: sqlTypeOther, nullable: true, editable: true)
VA_03 (type: esriFieldTypeSingle, alias: March Mean Monthly Velocity for Mean Monthly Flow in Feet per Second, SQL Type: sqlTypeOther, nullable: true, editable: true)
QC_03 (type: esriFieldTypeSingle, alias: March Mean Monthly Flow with Reference Gage Regression in Cubic Feet per Second, SQL Type: sqlTypeOther, nullable: true, editable: true)
VC_03 (type: esriFieldTypeSingle, alias: March Mean Monthly Velocity for Mean Monthly Flow with Reference Gage Regression in Feet per Second, SQL Type: sqlTypeOther, nullable: true, editable: true)
QE_03 (type: esriFieldTypeSingle, alias: March Mean Monthly Flow from Gage Adjustment in Cubic Feet per Second, SQL Type: sqlTypeOther, nullable: true, editable: true)
VE_03 (type: esriFieldTypeSingle, alias: March Mean Monthly Velocity from Gage Adjustment in Feet per Second, SQL Type: sqlTypeOther, nullable: true, editable: true)
QA_04 (type: esriFieldTypeSingle, alias: April Mean Monthly Flow from Runoff in Cubic Feet per Second, SQL Type: sqlTypeOther, nullable: true, editable: true)
VA_04 (type: esriFieldTypeSingle, alias: April Mean Monthly Velocity for Mean Monthly Flow in Feet per Second, SQL Type: sqlTypeOther, nullable: true, editable: true)
QC_04 (type: esriFieldTypeSingle, alias: April Mean Monthly Flow with Reference Gage Regression in Cubic Feet per Second, SQL Type: sqlTypeOther, nullable: true, editable: true)
VC_04 (type: esriFieldTypeSingle, alias: April Mean Monthly Velocity for Mean Monthly Flow with Reference Gage Regression in Feet per Second, SQL Type: sqlTypeOther, nullable: true, editable: true)
QE_04 (type: esriFieldTypeSingle, alias: April Mean Monthly Flow from Gage Adjustment in Cubic Feet per Second, SQL Type: sqlTypeOther, nullable: true, editable: true)
VE_04 (type: esriFieldTypeSingle, alias: April Mean Monthly Velocity from Gage Adjustment in Feet per Second, SQL Type: sqlTypeOther, nullable: true, editable: true)
QA_05 (type: esriFieldTypeSingle, alias: May Mean Monthly Flow from Runoff in Cubic Feet per Second, SQL Type: sqlTypeOther, nullable: true, editable: true)
VA_05 (type: esriFieldTypeSingle, alias: May Mean Monthly Velocity for Mean Monthly Flow in Feet per Second, SQL Type: sqlTypeOther, nullable: true, editable: true)
QC_05 (type: esriFieldTypeSingle, alias: May Mean Monthly Flow with Reference Gage Regression in Cubic Feet per Second, SQL Type: sqlTypeOther, nullable: true, editable: true)
VC_05 (type: esriFieldTypeSingle, alias: May Mean Monthly Velocity for Mean Monthly Flow with Reference Gage Regression in Feet per Second, SQL Type: sqlTypeOther, nullable: true, editable: true)
QE_05 (type: esriFieldTypeSingle, alias: May Mean Monthly Flow from Gage Adjustment in Cubic Feet per Second, SQL Type: sqlTypeOther, nullable: true, editable: true)
VE_05 (type: esriFieldTypeSingle, alias: May Mean Monthly Velocity from Gage Adjustment in Feet per Second, SQL Type: sqlTypeOther, nullable: true, editable: true)
QA_06 (type: esriFieldTypeSingle, alias: June Mean Monthly Flow from Runoff in Cubic Feet per Second, SQL Type: sqlTypeOther, nullable: true, editable: true)
VA_06 (type: esriFieldTypeSingle, alias: June Mean Monthly Velocity for Mean Monthly Flow in Feet per Second, SQL Type: sqlTypeOther, nullable: true, editable: true)
QC_06 (type: esriFieldTypeSingle, alias: June Mean Monthly Flow with Reference Gage Regression in Cubic Feet per Second, SQL Type: sqlTypeOther, nullable: true, editable: true)
VC_06 (type: esriFieldTypeSingle, alias: June Mean Monthly Velocity for Mean Monthly Flow with Reference Gage Regression in Feet per Second, SQL Type: sqlTypeOther, nullable: true, editable: true)
QE_06 (type: esriFieldTypeSingle, alias: June Mean Monthly Flow from Gage Adjustment in Cubic Feet per Second, SQL Type: sqlTypeOther, nullable: true, editable: true)
VE_06 (type: esriFieldTypeSingle, alias: June Mean Monthly Velocity from Gage Adjustment in Feet per Second, SQL Type: sqlTypeOther, nullable: true, editable: true)
QA_07 (type: esriFieldTypeSingle, alias: July Mean Monthly Flow from Runoff in Cubic Feet per Second, SQL Type: sqlTypeOther, nullable: true, editable: true)
VA_07 (type: esriFieldTypeSingle, alias: July Mean Monthly Velocity for Mean Monthly Flow in Feet per Second, SQL Type: sqlTypeOther, nullable: true, editable: true)
QC_07 (type: esriFieldTypeSingle, alias: July Mean Monthly Flow with Reference Gage Regression in Cubic Feet per Second, SQL Type: sqlTypeOther, nullable: true, editable: true)
VC_07 (type: esriFieldTypeSingle, alias: July Mean Monthly Velocity for Mean Monthly Flow with Reference Gage Regression in Feet per Second, SQL Type: sqlTypeOther, nullable: true, editable: true)
QE_07 (type: esriFieldTypeSingle, alias: July Mean Monthly Flow from Gage Adjustment in Cubic Feet per Second, SQL Type: sqlTypeOther, nullable: true, editable: true)
VE_07 (type: esriFieldTypeSingle, alias: July Mean Monthly Velocity from Gage Adjustment in Feet per Second, SQL Type: sqlTypeOther, nullable: true, editable: true)
QA_08 (type: esriFieldTypeSingle, alias: August Mean Monthly Flow from Runoff in Cubic Feet per Second, SQL Type: sqlTypeOther, nullable: true, editable: true)
VA_08 (type: esriFieldTypeSingle, alias: August Mean Monthly Velocity for Mean Monthly Flow in Feet per Second, SQL Type: sqlTypeOther, nullable: true, editable: true)
QC_08 (type: esriFieldTypeSingle, alias: August Mean Monthly Flow with Reference Gage Regression in Cubic Feet per Second, SQL Type: sqlTypeOther, nullable: true, editable: true)
VC_08 (type: esriFieldTypeSingle, alias: August Mean Monthly Velocity for Mean Monthly Flow with Reference Gage Regression in Feet per Second, SQL Type: sqlTypeOther, nullable: true, editable: true)
QE_08 (type: esriFieldTypeSingle, alias: August Mean Monthly Flow from Gage Adjustment in Cubic Feet per Second, SQL Type: sqlTypeOther, nullable: true, editable: true)
VE_08 (type: esriFieldTypeSingle, alias: August Mean Monthly Velocity from Gage Adjustment in Feet per Second, SQL Type: sqlTypeOther, nullable: true, editable: true)
QA_09 (type: esriFieldTypeSingle, alias: September Mean Monthly Flow from Runoff in Cubic Feet per Second, SQL Type: sqlTypeOther, nullable: true, editable: true)
VA_09 (type: esriFieldTypeSingle, alias: September Mean Monthly Velocity for Mean Monthly Flow in Feet per Second, SQL Type: sqlTypeOther, nullable: true, editable: true)
QC_09 (type: esriFieldTypeSingle, alias: September Mean Monthly Flow with Reference Gage Regression in Cubic Feet per Second, SQL Type: sqlTypeOther, nullable: true, editable: true)
VC_09 (type: esriFieldTypeSingle, alias: September Mean Monthly Velocity for Mean Monthly Flow with Reference Gage Regression in Feet per Second, SQL Type: sqlTypeOther, nullable: true, editable: true)
QE_09 (type: esriFieldTypeSingle, alias: September Mean Monthly Flow from Gage Adjustment in Cubic Feet per Second, SQL Type: sqlTypeOther, nullable: true, editable: true)
VE_09 (type: esriFieldTypeSingle, alias: September Mean Monthly Velocity from Gage Adjustment in Feet per Second, SQL Type: sqlTypeOther, nullable: true, editable: true)
QA_10 (type: esriFieldTypeSingle, alias: October Mean Monthly Flow from Runoff in Cubic Feet per Second, SQL Type: sqlTypeOther, nullable: true, editable: true)
VA_10 (type: esriFieldTypeSingle, alias: October Mean Monthly Velocity for Mean Monthly Flow in Feet per Second, SQL Type: sqlTypeOther, nullable: true, editable: true)
QC_10 (type: esriFieldTypeSingle, alias: October Mean Monthly Flow with Reference Gage Regression in Cubic Feet per Second, SQL Type: sqlTypeOther, nullable: true, editable: true)
VC_10 (type: esriFieldTypeSingle, alias: October Mean Monthly Velocity for Mean Monthly Flow with Reference Gage Regression in Feet per Second, SQL Type: sqlTypeOther, nullable: true, editable: true)
QE_10 (type: esriFieldTypeSingle, alias: October Mean Monthly Flow from Gage Adjustment in Cubic Feet per Second, SQL Type: sqlTypeOther, nullable: true, editable: true)
VE_10 (type: esriFieldTypeSingle, alias: October Mean Monthly Velocity from Gage Adjustment in Feet per Second, SQL Type: sqlTypeOther, nullable: true, editable: true)
QA_11 (type: esriFieldTypeSingle, alias: November Mean Monthly Flow from Runoff in Cubic Feet per Second, SQL Type: sqlTypeOther, nullable: true, editable: true)
VA_11 (type: esriFieldTypeSingle, alias: November Mean Monthly Velocity for Mean Monthly Flow in Feet per Second, SQL Type: sqlTypeOther, nullable: true, editable: true)
QC_11 (type: esriFieldTypeSingle, alias: November Mean Monthly Flow with Reference Gage Regression in Cubic Feet per Second, SQL Type: sqlTypeOther, nullable: true, editable: true)
VC_11 (type: esriFieldTypeSingle, alias: November Mean Monthly Velocity for Mean Monthly Flow with Reference Gage Regression in Feet per Second, SQL Type: sqlTypeOther, nullable: true, editable: true)
QE_11 (type: esriFieldTypeSingle, alias: November Mean Monthly Flow from Gage Adjustment in Cubic Feet per Second, SQL Type: sqlTypeOther, nullable: true, editable: true)
VE_11 (type: esriFieldTypeSingle, alias: November Mean Monthly Velocity from Gage Adjustment in Feet per Second, SQL Type: sqlTypeOther, nullable: true, editable: true)
QA_12 (type: esriFieldTypeSingle, alias: December Mean Monthly Flow from Runoff in Cubic Feet per Second, SQL Type: sqlTypeOther, nullable: true, editable: true)
VA_12 (type: esriFieldTypeSingle, alias: December Mean Monthly Velocity for Mean Monthly Flow in Feet per Second, SQL Type: sqlTypeOther, nullable: true, editable: true)
QC_12 (type: esriFieldTypeSingle, alias: December Mean Monthly Flow with Reference Gage Regression in Cubic Feet per Second, SQL Type: sqlTypeOther, nullable: true, editable: true)
VC_12 (type: esriFieldTypeSingle, alias: December Mean Monthly Velocity for Mean Monthly Flow with Reference Gage Regression in Feet per Second, SQL Type: sqlTypeOther, nullable: true, editable: true)
QE_12 (type: esriFieldTypeSingle, alias: December Mean Monthly Flow from Gage Adjustment in Cubic Feet per Second, SQL Type: sqlTypeOther, nullable: true, editable: true)
VE_12 (type: esriFieldTypeSingle, alias: December Mean Monthly Velocity from Gage Adjustment in Feet per Second, SQL Type: sqlTypeOther, nullable: true, editable: true)
LakeFract (type: esriFieldTypeSingle, alias: Fraction of Lake Assigned to Flowline, SQL Type: sqlTypeOther, nullable: true, editable: true)
SurfArea (type: esriFieldTypeSingle, alias: Lake Surface Area Assigned to Flowline in Square Meters, SQL Type: sqlTypeOther, nullable: true, editable: true)
Max_Monthly_Velocity (type: esriFieldTypeDouble, alias: Max monthly velocity feet per second from gage adjustment, SQL Type: sqlTypeOther, nullable: true, editable: true)
Description: <span style="font-family:"Avenir Next W01", "Avenir Next W00", "Avenir Next", Avenir, "Helvetica Neue", sans-serif; font-size:16px;">Each drainage area is considered a Hydrologic Unit (HU) and is given a Hydrologic Unit Code (HUC) which serves as the unique identifier for the area. Hydrologic Units are delineated to nest in a multi-level, hierarchical drainage system with corresponding HUCs, so that as you move from small scale to large scale the HUC digits increase in increments of two. For example, the very largest HUCs have 2 digits, and thus are referred to as HUC 2s, and the very smallest HUCs have 12 digits, and thus are referred to as HUC 12s.</span><div style="font-family:"Avenir Next W01", "Avenir Next W00", "Avenir Next", Avenir, "Helvetica Neue", sans-serif; font-size:16px;"><br /></div><div style="font-family:"Avenir Next W01", "Avenir Next W00", "Avenir Next", Avenir, "Helvetica Neue", sans-serif; font-size:16px;"><div style="font-family:"Lucida Grande", "Lucida Sans Unicode", Arial, Helvetica, sans-serif; margin:0px; padding:0px; color:rgb(77, 77, 77); font-size:14px;"><img alt="WBD HUCs" src="https://downloads.esri.com/blogs/hydro/AGOL_Content/WBD.jpg" style="max-width:100%; height:auto;" /></div></div><div style="font-family:"Lucida Grande", "Lucida Sans Unicode", Arial, Helvetica, sans-serif; margin:0px; padding:0px; color:rgb(77, 77, 77); font-size:14px;"><br /></div><span style="font-family:"Avenir Next W01", "Avenir Next W00", "Avenir Next", Avenir, "Helvetica Neue", sans-serif; font-size:16px;">HUC 2s, 6s, 8s, 10s, & 12s, define the drainage Regions, Subregions, Basins, Subbasins, Watersheds and Subwatersheds, respectively, across the United States. Their boundaries are defined by hydrologic and topographic criteria that delineate an area of land upstream from a specific point on a river and are determined solely upon science based hydrologic principles, not favoring any administrative boundaries, special projects, or a particular program or agency. The Watershed Boundary Dataset is delineated and georeferenced to the USGS 1:24,000 scale topographic basemap.</span><div style="font-family:"Avenir Next W01", "Avenir Next W00", "Avenir Next", Avenir, "Helvetica Neue", sans-serif; font-size:16px;"><br /><div style="font-family:inherit;"><font size="4" style="font-family:inherit;">Dataset Summary</font></div><div style="font-family:inherit;"><br /></div><div style="font-family:inherit;"><b>Phenomenon Mapped</b>: Watersheds in the United States, as delineated by the Watershed Boundary Dataset (WBD).</div><div style="font-family:inherit;"><b>Coordinate System</b>: NAD83<br /></div><div style="font-family:inherit;"><b>Extent</b>: Contiguous United States, Alaska, Hawaii, Puerto Rico, Guam, US Virgin Islands, Northern Marianas Islands and American Samoa.</div><div style="font-family:inherit;"><b>Visible Scale</b>: Visible at all scales, however USGS recommends this dataset should not be used for scales of 1:24,000 or larger.<br /></div><div style="font-family:inherit;"><b>Source</b>: United States Geological Survey</div><div style="font-family:inherit;"><b>Publication Date</b>: July 27, 2023</div></div>
Copyright Text: The distributor shall not be held liable for improper or incorrect use of this data, based on the description of appropriate/inappropriate uses described in this metadata document. It is strongly recommended that this data is directly acquired from the distributor and not indirectly through other sources which may have changed the data in some way. These data should not be used at scales greater than 1:24,000 for the purpose of identifying hydrographic watershed boundary feature locations in the United States. The Watershed Boundary Dataset is public information and may be interpreted by all organizations, agencies, units of government, or others based on needs; however, they are responsible for the appropriate application of the data. Photographic or digital enlargement of these maps to scales greater than that at which they were originally delineated can result in misrepresentation of the data. If enlarged, the maps will not include the fine detail that would be appropriate for mapping at the small scale. Digital data files are periodically updated and users are responsible for obtaining the latest version of the data from the source distributor. Acknowledgment of the origination agencies would be appreciated in products derived from these data.
The United States Fish and Wildlife Service (Service) shall not be held liable for improper or incorrect use of the data described and/or contained herein. While the Service makes every reasonable effort to ensure the accuracy and completeness of data provided for distribution, it may not have the necessary accuracy or completeness required for every possible intended use. The Service recommends that data users consult the associated metadata record to understand the quality and possible limitations of the data. The Service creates metadata records in accordance with the standards endorsed by the Federal Geographic Data Committee. As a result of the above considerations, the Service gives no warranty, expressed or implied, as to the accuracy, reliability, or completeness of the data. It is the responsibility of the data user to use the data in a manner consistent with the limitations of geospatial data in general and these data in particular. Although these data have been processed successfully on a computer system at the Service, no warranty, expressed or implied, is made regarding the utility of the data on another system or for general or scientific purposes, nor shall the act of distribution constitute any such warranty. This applies to the use of the data both alone and in aggregate with other data and information.
Description: <span style="font-family:"Avenir Next W01", "Avenir Next W00", "Avenir Next", Avenir, "Helvetica Neue", sans-serif; font-size:16px;">Each drainage area is considered a Hydrologic Unit (HU) and is given a Hydrologic Unit Code (HUC) which serves as the unique identifier for the area. Hydrologic Units are delineated to nest in a multi-level, hierarchical drainage system with corresponding HUCs, so that as you move from small scale to large scale the HUC digits increase in increments of two. For example, the very largest HUCs have 2 digits, and thus are referred to as HUC 2s, and the very smallest HUCs have 12 digits, and thus are referred to as HUC 12s.</span><div style="font-family:"Avenir Next W01", "Avenir Next W00", "Avenir Next", Avenir, "Helvetica Neue", sans-serif; font-size:16px;"><br /></div><div style="font-family:"Avenir Next W01", "Avenir Next W00", "Avenir Next", Avenir, "Helvetica Neue", sans-serif; font-size:16px;"><div style="font-family:"Lucida Grande", "Lucida Sans Unicode", Arial, Helvetica, sans-serif; margin:0px; padding:0px; color:rgb(77, 77, 77); font-size:14px;"><img alt="WBD HUCs" src="https://downloads.esri.com/blogs/hydro/AGOL_Content/WBD.jpg" style="max-width:100%; height:auto;" /></div></div><div style="font-family:"Lucida Grande", "Lucida Sans Unicode", Arial, Helvetica, sans-serif; margin:0px; padding:0px; color:rgb(77, 77, 77); font-size:14px;"><br /></div><span style="font-family:"Avenir Next W01", "Avenir Next W00", "Avenir Next", Avenir, "Helvetica Neue", sans-serif; font-size:16px;">HUC 2s, 6s, 8s, 10s, & 12s, define the drainage Regions, Subregions, Basins, Subbasins, Watersheds and Subwatersheds, respectively, across the United States. Their boundaries are defined by hydrologic and topographic criteria that delineate an area of land upstream from a specific point on a river and are determined solely upon science based hydrologic principles, not favoring any administrative boundaries, special projects, or a particular program or agency. The Watershed Boundary Dataset is delineated and georeferenced to the USGS 1:24,000 scale topographic basemap.</span><div style="font-family:"Avenir Next W01", "Avenir Next W00", "Avenir Next", Avenir, "Helvetica Neue", sans-serif; font-size:16px;"><br /><div style="font-family:inherit;"><font size="4" style="font-family:inherit;">Dataset Summary</font></div><div style="font-family:inherit;"><br /></div><div style="font-family:inherit;"><b>Phenomenon Mapped</b>: Watersheds in the United States, as delineated by the Watershed Boundary Dataset (WBD).</div><div style="font-family:inherit;"><b>Coordinate System</b>: NAD83<br /></div><div style="font-family:inherit;"><b>Extent</b>: Contiguous United States, Alaska, Hawaii, Puerto Rico, Guam, US Virgin Islands, Northern Marianas Islands and American Samoa.</div><div style="font-family:inherit;"><b>Visible Scale</b>: Visible at all scales, however USGS recommends this dataset should not be used for scales of 1:24,000 or larger.<br /></div><div style="font-family:inherit;"><b>Source</b>: United States Geological Survey</div><div style="font-family:inherit;"><b>Publication Date</b>: July 27, 2023</div></div>
Copyright Text: The distributor shall not be held liable for improper or incorrect use of this data, based on the description of appropriate/inappropriate uses described in this metadata document. It is strongly recommended that this data is directly acquired from the distributor and not indirectly through other sources which may have changed the data in some way. These data should not be used at scales greater than 1:24,000 for the purpose of identifying hydrographic watershed boundary feature locations in the United States. The Watershed Boundary Dataset is public information and may be interpreted by all organizations, agencies, units of government, or others based on needs; however, they are responsible for the appropriate application of the data. Photographic or digital enlargement of these maps to scales greater than that at which they were originally delineated can result in misrepresentation of the data. If enlarged, the maps will not include the fine detail that would be appropriate for mapping at the small scale. Digital data files are periodically updated and users are responsible for obtaining the latest version of the data from the source distributor. Acknowledgment of the origination agencies would be appreciated in products derived from these data.
The United States Fish and Wildlife Service (Service) shall not be held liable for improper or incorrect use of the data described and/or contained herein. While the Service makes every reasonable effort to ensure the accuracy and completeness of data provided for distribution, it may not have the necessary accuracy or completeness required for every possible intended use. The Service recommends that data users consult the associated metadata record to understand the quality and possible limitations of the data. The Service creates metadata records in accordance with the standards endorsed by the Federal Geographic Data Committee. As a result of the above considerations, the Service gives no warranty, expressed or implied, as to the accuracy, reliability, or completeness of the data. It is the responsibility of the data user to use the data in a manner consistent with the limitations of geospatial data in general and these data in particular. Although these data have been processed successfully on a computer system at the Service, no warranty, expressed or implied, is made regarding the utility of the data on another system or for general or scientific purposes, nor shall the act of distribution constitute any such warranty. This applies to the use of the data both alone and in aggregate with other data and information.
Description: <span style="font-family:"Avenir Next W01", "Avenir Next W00", "Avenir Next", Avenir, "Helvetica Neue", sans-serif; font-size:16px;">Each drainage area is considered a Hydrologic Unit (HU) and is given a Hydrologic Unit Code (HUC) which serves as the unique identifier for the area. Hydrologic Units are delineated to nest in a multi-level, hierarchical drainage system with corresponding HUCs, so that as you move from small scale to large scale the HUC digits increase in increments of two. For example, the very largest HUCs have 2 digits, and thus are referred to as HUC 2s, and the very smallest HUCs have 12 digits, and thus are referred to as HUC 12s.</span><div style="font-family:"Avenir Next W01", "Avenir Next W00", "Avenir Next", Avenir, "Helvetica Neue", sans-serif; font-size:16px;"><br /></div><div style="font-family:"Avenir Next W01", "Avenir Next W00", "Avenir Next", Avenir, "Helvetica Neue", sans-serif; font-size:16px;"><div style="font-family:"Lucida Grande", "Lucida Sans Unicode", Arial, Helvetica, sans-serif; margin:0px; padding:0px; color:rgb(77, 77, 77); font-size:14px;"><img alt="WBD HUCs" src="https://downloads.esri.com/blogs/hydro/AGOL_Content/WBD.jpg" style="max-width:100%; height:auto;" /></div></div><div style="font-family:"Lucida Grande", "Lucida Sans Unicode", Arial, Helvetica, sans-serif; margin:0px; padding:0px; color:rgb(77, 77, 77); font-size:14px;"><br /></div><span style="font-family:"Avenir Next W01", "Avenir Next W00", "Avenir Next", Avenir, "Helvetica Neue", sans-serif; font-size:16px;">HUC 2s, 6s, 8s, 10s, & 12s, define the drainage Regions, Subregions, Basins, Subbasins, Watersheds and Subwatersheds, respectively, across the United States. Their boundaries are defined by hydrologic and topographic criteria that delineate an area of land upstream from a specific point on a river and are determined solely upon science based hydrologic principles, not favoring any administrative boundaries, special projects, or a particular program or agency. The Watershed Boundary Dataset is delineated and georeferenced to the USGS 1:24,000 scale topographic basemap.</span><div style="font-family:"Avenir Next W01", "Avenir Next W00", "Avenir Next", Avenir, "Helvetica Neue", sans-serif; font-size:16px;"><br /><div style="font-family:inherit;"><font size="4" style="font-family:inherit;">Dataset Summary</font></div><div style="font-family:inherit;"><b>Phenomenon Mapped</b>: Watersheds in the United States, as delineated by the Watershed Boundary Dataset (WBD).</div><div style="font-family:inherit;"><b>Coordinate System</b>: NAD83<br /></div><div style="font-family:inherit;"><b>Extent</b>: Contiguous United States, Alaska, Hawaii, Puerto Rico, Guam, US Virgin Islands, Northern Marianas Islands and American Samoa.</div><div style="font-family:inherit;"><b>Visible Scale</b>: Visible at all scales, however USGS recommends this dataset should not be used for scales of 1:24,000 or larger.<br /></div><div style="font-family:inherit;"><b>Source</b>: United States Geological Survey</div><div style="font-family:inherit;"><b>Publication Date</b>: July 27, 2023</div></div>
Copyright Text: The distributor shall not be held liable for improper or incorrect use of this data, based on the description of appropriate/inappropriate uses described in this metadata document. It is strongly recommended that this data is directly acquired from the distributor and not indirectly through other sources which may have changed the data in some way. These data should not be used at scales greater than 1:24,000 for the purpose of identifying hydrographic watershed boundary feature locations in the United States. The Watershed Boundary Dataset is public information and may be interpreted by all organizations, agencies, units of government, or others based on needs; however, they are responsible for the appropriate application of the data. Photographic or digital enlargement of these maps to scales greater than that at which they were originally delineated can result in misrepresentation of the data. If enlarged, the maps will not include the fine detail that would be appropriate for mapping at the small scale. Digital data files are periodically updated and users are responsible for obtaining the latest version of the data from the source distributor. Acknowledgment of the origination agencies would be appreciated in products derived from these data.
The United States Fish and Wildlife Service (Service) shall not be held liable for improper or incorrect use of the data described and/or contained herein. While the Service makes every reasonable effort to ensure the accuracy and completeness of data provided for distribution, it may not have the necessary accuracy or completeness required for every possible intended use. The Service recommends that data users consult the associated metadata record to understand the quality and possible limitations of the data. The Service creates metadata records in accordance with the standards endorsed by the Federal Geographic Data Committee. As a result of the above considerations, the Service gives no warranty, expressed or implied, as to the accuracy, reliability, or completeness of the data. It is the responsibility of the data user to use the data in a manner consistent with the limitations of geospatial data in general and these data in particular. Although these data have been processed successfully on a computer system at the Service, no warranty, expressed or implied, is made regarding the utility of the data on another system or for general or scientific purposes, nor shall the act of distribution constitute any such warranty. This applies to the use of the data both alone and in aggregate with other data and information.
{"renderer":{"type":"uniqueValue","field1":"Partner1_Contact","defaultSymbol":{"type":"esriSFS","style":"esriSFSSolid","color":[130,130,130,255],"outline":{"type":"esriSLS","style":"esriSLSSolid","color":[110,110,110,255],"width":0.7}},"defaultLabel":"","uniqueValueInfos":[{"symbol":{"type":"esriSFS","style":"esriSFSSolid","color":[130,130,130,0],"outline":{"type":"esriSLS","style":"esriSLSDash","color":[255,255,0,255],"width":1}},"value":"","label":""},{"symbol":{"type":"esriSFS","style":"esriSFSSolid","color":[255,255,115,255],"outline":{"type":"esriSLS","style":"esriSLSSolid","color":[168,168,0,255],"width":2}},"value":"South Dakota State University: Chris Cheek (christopher.cheek@sdstate.edu) and Jake Zona (jacob.zona@sdstate.edu)","label":"South Dakota State University: Chris Cheek (christopher.cheek@sdstate.edu) and Jake Zona (jacob.zona@sdstate.edu)"}],"fieldDelimiter":",","authoringInfo":{"colorRamp":{"type":"multipart","colorRamps":[{"type":"algorithmic","algorithm":"esriCIELabAlgorithm","fromColor":[197,252,221,255],"toColor":[197,252,221,255]},{"type":"algorithmic","algorithm":"esriCIELabAlgorithm","fromColor":[238,179,252,255],"toColor":[238,179,252,255]},{"type":"algorithmic","algorithm":"esriCIELabAlgorithm","fromColor":[252,189,179,255],"toColor":[252,189,179,255]},{"type":"algorithmic","algorithm":"esriCIELabAlgorithm","fromColor":[182,212,252,255],"toColor":[182,212,252,255]},{"type":"algorithmic","algorithm":"esriCIELabAlgorithm","fromColor":[252,238,182,255],"toColor":[252,238,182,255]},{"type":"algorithmic","algorithm":"esriCIELabAlgorithm","fromColor":[252,194,227,255],"toColor":[252,194,227,255]},{"type":"algorithmic","algorithm":"esriCIELabAlgorithm","fromColor":[204,244,252,255],"toColor":[204,244,252,255]},{"type":"algorithmic","algorithm":"esriCIELabAlgorithm","fromColor":[184,184,252,255],"toColor":[184,184,252,255]},{"type":"algorithmic","algorithm":"esriCIELabAlgorithm","fromColor":[199,252,179,255],"toColor":[199,252,179,255]},{"type":"algorithmic","algorithm":"esriCIELabAlgorithm","fromColor":[252,232,215,255],"toColor":[252,232,215,255]},{"type":"algorithmic","algorithm":"esriCIELabAlgorithm","fromColor":[229,210,252,255],"toColor":[229,210,252,255]},{"type":"algorithmic","algorithm":"esriCIELabAlgorithm","fromColor":[246,252,215,255],"toColor":[246,252,215,255]},{"type":"algorithmic","algorithm":"esriCIELabAlgorithm","fromColor":[215,252,202,255],"toColor":[215,252,202,255]}]}}},"scaleSymbols":true,"transparency":1,"labelingInfo":null}
HasZ: false
HasM: false
Has Attachments: false
Has Geometry Properties: true
HTML Popup Type: esriServerHTMLPopupTypeAsHTMLText
ID: South Dakota State University: Chris Cheek (christopher.cheek@sdstate.edu) and Jake Zona (jacob.zona@sdstate.edu)
Name: South Dakota State University: Chris Cheek (christopher.cheek@sdstate.edu) and Jake Zona (jacob.zona@sdstate.edu)
Domains:
Field Name: HUTYPE Inherited
Templates:
Name: South Dakota State University: Chris Cheek (christopher.cheek@sdstate.edu) and Jake Zona (jacob.zona@sdstate.edu)
Description:
Drawing Tool: esriFeatureEditToolPolygon
Prototype:
Attributes:
Partner1_Contact: South Dakota State University: Chris Cheek (christopher.cheek@sdstate.edu) and Jake Zona (jacob.zona@sdstate.edu)
Description: <span style="font-family:"Avenir Next W01", "Avenir Next W00", "Avenir Next", Avenir, "Helvetica Neue", sans-serif; font-size:16px;">Each drainage area is considered a Hydrologic Unit (HU) and is given a Hydrologic Unit Code (HUC) which serves as the unique identifier for the area. Hydrologic Units are delineated to nest in a multi-level, hierarchical drainage system with corresponding HUCs, so that as you move from small scale to large scale the HUC digits increase in increments of two. For example, the very largest HUCs have 2 digits, and thus are referred to as HUC 2s, and the very smallest HUCs have 12 digits, and thus are referred to as HUC 12s.</span><div style="font-family:"Avenir Next W01", "Avenir Next W00", "Avenir Next", Avenir, "Helvetica Neue", sans-serif; font-size:16px;"><br /></div><div style="font-family:"Avenir Next W01", "Avenir Next W00", "Avenir Next", Avenir, "Helvetica Neue", sans-serif; font-size:16px;"><div style="font-family:"Lucida Grande", "Lucida Sans Unicode", Arial, Helvetica, sans-serif; margin:0px; padding:0px; color:rgb(77, 77, 77); font-size:14px;"><img alt="WBD HUCs" src="https://downloads.esri.com/blogs/hydro/AGOL_Content/WBD.jpg" style="max-width:100%; height:auto;" /></div></div><div style="font-family:"Lucida Grande", "Lucida Sans Unicode", Arial, Helvetica, sans-serif; margin:0px; padding:0px; color:rgb(77, 77, 77); font-size:14px;"><br /></div><span style="font-family:"Avenir Next W01", "Avenir Next W00", "Avenir Next", Avenir, "Helvetica Neue", sans-serif; font-size:16px;">HUC 2s, 6s, 8s, 10s, & 12s, define the drainage Regions, Subregions, Basins, Subbasins, Watersheds and Subwatersheds, respectively, across the United States. Their boundaries are defined by hydrologic and topographic criteria that delineate an area of land upstream from a specific point on a river and are determined solely upon science based hydrologic principles, not favoring any administrative boundaries, special projects, or a particular program or agency. The Watershed Boundary Dataset is delineated and georeferenced to the USGS 1:24,000 scale topographic basemap.</span><div style="font-family:"Avenir Next W01", "Avenir Next W00", "Avenir Next", Avenir, "Helvetica Neue", sans-serif; font-size:16px;"><br /><div style="font-family:inherit;"><font size="4" style="font-family:inherit;">Dataset Summary</font></div><div style="font-family:inherit;"><br /></div><div style="font-family:inherit;"><b>Phenomenon Mapped</b>: Watersheds in the United States, as delineated by the Watershed Boundary Dataset (WBD).</div><div style="font-family:inherit;"><b>Coordinate System</b>: NAD83<br /></div><div style="font-family:inherit;"><b>Extent</b>: Contiguous United States, Alaska, Hawaii, Puerto Rico, Guam, US Virgin Islands, Northern Marianas Islands and American Samoa.</div><div style="font-family:inherit;"><b>Visible Scale</b>: Visible at all scales, however USGS recommends this dataset should not be used for scales of 1:24,000 or larger.<br /></div><div style="font-family:inherit;"><b>Source</b>: United States Geological Survey</div><div style="font-family:inherit;"><b>Publication Date</b>: July 27, 2023</div></div>
Copyright Text: The distributor shall not be held liable for improper or incorrect use of this data, based on the description of appropriate/inappropriate uses described in this metadata document. It is strongly recommended that this data is directly acquired from the distributor and not indirectly through other sources which may have changed the data in some way. These data should not be used at scales greater than 1:24,000 for the purpose of identifying hydrographic watershed boundary feature locations in the United States. The Watershed Boundary Dataset is public information and may be interpreted by all organizations, agencies, units of government, or others based on needs; however, they are responsible for the appropriate application of the data. Photographic or digital enlargement of these maps to scales greater than that at which they were originally delineated can result in misrepresentation of the data. If enlarged, the maps will not include the fine detail that would be appropriate for mapping at the small scale. Digital data files are periodically updated and users are responsible for obtaining the latest version of the data from the source distributor. Acknowledgment of the origination agencies would be appreciated in products derived from these data.
The United States Fish and Wildlife Service (Service) shall not be held liable for improper or incorrect use of the data described and/or contained herein. While the Service makes every reasonable effort to ensure the accuracy and completeness of data provided for distribution, it may not have the necessary accuracy or completeness required for every possible intended use. The Service recommends that data users consult the associated metadata record to understand the quality and possible limitations of the data. The Service creates metadata records in accordance with the standards endorsed by the Federal Geographic Data Committee. As a result of the above considerations, the Service gives no warranty, expressed or implied, as to the accuracy, reliability, or completeness of the data. It is the responsibility of the data user to use the data in a manner consistent with the limitations of geospatial data in general and these data in particular. Although these data have been processed successfully on a computer system at the Service, no warranty, expressed or implied, is made regarding the utility of the data on another system or for general or scientific purposes, nor shall the act of distribution constitute any such warranty. This applies to the use of the data both alone and in aggregate with other data and information.