Skip to content

freemapper-courseplan v0.16.0

Choose a tag to compare

@github-actions github-actions released this 13 Nov 06:51
· 35 commits to main since this release

Added

  • Three recommendations of the project owner, each with a setting in the [score] table (ADR 0085 to 0087). A manual course may deviate; check only warns, hints or reports, and score suggest and score draft keep to them.
    • Dead ends: check warns when a control stands deeper in a dead end than dead_end_max_m (default 60 m, 20 to 300; rule wkb2026.control.dead_end, sprint and schoolyard maps). The depth is the walk from the control to where the path network offers a choice again; open areas and courtyards are no corridors. A control beside a wall, fence or thin building is also judged from the free cells a few metres around it, and the deepest answer counts. The draft and the suggestion leave such sites out. On the Gleisdreieck map a quay spur of 208 m is the case; a control that stood 68 m deep on it set the default (ADR 0085).
    • Start and finish: check gives a hint when they are more than start_finish_max_m (default 400 m, 50 to 2000) apart in a straight line (rule wkb2026.course.start_finish_distance). score draft, and score suggest --course, refuse such a start and finish with a message that names both positions, the distance, the limit and the setting (ADR 0086).
    • Margin from the edge of the mapped area: check reports a start, finish, control or crossing point closer than map_margin_m (default 50 m, 0 to 200) to the edge as an error (rule wkb2026.map.margin). The edge is where no map object lies within 40 m any more; the distance is measured on a raster, to about 2 m. The draft leaves such sites out and refuses a start or finish that is too close (ADR 0087).
    • The settings come with score settings --dead-end-max M --start-finish-max M --map-margin M, the tool set_score_settings and three fields in the Score settings panel of the editor.
  • check reports a start, finish, control or crossing point in the blank part of the sheet as an error. The new rule wkb2026.map.inside (source BL02, as the research file cites it) measures against the map objects themselves: a position counts as mapped when a map object lies within 40 m of it. The sheet frame (an axis-aligned rectangle line that spans 80 percent of the terrain) and layout symbols such as the north lines pattern (601, 602) do not count as objects. The message names the position, the nearest object and the limit. map_edge stays as it was; it measures against the box around the map objects and did not see a position in the blank corner of a diagonal map. Score courses are tested with start, controls and finish. See ADR 0084.
  • The pictures of the examples: the examples page and both example READMEs show the course in the editor, with start and finish on the map. The Gleisdreieck picture is new (docs/manual/images/gleisdreieck-course.jpg).

Changed

  • The example "Gleisdreieck" is redrafted under the new limits: 32 minutes, 26 controls, 63 points, the very good runner inside the band and the good runner near the target (before: 34 minutes, 33 controls, 95 points). Control 54 of the old version stood at the tip of the quay spur, 208 m deep, and six more controls were 39 to 47 m from the edge of the mapped area. Project file, IOF XML, control list, sheets, transcripts, check output, READMEs, the manual and its four Gleisdreieck pictures follow; the files score-34.* became score-32.*. check is quiet apart from four accepted warnings (three alike code pairs and the share of hard controls).
  • The score drafts on the Rummelsburger Bucht reach 11 minutes with both runners inside their bands and 12 near the target (before: 16 and 17), since sites keep 50 m from the edge of this narrow strip. Start, finish and the four controls of the example course already kept the margin and stay.
  • The score draft keeps its sites off the sheet frame by the same test as the new rule, with the extent of the terrain objects instead of the extent of all objects. On the Rummelsburger Bucht the frame was not recognised before, so a draft could take sites at its corners. The largest draft with both runners in their bands on that map is now 16 minutes (17 near the target). See ADR 0084.
  • The README of the Rummelsburger Bucht example and the manual (captions, section "Checking") follow the new course, and the manual pictures of the example are new.

Fixed

  • The example "Rummelsburger Bucht" had its finish in the blank part of the sheet, beside the map, and its start far from it. Start and finish now stand in the park in the middle, 34 m apart, and the course is a loop of four controls and 905 m (before: five controls, 1226 m). Project file, IOF XML, Purple Pen file, outputs, READMEs and all editor pictures of the example follow. check is clean. The example "Gleisdreieck" was checked: its start and finish (60 m apart) and all controls lie on the map.

Download the archive for your system, unpack it and start freemapper-courseplan
(Windows: freemapper-courseplan.exe) from a terminal or register it with your AI assistant.
Installation and first steps: see README.md (Deutsch) / README.en.md (English) in the
archive or https://github.com/HenryJobst/freemapper-courseplan#readme

  • Windows: freemapper-courseplan-v0.16.0-windows-x86_64.zip
  • macOS Apple Silicon (M1 and newer): freemapper-courseplan-v0.16.0-macos-arm64.tar.gz
  • macOS Intel: freemapper-courseplan-v0.16.0-macos-x86_64.tar.gz
  • Linux: freemapper-courseplan-v0.16.0-linux-x86_64.tar.gz (ARM: linux-arm64)

The .gz files and freemapper-courseplan-update.json with its signature are for freemapper update.

Full Changelog: v0.15.0...v0.16.0