z-logo
Premium
Canonical correspondence analysis of early volcanic succession on Mt Usu, Japan
Author(s) -
Tsuyuzaki Shiro,
Moral Roger
Publication year - 1994
Publication title -
ecological research
Language(s) - English
Resource type - Journals
SCImago Journal Rank - 0.628
H-Index - 68
eISSN - 1440-1703
pISSN - 0912-3814
DOI - 10.1007/bf02347489
Subject(s) - canonical correspondence analysis , tephra , ecological succession , vegetation (pathology) , revegetation , volcano , physical geography , aeolian processes , primary succession , plant cover , pumice , environmental science , geology , chronosequence , ecology , topsoil , erosion , habitat , plant community , soil science , geography , geomorphology , soil water , biology , geochemistry , medicine , pathology , species richness
Canonical correspondece analysis (CCA) was applied to explore revegetation patterns during early succession on Mt Usu. Vegetation was buried by deposits of ash and pumice from 1 to 3 m in depth from the 1977–78 eruptions. Three habitats were selected: tephra, tephra in gully and original surface. Plant density and plant cover data were analyzed separately. Environmental factors consisted of five quanticative variables (organic matter, elevation, distance from colonizing source, erosion and deposition of volcanic deposits) and three nominal variables (habitat types: tephra, tephra in gully and original surface). Canonical correspondence analysis showed that the original surface played a special role in vegetation development because the old topsoil supplied both nutrients and seed‐bank species. The CCA also suggested that the environmental factors that influence plant density and cover differ. Distance from colonizing source affected plant density while erosion affected cover. Using CCA, factors could be distinguished that influenced seedling establishment from vegetation expansion and vegetation recovery dynamics could also be more clearly interpreted.

This content is not available in your region!

Continue researching here.

Having issues? You can contact us here