go-v.orgdoi

The Digital Workflow of the Cultural Heritage Response Unit (CHRU)

Pouria Marzban, Elvira Iacono, Bernhard Fritsch, Helena Brinckmann, Sibel Erhan, Benjamin Ducke, Tobias Busen, Katja Piesker · Journal of Computer Applications in Archaeology · 2026

  • DOI 10.5334/jcaa.233
  • Publisher Ubiquity Press
  • Type article
  • Issued 2026

Not cached yet. This record was fetched live for this request and is stored after the lookup. Reopening the page should serve the cached copy.

Journal of Computer Applications in Archaeology · Ubiquity Press · article · 2026

Abstract

Natural disasters and intensive land use increasingly threaten archaeological and cultural heritage (ACH) sites. To address this, the German Archaeological Institute (DAI), with the Leibniz Centre for Archaeology (LEIZA) and the Federal Agency for Technical Relief (THW), launched in 2021 the project KulturGutRetter (KGR), establishing a rapid-deployment Cultural Heritage Response Unit (CHRU) with the focus on safeguarding worldwide cultural heritage at risk after disasters.

While the CHRU has not officially declared operational readiness yet, it was able to gain valuable experience during a national full-scale exercise and by participating in an EU MODEX (Module Exercise) in the Venice Lagoon (both in autumn 2024; e.g. Papa et al., 2025), which it has incorporated into its further development. Part of this experience also relates to the digital infrastructure, which CHRU relies on for efficient and uniform data collection during operations. Before, during and after missions, the CHRU employs fully open-source, standardised workflows for the documentation and assessment of affected cultural heritage, spanning the entire disaster-response chain.

Before teams are dispatched, a remote-sensing and GIS (Geographic Information Systems) support group compiles the latest satellite imagery, augments it with the in-house “KGR Finder” archaeological tool, and produces layered risk and damage maps. These datasets, packed together with a standard data model, are loaded to handheld devices running mobile GIS software for immediate field use. On site, CHRU team members record damage through structured digital forms and, when conditions allow, they conduct UAV (Unmanned Aerial Vehicle) photogrammetry, laser scanning and other 3D survey methods.

Moveable artefacts are registered on the spot: each object receives a QR-coded ID-card, enabling real-time assessment and tracking. A portable IT stack underpins this workflow. A mobile server hosts a PostgreSQL/PostGIS database, network-attached storage and synchronisation services, all accessible via an ad-hoc Wi-Fi or local cellular network. This lets teams consolidate data from multiple instruments instantly, secure it redundantly and keep every device in sync even in disconnected environments.

After a mission, all remotely sensed and field data that are free of third-party restrictions are transferred to the host nation’s antiquities authorities as a structured package, then archived on DAI servers for future research and publication upon agreement. The field records also provide essential ground truth for refining satellite-based assessments. This paper outlines the open-source technologies, data standards and practical lessons that make CHRU deployments globally scalable, rapid and resilient, thus offering a blueprint for safeguarding ACH under growing disaster pressure.

Highlights A general overview of all the digital components of the CHRU is given We illustrate the workflow of different components and how the data is gathered or recorded and further analysed Data management infrastructure is described, including both software and hardware perspectives The aim is to make a clear workflow of handling different datasets from the beginning to the end of a mission

Open the resolved locator · 10.5334/jcaa.233

Metadata licence: OpenAlex metadata (CC0)

Registry
OpenAlex DOI index + API
Fetched
2026-11-19 21:50 UTC
Cache state
not cached yet (bulk-index+openalex)
Locator
https://doi.org/10.5334/jcaa.233
Metadata licence
OpenAlex metadata (CC0)
Scope
Metadata as returned by the resolver; abstracts are never generated here.