freemapper14. Working on later
- Your map is safe: running
runagain (or "please fetch again") leaves an existing map unchanged. It only updates the templates and candidates. If buildings or canopies are missing from the map, freemapper tells you. - Write it again:
--forcereplaces the map. The old one is kept as.omap.bak. - Training map: it too stays as it is on another
run --training. freemapper builds it from the data, so your corrections in OOM do not reach it. To write only the training map again, delete<name>-training.omapand callrun --training.run --training --forcereplaces the base map as well (chapter 10). - Water in an older map: a map made before this version has no water yet. Running
runagain does not add it. Onlyrun --forcewrites the map again, with water, as for all other map objects. The old map is kept as.omap.bak, the OCAD map as.ocd.bak. Everyrunrenews the candidates and the check print (--pdf-candidates). So the check print shows the water without--force, and the candidates show the water from OSM and the narrow water from the cadastre. - Change the area: run
selecton the existing folder, thenrunagain. - Without internet:
--offlineworks with the data downloaded before. - Data currency: freemapper only downloads what was republished. If a provider changes a tile, you get a "changed upstream" warning.