ArcGIS REST Services Directory
JSON

Layer: Aquatic Ecosystem Classification (ID:0)

View In:   Map Viewer

Name: Aquatic Ecosystem Classification

Display Field: FID_AquaticEcosystemClassificat

Type: Feature Layer

Geometry Type: esriGeometryPolyline

Description:

The main objective for this component of the study was to improve the extent and locational accuracy of 1st and 2nd order watercourses, which are often difficult to locate and map when working at a large scale such as the Muskoka River Watershed. The DTM used was 50cm bare-earth terrain derived from a classified lidar point cloud, which provided a much higher resolution picture of the study area’s topography than previously available. To ensure the watercourse modelling was as detailed as possible the DTM was not resampled and was kept at the original 50cm resolution. Flow Direction was determined first using the D8 algorithm, followed by flow accumulation. A flow accumulation cut-off of 175000 pixels was used after careful comparison with known watercourses. Watercourses were the extracted from the flow accumulation raster, simplified and connected across the watershed.

The flow direction has been set to match the start/end geometry of the line. Flow direction has been set for the geometric network using the source/sinks option. Flow direction can be viewed by selecting the "display arrows" button on the Utility Network Analyst toolbar in ArcMap.

Aquatic Ecosystem Classification mapping processes and techniques were applied to the Muskoka River Watershed LiDAR watercourses to quantify general attributes using a combination of existing data and modeling. Primary attributes were calculated including:  Reach, Reach Slope, Reach Catchment Area, Velocity Class, Network Line Type. For full methods on the application of the AEC reference Muskoka River Watershed IWM Natural Capital Inventory - Addendum 5: Aquatic Ecosystem Classification.



Copyright Text:

Min. Scale: 0

Max. Scale: 0

Default Visibility: true

Max Record Count: 2000

Supported query Formats: JSON, geoJSON, PBF

Use Standardized Queries: True

Extent:

Drawing Info:

HasZ: false

HasM: false

Has Attachments: false

Has Geometry Properties: true

HTML Popup Type: esriServerHTMLPopupTypeAsHTMLText

Object ID Field: OBJECTID

Unique ID Field:

Global ID Field:

Type ID Field: Temperature_Class

Fields:
Types:

Is Data Versioned: false

Has Contingent Values: false

Supports Rollback On Failure Parameter: true

Last Edit Date: 10/11/2024 7:23:10 PM

Schema Last Edit Date: 10/11/2024 7:23:10 PM

Data Last Edit Date: 8/16/2024 6:45:34 PM

Supported Operations:   Query   Query Pivot   Query Top Features   Query Analytic   Query Bins   Generate Renderer   Validate SQL   Get Estimates   ConvertFormat