Not logged in
PANGAEA.
Data Publisher for Earth & Environmental Science

Sturzenegger, Matthieu; Stead, Doug; Gosse, John; Ward, Brent; Froese, Corey (2014): Palliser Rockslide cosmogenic 36Cl exposure ages (raw data) and erosion effect on the cosmogenic [dataset publication series]. PANGAEA, https://doi.org/10.1594/PANGAEA.833893, Supplement to: Sturzenegger, M et al. (2014): Reconstruction of the history of the Palliser Rockslide based on 36Cl terrestrial cosmogenic nuclide dating and debris volume estimations. Landslides, 12(6), 1097-1106, https://doi.org/10.1007/s10346-014-0527-4

Always quote citation above when using data! You can download the citation in several formats below.

RIS CitationBibTeX CitationShow MapGoogle Earth

Abstract:
This paper presents the results of a combined study, using cosmogenic 36Cl exposure dating and terrestrial digital photogrammetry, of the Palliser Rockslide located in the southeastern Canadian Rocky Mountains. This site is particularly well-suited to demonstrate how this multi-disciplinary approach can be used to differentiate distinct rocksliding events, estimate their volume, and establish their chronology and recurrence interval. Observations suggest that rocksliding has been ongoing since the late Pleistocene deglaciation. Two major rockslide events have been dated at 10.0 ± 1.2 kyr and 7.7 ± 0.8 kyr before present, with failure volumes of 40 Mm3 and 8 Mm3, respectively. The results have important implications concerning our understanding of the temporal distribution of paraglacial rockslides and rock avalanches; they provide a better understanding of the volumes and failure mechanisms of recurrent failure events; and they represent the first absolute ages of a prehistoric high magnitude event in the Canadian Rocky Mountains.
Coverage:
Latitude: 50.630000 * Longitude: -115.160000
Event(s):
Palliser_Rockslide * Latitude: 50.630000 * Longitude: -115.160000 * Location: Canada
Size:
2 datasets

Download Data

Download ZIP file containing all datasets as tab-delimited text — use the following character encoding: