Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

feat(wasserfoerderung): Einsatzauftrag per pump position with Funkrufname and UTMREF

Open
  • Is something wrong?
#586 0 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
15/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Active
Tech stack
android, csharp, sqlite
Domain
desktop

Research direction

The payload names no files or tests. Start with the analysis in the review comment on #150 and the Stammdaten vehicle model that the Funkrufname picker reads from. The UTMREF/MGRS conversion is the most self-contained piece and should be checked against known reference points. Done means one overview page and one A4 page per pump position render, with the 'Koordinate nicht hinterlegt' fallback for profiles without coordinates.

Written by the indexing model from the issue text.

Description

Slice 3 of the Wasserförderung restart (#150), and the bridge to execution mode (#87). Analysis: see the review comment on #150.

Add an Einsatzauftrag: one overview page plus one A4 page per pump position, to hand to each vehicle.

Scope
  • Assign a Funkrufname to every pump position, picked from the Stammdaten vehicles. Copy the value into the incident; never store a reference.
  • Per page:
    • Fahrzeug and role.
    • Standort as UTMREF/MGRS (32U PU 12345 67890, what German BOS maps use) plus WGS84 decimal; Höhe and Station.
    • Ausgangsdruck to set and Eingangsdruck to expect.
    • B-20 hoses to the next pump, section length and rise.
    • Where the water comes from and where it goes (the neighbouring Pos and Fahrzeug).
    • Rückmeldung box.
  • UTMREF conversion is BCL-only and tested against known reference points.
  • A profile entered without coordinates still gets its pages, with "Koordinate nicht hinterlegt".
Not taking
  • what3words (proprietary, needs an API key).
  • Plus Codes as the primary location.

🤖 Generated with Claude Code

Dominant language
C#
Stars
1
Forks
3
Avg merge
4h 34m
Merged PRs (30d)
182

Getting set up

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from CodeForFire/lagebuch

All issues in CodeForFire/lagebuch

Similar issues

More C# issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.