Skip to content

freemapper v0.18.0

Choose a tag to compare

@github-actions github-actions released this 13 Nov 22:13
· 335 commits to main since this release

Added

  • Baden-Württemberg (ADR 0119): maps in Baden-Württemberg, in UTM zone 32. The orthophoto comes from the map service of the LGL, with the flight date of the tile at the centre of the area. freemapper reads the terrain model (DGM1) and the surface model tile by tile out of the 2 km archives of the LGL, about 3.5 MB per tile. The surface is the nDOM1 from the aerial images of a summer flight: it shows the trees in leaf and usually comes from the flight of the orthophoto or the one before it. Buildings and land use come from the ALKIS service of the LGL. It holds whole buildings only, so no canopies, and street areas include the green beside them. OSM comes from the extracts of the four Regierungsbezirke (130 to 215 MB). Credit: Datenquelle: LGL, www.lgl-bw.de, dl-de/by-2-0 (Daten geändert, <year>). Example: Heidelberg old town and castle.
  • Bremen (ADR 0121): maps in Bremen and Bremerhaven, in UTM zone 32. The orthophoto comes from the map service of the Landesamt GeoInformation Bremen, which has one layer per flight and city; freemapper takes the newest colour flight of each city (2025) and gives the flight year as the date. It reads the terrain model (DGM1) and the surface model (DOM1) tile by tile out of the archive of the city, about 3.5 MB per tile. Both come from the laser scans of 2017 (Bremen) and 2015 (Bremerhaven); freemapper warns at the fetch that newer buildings and trees may be missing from the nDSM. Bremen has no simplified ALKIS. Buildings, building parts, canopies and land use therefore come from the full ALKIS, which the LGLN runs for Bremen, with the same names as in the other states. The same service gives the surveyed lines as in Brandenburg: stairs, ramps, retaining walls, monuments, embankment tops and bridges. An area in Lower Saxony that reaches into Bremen now gets buildings and land use from Bremen's cadastre there, in place of the warning that it lies outside the supported states; that warning now names Bavaria and Thuringia as examples. The area page shows the aerial photo of the city of Bremen only, not of Bremerhaven. Credit: © GeoBasis-DE / Landesamt GeoInformation Bremen (<year>), CC BY 4.0, Daten geändert. Example: old town of Bremen and Wallanlagen.
  • Permit notes in Berlin (ADR 0120): when the map area lies in Berlin, permits.md and permits.json also name the Bezirke with their share, the green spaces with their Bezirk and dedication, the number of public playgrounds, the share of the area owned by the state of Berlin and by the Bund (one line per owner; any other owner is not named and shares the line "Other public owners"), the monuments per kind with up to 20 links into the Denkmaldatenbank, and natural monuments, protected landscape features and areas with special rules. The hints then name, for each Bezirk that is more than an edge of the area, the Ordnungsamt, the Straßen- und Grünflächenamt, the lower monument authority and the lower nature conservation authority of the Bezirksamt. The data come from five services of the Geoportal Berlin (dl-de/zero-2-0, the licence text verbatim in the table of sources). freemapper asks them only when permit notes are wanted and the area lies in Berlin, and only through the hosts of Berlin's adapter. A service that is down takes only its own section with it. A region adapter can now bring such sources (RegionAdapter::permit_sources). permits.json stays at schema 1; older files and data/permits/sources.json still read. Described in the user manual, chapter 12.

Changed

  • Smaller PDFs: --pdf and --pdf-candidates write their paths with the compact path writer of freemapper-core 0.26.0 (freemapper-core decision 0033). Path coordinates are rounded to 1/1000 point. Small shapes of four points or more within 7 mm, such as the dots of point symbols, are written relative to their first point, so repeated symbols compress well. The 26 PDFs of the 12 example maps with data (Dammheide left out) shrink by 22 to 79 %, from 16.9 MB to 8.3 MB together; Sanssouci's map goes from 1.45 MB to 304 KB. The maps look the same: rasterised at 150 dpi with poppler, 6 of 113 million pixels differ by more than 12 %. Texts, fonts, colours, page size and the clip to the map area stay as they were. A shape with a coordinate that is not a finite number is left out instead of breaking the page. All libraries of freemapper-core move to v0.26.0; 0.26.0 changes nothing else for freemapper.
  • School and forest maps: the minimum sizes of the norm now grow with the symbols (ADR 0118). On a school map (symbols at 125 %) the smallest building or canopy is 0.625 mm instead of 0.5 mm, on a forest map at 1:10 000 (150 %) 0.75 mm; likewise the shortest line by ISSprOM 4.5, the smallest areas of out-of-bounds land, paving, green, open land and water, the shortest contour and the smallest contour ring, landforms and the smallest vegetation area. Such maps show a little less small detail. Sprint maps (100 %) stay the same. The contours, landforms and vegetation of an existing project change only when derive runs again. The Dammheide example is rebuilt with it. Most of what went are small buildings and canopies in the settlements and short index contours: 560 buildings instead of 757, 7 canopies instead of 24.
  • Internal: lengths on paper now have a type (ADR 0118). A paper measure (PaperMm) holds on the printed sheet, a symbol measure (SymbolMm) grows with the symbol enlargement of the map kind and cannot be converted without it. The roughly 45 hand-written conversions to ground metres and map coordinates are replaced; the norm's line gap, line widths and point sizes are written down once in build/symbol_measures.rs. No measure changes, the maps stay the same.
  • Internal: the rule for overlapping walls, fences and hedges now converts its distances like every other rule (addendum to ADR 0118). On a forest map at 1:10 000 two limits move by the last digit of the floating-point number; all other maps compute as before. The shortest stubs of a cut line stay 1 mm on the sheet and do not grow with the symbols; that is now decided. Four tests of the order of the map assembly run without a project folder (build/assembly.rs).

Fixed

  • Baden-Württemberg: when the server answers 404 for the 2 km archive of a block that holds a tile inside the state, the fetch of the terrain now stops with an error that names the archive's address (for the surface model a warning names it), instead of leaving a 1 km hole in the templates with only a warning about a missing tile.
  • Small compact areas are no longer dropped as "too narrow" (ADR 0122). Out-of-bounds land, paving, green, open land and water leave out slivers: pieces below (1 mm)² or narrower than 1 mm. The width used to be 2 · area / perimeter, which is only half the side of a square: a square piece needed a side of 2 mm to count as 1 mm wide. Now the short side of the rectangle with the same area and perimeter counts. On forest maps 1 mm of the norm is 15 m on the ground; there, plots up to 30 × 30 m fell out of the out-of-bounds areas and left white holes in the settlements. The Dammheide example now keeps 144 of 146 out-of-bounds areas (113 without the fix) and 9 of 10 open-land areas (2 without). Sprint maps gain a few small pieces, mostly out-of-bounds candidates of 40 to 100 m²; no area that was drawn before is dropped. Strips are as wide as before, and the rule for narrow ALKIS water (a candidate below 2 m mean width) stays.
  • Forest maps: the north lines are now 20 mm (1:15 000) or 30 mm (1:10 000) apart, 300 m on the ground, as ISOM 2017-2 requires; before they were 450 m apart, as in ISOM 2000. The Dammheide example is rebuilt with it.
  • The OCAD hint after --ocad: on a forest map freemapper told you to load the ISSprOM 2019 or school symbol set in OCAD. The hint now names the set of the map kind: ISOM 2017-2 for forest maps, ISSprOM 2019 for sprint maps, the IOF school set 2019 for schoolyard maps. The same goes for the summary through MCP and on the area page. The README now names ISOM 2017-2 as well.

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.18.0-windows-x86_64.zip
  • macOS Apple Silicon (M1 and newer): freemapper-v0.18.0-macos-arm64.tar.gz
  • macOS Intel: freemapper-v0.18.0-macos-x86_64.tar.gz
  • Linux: freemapper-v0.18.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

  • Paper and symbol measures are types (ADR 0118) by @HenryJobst in #81
  • Permit notes in Berlin: Bezirk, green spaces, public land, monuments and Naturdenkmale by @HenryJobst in #83
  • School and forest maps: the norm's minimum sizes grow with the symbols (ADR 0118) by @HenryJobst in #84
  • Baden-Württemberg: the thirteenth state (ADR 0119) by @HenryJobst in #82
  • Smaller PDFs: paths through core's compact path writer (core v0.26.0) by @HenryJobst in #85
  • Dammheide example rebuilt with the minimum sizes of ADR 0118 by @HenryJobst in #86
  • Bremen: the fourteenth state (ADR 0121) by @HenryJobst in #87
  • OCAD hint names the symbol set of the map kind by @HenryJobst in #88
  • Forest maps: north lines 300 m apart, as ISOM 2017-2 says by @HenryJobst in #89
  • Small compact areas are no longer dropped as slivers; Dammheide rebuilt (ADR 0122) by @HenryJobst in #90
  • Baden-Württemberg: a missing archive inside the state is an error; Bremen: templates beyond the border by @HenryJobst in #91
  • Small cleanups: barrier limits convert like the rest, four order tests in the assembly, line stubs decided by @HenryJobst in #92

Full Changelog: v0.17.0...v0.18.0