freemapperDeutsch

Manual › freemapper

7. The result

Among other files, the project folder then holds:

FileWhat it is
<name>.omapthe map for OpenOrienteering Mapper, georeferenced, with buildings, canopies, water and the peripheral information
templates/the templates: orthophoto, hillshade, slope, local relief, nDSM and the candidates map, in Berlin also the K5 (chapter 13)
ocad/with --ocad: the OCAD map and its templates
<name>.pdfwith --pdf: the print-ready map without candidates
<name>-candidates.pdfwith --pdf-candidates: the check print, the map with every candidate
<name>-training.omap, <name>-training.pdfwith --training: the training map (chapter 10), with --ocad also ocad/<name>-training.ocd
<name>-preview.webpan image of the map objects (no candidates, no sheet), written together with the .omap; the area page shows it
ATTRIBUTION.txtthe attribution of the data sources
freemapper.tomlthe project's settings and data currency
permits.md, permits.jsonwith --permits or freemapper permits: the permit notes (chapter 12)

Open the .omap file in OOM. The templates are already linked; show and hide them in the Templates menu. The candidates (templates/candidates.omap) are a separate map on top: fences, hedges, benches, contours, out-of-bounds areas, water from OSM and bridges. Check them and take over what is right: trace them, or open the candidates map and copy and paste the objects. Both maps have the same georeferencing.

On the sprint map the walkable area lies under everything: one area in the lower brown (the tone of 501.5) over the whole map sheet, in its own map part base. It fills whatever nothing else shows. Buildings, streets, out-of-bounds areas, parks, forest, paths, water and contours lie on top. A sprint map without this area is incomplete, because where nothing is mapped it would stay white and look like forest. You can delete it in OOM, but that is not intended. In greyscale the lower brown comes close to the path areas and to paper white, so print sprint maps in colour. The schoolyard map has no walkable area.

Parks are yellow. Green spaces, parks, settlement green and grassland from the cadastre become open land (401) on the map, woods and copses forest (405), heath 403. Cemeteries and other farmland, moor and swamp are candidates, and so are parks and lawns from OSM where no cadastre park lies.

Point symbols such as trees, fountains or bollards keep the gap that ISSprOM asks for. Where two would touch on paper, freemapper keeps the larger one. A dense group of trees becomes an area: paved area with scattered trees, open land with scattered trees, or forest. Paths and paving stay clear. Chapter 9 says what to check there.

freemapper draws water on both map kinds. Rivers, canals, lakes, ponds, harbour basins and sea from the cadastre become uncrossable bodies of water: a blue area (301.1) with a black bank line (301.6). The cadastre often splits a river into many separate areas. freemapper dissolves them into one, so no lines run across the water. Where the water reaches beyond the map area and buffer, it gets no bank line on that edge; islands keep theirs. Water with a mean width under 2 m goes into the candidates only. The contours stop at the shore of this water, in the candidates, on the check print and on the training map.

OSM adds more candidates:

  • Ponds, basins, outdoor swimming pools and fountain basins as areas (301). If at least half of such an area lies in water from the cadastre, freemapper leaves it out, also a lake with islands.
  • Streams and drains (drain) as lines: 305 if they carry water all year, otherwise 306. Ditches (ditch) are always 306. Culverted sections are left out.
  • Fountains and wells (311) and springs (312) as points, and on schoolyard maps also drinking fountains (313). freemapper leaves out fountain points that stand in water, because they are mostly the jets in a basin.
  • Bridges as paved areas (501.5), on sprint maps only. They lie over the water.

OSM areas that are multipolygon relations count like ways: a lake with islands, a park cut by a road or a building with a courtyard. The holes stay empty in the map object, so the courtyard stays out of the building. The relation's own tags decide; its ways need none. A map made earlier gets these areas only with run --force.

Sea that is not in the cadastre stays white. freemapper does not read the OSM coastline.

OSM data on sprint maps. Besides water, OSM supplies these candidates (rules in assets/rules/osm-candidates.toml; existing maps get them with run --force):

  • Passages through buildings and arcades (tunnel=building_passage, covered=yes) on sprint maps as a strip along the way (522), 3 m wide or as wide as the width tag says. The building stays whole. Where ALKIS or the Berlin building parts also know the passage, freemapper keeps the cadastre one and names the OSM way in freemapper:also (see "Duplicates" below). Check on site whether the passage can be used in the race (ISSprOM 2.3 allows two running levels).
  • Private and closed ways and areas as areas that shall not be entered (520). A footway, path, pedestrian way or steps with access=private|no or foot=private|no, and a service road, track or cycleway with access=private|no, become a strip 2 m wide (3 m for roads), and the path line is gone. foot=yes, permissive or designated keeps the way as it was, and so does access=destination or customers. Areas with access=private|no (a land use, garden, pitch, car park, school grounds) are 520 in their own shape; a private pool stays water. Check the 520 against the signs and fences on site, and keep the entrances clear (ISSprOM 520).
  • Paths by surface. Compacted and fine gravel is firm ("hard gravel" in ISSprOM 501), so such a path is a paved line on the map (501.6 to 501.9 by width: 1.4, 2, 3, 4 m), not an unpaved path. Where ALKIS or the survey already draw paving (501.5) as a map object, freemapper does not draw the way twice: the part within the paving and pieces under 1 mm on paper go. A way inside an ALKIS Weg parcel (only a 501.5 candidate) stays whole. Loose gravel, sand, earth and grass stay unpaved on the map: 506 under 1.5 m wide, 505.1, and 505.2 from 3 m. A track without surface follows tracktype: grade1 is paved, grade2 firm (501.7, map), grade3 to grade5 unpaved (505.2, candidate).
  • Railway tracks (sprint, map objects). Tracks from OSM (railway=rail, light_rail, narrow_gauge, bridges and sidings included) are map objects with 509.1, a line at least 4 mm long on paper; each track is a line of its own. freemapper does not draw tunnels, disused, razed and planned tracks, or crossovers. Subway tracks that are not in a tunnel are candidates, on an elevated viaduct (bridge=yes) map objects. Tram tracks (railway=tram) are candidates, 509.2, because the norm draws them only when they help navigation. A forest is cut at a track. The railway land of ALKIS stays a 520 candidate (area that shall not be entered) and the tracks in it stay. Schoolyard maps have no tracks.
  • Control sites for course setters: bollards, street lamps, waste baskets, bicycle racks and benches as points (531, prominent man-made feature) among the candidates, never on the map itself. In Berlin the street survey and the lighting cadastre add bollards, masts, flag poles, benches, lamps and advertising columns. Each has the tag freemapper:control with its kind; select all objects of symbol 531 in OOM to find them. An object that has one of its own kind within 25 m is left out, whichever source it comes from: you cannot tell a bollard in a row, a pair of benches or one lamp in a series from its neighbour. A control site also gives way to every other symbol. Before you use a site, check on site that it is still there, and write the definition of 531 into the legend of the map, as ISSprOM requires.
  • Power lines, pipelines, towers and masts (sprint, candidates only). Overhead power lines are 510, those of 110 kV and more 511 (a double line); the norm leaves out a line that runs along a road or path without extra use for navigation, and freemapper does not compare, so you do. Pipelines above ground are 528 (low) or 529 (high, uncrossable); the norm asks for a definition of both in the legend, and a pipeline without location in OSM is taken to be buried and missing. Towers, masts, chimneys, water towers, lighthouses and pylons are points: 524 (high) or 525 (under 20 m), each with freemapper:control (pylon, mast, tower, chimney, water_tower, lighthouse); one of its kind within 25 m takes both out. Where a pylon stands on a 510 line, the bars already show it: delete one. Lines are left out below the norm's minimum length (3.75 mm for 510 and 511, 2.2 mm for 528, 3 mm for 529).
  • Memorials and boundary stones (historic=memorial, monument, wayside_cross, boundary_stone) as points (526) among the candidates. Stolpersteine, plaques and memorials that are a bench, a tree or a mural are left out, because 526 is for objects that are obvious on the ground (ISSprOM 526). Where the cadastre also knows the monument, you see two points; keep one.
  • Passages (522) that no runner can reach are hidden. A passage that touches only buildings, areas that shall not be entered or water, or joins two walled-in courtyards, is not drawn on the check print or the training map, but stays in the candidates with the tag freemapper:hidden=unreachable. Look at it if you know that the courtyard has a gate. A candidate point (memorial, lamp, bin) that lies inside a building footprint is dropped.
  • Duplicates. When two sources give the same object, freemapper keeps one: the register before ALKIS, ALKIS before the Berlin street survey, the survey before OSM. For areas it measures how much of the weaker one lies under the stronger ones of the same symbol, widened by 0.25 mm on paper (1 m at 1:4000). A passage (522) or a canopy goes when half of it is covered, a private strip (520) inside an ALKIS area that shall not be entered when 80 % is, an OSM bridge over a Berlin bridge deck at half. An OSM memorial within 5 m of a cadastre monument, OSM kerbs along surveyed ones and an OSM stair that lies with at least half its length on a stair of the cadastre or the survey go too. The object that stays names the dropped one in freemapper:also (e.g. osm/way/123). An OSM strip that is much larger than the cadastre polygon it covers stays, because it adds extent.

Below the map is the peripheral information: title, scale, contour interval, scale bar and the attribution. Keep the attribution on printed maps (chapter 16). The north lines belong to the map and sit in the map part "default part". Break them in OOM where they hide small objects, such as boulders, path ends or wall corners.

The example projects in the repository show what the result looks like, one per state: examples/. Each has the OOM map, the OCAD starting point and the PDF.

Forest maps

A forest map (--kind forest) follows ISOM 2017-2. It is meant for small forests you need a training map of quickly. The scale is 1:15 000 (default), 1:10 000 or 1:7500. At 1:10 000 freemapper draws the symbols at 150 %, at 1:7500 at 200 %, as the norm says for enlarged maps.

freemapper init dammheide --osm relation/4513841 --kind forest --scale 10000
freemapper run dammheide --training
  • Paths come from OSM and go straight onto the map: main roads as 502, other roads as 503, tracks of grade 1 and 2 or at least 3 m wide as 504, the other tracks, cycleways and wide or firm footpaths as 505, narrow paths as 506, faint paths (trail_visibility=bad or informal=yes) as 507 and stairs as 532. Private ways stay paths. Sidewalks along roads, crossings, driveways and parking aisles are left out. On the map freemapper moves and joins nothing; only the training map joins ways and moves trees (chapter 10). What OSM has wrong, you correct in OOM.
  • Forest is the white paper. Where OSM or ALKIS says forest, freemapper draws no open land, even where ALKIS calls the land a park or a recreation area.
  • Green comes only where OSM says so: scrub (natural=scrub) becomes candidate 406, dense scrub 408. Meadows and grassland become candidates 401, heath and clearings 403. freemapper takes no green from the nDSM. The vegetation from laser point clouds (group vegetation) can be switched on as for sprint maps; Berlin was flown without leaves, so it finds little there.
  • Contours lie every 5 m, every 2.5 m in flat land and every 10 m in steep land. An area is flat when its terrain heights between the 5th and the 95th percentile span less than 15 m. It is steep when on more than a tenth of it contours 5 m apart would lie closer than 0.35 mm on the map (enlarged like the symbols), so that they run into a brown area, as in the Bode valley or at the Bastei. The ISOM 2017-2 knows only 5 m and 2.5 m; derive names the 10 m in a line, and --contour-interval 5 keeps 5 m. You set the interval yourself with --contour-interval 2.5 on init, derive or run, in the field "Contour interval" on the area page, or as contour_interval_m = 2.5 in freemapper.toml; auto ("automatic" on the page) gives the choice back. For a finished map then run freemapper run <folder> --force (or derive and export --force). The margin names the interval ("Äquidistanz 2,5 m"). When it is not the default, derive also writes it into freemapper.toml as [contours] interval_m, where freemapper-print reads it.
  • Cliffs from OpenStreetMap are generalized (ADR 0126): in rock country OSM has them cliff by cliff, more than 2000 at the Bastei. freemapper reads each cliff on the terrain model: how high the rock stands above its slope and which side is lower; the tags point there. A way is judged in stretches, and pieces of one face are joined. A stretch less than 3 m above its slope goes to the candidates map. A closed cliff with the lower side outside is a rock pillar and becomes 206 (enlarged to the norm's 0.3 mm² where smaller); one with the lower side inside is a hollow and stays a cliff. The highest cliffs are kept first; each keeps the gap of 0.25 mm between the sides that face each other (ISOM 2017-2; enlarged like the symbols). Where only its line has room it is drawn as the top line 201.3, two cliffs back to back closer than that become one rock fin 206, and elsewhere a cliff is cut. The cliffs are smoothed, so that the zigzag of the OSM lines goes. What goes is in the candidates map, tagged freemapper:generalized with the reason; the check print and the training map leave it out. The contours stop below the cliffs drawn and run on elsewhere; knolls and depressions of the terrain on the rock are hidden. For the heights a forest map in a state whose terrain model comes in tiles keeps it as data/terrain.tif. A cliff the orthophoto shows as rock is kept first (freemapper:rock-seen); one it does not show loses nothing, since most faces are vertical or under trees. The training map generalizes the rock more than the map: cliffs of 5 m, no top lines, longer pieces; the candidates keep every OSM cliff. Sprint maps generalize their cliffs the same way, with the values of the ISSprOM 2019-2 (cliffs from 1.5 m, at least 0.9 mm long; on the training map from 3 m; ADR 0134).
  • Buildings, water, walls, fences, power lines, railways and out-of-bounds areas (520) come as on the sprint map. Benches, bollards, street lamps and other street furniture, trees from tree cadastres and single OSM trees are left out. Only a tree tagged denotation=natural_monument becomes candidate 417.

For a quick training take the training map (--training, chapter 10). For mapping you take the .omap, as for the other map kinds.

Version: v0.22.0 · Source on GitHub