View In:
ArcGIS JavaScript
ArcGIS Online Map Viewer
Service 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 'RivEX' 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 & 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 & 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.
All Layers and Tables
Has Versioned Data: false
MaxRecordCount: 2000
Supported Query Formats: JSON
Supports Query Data Elements: true
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 'RivEX' 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 & 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 & 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: 14901540b1b7451998008e966a745364
Copyright Text:
Spatial Reference:
102100
(3857)
LatestVCSWkid(0)
Initial Extent:
XMin: 1.591938482673992E7
YMin: -4387152.169095548
XMax: 1.6859477281207312E7
YMax: -3282647.4313972183
Spatial Reference: 102100
(3857)
LatestVCSWkid(0)
Full Extent:
XMin: 1.5692893260364095E7
YMin: -4507744.769072667
XMax: 1.771129010394653E7
YMax: -3264540.3422296606
Spatial Reference: 102100
(3857)
LatestVCSWkid(0)
Units: esriMeters
Document Info:
Title: Map
Author:
Comments:
Subject:
Category:
Keywords:
AntialiasingMode: null
TextAntialiasingMode: null
Enable Z Defaults: false
Supports ApplyEdits With Global Ids: false
Support True Curves : true
Only Allow TrueCurve Updates By TrueCurveClients : true
Supports Return Service Edits Option : true
Supports Dynamic Layers: false
Child Resources:
Info
Uploads
Query Data Elements
Relationships
Supported Operations:
Query
Query Contingent Values
QueryDomains
Apply Edits
Extract Changes
Get Estimates