Not logged in
Data Publisher for Earth & Environmental Science

Achterberg, Inke E M; Eckstein, Jan; Birkholz, Bernhard; Bauerochse, Andreas; Leuschner, Hanns Hubert (2017): Dendrochronological dates of subfossil pines (Pinus sylvestris L.), relative dates of floating chronology, and peat stratigraphy from site "TOMO_south" at Totes Moor, northwest Germany. PANGAEA,, Supplement to: Achterberg, IEM et al. (2018): Dendrochronologically dated pine stumps document phase-wise bog expansion at a northwest German site between ca. 6700 and ca. 3400 BC. Climate of the Past, 14(1), 85-100,

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

RIS CitationBibTeX CitationShow MapGoogle Earth

This is a dendrochronological investigation of a mire site densely covered by peat-preserved pine stumps (Pinus sylvestris). The site in the northwest German Tote Moor revealed to feature trees from various Holocene millennia. The dendrochronologically dated site chronology covers 2345 years between 6703 BC and 3403 BC, containing 5 gaps between 6 and 550 years in length. It consists of 477 trees. A floating chronology segment of 309 years, containing 30 trees, was radiocarbon dated to the beginning of the 7th millennium cal. BC. The tree ring data from the site documents environmental changes over a larger period of time. Furthermore, the site is covered densely with in situ tree stumps from the fen-bog transition. This facilitates the spatio-temporal reconstruction of mire development, which is based on 212 in situ tree stumps in the case study presented here. Peat-stratigraphical survey was carried out additionally, and elevations a.s.l. were determined at several locations.
Median Latitude: 52.502872 * Median Longitude: 9.383946 * South-bound Latitude: 52.498880 * West-bound Longitude: 9.376340 * North-bound Latitude: 52.505840 * East-bound Longitude: 9.389830
Date/Time Start: 2009-07-15T00:00:00 * Date/Time End: 2009-09-11T00:00:00
3 datasets

Download Data

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