Fisheries monitoring and biological data of the Yellowknife River Cisco (Coregonus artedi) population, 1999–2020

PURPOSE:

"Biological, relative abundance, and environmental data have been collected from the Yellowknife River Cisco population that can be used to inform fisheries management decision-making. Under the conditions of a commercial licence issued under the New Emerging Fisheries Policy, licence holders are required to record catch and biological information to support the assessment of the feasibility and sustainability of the fishery over time, and potential advancement in the stages of a developing fishery. In addition to the information collected from the commercial harvest (fishery-dependent), a fishery-independent sampling and snorkel survey program was conducted with the objective of collecting additional biological, observational, and environmental data during the fall spawning run.

The objective of this report is to compile available data from fishery-dependent and fishery-independent sampling of adfluvial Yellowknife River Cisco during fall, 1998-2020*, specifically by:

• Summarizing commercial fishery quotas and reported harvest;

• Characterizing population demographics and examining for trends over time;

• Summarizing metrics of relative abundance (i.e., catch-per-unit-effort data and snorkel survey observations) and examining for trends over time; and

• Determining if there were any associations between relative abundance of Cisco and river discharge and temperature.

*A commercial harvest occurred in 1998, although no biological or catch-effort records were located. In addition, in response to concerns about the status of the population, the fishery was put on hold 2006–2009 to allow for a population assessment (no data during that time).

DESCRIPTION:

Cisco (Coregonus artedi) from the Yellowknife River, Northwest Territories, are an important fishery resource for nearby communities. Biological, catch-effort, and environmental data were collected from the Yellowknife River (Tartan Rapids and Bluefish areas) during their fall spawning run from Great Slave Lake. Data from the commercial harvest (fishery-dependent; 1998–2020) and supplementary monitoring (fishery-independent; 2013–2020) of these adfluvial Cisco were compiled to summarize commercial fishery quotas and reported harvest, characterize population demographics and catch-effort over time, and assess potential associations between relative abundance and seasonal river characteristics. A single commercial fishing licence for Cisco was issued on an annual basis each fall for 1,000 kg from 1998–2002, 2,000 kg from 2004–2005, 1,000 kg from 2010–2018, and 1,500 kg from 2019–2020. Cisco ranged from 102–239 mm fork length, 10.0–139.6 g round weight, and 1 and 9 years of age, with the majority of fish (>99%) being sexually mature. The demographics (length, weight, age) of the spawning population collected from the commercial fishery remained relatively stable between 1999 and 2020. Catch-effort of the commercial fishery varied widely among years without trend, although this was not standardized to the number of individuals/nets used to capture the fish. The biological, catch-effort, and environmental data collected from the Yellowknife River spawning population of Cisco serve as a benchmark for their ongoing assessment and management.

Datasets available for download

Additional Info

Field Value
Last Updated October 22, 2024, 15:37 (UTC)
Created October 1, 2024, 07:25 (UTC)
Domain / Topic
Domain or topic of the dataset being cataloged.
Biota, Environment, Inland Waters
Description
A description of the dataset.

PURPOSE:

"Biological, relative abundance, and environmental data have been collected from the Yellowknife River Cisco population that can be used to inform fisheries management decision-making. Under the conditions of a commercial licence issued under the New Emerging Fisheries Policy, licence holders are required to record catch and biological information to support the assessment of the feasibility and sustainability of the fishery over time, and potential advancement in the stages of a developing fishery. In addition to the information collected from the commercial harvest (fishery-dependent), a fishery-independent sampling and snorkel survey program was conducted with the objective of collecting additional biological, observational, and environmental data during the fall spawning run.

The objective of this report is to compile available data from fishery-dependent and fishery-independent sampling of adfluvial Yellowknife River Cisco during fall, 1998-2020*, specifically by:

• Summarizing commercial fishery quotas and reported harvest;

• Characterizing population demographics and examining for trends over time;

• Summarizing metrics of relative abundance (i.e., catch-per-unit-effort data and snorkel survey observations) and examining for trends over time; and

• Determining if there were any associations between relative abundance of Cisco and river discharge and temperature.

*A commercial harvest occurred in 1998, although no biological or catch-effort records were located. In addition, in response to concerns about the status of the population, the fishery was put on hold 2006–2009 to allow for a population assessment (no data during that time).

DESCRIPTION:

Cisco (Coregonus artedi) from the Yellowknife River, Northwest Territories, are an important fishery resource for nearby communities. Biological, catch-effort, and environmental data were collected from the Yellowknife River (Tartan Rapids and Bluefish areas) during their fall spawning run from Great Slave Lake. Data from the commercial harvest (fishery-dependent; 1998–2020) and supplementary monitoring (fishery-independent; 2013–2020) of these adfluvial Cisco were compiled to summarize commercial fishery quotas and reported harvest, characterize population demographics and catch-effort over time, and assess potential associations between relative abundance and seasonal river characteristics. A single commercial fishing licence for Cisco was issued on an annual basis each fall for 1,000 kg from 1998–2002, 2,000 kg from 2004–2005, 1,000 kg from 2010–2018, and 1,500 kg from 2019–2020. Cisco ranged from 102–239 mm fork length, 10.0–139.6 g round weight, and 1 and 9 years of age, with the majority of fish (>99%) being sexually mature. The demographics (length, weight, age) of the spawning population collected from the commercial fishery remained relatively stable between 1999 and 2020. Catch-effort of the commercial fishery varied widely among years without trend, although this was not standardized to the number of individuals/nets used to capture the fish. The biological, catch-effort, and environmental data collected from the Yellowknife River spawning population of Cisco serve as a benchmark for their ongoing assessment and management.

Tags
Keywords/tags categorizing the dataset.
Format (CSV, XLS, TXT, PDF, etc)
File format of the dataset.
Dataset Size
Dataset size in megabytes.
Metadata Identifier
Metadata identifier – can be used as the unique identifier for catalogue entry
Published Date
Published date of the dataset.
2024-05-23
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).
License
License used to access the dataset.
Open Government Licence - Canada
Limits on use
Limits on use of data.
Location
Location of the dataset.
Data Service
Data service for accessing a dataset.
Owner
Owner of the dataset.
Fisheries and Oceans Canada | Pêches et Océans Canada
Contact Point
Who to contact regarding access?
Government of Canada; Fisheries and Oceans Canada, dfo.opaarddata-donneesdeladraaop.mpo@dfo-mpo.gc.ca
Contact Point Email
The email to contact regarding access?
Publisher
Publisher of the dataset.
Publisher Email
Email of the publisher.
colin.gallagher@dfo-mpo.gc.ca
Accessed At
Date the data and metadata was accessed.
Field Value
Identifier
Unique identifier for the dataset.
Language
Language(s) of the dataset
Link to dataset description
A URL to an external document describing the dataset.
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?
Field Value
Source
Source of the dataset.
https://open.canada.ca/data/en/dataset/06e53cec-1215-11ef-90aa-8b219c568296
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.
Number of data columns
If tabular dataset, total number of unique columns.
Number of data cells
If tabular dataset, total number of cells with data.
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

Please login or register to comment.