ArcGIS REST Services Directory Login
Home > services > Water > Hydro_Line_2012_Strahler_Stream_Order_Classification (MapServer) API Reference
JSON | SOAP | WMS | WFS | WMTS

Water/Hydro_Line_2012_Strahler_Stream_Order_Classification (MapServer)

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

Service Description: <p style='&apos;text-align:justify;&apos;'>This dataset represents a stream network (centreline) of features both natural and artificial across NSW, classified using the Strahler Stream Order method, undertaken by the Department in 2013.</p><p style='&apos;text-align:justify;&apos;'>This is a legacy, best endeavours dataset based upon a static (2012) copy of the now NSW Department of Customer Services (DCS) | Spatial Services: NSW Hydro Line. Today this data forms part of the NSW Digital Topographic Database and NSW Foundation Data Framework administered by DCS.</p><p style='&apos;text-align:justify;&apos;'>Classification of the stream network was completed using the &apos;RivEX&apos; tool (<a href='&amp;apos'>www.rivex.co.uk</a>) in combination with ESRI ArcMap by the Departments Geospatial practitioners.</p><p style='&apos;text-align:justify;&apos;'>The dataset was initially broken up roughly the 13 Catchment Management Authority boundaries (as at 2012). This was simply a data size management step, and the catchment boundaries generally followed hydrology. The edges of the subsets were checked, so the hydro lines stayed within the correct subset for water flow.</p><p style='&apos;text-align:justify;&apos;'>These catchments were often further broken down into smaller hydrological sub-catchments if the dataset remained to large. There were issues with the RivEx processing time if there were too many features processed at once. Checks were done to make sure no line appeared in more than one subset.</p><p style='&apos;text-align:justify;&apos;'>Catchment subsets were processed in order of stream flow, so the order at the end of one catchment was used as the beginning of any it flowed into.</p><p style='&apos;text-align:justify;&apos;'>For Victorian and Queensland datasets - any streamlines that flowed into NSW waterways were extracted (by complete catchment) and processed in exactly the same way as the NSW hydrolines data. Queensland was processed first so the Strahler results could be incorporated in the northern catchments of the state. Victoria was done before the Murray &amp;amp; LMD areas in case those Strahler numbers were going to impact the Murray River stream order.</p><p> A summarised workflow is provided below: </p><ul><li>The input dataset: 2012 DCS NSW Hydro Line</li><li>Break the input dataset into manageable catchments for processing</li><li>Complete topology checks (ArcMap) on catchment subsets</li><li>Undertake basic hydrological enforcement by flipping geometric line directions where required to align with stream flow / class order direction.</li><li>Run Strahler processing (RivEX)</li><li>Undertake visual quality assurance of results &amp;amp; manually resolve issues.</li><li>Recombine catchments to assemble a statewide dataset</li><li>The output dataset: Hydro Line (2012) Strahler Stream Order Classification</li></ul><p>Note: Victorian and Queensland data was also sought (best available) so accurate Strahler assessments at the State borders could be assessed.</p>

Map Name: Map

Legend

All Layers and Tables

Dynamic Legend

Dynamic All Layers

Layers: Description: This dataset represents a stream network (centreline) of features both natural and artificial across NSW, classified using the Strahler Stream Order method, undertaken by the Department in 2013.This is a legacy, best endeavours dataset based upon a static (2012) copy of the now NSW Department of Customer Services (DCS) | Spatial Services: NSW Hydro Line. Today this data forms part of the NSW Digital Topographic Database and NSW Foundation Data Framework administered by DCS.Classification of the stream network was completed using the &apos;RivEX&apos; tool (www.rivex.co.uk) in combination with ESRI ArcMap by the Departments Geospatial practitioners.The dataset was initially broken up roughly the 13 Catchment Management Authority boundaries (as at 2012). This was simply a data size management step, and the catchment boundaries generally followed hydrology. The edges of the subsets were checked, so the hydro lines stayed within the correct subset for water flow.These catchments were often further broken down into smaller hydrological sub-catchments if the dataset remained to large. There were issues with the RivEx processing time if there were too many features processed at once. Checks were done to make sure no line appeared in more than one subset.Catchment subsets were processed in order of stream flow, so the order at the end of one catchment was used as the beginning of any it flowed into.For Victorian and Queensland datasets - any streamlines that flowed into NSW waterways were extracted (by complete catchment) and processed in exactly the same way as the NSW hydrolines data. Queensland was processed first so the Strahler results could be incorporated in the northern catchments of the state. Victoria was done before the Murray &amp;amp; LMD areas in case those Strahler numbers were going to impact the Murray River stream order. A summarised workflow is provided below: The input dataset: 2012 DCS NSW Hydro LineBreak the input dataset into manageable catchments for processingComplete topology checks (ArcMap) on catchment subsetsUndertake basic hydrological enforcement by flipping geometric line directions where required to align with stream flow / class order direction.Run Strahler processing (RivEX)Undertake visual quality assurance of results &amp;amp; manually resolve issues.Recombine catchments to assemble a statewide datasetThe output dataset: Hydro Line (2012) Strahler Stream Order ClassificationNote: Victorian and Queensland data was also sought (best available) so accurate Strahler assessments at the State borders could be assessed.

Service Item Id: f620e8e746284441b04325b11bb2e9d9

Copyright Text:

Spatial Reference: 102100  (3857)  LatestVCSWkid(0)


Single Fused Map Cache: true

Tile Info: Storage Info: Initial Extent: Full Extent: Units: esriMeters

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

MaxSelectionCount: 2000

MaxImageHeight: 4096

MaxImageWidth: 4096

Supported Query Formats: JSON, geoJSON, PBF

Supports Query Data Elements: true

Min Scale: 5.91657527591555E8

Max Scale: 9027.977411

Min LOD: 0

Max LOD: 16

Supports Datum Transformation: true



Child Resources:   Info   Dynamic Layer

Supported Operations:   Export Map   Identify   QueryLegends   QueryDomains   Find   Return Updates