IWM Aquatic Ecosystem Classification
Watercourses generated from high accuracy LiDAR DEM (1st and 2nd Order) merged with the Ontario Integrated Hydrology (OIH) network (3rd order and above). Aquatic Ecosystem Classification added to the network.
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.
Datasets available for download
-
Aquatic Ecosystem ClassificationFeature Layer
Layer 0 via ArcGIS REST API
Additional Info
| Field | Value |
|---|---|
| Last Updated | March 24, 2026, 20:49 (UTC) |
| Created | March 24, 2026, 20:49 (UTC) |
|
Domain / Topic
Domain or topic of the dataset being cataloged.
|
|
|
Title
Title for the Dataset.
|
IWM Aquatic Ecosystem Classification |
|
Description
A description of the dataset.
|
Watercourses generated from high accuracy LiDAR DEM (1st and 2nd Order) merged with the Ontario Integrated Hydrology (OIH) network (3rd order and above). Aquatic Ecosystem Classification added to the network. 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. |
|
Tags / Keywords
Keywords/tags categorizing the dataset.
|
|
|
Format (CSV, XLS, TXT, PDF, etc)
File format of the dataset.
|
|
|
Dataset Size
Dataset size in megabytes.
|
104392.0 |
|
Metadata Identifier
Metadata identifier – can be used as the unique identifier for catalogue entry
|
|
|
Published Date
Published date of the dataset.
|
2024-08-16 |
|
Time Period Data Span (start date)
Start date of the data in the dataset.
|
|
|
Time Period Data Span (end date)
End date of time data in the dataset.
|
|
|
GeoSpatial Area Data Span
A spatial region or named place the dataset covers.
|
| Field | Value |
|---|---|
|
Access category
Type of access granted for the dataset (open, closed, service, etc).
|
public |
|
License
License used to access the dataset.
|
License not specified |
|
Limits on use
Limits on use of data.
|
|
|
Location
Location of the dataset.
|
https://map.muskoka.on.ca/datasets/5aee5578d29c44119ec296a166a23c52 |
|
Data Service
Data service for accessing a dataset.
|
|
|
Owner
Owner of the dataset.
|
dm.admin |
|
Contact Point
Who to contact regarding access?
|
|
|
Contact Point Email
The email to contact regarding access?
|
|
|
Publisher
Publisher of the dataset.
|
|
|
Publisher Email
Email of the publisher.
|
|
|
Author
Author of the dataset.
|
dm.admin |
|
Author Email
Email of the author.
|
|
|
Accessed At
Date the data and metadata was accessed.
|
2024-08-16 |
| Field | Value |
|---|---|
|
Identifier
Unique identifier for the dataset.
|
5aee5578d29c44119ec296a166a23c52 |
|
Language
Language(s) of the dataset
|
English |
|
Link to dataset description
A URL to an external document describing the dataset.
|
https://map.muskoka.on.ca/datasets/5aee5578d29c44119ec296a166a23c52 |
|
Persistent Identifier
Data is identified by a persistent identifier.
|
|
|
Globally Unique Identifier
Data is identified by a persistent and globally unique identifier.
|
|
|
Contains data about individuals
Does the data hold data about individuals?
|
|
|
Contains data about identifiable individuals
Does the data hold identifiable data about individual?
|
|
|
Contains Indigenous Data
Does the data hold data about Indigenous communities?
|
|
|
Portal Type
Platform type of the source portal.
|
| Field | Value |
|---|---|
|
Version
Version of the datatset
|
None |
|
Source
Source of the dataset.
|
None |
|
Version notes
Version notes about the dataset.
|
|
|
Is version of another dataset
Link to dataset that it is a version of.
|
|
|
Other versions
Link to datasets that are versions of it.
|
|
|
Provenance Text
Provenance Text of the data.
|
|
|
Provenance URL
Provenance URL of the data.
|
|
|
Temporal resolution
Describes how granular the date/time data in the dataset is.
|
|
|
GeoSpatial resolution in meters
Describes how granular (in meters) geospatial data is in the dataset.
|
|
|
GeoSpatial resolution (in regions)
Describes how granular (in regions) geospatial data is in the dataset.
|
| Field | Value |
|---|---|
|
Indigenous Community Permission
Who holds the Indigenous Community Permission. Who to contact regarding access to a dataset that has data about Indigenous communities.
|
|
|
Community Permission
Community permission (who gave permission).
|
|
|
The Indigenous communities the dataset is about
Indigenous communities from which data is derived.
|
| Field | Value |
|---|---|
|
Number of data rows
If tabular dataset, total number of rows.
|
147698 |
|
Number of data columns
If tabular dataset, total number of unique columns.
|
27 |
|
Number of data cells
If tabular dataset, total number of cells with data.
|
3987846 |
|
Number of data relations
If RDF dataset, total number of triples.
|
|
|
Number of entities
If RDF dataset, total number of entities.
|
|
|
Number of data properties
If RDF dataset, total number of unique properties used by the triples.
|
|
|
Data quality
Describes the quality of the data in the dataset.
|
|
|
Metric for data quality
A metric used to measure the quality of the data, such as missing values or invalid formats.
|
0 Comments