kansas_streams_order3_9_webmerc (MapServer)

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

Service Description: <div style='text-align:Left;'><div><div>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.</div></div></div>

Map Name: Map

Legend

All Layers and Tables

Dynamic Legend

Dynamic All Layers

Layers:

kansas_streams_order3_9_webmerc (0)

Description: <DIV STYLE="text-align:Left;"><DIV><DIV>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.</DIV></DIV></DIV>

Service Item Id: e802cb509327448bb6a0ee21a90171ef

Copyright Text: Phillips, S.J., R.P. Anderson, R.E. Schapire. 2006. Maximum entropy modeling of species geographic distributions. Ecological Modeling 190: 231–259. Mark Van Scoyoc, Stream Survey Program Coordinator, Kansas Department of Wildlife, Parks, and Tourism, 512 SE 25th Ave. Pratt, KS 67124; 620-672-5911. Fish collections from Kansas Department of Wildlife and Parks Stream Assessment Program, University of Kansas and Sternberg Museum of Natural History collection records. Maxent processing performed by Dr. Keith B. Gido, Kansas State University, 208 Bushnell Hall, Manhattan, KS 66506; 785-532-5088. GIS processing to integrate Maxent results to NHD stream segments conducted by Michael Houts, Kansas Applied Remote Sensing Program.

Spatial Reference: 4269 (4269) LatestVCSWkid(0)

Single Fused Map Cache: false

Initial Extent:

Full Extent:

Units: esriDecimalDegrees

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

Document Info:

Supports Dynamic Layers: true

MaxRecordCount: 2000

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