View In:   ArcGIS JavaScript   ArcGIS Online Map Viewer   ArcGIS Earth   ArcMap   ArcGIS Pro

View Footprint In:   ArcGIS Online Map Viewer

Service Description: Stream network data originated from USGS National Hydrologic Database (NHD). While the NHD is a very useful and spatially accurate dataset, it is missing one attribute that is commonly referenced as a method to classify and stratify streams, the Strahler Stream Order. Stream order information was available on the Surface Waters Information Management System (SWIMS), digitized from 1:100,000 scale maps. ArcGIS was used converted the SWIMS vectors to points, spaced at 100 meter intervals, and then to calculate the distance to nearest point (NHD stream to SWIMS points). For each arc segment, the attributes of the nearest point were then appended to the attribute table. While this process successfully added the stream order to the NHD arcs, there were some errors. There were instances of the nearest point to a segment actually belonging to a tributary, and being incorrectly assigned to the wrong stream segment. Also, since the NHD data is much more detailed in its inclusion of smaller streams, the origin for the calculation of 1st order and 2nd order streams is different. Efforts were made to address and correct both of these issues, but users should recognize that not all errors were corrected. The stream network was manually scanned for inconsistencies in stream order flow (jumping from a 3rd order to 1st order, and then back to a 3rd order) and corrected. Emphasis was placed on correcting the larger (3rd order and greater) steams first, and many (but not all) of the 1st and 2nd order. Instances of stream beginnings being mislabeled as an order greater than 1st order were corrected by searching for all dangling arcs (stream beginnings) and then recoding them to a order of 1. This process corrected 1,199 arcs that had been incorrectly coded. One last issue users should be aware of is that since the NHD includes streams not used in calculating the Strahler order in the SWIMS dataset, there are inconsistencies in the labeling of 1st and 2nd order streams. Some corrections were made where obvious lager gaps were in the SWIMS database, but for the most part the original SWIMS stream order was transferred directly. Where adjustments were made, they were only made to lower (less then 4th order) streams. Last updated: October 2013.

Map Name: Kansas Streams Order 3-9

Legend

All Layers and Tables

Dynamic Legend

Dynamic All Layers

Layers:

• Kansas NHD Waterways Order 3-9 (0)

Description: Stream network data originated from USGS National Hydrologic Database (NHD). While the NHD is a very useful and spatially accurate dataset, it is missing one attribute that is commonly referenced as a method to classify and stratify streams, the Strahler Stream Order. Stream order information was available on the Surface Waters Information Management System (SWIMS), digitized from 1:100,000 scale maps. ArcGIS was used to convert the SWIMS vectors to points, spaced at 100 meter intervals, and then to calculate the distance to nearest point (NHD stream to SWIMS points). For each arc segment, the attributes of the nearest point were then appended to the attribute table. While this process successfully added the stream order to the NHD arcs, there were some errors. There were instances of the nearest point to a segment actually belonging to a tributary, and being incorrectly assigned to the wrong stream segment. Also, since the NHD data is much more detailed in its inclusion of smaller streams, the origin for the calculation of 1st order and 2nd order streams is different. Efforts were made to address and correct both of these issues, but users should recognize that not all errors were corrected. The stream network was manually scanned for inconsistencies in stream order flow (jumping from a 3rd order to 1st order, and then back to a 3rd order) and corrected. Emphasis was placed on correcting the larger (3rd order and greater) steams first, and many (but not all) of the 1st and 2nd order. Instances of stream beginnings being mislabeled as an order greater than 1st order were corrected by searching for all dangling arcs (stream beginnings) and then recoding them to a order of 1. This process corrected 1,199 arcs that had been incorrectly coded. One last issue users should be aware of is that since the NHD includes streams not used in calculating the Strahler order in the SWIMS dataset, there are inconsistencies in the labeling of 1st and 2nd order streams. Some corrections were made where obvious lager gaps were in the SWIMS database, but for the most part the original SWIMS stream order was transferred directly. Where adjustments were made, they were only made to lower (less then 4th order) streams. Last updated October 2013.

Copyright Text: Kansas Biological Survey / Kansas Applied Remote Sensing Program

Spatial Reference: 102100  (3857)


Single Fused Map Cache: false

Initial Extent:

XMin: -1.135284092878821E7
YMin: 4537503.504578777
XMax: -1.0536662306011794E7
YMax: 5029623.877974059
Spatial Reference: 102100  (3857)

Full Extent:

XMin: -1.13600100124E7
YMin: 4438783.796400003
XMax: -1.05294932224E7
YMax: 4866339.044100001
Spatial Reference: 102100  (3857)

Units: esriMeters

Supported Image Format Types: PNG32,PNG24,PNG,JPG,DIB,TIFF,EMF,PS,PDF,GIF,SVG,SVGZ,BMP

Document Info:

Title: Kansas Streams - NHD Waterways Orders 3-9
Author: Kansas Biological Survey / Kansas Applied Remote Sensing Program
Comments: Stream network data originated from USGS National Hydrologic Database (NHD). While the NHD is a very useful and spatially accurate dataset, it is missing one attribute that is commonly referenced as a method to classify and stratify streams, the Strahler Stream Order. Stream order information was available on the Surface Waters Information Management System (SWIMS), digitized from 1:100,000 scale maps. ArcGIS was used converted the SWIMS vectors to points, spaced at 100 meter intervals, and then to calculate the distance to nearest point (NHD stream to SWIMS points). For each arc segment, the attributes of the nearest point were then appended to the attribute table. While this process successfully added the stream order to the NHD arcs, there were some errors. There were instances of the nearest point to a segment actually belonging to a tributary, and being incorrectly assigned to the wrong stream segment. Also, since the NHD data is much more detailed in its inclusion of smaller streams, the origin for the calculation of 1st order and 2nd order streams is different. Efforts were made to address and correct both of these issues, but users should recognize that not all errors were corrected. The stream network was manually scanned for inconsistencies in stream order flow (jumping from a 3rd order to 1st order, and then back to a 3rd order) and corrected. Emphasis was placed on correcting the larger (3rd order and greater) steams first, and many (but not all) of the 1st and 2nd order. Instances of stream beginnings being mislabeled as an order greater than 1st order were corrected by searching for all dangling arcs (stream beginnings) and then recoding them to a order of 1. This process corrected 1,199 arcs that had been incorrectly coded. One last issue users should be aware of is that since the NHD includes streams not used in calculating the Strahler order in the SWIMS dataset, there are inconsistencies in the labeling of 1st and 2nd order streams. Some corrections were made where obvious lager gaps were in the SWIMS database, but for the most part the original SWIMS stream order was transferred directly. Where adjustments were made, they were only made to lower (less then 4th order) streams. Last updated: October 2013.
Subject: National Hydrography Dataset (NHD) stream segments with a Strahler stream order.
Category:
Keywords: lakes,rivers,stream flow,streams,strohler stream order,water
AntialiasingMode: None
TextAntialiasingMode: Force

Supports Dynamic Layers: true

MaxRecordCount: 1000

MaxImageHeight: 4096

MaxImageWidth: 4096

Supported Query Formats: JSON, geoJSON, PBF

Supports Query Data Elements: true

Min Scale: 0

Max Scale: 0

Supports Datum Transformation: true



Child Resources:   Info   Dynamic Layer

Supported Operations:   Export Map   Identify   QueryLegends   QueryDomains   Find   Return Updates   Generate KML