Floods, fights and a fluid river: the Viennese Danube in the sixteenth century
Bibliographic record
Abstract
Alluvial rivers can show unpredictable channel changes and humans living along the river corridor repeatedly have to cope with the alterations of their physical environment. This was specifically the case in the mid-sixteenth century, when the Viennese were confronted with one major problem: the Danube River successively abandoned its main arm that ran close to the city and shifted further north. This was at the time when Vienna became the permanent residence of the Holy Roman Empire (except from 1583 to 1611 when it was moved to Prague), due to the Habsburgs holding the crown. Vienna was also the capital of the so-called Danube Monarchy, which came into being in the early sixteenth century. The city assumed increasing significance, being home to and hosting important authorities and persons. In particular after the first siege by the Ottoman army in 1529, the resource need for a complex fortification system was extremely high. This paper aims to highlight: (1) the morphological Danube dynamics together with floods and extreme weather situations in the sixteenth century; (2) the main actors in the transformation of the Danube; (3) changes of the river’s course from 1550 to 1600/1650 and the consequences for bridging the river and the infrastructure as a whole; (4) the massive engineering measures that were undertaken in order to secure Vienna’s requirements in the sixteenth century; (5) the question of floodplain settlements, and (6) the contested use of resources on the Viennese Danube floodplain.
Fetched live from OpenAlex and de-inverted. Abstracts are not stored in this database: the inverted indexes are 8.6 GB of the frame’s 9.3 GB of text, and the host has 13 GB free.
How this classification was reachedexpand
Full frame machine prediction
Teacher imitationNot calibrated prevalence, not ground truth. Human validation pending. The Gemma side is a direct model label for every work in the frame, read from the title-only record. The Codex side is a classifier learned from the 10,348 direct Codex labels and calibrated to design-weighted sample rates; fields without enough sample support carry no Codex call. Candidate is the union of the two sides; consensus is their intersection. These outputs are machine_predicted_unvalidated and are not human labels.
Distilled classifier scores by category (both heads)
| Category | Codex | Gemma |
|---|---|---|
| Metaresearch | 0.000 | 0.000 |
| Meta-epidemiology (narrow) | 0.000 | 0.000 |
| Meta-epidemiology (broad) | 0.000 | 0.000 |
| Bibliometrics | 0.000 | 0.001 |
| Science and technology studies | 0.003 | 0.005 |
| Scholarly communication | 0.002 | 0.001 |
| Open science | 0.000 | 0.003 |
| Research integrity | 0.001 | 0.001 |
| Insufficient payload (model declined to judge) | 0.002 | 0.000 |
Machine scores (provisional)
The two teacher heads of the student model, read on this work. A score orders the frame for review; it never asserts a category, and the validation status ships verbatim with every row.
Baseline scores from an immature model (maturity gate not passed, 7 training rounds). Scores rank; they never assert a category.
score_only:v0-immature-baseline · verbatim from the scoring run: score_only means the number may rank works, and no category label ships from itClassification
machine, unvalidatedMachine predicted; a candidate call from one source (direct Gemma or distilled Codex), not a consensus.
How this classification was reached, model by model and score by score, is at the end of the page under "How this classification was reached".