Skip to content

freemapper v0.16.0

Choose a tag to compare

@github-actions github-actions released this 13 Nov 07:53
· 480 commits to main since this release

Added

  • Vegetation from laser point clouds in Saarland too (ADR 0105): LVGL offers the 2025 point cloud in six large zip64 archives by district, on the same share as the height models. freemapper reads only the tiles of the map area out of them by byte ranges, about 40 MB per square kilometre, and checks them against the archive's CRC. The scan was made in February without leaves, and the point cloud is thinned to one point per 0.5 m; freemapper still finds the crowns. Checked on the old town of Saarlouis. Saxony gets no point clouds for now: GeoSN took them off its download area in November 2026.
  • Vegetation from laser point clouds in Rhineland-Palatinate too (ADR 0105): fetch loads the LAZ tiles of LVermGeo RP, mostly 110 to 500 MB per square kilometre, and keeps a tile only when its size and SHA-256 match the Metalink file of the state. The day of the scan comes from the metadata of the tile; when the tile is cached, freemapper asks only for that. Checked on the Stadtpark in Mainz.
  • Vegetation from laser point clouds in Berlin too (ADR 0105): the Geoportal Berlin offers the point cloud only in nine large zip64 archives. freemapper reads just the tiles of the map area out of them by byte ranges, about 240 MB per square kilometre, checks them against the archive's CRC and keeps them in the cache as LAZ (about 100 MB). The 2021 scan was made without leaves, so freemapper recognises dense shrubs there less well. Checked on the Viktoriapark.

Changed

  • The manual's pictures of the area page are taken again (area selection, options, progress), with a new picture of the section "What goes onto the map" and all its groups. The hint of the profile "Balanced" on the page now says what the profile does: contours and the areas that shall not be entered along railway tracks go onto the map, and stairs, banks, monuments and passages also come from OpenStreetMap.
  • The examples Sanssouci, Viktoriapark, Monschau, Cochem and Saarlouis are rebuilt with --content-set vegetation=candidates: their training maps now show the vegetation from the point clouds. The map objects of the first four are unchanged; Saarlouis has 109 street areas instead of 32 and the Saar from ALKIS, through the fix of the land uses. Bautzen stays without vegetation, because Saxony offers no point clouds at present.
  • The boundaries of Lower Saxony and Schleswig-Holstein no longer overlap in the mouth of the Elbe. The cadastres of both states hold the same 89 km² of water off Cuxhaven; freemapper now splits that area at the line of equal distance from the two claim lines (ADR 0113). Maps do not change, the area is open water.
  • The adapter guide says what a code adapter can bring beyond the cadastre and the rasters: sets of extra layers and raster templates. ADR 0114 records how Berlin's registers and the K5 moved from the engine into the adapter and what stays open.
  • Internal: the engine no longer asks "is this Berlin?" anywhere. The warning about missing buildings, the list of templates and every fetch for an adapter go through the registry; the K5 service lives with Berlin's adapter, the reader of stored layers in freemapper-sources. A test holds that the engine names no state outside the draw rules and reaches into the adapter crate only at the lines listed there. Maps, messages and files do not change.
  • Internal: an adapter can name raster templates it fetches with code of its own (RegionAdapter::templates). Berlin's map 1:5000 (K5) is the first: the engine asks the adapter of the registry and takes the date, the messages and the item of the estimate from there. The template, the messages and the estimate do not change.
  • Internal: an adapter can name sets of extra layers it fetches with code of its own (RegionAdapter::extras). Berlin's registers and surveys are the first such set: the engine asks the adapter of the registry instead of calling the Berlin module, and takes the item of the estimate from there too. Maps, messages, files and estimates do not change; the one exception is under "Fixed".
  • Internal: the extra layers of a project (Berlin's registers, the full ALKIS, the tree cadastres) are fetched, stored, removed and read in one place instead of in three equal copies. A first step towards an engine that names no state; maps, messages and files do not change.
  • Internal: the modules in freemapper::sources that only passed on what has lived in freemapper-adapters-de and freemapper-sources since the adapter work are removed, and so is the raster fetch for Saxony-Anhalt in program code that nothing used any more. The state still fetches through the services its manifest names; maps and requests do not change.

Fixed

  • Vegetation from point clouds stops at areas that shall not be entered (520). Before, the forest candidates punched white holes into the olive green private gardens and courtyards of the candidates map and the training PDF, because the white of the forest lies above the olive green in the colour order. On the map this holds for the areas of the map, in the candidates for those of the map and of the candidates (ADR 0105).
  • freemapper adapters check --live for an area near Berlin no longer fetches Berlin's registers and the K5 template when another adapter is checked. Before, those requests went out without the host rules of Berlin's adapter, and the next command dropped the records again.
  • Saarland: the WFS of LVGL writes the land use classes Strassenverkehr and Fliessgewässer. freemapper knew only Straßenverkehr and Fließgewässer, so Saarland maps lacked the street areas from ALKIS, the rivers from ALKIS and everything that depends on them, and the vegetation from the point cloud put open land on the streets. Every land use class from a WFS is now brought into the LGB spelling, as for Hamburg already; in Rhineland-Palatinate Unland, Vegetationslose Fläche thereby reads Unland/Vegetationslose Fläche as everywhere else.

Download the archive for your system, unpack it and start freemapper
(Windows: freemapper.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#readme

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

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

What's Changed

  • ci: pull requests run on Linux unless labelled all-systems by @HenryJobst in #56
  • Remove the re-exporting source modules and the unused backend of Saxony-Anhalt by @HenryJobst in #57
  • feat(vegetation): point clouds of Saarland; Saxony has none for now by @HenryJobst in #58
  • Split the mouth of the Elbe between Lower Saxony and Schleswig-Holstein at the line of equal distance by @HenryJobst in #59
  • fix(saarland): land use classes in the LGB spelling by @HenryJobst in #61
  • Extra layers, step 1: one mechanism for Berlin's layers, the full ALKIS and the tree cadastres by @HenryJobst in #62
  • Extra layers: the review points of step 1 (table keys, one lookup, tests, changelog) by @HenryJobst in #63
  • Extra layers, step 2: an adapter names its sets and the engine asks the registry by @HenryJobst in #64
  • Extra layers, step 2d: the K5 map is a raster template of Berlin's adapter by @HenryJobst in #65
  • Extra layers, step 3: the engine names no region outside its draw rules by @HenryJobst in #66
  • Extra layers, step 4: ADR 0114 and the adapter guide by @HenryJobst in #67
  • Vegetation stops at out-of-bounds areas; four examples rebuilt with point-cloud vegetation by @HenryJobst in #60

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