freemapper15. Messages and what to do
freemapper has German and English texts. The language comes from --lang de or --lang en, else from the environment variable FREEMAPPER_LANG, else from the system language (LANG), else it is English. On Windows LANG is usually not set; use --lang de there if you want German.
German covers the lines the program prints at the end of a step, such as "Wrote …" and the hints after run and export, and the error messages. An error message starts with error: (German Fehler:), and the program then ends with exit code 1. The MCP server and the area page report errors in the program's language too. What a server, the operating system or a parser says inside an error stays as it is.
Progress lines and warnings come in the program's language too; a warning starts with warning: (German Warnung:). The help (--help, freemapper help <command>) and the messages about wrong calls are translated too; only the placeholders of the usage line such as [OPTIONS] and <DIR> stay. The MCP server describes its tools to the assistant in the program's language and answers in it; --lang en after mcp keeps it English. The area page takes the program's language when --lang, FREEMAPPER_LANG or the system names one; otherwise it follows the browser's language. The most important messages, in their English wording:
| Message (start) | Meaning | What to do |
|---|---|---|
the map area lies outside the supported states | The area is not in Brandenburg, Berlin, Saxony, Saxony-Anhalt, Hamburg, Hesse, Schleswig-Holstein, Mecklenburg-Vorpommern, North Rhine-Westphalia, Lower Saxony, Rhineland-Palatinate, Saarland, Baden-Württemberg or Bremen. | Choose another area; more states will follow. |
another freemapper run is using this folder (since … | A second freemapper (a terminal, an AI assistant or the area page) works in this project folder. The file .freemapper-run.lock in the folder shows it. | Wait until the other run is done, or stop it. A run that was killed leaves the file behind; after a minute without a sign of life it is replaced automatically. |
map area plus buffer is … more than 4000 m per side | The area is too large. | Draw it smaller or split it into several maps. |
no area found for … | The place was not found, or its grounds are several parts in OSM. | Spell it differently, draw the area in the browser, or pick a part with --osm <id> --part <n>. |
… is an area of … separate parts (…) | The OSM object is several separate areas. The brackets give their sizes, largest first. | Pick one with --part <n> (1 is the largest), or with part over MCP. Or save the outline as GeoJSON and use --geojson. |
… has … parts; there is no part … | The number given to --part is larger than the number of parts. | Pick a smaller number. |
… not found. Nominatim lists only tagged OSM objects … | Nominatim does not know the OSM object. Often it is an outer way of a multipolygon relation without tags of its own. | Use the relation (--osm relation/…), or save the outline as GeoJSON and use --geojson. |
--part picks a part of an OSM area and needs --osm | --part only works with --osm. | Look up the OSM id and give --osm <id> --part <n>. |
MultiPolygon with … parts | The chosen grounds consist of several parts. | Draw one connected area in the browser. |
warning: no ALKIS buildings found in the map area | There are no buildings in the area, e.g. in a forest. | Nothing, if that is right. Otherwise fetch again later. |
warning: the map is written, but its preview is missing: … | The map was written, but <name>-preview.webp could not be written, for example because the disk is full or a folder of that name is in the way. The OCAD files and PDFs are still written. | Make room or remove what is in the way, then run again with "Replace the existing map" (--force). |
the map area reaches beyond the state border | Part of the area lies in the neighbouring state. The orthophoto and height models come from the state holding the centre, ALKIS and OSM from both states. | The templates stay empty where that state's orthophoto and height models end. Draw that part by hand. |
warning: part of the map area lies outside the supported states | Part of the area lies outside every supported state: abroad, at sea or in a German state freemapper does not support yet. That is only Thuringia now. The sea includes the Baltic off Schleswig-Holstein and Mecklenburg-Vorpommern and the Schleswig-Holstein Wadden Sea, for example between Föhr and Dagebüll. The boundaries of these two states leave that water out. There are no state data there, the orthophoto can be white, and ALKIS gives no buildings or land use. freemapper reports this when it fetches, not in the size estimate. A strip of up to 50 m beyond the border does not trigger the warning. | Draw that part by hand or move the area. |
warning: no building file for tile 726_5434 on the server; the map may lack buildings there | Bavaria: the server has no building file for a 2 km square inside the state. For squares without buildings it keeps an empty file; when the file is missing altogether, it was probably moved. The map is made without the buildings of that square. freemapper asks for the file again at every fetch with a network connection. | Fetch again later. If the warning stays, please report it as an issue. |
warning: could not check whether <address> is still current (…); using the cached file, and the other cached files of this server without asking | Bavaria: the server did not answer when freemapper asked whether a cached file is still the current one. The map is made with the files in the cache. The warning comes at most once per kind of data. | Nothing. Fetch again later for the newest state. |
download of … failed or invalid ALKIS data | A server was unreachable or sent nonsense. | Try again later. Data fetched before is kept. |
| Area selection: "access blocked" / 403 from OpenStreetMap, or the base map stays grey | The base map comes from tile.openstreetmap.org. Its tile policy asks for an identifiable application (User-Agent) or a valid Referer; the browser sends no Referer here. Up to 0.9.1 the browser loaded the tiles itself and got 403. Since 0.9.2 the local server fetches the tiles with User-Agent: freemapper/<version> (+https://github.com/HenryJobst/freemapper) and passes them to the browser. | Update freemapper. The computer needs internet access. If the server answers 502, the reason is in the response (for example HTTP 403 or no connection). The state aerial images are not affected. |
… refused the request (HTTP 400) | A service refuses the request. | Try again. If it persists, report a bug. |
…: freemapper does not send requests to this address: the adapter of … does not name the host … | For a state freemapper asks only the servers its adapter names. A service moved to another server, redirected there or pointed there in its answer. The message starts with the refused address and ends with the command that allows the host. | If you trust the server (it plainly belongs to the agency of the state): run the command from the message, freemapper adapters allow-host <adapter> <host>, repeat the run and report the move (chapter 17). See "When a service moves" in chapter 13. For an adapter of your own, add the host to [net] hosts of its manifest. |
…: freemapper does not send requests to this address: … with another reason | freemapper never connects to an address of this computer or of the local network, follows at most three redirects in a row and no redirect to http. | Nothing to allow. For a built-in state, report a bug. |
… ignored the byte range | The server (height models of Hamburg or Hesse) sends the whole archive instead of the tile; freemapper stops rather than download over 1 GB. | Try again later, otherwise report a bug. |
download of … is larger than … MB; stopped | A server (the OSM extract, the Downloadportal of Schleswig-Holstein, the full ALKIS or the Potsdam tree cadastre) sends far more than the file can be; freemapper stops and removes the partial download. For the trees it stands in the brackets of warning: potsdam tree cadastre unavailable. | Try again later, otherwise report a bug. |
… not found on the server with the address of an archive Gitternetz_…_ASCII_XYZ.zip or …_2_bw.zip | Bremen: the archive of a height model is no longer at its address. Its name carries the year of the laser scan; the agency has probably published a newer scan. Baden-Württemberg: the 2 km archive of a block with a tile inside the state is not at its address; the LGL has probably renamed it or is replacing it. | Report a bug (chapter 17). With --offline freemapper goes on with the tiles it has fetched already. |
no tile of the … covers the map area | Hamburg: the statewide archive has no tile for the area; it was probably renamed. Saarland: none of the district archives has a tile for the area; the LVGL probably replaced them with a newer survey. Baden-Württemberg: none of the 2 km archives has a tile for the area; the LGL probably renamed the tiles in them. Bremen: the archive of the city has no tile for the area. Hesse: the Downloadcenter may have changed. Schleswig-Holstein and Mecklenburg-Vorpommern: the Downloadportal may have changed. North Rhine-Westphalia: the tile list of Geobasis NRW names no tile for the area. Rhineland-Palatinate: after the colon follows the reason for each tile, for example not on the server (404), not in LVermGeo RP's tile list or no flight year in LVermGeo RP's tile list (Laserbefliegung). | Report a bug. |
warning: … an archive could not be read (…); it was passed over … / …; its directory kept from an earlier run is used … | Saarland: one of the six district archives of the height model could not be read; the address in brackets names it. In the first case the tiles of your area were in other archives, and the map is complete. In the second case freemapper used the list of tiles it kept from an earlier run of yours; the tiles in the cache fit that list, but a tile the LVGL replaced since would not be noticed. | Nothing, if it happens once. If it stays, the LVGL renamed the archive: report it (chapter 17). |
warning: the … has no tile(s) … inside Hamburg | Single tiles are missing from the archive. | The templates stay empty there. |
warning: the … has no tile(s) … inside Hesse | Single tiles are missing from the municipality's Downloadcenter archive. | The templates stay empty there. |
warning: the Downloadcenter has no file for "…" | The Downloadcenter has no file for the place (e.g. an unincorporated area). The tiles it names after ; (if any) stayed empty because no other municipality's file holds them. | Tiles taken from neighbouring municipalities need no action; the named tiles stay empty. |
warning: the metadata list has no readable Bildflugdatum for tile … | The HVBG metadata list has no flight date for these tiles. | Only the date in the project record is missing. |
warning: the new HVBG metadata list … could not be read … | The newly published list could not be read; the older kept list is used. | Update freemapper if it persists. |
warning: the … has no tile(s) … inside Schleswig-Holstein | Single tiles are missing from the Downloadportal. | The templates stay empty there. |
the Downloadportal lists at most … tiles per request | (Schleswig-Holstein, Mecklenburg-Vorpommern) The area needs more tiles than the Downloadportal lists per request. | Choose a smaller area. |
the Downloadportal answered with an error page | The Downloadportal (Schleswig-Holstein) sends an error page instead of the tile. | Try again later; freemapper retries the tile once itself. |
warning: DGM1 tile … is not in the INSPIRE ATOM directory / … does not read (…); used its XYZ from the Downloadportal | The GeoTIFF of the terrain tile is missing in the INSPIRE ATOM directory or does not read (error page, another grid, server error); freemapper took the same tile as XYZ from the Downloadportal. If that fails too, the error names both reasons. | Nothing; the heights are the same. |
the Downloadportal's tile list … could not be read | (Schleswig-Holstein, Mecklenburg-Vorpommern) The tile list could not be read; the one from an earlier run is used. | Nothing, as long as the data is the same. |
warning: the surface model (bDOM …) is older than the orthophoto (…) | The bDOM is at least a year older than the orthophoto (in Schleswig-Holstein from the 2025 half on). | Check new buildings in the nDSM by hand if needed. |
warning: surface model (LVermGeo SH bDOM) unavailable | The bDOM could not be fetched; an error there is only a warning. With …; kept the surface model fetched on … the surface model of an earlier fetch of the same area is kept and the nDSM still comes from it (also for the HVBG DOM1). | With no nDSM template the nDSM template is missing; try again later. |
downloading bDOM tile … (105 MB, … of …) | Progress message: freemapper downloads a whole tile, which takes about 90 s. | Wait. |
geodaten.schleswig-holstein.de answered with a redirect (HTTP …) to … | The Downloadportal forwards to another address. freemapper does not follow it, because it checks this server against its own certificates only. | Report a bug. |
… certificate … (server geodaten.schleswig-holstein.de) | The certificate check for the Downloadportal failed, for example because its certificate authority changed. | Update freemapper, otherwise report a bug. |
warning: the … has no tile(s) … inside Mecklenburg-Vorpommern | Single tiles are missing from the state survey's Downloadportal (only inside the state). | The templates stay empty there. |
… cells inside the Mecklenburg-Vorpommern tiles have no height | Single cells inside the state tiles have no value in the height model. | The templates stay empty there. |
… no date for the centre tile … | The Downloadportal names no date for the tile at the centre of the map area (border map, centre beyond the state tiles). | Only the date in the project record is missing. |
no TIFF in the WCS answer: … | The WCS service of the Mecklenburg-Vorpommern or Lower Saxony height models sent an error message instead of the image; its text follows. In Lower Saxony this can be an HTML page "MapServer Message". freemapper tries three times before it gives up. | Try again later, report a bug if it persists. |
the WCS answered with an error: … / not a JPEG (…): … | The WCS service of the Mecklenburg-Vorpommern orthophoto sent an error message or something other than a JPEG instead of the image; the cleaned start of the answer follows. | Try again later, report a bug if it persists. |
…; the stored model keeps its recorded date | Offline: the tile list could not be read; the stored height model is used and keeps the date of its record. | Fetch once online. |
no … stored for this map area | Offline (Mecklenburg-Vorpommern, Lower Saxony): no stored height model covers the whole area. The message names the file freemapper looked for. | Fetch once online. |
warning: … unavailable (…); no nDSM template (LAiV M-V, LGLN and LVermGeo RP DOM1) | The DOM1 could not be fetched; an error there is only a warning. | The nDSM template is missing; try again later. |
warning: the … has no tile(s) … inside North Rhine-Westphalia | Single tiles of the area are missing (only inside the state): either the Geobasis NRW tile list does not name them, or it names them and the server has no file (HTTP 404). A 404 is noted, so later runs do not ask again until the list has a new release. | The templates stay empty there. |
… tile …: … cells of the map area have no height | Single cells of a Geobasis NRW or LVermGeo RP tile have no height value. | The templates stay empty there. |
the tile list gives no date for the … / the … tile … has no date: LVermGeo RP's tile list (Laserbefliegung) … / the tile list names no … tile … at the centre of the map area, so there is no date / the … tile … at the centre of the map area is missing, so there is no date | The Geobasis NRW tile list or the LVermGeo RP flight index has no date, or no tile, for the tile at the centre of the map area, or that tile is missing. | Only the date in the project entry is missing. |
… rows of the … tile list have no usable tile name; skipped / … have no readable date | Single rows of the Geobasis NRW tile list could not be read. | Nothing; the other rows apply. |
the tile list of the … could not be read (…); used the one kept from an earlier run | The Geobasis NRW tile list could not be read; the one from an earlier run is used. | Nothing, as long as the data is the same. |
the server's tile list of the … dates from …, older than the kept one | The server returns an older tile list than the stored one (a mirror behind the origin); freemapper keeps the newer. | Nothing. |
warning: no North Rhine-Westphalia district extract within 100 m of the area; reading the nearest, … | The area lies more than 100 m from all five Regierungsbezirke, for example just beyond the state border. freemapper reads the nearest extract. | Nothing; features beyond it do not come from OSM. |
download of … is not a complete OSM extract: … | An OSM extract (for example a Regierungsbezirk one) is incomplete or damaged. freemapper discards it. | Try again; the extract is fetched anew. |
the orthophoto was flown on …, with the trees bare / …, with the trees in leaf; their crowns hide what lies below them | Lower Saxony: a progress message with the flight date of the orthophoto. From May to October the trees count as in leaf, otherwise as bare. | With a leaf-on orthophoto, check paths, fences and small features under the crowns in the terrain. |
warning: the surface model (LGLN DOM1) is from …, the orthophoto from … | The DOM1 is more than 24 months older than the orthophoto, in Lower Saxony usually 5 to 9 years. New buildings and young trees can be missing from the nDSM, and demolished buildings can still be in it. | Compare the nDSM with the orthophoto and check differences in the terrain. |
warning: orthophoto (LGLN WMS): no flight date, … / warning: orthophoto (LGLN WMS): the STAC …; kept the stored orthophoto and its flight date … | The LGLN STAC search lists no orthophoto at the centre of the map area (the STAC lists no image …), or it failed (the STAC search failed (…), with the reason in brackets). A stored orthophoto is kept with its flight date; otherwise freemapper fetches the orthophoto without a date. Without a flight date there is no comparison with the DOM1. | Fetch again later. If it persists, report a bug. |
warning: terrain model (LGLN DGM1): no date … / warning: surface model (LGLN DOM1): no date … | The STAC search lists no height model at the centre of the map area, or it failed (the reason follows in brackets, for example not a STAC search answer: …). The model itself was fetched. | Nothing; only the date in the project entry is missing. Without a DOM1 date there is no comparison with the orthophoto. |
the terrain model (LGLN DGM1) has no height in the map area / the surface model (LGLN DOM1) has no height … | The LGLN WCS service returned only cells without a height for the whole area. freemapper writes no file. For the DGM1 the fetch stops; for the DOM1 the nDSM template is missing. | Try again later. If the area lies in Lower Saxony and it persists, report a bug. |
warning: the … has no tile(s) … inside the map area | Single tiles of the area are missing. Either the Laserbefliegung flight index does not name them (reported only for tiles whose centre lies in the state), or it gives no flight year and the Metalink file names no file, or the server answers 404. freemapper notes a 404 and asks again only after 30 days. | The templates stay empty there. |
warning: … tile …: this 1 km square has no heights in the map | Rhineland-Palatinate: the flight index gives this tile no flight year, or no flight days that read and agree, so the file name is not known. If the message ends with and its Metalink names no file for it either, the Metalink file does not know the tile either. | The templates stay empty there. If it persists, report a bug. |
the LVermGeo RP tile list could not be read (…); used the one kept from an earlier run | The flight index could not be fetched; freemapper uses the one from an earlier run for the same area. | Nothing, as long as the data is the same. |
… features of the tile list have no usable tile key; skipped | Single entries of the flight index could not be read. | Nothing; the other entries apply. |
the LVermGeo RP Metalink of the … could not be read (…); used the one kept from an earlier run / …, so the tiles its tile list gives no flight year for stay without heights | The Metalink file could not be fetched. With the first message freemapper uses the kept one; with the second the tiles without a flight year stay empty. | Fetch again later. |
… not a tile list (Laserbefliegung): … / … not a GeoTIFF: … / … not a Metalink: … / the tile list holds … of the … tiles it matched | An LVermGeo RP server sent something other than the flight index, the tile or the Metalink file, usually an HTML error page; the cleaned start of the answer follows. The last message means the index arrived incomplete. | Try again later, report a bug if it persists. |
orthophoto unchanged (date of creation …) | Rhineland-Palatinate: freemapper keeps the stored orthophoto, because the map service gives the same date of creation (or none just now, and the image is less than 30 days old). That date counts as the flight date. | Nothing. |
downloading Berlin ALKIS structures, tree cadastre, street survey and point layers | Progress message: freemapper fetches the Berlin layers, about 12 MB per km² in the city centre (9.8 MB at Viktoriapark). | Wait. |
warning: Berlin … unavailable (…); keeping the stored layer / …; layer skipped | A Geoportal Berlin layer (e.g. bauwerke-linien or sb-moebel) could not be fetched. A layer that holds several object types, as sb-moebel holds the benches, bollards and hydrants, is missing as a whole when one of them fails. With keeping the stored layer the stored layer, which still covers the area, stays. With layer skipped its candidates are missing. The fetch goes on. | Fetch again later. |
no Berlin ALKIS structures stored; run `freemapper fetch` online … | Offline: no structures, trees or canopies are stored for the Berlin area. | Fetch once online. |
removing the stored Berlin layers: the map area is no longer near Berlin | The area is no longer near Berlin. freemapper deletes the stored Berlin layers. | Nothing. |
warning: freemapper.toml: ignored the Berlin layer entry / … the NAS layer entry / … the tree layer entry | The project file records a Berlin layer, a full ALKIS layer or a tree cadastre under a name freemapper does not know, or under a name that would point to another folder (../, /, \, a drive letter, control characters). The file was edited by hand or comes from someone else. freemapper ignores the entry, deletes no file for it and leaves it out when it saves the project file. | Nothing. If you did not edit the file yourself, check where the project came from. |
warning: Berlin … unavailable (data/berlin leads out of the project folder) | The folder data/berlin in the project is a link to a place outside the project folder. freemapper writes and deletes no Berlin layer there, so the Berlin candidates are missing. | Replace the link with a normal folder and fetch again. |
…: a link leads out of the project folder, so freemapper writes nothing there | The named folder (data, templates or ocad) or the folder of the named file is a link to a place outside the project folder. This happens with project folders from someone else. freemapper stops before it writes anything there. If only a single file in the project is a link, freemapper replaces it with a normal file and goes on. | Replace the link with a normal folder and run the command again. |
…: a link or outside the project folder, so freemapper does not copy it | A file freemapper would copy is a link or lies outside the project folder. As a warning (…; the OCAD map gets no background from it), it concerns a template image or its world file: the OCAD map lacks that background, the rest is written. As an error, it concerns the map file before its backup .omap.bak or .ocd.bak. | Replace the link with the real file and run the command again. |
downloading the full ALKIS structures (NAS) | Progress message: in Brandenburg and Bremen freemapper fetches the full ALKIS, about 1 MB per km². Then each layer gives its count, e.g. 780 ALKIS NAS sonstiges-bauwerk features at Park Sanssouci. | Wait. |
warning: ALKIS NAS … unavailable (…); keeping the stored layer / …; layer skipped | A full ALKIS layer (e.g. sonstiges-bauwerk) could not be fetched. The brackets give the reason, e.g. LGB ALKIS (NAS) answered adv:AX_… with an exception report: …. With keeping the stored layer the stored layer, which still covers the area, stays. With layer skipped its candidates are missing. The fetch goes on. | Fetch again later. |
… returned … of … features; choose a smaller area | Stands in the brackets of the warning above. The area holds more objects than the service sends in one answer, even after freemapper split it into quarters four levels deep. | Draw the area smaller or split it into several maps. |
skipped … ALKIS NAS … features: … | Single objects of a full ALKIS layer have a geometry freemapper cannot read, e.g. unsupported GML element Clothoid or no geometry. freemapper names them and leaves them out. | Nothing. If many are missing, report a bug. |
no full ALKIS structures stored; run `freemapper fetch` online … | Offline: no full ALKIS layers are stored for the area in Brandenburg or Bremen. | Fetch once online. |
removing the stored full ALKIS layers: the map area is no longer in a state with a NAS service | The area no longer lies in Brandenburg or Bremen. freemapper deletes the stored full ALKIS layers. | Nothing. |
warning: full ALKIS layers skipped (data/alkis-nas leads out of the project folder) | The folder data/alkis-nas in the project is a link to a place outside the project folder. freemapper writes and deletes no layer there, so the full ALKIS candidates are missing. The same reason can stand in the brackets of warning: ALKIS NAS … unavailable. | Replace the link with a normal folder and fetch again. |
downloading the objects of the ATKIS Basis-DLM | Progress message: in Bavaria freemapper fetches objects of the landscape model. After it a line per layer, … ATKIS Basis-DLM dlm-… features, gives their number. The messages of the rows above come here with "ATKIS Basis-DLM" in place of "ALKIS NAS"; they mean the same. | |
downloading the city tree cadastres | Progress message: freemapper fetches the Potsdam trees. Then … potsdam trees gives their number, e.g. 1964 potsdam trees at Park Sanssouci. | Wait. |
warning: potsdam tree cadastre unavailable (…); keeping the stored one / …; trees skipped | The Potsdam trees could not be fetched. One of the three datasets failing is enough. With keeping the stored one the stored trees, which still cover the area, stay. With trees skipped the tree candidates are missing. With data/trees leads out of the project folder in the brackets, that folder is a link to a place outside the project. | Fetch again later. Replace a linked folder with a normal one first. |
skipped … potsdam trees: … | Single trees could not be read, e.g. no point. freemapper names them and leaves them out. | Nothing. |
no city tree cadastre stored; run `freemapper fetch` online … | Offline: no Potsdam trees are stored for the area. | Fetch once online. |
removing the stored tree cadastres: the map area is no longer in a city with one | The area no longer lies in Potsdam. freemapper deletes the stored trees. | Nothing. |
warning: the K5 map template is unavailable (…); skipped | The K5 could not be fetched. The template is missing, the fetch goes on. | Fetch again later. |
k5 is not made yet; run freemapper fetch or run … | The assistant or the preview asks for the K5 template, but there is none: the area is not in Berlin, it was not fetched yet, or the fetch failed. | In Berlin, run fetch or run. |
warning: the map area now lies in another state's data | The area now lies with another provider. | Nothing; freemapper fetches everything again. |
offline and not cached / no OSM extract cached | Data is missing for --offline. | Fetch once with internet. |
no tiles fetched yet / the map area needs tiles … that were not fetched | Nothing was fetched yet, or the area changed. | Run run or fetch. |
map already exists (it may contain your work) | A map exists already. | Use --force only if it should be replaced. |
The map lacks the ALKIS canopies and carports (522) that are now map objects | The map dates from before the ALKIS canopies. freemapper kept the map, and the canopies are not in it. | Write it again with run --force. The old map stays as .omap.bak. Or copy the canopies over by hand. |
warning: … changed upstream | The provider published new data. | Nothing; the templates are current now. |
warning: freemapper skips the … for lack of disk space | The disk has no room for this part (the surface model, the update of the OSM extract, the Berlin layers with structures, trees, street survey and registers, the Berlin K5, the full ALKIS structures and the tree cadastres in Brandenburg, or the objects of the landscape model in Bavaria) once 1 GB stays free. freemapper leaves it out. A stored surface model of the same area stays, and so do the older OSM extract and the stored Berlin, full ALKIS and tree layers. The message says how much the part needs and how much is free. | Free some space and run freemapper fetch again. |
freemapper keeps the surface model fetched on … for the nDSM template / freemapper keeps the cached surface model of tile(s) … for the nDSM template | Follows the message above: the surface model of an earlier fetch (or the named tiles in the cache) still covers the area, and the nDSM template keeps coming from it. | Nothing. |
not enough disk space for the … | There is no room for the map data, the terrain model or the orthophoto. Without them there is no map, so freemapper stops before it downloads anything. | Free some space, or put the cache on another drive with --cache-dir, then start again. |
the disk is full, so freemapper could not write … | The disk filled up while freemapper wrote a file, for example because another program used space at the same time. freemapper deletes the half-written file, so nothing broken stays in the cache. | Free some space and try again. |
warning: the disk is full, so freemapper uses the cached OSM extract from … | The new OSM extract no longer fitted on the disk. freemapper uses the older one. | Free some space and fetch again later. |
warning: cannot read the free disk space of … | The system does not report the free space, as with some network drives. freemapper downloads without the check. | Nothing. If the disk fills up, freemapper reports the disk is full. |
freemapper … is available (you have …). Update with: freemapper update | The daily check found a newer release (chapter 3, "Updating"). The line comes after the command's output, also after an error. | Run freemapper update when it suits you, or switch the check off with freemapper update --mode off. |
This freemapper was built from source. | freemapper update in a build you made yourself with cargo. | Update with git pull and cargo build --release --locked. |
the input is not a terminal, so freemapper cannot ask before installing | freemapper update ran in a script or another place where it cannot ask. | Run freemapper update --yes. |
cannot write to the program folder … | freemapper may not write to its own folder and does not ask for administrator rights. | Unpack the new release there by hand, or move freemapper to a folder you can write to. |
the release could not be verified (…); nothing was installed | The signature of the release does not match the key built into freemapper. The old program stays. | Try again later. If it persists, report a bug and download the archive by hand. |
warning: the newest freemapper release could not be verified (…); nothing was installed | The daily check after a command found a release whose signature does not match. The line comes after the command's output and at most once a day; the exit code stays the same. | Nothing to do now. Install nothing by other means; if it persists, report a bug. |
the newest release cannot install itself (it has no update manifest); download it from … | The newest release has no freemapper-update.json, so freemapper update cannot install it. The daily check says nothing in this case. | Download the archive from the linked release page and unpack it as in chapter 3. |
release … does not exist or cannot install itself (it has no update manifest) | freemapper update --version names a release that does not exist or has no freemapper-update.json. | Check the version on the linked page of all releases. |
freemapper … cannot be installed by the self-update of … | The new release needs a newer starting version than yours. update --check exits with 10 here too. | Install the version named in the message by hand from the linked release page, as in chapter 3. |
the release has no program for this system (…) | The release has no program file for your system. | Report a bug. |
another update or rollback is running in the program folder | A second freemapper update works in the same folder. | Wait for it to finish and try again. |
there is no previous version to go back to | --rollback finds no freemapper.previous, because no update ran yet or the file was deleted. | Nothing to undo. Install an older version with freemapper update --version <x.y.z> if needed. |
the update failed: … | Another error during the update, for example a download that broke off. The old program stays. | Try again later. |
warning: freemapper … was not installed: … | In mode install the install after the command failed. The command itself ran and keeps its exit code. | Try freemapper update by hand; the reason follows the colon. |
no source of the permit notes could be read (…) | freemapper permits got data neither from VG250 nor from the BfN nor from OSM. With --offline there are no stored data yet, or they belong to another map area. | Run it again without --offline and with network. Without an OSM extract, run freemapper fetch first. |
warning: … could not be read, so the permit notes leave it out: … / warning: the permit notes leave out …: … | A federal service could not be reached, or no OSM extract was in the cache. The file is written all the same and names the missing source. | Run freemapper permits again later. For OSM, run freemapper fetch first. |
warning: the permit notes could not be written: … | With run --permits the notes failed. The map is written and the run counts as a success. | Read the reason after the colon and run freemapper permits on its own later. |