Dropdown contents (roles, vehicles, personnel, ...) are treated as PII and are never compiled into the application. A fresh install starts with empty master data; you populate it in the in-app Stammdaten editor by importing a JSON file, and can write your own data back out again.
Each Trupp-Typ row holds the crew size (Stärke, 2 or 3) and the Einsatzzeit the
Atemschutz form suggests when that type is picked. A CSA-Trupp is three people on a
shorter clock because its Stammdaten row says so — not because the app recognises the
word "CSA". Rename it, add a Chemietrupp of your own, or give a Sicherheitstrupp a
longer Einsatzzeit, and the rules follow the row.
A Trupp is never fewer than two people and never more than three: the Atemschutzüberwachung has exactly three positions (Truppführer, Truppmann, 2. Truppmann) and nowhere to write a fourth name.
There is no separate list of brigades (Wachen) or radio call signs (Funkrufnamen): both are derived from the vehicles — every vehicle's Wache becomes a brigade suggestion, and every vehicle's call sign (plus every roster person's call sign) becomes a call-sign suggestion. Maintaining the vehicle list is all that is needed; every field still accepts free text for anything not in it (a Leitstelle, a mutual-aid unit).
textSnippets is one list, Textbausteine in the Stammdaten editor. Each
Textbaustein says which areas offer it, with one checkbox per area:
| Checkbox | JSON | Offered in |
|---|---|---|
| ETB | etb |
the ETB entry, the ETB edit panel |
| AUFGABEN | tasks |
the Aufgaben dock, the Aufgabe dialog, the Aufgabe edit panel |
What a Funker reports ("Einsatzstelle erreicht, Erkundung läuft") is usually
ticked for the ETB only, and what the Lagebuchführer gives out ("Energieversorger
informieren") for Aufgaben only. A phrase both use ("Polizei verständigen") is
ticked for both and kept once. A missing etb or tasks reads as true, so a
hand-written entry that names no area is offered everywhere. One ticked for
neither is kept but offered nowhere. More areas will come as further keys.
Each entry has a shortcut (the Kürzel), a text and an optional category.
Typing :: in a field lists the Textbausteine ticked for its area; the letters
after :: narrow the list — Kürzel first, then any whose text or Kategorie
contains them. ↑/↓ choose, Enter or Tab insert, Esc closes the list and leaves
the typed text alone. A tap inserts on a phone.
[…] in a text marks a gap: after inserting, the first one is selected, so
::lgb followed by Zimmerbrand 2. OG reads Lage bestätigt: Zimmerbrand 2. OG.
(On Android the caret simply follows the text, because the soft keyboard and
a programmatic selection do not get along.)
A Kürzel is stored lower case, letters and digits only, at most 12 characters;
::STL, stl and s-t-l are the same Kürzel. Each Kürzel exists once in the
list, whichever areas it is ticked for. The editor names a duplicate instead of
saving it, and an import keeps the first.
A text is cut to 1000 characters, what an Aufgabe may hold. The inserted text
is plain text in the entry: changing a Textbaustein later changes no entry.
premises is the list Objekte in the Stammdaten editor: buildings in the
Ausrückebereich whose structure is known long before the call, such as a
recurring Wohnanlage. Each Objekt has a name, an optional address (street,
houseNumber, postalCode, place) and the structure a Haus in the
Gasmessprotokoll starts with:
| Field | JSON | Range | Missing reads as |
|---|---|---|---|
| Geschosse | floors |
1–50 | 8 |
| Wohnungen/Geschoss | apartmentsPerFloor |
1–30 | 10 |
| Untergeschosse | undergroundFloors |
0–3 | 1 |
apartmentLabels names Wohnungen, keyed "floor:apartment": "0:1" is the
first Wohnung in the EG, "2:3" the third in the 2. OG and "-1:1" the first
in the 1. UG. The editor shows them as a grid of every floor and Wohnung under
WOHNUNGEN BENENNEN. A Wohnung without a label keeps the name the CO matrix
gives it (Links/Mitte/Rechts on a floor of three, Whg. N otherwise). A
label is cut to 60 characters, and a key that names no floor or Wohnung of the
Objekt is dropped.
Typing in BEZEICHNUNG in the Gasmessprotokoll's HAUS HINZUFÜGEN dialog suggests the Objekte. Picking one fills Geschosse, Wohnungen/Geschoss and Untergeschosse, unless one of them was already changed by hand, and the Haus is created with the Objekt's Wohnungsbezeichnungen. These values are copied into the Einsatz. Editing or deleting the Objekt later changes no Haus already in an Einsatzdatei. A name that matches no Objekt adds a Haus exactly as before.
The address is not copied, because a Haus in the Gasmessprotokoll has none. It tells two Objekte apart in the list. Out-of-range numbers are clamped, rows without a name are skipped, a second Objekt of the same name (ignoring case) is dropped, and a list holds at most 500 Objekte.
gases is the list Messgase: the gases a crew reads off its multi-gas meter
or detector tubes in the Gasmessung, at most eight, in the order every Einsatz shows them.
| Field | JSON | Meaning |
|---|---|---|
| Gas | name |
the label on the tile, in the editor, the ETB and the PDF; at most 12 characters |
| Einheit | unit |
free text, e.g. ppm, %UEG, Vol-%, mg/m³; at most 10 characters |
| Richtung | direction |
"steigend" (higher is worse) or "fallend" (lower is worse, for O₂); anything else reads as steigend |
| Erhöht / Gefährlich / Lebensgefährlich | elevated / dangerous / lethal |
the bands, each optional, ordered in the gas's direction |
| Plausibel bis | plausibleUpTo |
optional; a reading above it gets the "bitte auf Tippfehler prüfen" hint and is still recorded |
| Anreicherung ab | upperAlarm |
optional, fallend only; a reading at or above it counts as Gefährlich, e.g. O₂ enrichment from 23 Vol-% |
A falling gas can be dangerous both ways: O₂ below 19 Vol-% is a lack of oxygen, O₂ from about 23 Vol-% an enrichment that feeds a fire. Anreicherung ab is the upper limit for that second case. A reading at or above it is coloured as Gefährlich and counts towards the worst gas of the Wohnung, like any band. It must lie above the gas's mildest band (Erhöht, or the next one set) and not above Plausibel bis. It assumes no particular instrument: a Gastec 31B tube reads O₂ from 6 to 24 %, so 23 Vol-% is a limit a tube can show as well as a multi-gas meter. On a steigend gas the field means nothing; the editor hides it and the import drops it.
Numbers may carry decimals (20.9 in the file, 20,9 on screen). A gas without
any band is recorded and shown without colour. A Stammdaten file without gases,
or with an empty list, measures CO in ppm, steigend, 20 / 60 / 200, plausible
up to 2000. Those are the alarm thresholds A1 / A2 / A3 that DGUV FBFHB-021 gives a
three-threshold CO meter (Dräger, Alarmschwellen BOS, 08/2024), so the tile turns
when the crew's meter alarms. An Einsatzdatei from before the Messgase list keeps
the bands the app used then, 30 / 200 / 800, so reopening it recolours nothing.
The bands are meant to match the crew's own meters:
| Band | Meter | Means |
|---|---|---|
| Erhöht | A1 | first alarm |
| Gefährlich | A2 | second alarm |
| Lebensgefährlich | A3, the highest threshold | Rückzug |
A two-threshold meter alarms at A1 and A2 only (DGUV: 20 and 200 ppm for CO). Its A2 is the Rückzug threshold, so set Lebensgefährlich to it and leave Gefährlich empty: 20 / — / 200. Check the values against your own devices and Dienstanweisung before relying on them.
The import rejects a file whose bands, or Anreicherung ab, are out of order for their gas, because guessing which of them was meant would colour a Wohnung wrongly; a band that is not a number, negative or above 100 000 rejects it too. More than eight gases are cut at eight, an overlong name or unit is cut, and a second gas of the same name (ignoring case) is dropped. The editor names the same problems and does not save until they are fixed.
The list is copied into an Einsatz when the Gasmessung opens its first Haus. From then on the Einsatz keeps its own copy: editing the Messgase later changes no Einsatzdatei, and a joined device shows the host's list.
talkGroups lists the Funkgruppen a Führungsstelle works on: each has a name, an
optional number (the Kurzwahl, the short dial a radio selects the group by), a kind
("tmo" or "dmo", TMO when missing or unknown) and an optional note saying what the
group is for. A picker lists a group as 307_F (KW: 307), with its note underneath.
favorite: true marks a group used most often; every Funkgruppen
picker lists the favourites first, then the rest alphabetically, and a missing
favorite means no favourite. A name is required and at most 200 characters. The editor shows them in
a Funkgruppen section, and an Einsatz copies the text it uses, so renaming or
deleting a group here never changes a past Einsatz.
A role may carry an optional slot — leiter, melder, fuehrungsassistent or
fachberater — the post on the Führungstafel its holder fills. A missing or unknown
slot means none. The editor shows the slot in the Führungs-Organisation column and
calls fuehrungsassistent "Führungsunterstützung", the name the FÜHRUNG board uses; the
key itself is unchanged.
dispatchPlaceNames tells the alarm import (alarmierung-ff-agent.md)
how the Leitstelle spells a place that the vehicles' Funkrufnamen abbreviate. Each entry has a
name, the place as the alarm writes it ("Fürstenfeldbruck"), and an abbreviation, the
place as the Funkrufnamen write it ("FFB"). Both are required and at most 100 characters.
With that entry an alarmed Florian Fürstenfeldbruck 2/40/1 finds the vehicle FFB 2/40/1. The
place is replaced as whole words, in any case, and the longest place name is tried first. A
Funkrufname the alarm already ends with, such as Maisach 40/1, needs no entry. The editor shows
the list in an Alarmierung section. The list is used only for matching; nothing of it enters
an Einsatz.
vehicleTypeCodes maps the Fahrzeugkennung, the middle number of a Funkrufname such as
FFB 1/12/1 or Florian Emmering 1/12/1, to the Fahrzeugtyp it stands for:
{ "kennung": "12", "vehicleType": "MZF" }. Both fields are required and at most 16
characters, the cap a Fahrzeugtyp has everywhere. A Funkrufname that does not end in three numbers
split by slashes (Florian Musterdorf 40/1) has no Kennung and is left alone.
A vehicle whose Fahrzeugtyp is empty takes it from this list: in the editor as its Funkrufname is typed, in the Kräfte form when it is picked, and in the alarm import, which also types a unit the Stammdaten do not know. A Fahrzeugtyp already chosen is never replaced. For a Kennung listed twice the first entry wins. The editor shows the list in a Fahrzeugkennungen section. Only the type's text enters an Einsatz, never a reference to the list.
A personnel row carries an optional email and an optional note besides the
name, role, call sign and phone number. The Kontakte tab in the Einsatz rail
lists the roster and searches all of them at once.
note is free text the brigade maintains, and in practice it holds one of two
things: a Fachgebiet (KBM Gefahrgut, Fachberater Arbeits- und Gesundheitsschutz, Fachberater EDV, PSNV-E Team) or the Feuerwehren someone
covers (Alling, Biburg, Eichenau, Emmering). That is what makes the tab able
to answer "wer ist zuständig für ABC?" — the search splits the query on spaces
and keeps a person when every term matches somewhere, so gefahrgut,
kbm gefahrgut and gefahrgut kbm all find the same person.
Telefonnummer and E-Mail-Adresse open the device's dialer and mail app.
Lagebuch never places a call itself: the dialer comes up prefilled and the
operator still presses call. Both values are validated before they reach the
platform, because they arrive from an imported file rather than from the
operator's keyboard — an address carrying a line break or a ?bcc=, or a number
carrying a USSD code, is refused rather than launched.
Both fields are optional everywhere. A roster that has neither still works, and a person without an address simply shows no mail button.
The Stammdaten editor checks an address against the same rules the launcher applies, and names anyone whose address could not be opened instead of letting SPEICHERN write it — the operator who typed it is the one who can still fix it. The same check runs right after an import, which is where an unusable address most often comes from.
The Ortsteile (districts) and Straßen (streets) are offered as
suggestions in the STRASSE and ORTSTEIL fields of the Einsatzdaten. Picking a
street fills in its Ortsteil, PLZ and Ort, but only into fields that are still
empty, and only where every row of that street agrees. A street that runs through
two Ortsteile is two rows, and picking it leaves ORTSTEIL for the
Lagebuchführer. Both lists are suggestions, never a closed set: an address that
is not listed is still recorded as typed.
A Gemeinde has hundreds of streets, so nobody types them in. make osm-streets
fetches them from OpenStreetMap through the Overpass API:
# districts and streets as a JSON fragment
make osm-streets AGS=09179121 OUT=strassen.json
# or replace them inside an exported Stammdaten file, then IMPORTIEREN it
make osm-streets AGS=09179121 MERGE=meine.masterdata.jsonAGS is the eight-digit amtlicher Gemeindeschlüssel (09179121 is
Fürstenfeldbruck). It identifies the Gemeinde unambiguously, where a name would
not: several Gemeinden are called Puch. Outside Germany, pass the boundary's OSM
relation id as RELATION= instead. MERGE rewrites only districts and
streets and leaves the rest of the file as it was. Two runs over unchanged map
data give a byte-identical file, so a regenerated list only shows a diff where
the map changed.
What the list contains is decided by what OpenStreetMap holds:
- Street names come from named roads. An address only confirms a name that a
road already has, because
addr:streettags carry typos. A Weiler that is addressed by its own name („Rothschwaig 1") is listed as a street too. - PLZ and Ort come from the street's own addresses, and otherwise from the Gemeinde, if it has only one PLZ.
- Ortsteile are the Gemeinde's
placenodes (village, hamlet, suburb …). Which Ortsteil a street is in is filled in only where its addresses say so (addr:suburb,addr:hamlet). That is rare: in Fürstenfeldbruck it is the streets of Puch and Aich. OpenStreetMap has no Ortsteil boundaries to test a street against, and a nearest-point guess would put wrong Ortsteile into an Einsatz, so the tool does not guess. Fill in the rest in the Straßen editor, or in your own generator.
The data is © OpenStreetMap contributors, available under the ODbL 1.0. Keep that attribution with any file you pass on.
samples/demo-stammdaten.json is a complete,
fictional set (two Wachen, seven vehicles, a small roster, checklists, links)
for trying the app out. samples/uebung.lagebuch
is a matching fictional incident. Both are regenerated with make samples;
the round-trip test in tests/LageBuch.Persistence.Tests/DemoIncidentTests.cs
keeps them valid as the schema evolves.
Checklisten sind Stammdaten: Sie legen beliebig viele an — keine, zwei, fünf — geben jeder einen Namen, und jeder neue Einsatz startet mit einer eigenen Kopie davon. Ein späteres Umbenennen oder Löschen einer Vorlage rührt einen laufenden oder abgeschlossenen Einsatz nicht an; der trägt seine Listen selbst.
Die Kategorie Navigation bestimmt, was die Seitenleiste eines Einsatzes zeigt und in welcher Reihenfolge: die eingebauten Module und jede Checkliste in einer Liste, jeweils ein- oder ausschaltbar. Das ETB ist immer sichtbar und lässt sich nicht abschalten — es ist die rechtlich relevante Aufzeichnung, und jede Systemmeldung landet dort. Verschieben lässt es sich sehr wohl.
Eine leere Navigation bedeutet „Standard": die Reihenfolge, mit der Lagebuch ausgeliefert wird. Das ist Absicht — so taucht ein Modul, das eine spätere Version ergänzt, bei allen auf, die die Liste nie angefasst haben.
Funktionen und Kräfte sind keine eigenen Einträge mehr, sondern Reiter von Führung — neben der Führungsorganisation. Eine früher gespeicherte Navigation, die sie noch einzeln nennt, zeigt Führung an der Stelle des ersten der drei Einträge; eingeblendet ist es, wenn einer von ihnen eingeblendet war. Beim nächsten Speichern der Navigation steht es so auch in den Stammdaten.
Beim Öffnen eines älteren Einsatzes gilt: Was die Navigation nennt und der Einsatz hat, wird gezeigt; was sie nennt, der Einsatz aber nicht hat, entfällt; und eine Checkliste, die der Einsatz hat, die Navigation aber nicht kennt, wird hinten angehängt. Eine archivierte Einsatzdatei zeigt damit immer alle ihre Listen.
On first start an empty masterdata.db is created. It is the live database the
app reads and writes from then on, and where the Stammdaten editor saves:
| Platform | Path |
|---|---|
| Windows | %AppData%\Lagebuch\masterdata.db |
| Linux | ~/.config/Lagebuch/masterdata.db |
| macOS | ~/.config/Lagebuch/masterdata.db |
On macOS the app uses ~/.config, not ~/Library/Application Support —
that is simply where .NET's ApplicationData folder resolves on Unix. To start
over, delete masterdata.db; the app recreates it empty on the next launch.
When you join another device's incident ("Mit Gerät verbinden"), that device's master data is used for the whole session — its vehicles (and the brigades and call signs derived from them), its roster, its Trupp-Typen with their Stärke and Einsatzzeit, and its Rückzugsdruck. The host is the master, so both devices always agree: an Atemschutz-Trupp registered from a joined tablet gets exactly the crew size and Einsatzzeit the host would have used.
The join flow itself never reads or writes your own masterdata.db — it just
isn't consulted while you're joined. (You can still open Stammdaten and
edit it deliberately; that has no effect on the joined session, which keeps
using the host's set.) Leaving the incident returns the device to its own
master data — there is nothing to back up and nothing to restore. If the host
has no master data at all, the joined device shows empty dropdowns too; every
field still accepts free text.
Open Stammdaten and use the header buttons:
- IMPORTIEREN — offered only while the data is still empty (a first-run
bootstrap, not a merge). Pick a JSON file; its contents load into the editor as
unsaved changes for review, and reach
masterdata.dbonly when you press SPEICHERN (or VERWERFEN to discard). - EXPORTIEREN — writes the current master data (including unsaved edits) to a JSON file you can back up or hand to another install.
The file is one JSON object; every top-level key is optional, so a file may hold
the whole set, only the roster, or anything in between. See
master-data.example.json for the full schema.
A file exported by an older version may still carry brigades and
radioCallSigns lists; those keys are ignored, and any entry in them that no
vehicle or roster person covers is listed in a notice after the import so you
can add a vehicle for it before saving.
Such a file also has truppTypes as a plain list of names, from before the
Stärke and Einsatzzeit moved onto the row. It still imports: each name becomes a
two-person Trupp-Typ on the standard Einsatzzeit, except CSA-Trupp and
LPA-Trupp, which get the values the old hard-coded rule gave them (3 / 20 min
and 2 / 60 min). Your existing masterdata.db is migrated the same way, once,
the first time this version opens it — so nothing changes for a brigade using
the shipped spellings, and a brigade that had renamed the type gets the row it
can now correct itself.
roles carries how often a Funktion may be held: multiple (the default, so
any number of people may hold it), uniquePerIncident (one holder for the whole
Einsatz, whatever Abschnitt either of them is in) or uniquePerSection (one per
Abschnitt; an empty Abschnitt counts as a bucket of its own). A file exported
before this version has roles as a plain list of names, from before the
setting moved onto the row. It still imports, and every name comes
back as multiple. Your existing masterdata.db is widened the same way, the
first time this version opens it — the new column is simply absent before, and
absent reads as multiple too. Nothing is marked for you: a Funktion that may
not be held twice has to be marked in the editor afterwards.
Any real master-data or personnel JSON — street lists, station and call-sign
names, and above all names, mobile numbers and e-mail addresses — is
personal/identifying data and
must be kept out of the repository. seed-source/ and *.masterdata.json
are gitignored for exactly this reason; only the anonymised example and demo
files under docs/ are tracked. An empty roster is a fully supported state:
the name field on the Funktionen tab offers the roster as suggestions but
always accepts free text, so off-roster and mutual-aid personnel can be entered
either way.
datenschutz-und-sicherheit.md is the German
page for the people who have to sign this off — it covers every category of
personal data the app holds, all of the storage locations above, what the
multi-device connection transmits, and the full deletion checklist.