12.07.2015 Views

Fraser River sockeye salmon: data synthesis and cumulative impacts

Fraser River sockeye salmon: data synthesis and cumulative impacts

Fraser River sockeye salmon: data synthesis and cumulative impacts

SHOW MORE
SHOW LESS
  • No tags were found...

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

did not correlate well with differences in productivity among different <strong>Fraser</strong> Basin stocks. Forexample, the two <strong>Fraser</strong> <strong>sockeye</strong> stocks that have done well over the last two decades (Harrison<strong>and</strong> Late Shuswap) have shown, respectively, moderate <strong>and</strong> high relative indices of <strong>cumulative</strong>habitat stress on spawning <strong>and</strong> rearing habitats (Table 18 in Nelitz et al. 2011). Furthermore,Nelitz et al. (unpub. analyses) found that indices of the intensity of habitat stressors <strong>and</strong> habitatvulnerability were not consistent with estimates of the current status of conservation units basedon Pestel <strong>and</strong> Cass (2009), that is, stock status did not decline with increasing indices of habitatstress <strong>and</strong> vulnerability.Looking across time, Neltiz et al. found that trends in overall <strong>sockeye</strong> productivity 9 across 17<strong>sockeye</strong> stocks were not correlated with either the intensity of habitat stressors on nursery lakesor their core measures of habitat vulnerability. 10 The only variable correlated with trends in<strong>sockeye</strong> productivity was migration distance (i.e., stocks with longer migration distances showedgreater rates of decline), which may reflect other correlated factors (e.g., watershed position,nursery lake elevation) rather than being a direct causative factor. Juvenile productivity (i.e.,juveniles/spawner) was unrelated to indices of forest harvesting <strong>and</strong> mountain pine beetledisturbance, but showed some indications of negative associations with spring air temperatures atnursery lakes (i.e. juvenile productivity decreases as spring temperatures increase). Finally, thestability over time in juvenile productivity despite declines in overall life cycle productivitysuggests that freshwater habitat factors are not a primary driving factor in the observedproductivity declines, though it is possible that some non-lethal effects during spawning <strong>and</strong>rearing affect later life history stages. These results are similar to those found in the PSC report(Peterman et al. 2010; Section 4.6).Johannes et al. (2011; Table 2) found that there was either no risk or low risk of <strong>impacts</strong> tospawning <strong>and</strong> rearing habitats in the Lower <strong>Fraser</strong> from population growth, industrial <strong>and</strong>infrastructure projects, liquid <strong>and</strong> solid wastes, ships <strong>and</strong> vessels, dredging <strong>and</strong> diking,contaminated materials <strong>and</strong> exotic species. They assigned a moderate risk level to agriculture <strong>and</strong>forestry activities in Lower <strong>Fraser</strong> watersheds where there is a longer duration <strong>and</strong> greatermagnitude of potential interactions.9 trends in annual residuals in returns/spawner, relative to the expected life cycle productivity based on the numbersof spawners in the brood year, indicator #2 in section 4.1; <strong>data</strong> from Peterman et al. (2010)10 Predictor variables included those relating to habitat vulnerability (migration distance, ratio of lakeinfluenced:total spawning extent, area of all nursery lakes) <strong>and</strong> habitat stress (total water license allocations,municipal area, forest harvested area within the last 15 years, road density, water licence restrictions, agriculturalarea, <strong>and</strong> area disturbed by Mountain Pine Beetle). Source: Table 16 in Nelitz et al. (2011).44

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!