Repository navigation
freemapper v0.19.0
Added
- Bavaria (ADR 0123): maps in all of Bavaria, in UTM zone 32, also east of 12° E. The orthophoto comes from the map service of the Bayerische Vermessungsverwaltung, with the date of the flight. freemapper reads the terrain model (DGM1) tile by tile, about 2.8 MB each. Bavaria has no surface model at 1 m; freemapper takes the DOM20 of 20 cm (about 45 MB per km²), reduces it to 1 m and keeps only the reduced tiles. Bavaria has no service for its cadastre. So buildings and canopies come from the LoD2 tiles, one file per 2 km square (about 3 MB in the country, 60 to 160 MB in a city centre), and the land use from the file of each Kreis at the area (2 to 13 MB). Bridges and walls in LoD2 do not go onto the map. The estimate before the run lists all five downloads. freemapper downloads a cached file again only when the server has a newer one; offline (
--offline) the same map is made. Stairs, walls and embankments from the cadastre and vegetation from point clouds are not there for Bavaria yet. Examples: the old town of Regensburg (sprint map) and the Schmausenbuck in the Nürnberger Reichswald (forest map). Thuringia is now the only state without data sources; the warning for areas beyond the coverage names Thuringia alone. - Examples: a forest map (1:10 000) for every state; besides the Dammheide in Berlin, 13 new ones in
examples/, from the Elbe sandstone at the Bastei to the Bürgerpark in Bremen. They were chosen by relief and path network out of some 30 trial runs. In Brandenburg, North Rhine-Westphalia and Saarland they hold the vegetation from laser point clouds as candidates; in Rhineland-Palatinate the state office's Metalink file does not match the files for the tiles near Dahn, so freemapper leaves them out. The table is in the examples overview.
Changed
- Examples: the 14 sprint maps in
examples/are rebuilt, all but Regensburg, which already comes from the current code. They now show what version 0.18.0 draws. Small compact areas are no longer dropped (ADR 0122), so the old towns have more out-of-bounds areas (520) among the candidates and more paved areas (501.5) on the map: Lübeck has 1834 candidates instead of 1365, Wismar 1660 instead of 1416. With the compact path writer the 14 training maps take 5.6 MB together instead of 10.1 MB. The tables and numbers inexamples/README.en.mdand the comparison of the three content profiles for Cochem are counted again.
Fixed
- Saarland: in forest areas the ALKIS land use was missing with the warning "LVGL ALKIS returned 22 of 26 features in the area", also after a new
fetch. The service lists a forest once per vegetation feature (such as deciduous wood and short-rotation coppice), with the same object id and the same geometry. freemapper keeps one row of them and now counts the others towards the service's matches. A feature repeated on a later page is still an error. At the Saarschleife near Mettlach this brings 684 land use areas and 132 more out-of-bounds candidates.
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.19.0-windows-x86_64.zip
- macOS Apple Silicon (M1 and newer): freemapper-v0.19.0-macos-arm64.tar.gz
- macOS Intel: freemapper-v0.19.0-macos-x86_64.tar.gz
- Linux: freemapper-v0.19.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
- Saarland: forest land use no longer lost to rows of one object by @HenryJobst in #93
- Bavaria: the fifteenth state, its cadastre read from files (ADR 0123) by @HenryJobst in #94
- A forest map example for every state by @HenryJobst in #95
- Sprint examples rebuilt with the current code by @HenryJobst in #97
Full Changelog: v0.18.0...v0.19.0