Thames Holocene: A geoarchaeological approach to the investigation of the river floodplain for High Speed 1, 1994–2003
Description:
The archaeological investigation of the route of High Speed 1 (HS1; formerly the Channel Tunnel Rail Link) through the Thames Marshes required an innovative approach to mitigation in order to find and reach the deeply buried, but highly significant, palaeoenvironmental and geoarchaeological sequences. Early on in the construction project it was evident that a geoarchaeological approach would be necessary because of the depth of sequences and the relative invisibility of the archaeological resource, both within the Historic Environment Record, and to conventional archaeological prospection. An initial desk-based study of geotechnical and geomorphological data produced a model for the alluvial corridor which categorised zones of potential that could be compared against construction impacts. Subsequent field survey included geophysical investigation of buried sediment bodies, the use of boreholes, cone penetration testing and conventional test pitting and trenching. The project was highly successful in predicting the location of buried archaeological remains in a number of locations. Key amongst these are extensive remains excavated in the Ebbsfleet Valley, Mesolithic flint scatters at Tank Hill Road, Aveley, and Late Upper Palaeolithic and Neolithic scatters on Swanscombe Marsh. Other sites described here include an in situ Early Neolithic flint scatter and evidence of seasonal Roman and medieval activity on Rainham and Wennington Marshes. As important, in addition to the archaeological results, this work also presents the methodological approach that was adopted for the investigation of approximately 18km (17%) of the HS1 route across an area of thick alluvium.
We're an Amazon Associate. We earn from qualifying purchases at Amazon and all stores listed here.
Want a Better Price Offer?
Set a price alert and get notified when the book starts selling at your price.
Want to Report a Pricing Issue?
Let us know about the pricing issue you've noticed so that we can fix it.