6 datasets found

Licenses: Other (Not Open) Categories and Collections: Morice Watershed Collection Tags: catchability

Filter Results
  • Bulkley River Steelhead Trout: A Report on Angler Use, Tagging, and Life Hist...

    The Bulkley River and its major tributary, Morice River, support one of the most intense steelhead trout fisheries in British Columbia. Recent mailed questionnaire surveys of steelhead anglers have shown that the Bulkley-Morice system ranked second in...
  • Toboggan Creek Hatchery Annual Reports

    The Toboggan Creek Hatchery attempts to preserve and enhance the stocks of Coho and Chinook salmon populations in the Bulkley-Morice drainages. This dataset includes annual reports on the brood, escapement and return for the Toboggan Creek Hatchery.
  • Skeena River Sockeye Escapement and Distribution

    This report presents the various methods employed for determining the escapements to each known spawning area, the spawning estimates made for the years 1944 to 1948, and maps of the sockeye distribution in the Skeena watershed.
  • Morice River Downstream Migrant Survey 1961

    This report determines the timing of sockeye, spring and coho migration leaving Morice Lake, the population size of sockeye smolts leaving Morice Lake, and the length weight, age and scale characteristics of the sockeye migrants.
  • Bulkley/Morice Steelhead Assessment, 2000: A Petersen Capture-Recapture Estim...

    This steelhead tagging program, combined with a recapture phase, allows an estimate of the number of steelhead in the Bulkley system upstream of Moricetown Canyon. In Autumn 2000~ the program was again conducted, with tags applied in three different...
  • Biological Assessment of Skeena River Coho Salmon

    This paper provides data on juvenile densities throughout the Skeena watershed in the year following record low escapements and documents the responses in escapement to the conservation measures taken in 1998. For the Babine Lake coho aggregate, advice is...
You can also access this registry using the API (see API Docs).