Several types of orienteering competitions use maps standardized by the IOF.

Contents 1 IOF Standard Orienteering Maps 2 OSM and IOF mapping 3 Practical IOF Mapping 3.1 Elevation data and contours 3.2 Editing 3.2.1 JOSM 3.2.2 Merkaartor 3.3 Old map as editor background 3.4 Rendering 3.4.1 Mapnik 3.4.2 Osmarender 3.4.3 Inkscape 3.4.4 Colour profiles 3.4.5 rounded (bézier) curves 3.4.6 Rendering problems 4 Working with other mapping software 4.1 Comparison 4.2 Converting Shapefiles 4.3 Converting dxf files 4.4 Converting to OCAD 5 Setting up a local database 6 IOF codes and their corresponding OSM map features 6.1 OSM Map Features 6.2 IOF codes (ISOM) 6.2.1 Land Forms 6.2.2 Rock and boulders 6.2.3 Water and marsh 6.2.4 Vegetation 6.2.5 Man-made features 6.2.6 Technical symbols 6.2.7 Overprinting symbols 6.2.8 Discipline specific 6.2.8.1 Sprint Orienteering (ISSOM) 6.2.8.2 Ski Orienteering (ISSKIOM) 6.2.8.3 MTB Orienteering (ISMTBOM) 7 Links and Contacts

IOF Standard Orienteering Maps

The IOF is the International Orienteering Federation. (see http://orienteering.org)

The IOF has released standard mapping specifications for several different types of orienteering sport competitions.

As a general rule, orienteering maps usually provide contour data and (with a standard scale of 1:15000 or 1:10000) an above avarage level of detail in natural / vegetation features.

OSM and IOF mapping

IOF mapping with OSM means:

• OSM data can be rendered with IOF symbols and style definitions. (Optionally showing additional features.)
• Corresponding OSM tags are defined for each IOF code.
• OSM Editor Templates/Symbolbars are provided so mappers can choose the tagging by IOF codes/symbols.

As a result, it has become possible to create orienteering maps using GPL'ed Free Software. This is important for mainly two reasons. First, so that cartographic beginners can try the art of map-making without having to buy an expensive software. Secondly, today's leading map-making software lacks many features, e.g being able to making maps cooperatively in a group. Anyone can make the changes they need to free software (or have them made), which is not possible with proprietary software.

We use our Free Software for making free maps, but are of course free to choose under which terms and conditions we use and distribute our maps.

Keep in mind that full detail orienteering maps must not be released until after the last competitor starting in the competition has gotten his map and started.

Therefore the mappers of a orienteering map will usually start off with two separte working layers in their editors first. (The free osm layer and a private layer that is stored in a local file or database.) As they conduct the survey they will correct and add to the OSM data layer (man-made, water and marsh features), while keeping additional landform, rock, boulder, trails and vegetation features in the private layer, which will not be made public until after the competition event.

We would love to get feedback if you are using the software described here to make maps. For contact information see bottom of page.

Practical IOF Mapping

For a general indroduction see GIS_for_Dummies_(written_by_a_dummy) and look around in the OSM Wiki. Follow good practices and check out the FAQ. With OSM we are not using a map drawing program, we are using a GIS application. (Geographical Information System)

The basic understanding is that we "record whats actually on the ground". Configuring or changing the "renderer" programm to adjust how a map generated from the data looks like, is a different task.

For IOF mapping with OSM you will currently need at least two OSM programs with special IOF additions: A map object editor and a renderer (map generator). (The renderers that are build into the available editors are not (yet) cabable of rendering IOF maps directly.)

That means that as long as not all features needed for IOF mapping are available in the programs upsteam, you need to download specially enhanced versions. Please refer to the sections below to determine the patched files you'll need.

Elevation data and contours

Orienteering maps need contours. However, since digital elevation model (DEM) data requirements are diverse and different models exist, the OSM map servers do not provide elevation data.

Elevation data for creation of contours has to be fetched from a separate source like the Shuttle Radar Topography Mission (SRTM) or ASTER.

Remember not to upload contour lines to the OSM map servers.

Options:

• Contours decribes some OSM server side methods.
• Srtm2Osm
• GroundTruth
• TopOSM
• DE:OSMC_Reitkarte
• dem2topo
• Blackart
• German Howto "Herstellung von Höhenlinien" (von Jörn Weber)

Editing

For the editor you can choose between JOSM and Merkaartor.

• JOSM has some advanced functions and many plugins
• Merkaartor looks more close to the final map. Someone used to OCAD might be more comfortable with this one.

It is recommended to test both programs to see what suits you best. Read more instructions on how to use the programs on their wiki pages.

You can switch and use different editors while working on the same map data. (Even concurrenly if you are working with a database.)

JOSM

JOSM is a map editor with some advanced functions and many plugins.

You can configure which server to use under: Settings -> Connection Settings (2nd tab). (Set Base Server URL, your username and password.)

IOF mapping additions:

• IOF taging presets
  • Download JOSM IOF presets to your JOSM directory.
  • Open the settings panel in JOSM and select the map settings tab. Under "Tagging Presets" de-select "Enable defaults" and add a new tagging presets source. In the popupbox write the path to your saved file (if placed in the same folder as the jar-file, this is simply "isompresets.xml"), press OK and restart JOSM.

• IOF editor style
  This changes the style and colours of the map in JOSM.
  • Download the iof-png-icons and extract the archive in your JOSM directory.
  • Download JOSM IOF style and save it your JOSM directory.
  • Open the settings panel and in the advanced settings tab set the following values:
    • mappaint.style: comostyle
    • mappaint.icon.sources: comostyle=iof-png-icons
    • mappaint.style.sources: comostyle=comostyle.xml

• Optionally set these:
  • mappaint.icon.enable-defaults=false
  • mappaint.style.enable-defaults=false
  • mappaint.useRealWidth=false

For more information see JOSM/MapPaint.

Merkaartor

The edited map in Merkaartor looks more close to the final map (as in what you see is what you get). Someone used to OCAD might be more comfortable with this one.

See Merkaartor/Documentation.

You can configure which server to use under: Preferences -> Data tab (Set website path, your username and password.)

IOF mapping additions:

• IOF editor style (Note, the IOF style for Merkaartor is not yet complete.)
  • Download isom.mas
  • Under Preferences->Style enter the path to the .mas file.

Old map as editor background

Both JOSM and Merkaartor support loading your old maps as a (picture) background. (You need to make sure you are allowed to use and publish derived works.)

Your options are:

• (simple but not recommended) Use the picture layer feature of your editor to load a picture as background, then move, rotate and scale it.

• Use a Web Map Service (WMS). With this, many persons can use the same image layer, and you only have to position the image once. You may upload your image to a web service (like http://warper.geothings.net/) but this has some limitations (e.g. max file size). You can also put up your own. This is a map rectifier and WMS: http://svn2.geothings.net/mapwarper/ (not tried).

Rendering

After a while of editing you probably want to see what your map will look like.

In contrast to OCAD, JOSM (and to some degree Merkaartor) do not show exactly how the printed map will look, and it is not possible to print it directly. To get the final map image file, you have to use a renderer, which creates a map combining the objects data with a symbol set. There are at least four renderers available for OSM data: Mapnik, Osmarender, Kosmos and Maperitive.

In order to make IOF orienteering maps that draw areas and cliffs with patterns the renderers need to be patched to be able to do this.

Mapnik

Mapnik is rather difficult to install and can't use the map data directly without conversion. Related information and some ISOM rendering can be found on HikingBikingMaps and OpenOrienteeringMap.

Osmarender

Osmarender was easier to use and adopt.

The Osmarender output is a file in the Scalable Vector Graphics (SVG) format. All major modern web browsers except Internet Explorer can show SVG images. (Adobe has a plugin for IE to show SVG.)

Osmarender is an XSL file, which defines the necessary transformations to get the SVG image according to the rule file. For doing this transformations, it is necessary to have an XSL transformer program. You could use a web browser that supports XSL like Firefox to view the map directly and (with the Web Developer addon) even save it. (View generated source, and save it as an .svg file.) Otherwise you need a separate program that can do the transformation, see Osmarender/Howto. With Linux and Mac OS "xsltproc" is usually already installed.

There is a special Osmarender version enhanced for IOF mapping. So you must download this and not the OSM standard version.

• Save your map data to a file (called map.osm).
• Download the iof-svg-symbols and extract the archive.
• Download the enhanced osmarender.xsl file.
• Download the isomrules.xml file.

The .xsl file defines transformations of map objects and symbol files onto a map, and the rule file contains the rules to use the transformations so that the map looks like an orienteering map. The rules file is different if you want to make an isom, issom or some other map.

It would be good to be able to use the Osmarender_Frontend to configure the tags to render as IOF special land form, water and man-made symbols.

Besides the deviations in the version to download you can refer to the instructions on the Osmarender/Howto page to render your map.svg file.

Since the map is a vector graphics file, the pixel density can easily be adopted when printing the map, and the map will scale nicely to other sizes. For example scale to 50%, if you want a 1:10000 scale instead of 1:15000.

Inkscape

It is recommended to download Inkscape, a good vector graphics editor. Use it to generate the final layout of your map with all logos and pictures you'll want to include.

Image:Osm button-path.pdf
Image:Osm button-path.svg

Finaly you can print the map with Inkscape or save it in a format your print shop can handle.

Colour profiles

Adopting colours for different printers or screens.

If you don't use Inkscape you could create a search and replace script to change the colour definitions in the .svg file.

Example for changing one colour:

sed -i s/<colour-to-replace>/<new-colour>/ map.svg

rounded (bézier) curves

It is possible to make the bending curves a bit more softly after generating the map file. (post-processing)

Download lines2curves and install Perl if you don't have it installed already. You probably need to install the Math::Vec methods from http://search.cpan.org/dist/Math-Vec (see README instructions).

Then it is done with a simple command like this:

lines2curves.pl map.svg > map-bezier.svg

Bézier curve support in OSM would be very good. Follow the discussions at OSM. See Bezier_curves and Osmarender/BezierCurves.

Rendering problems

Current rendering problems or where improvements would be good:

• Ruin with dashes (gaps in the middle of the segments / only draw corners)
• Major power line (without fill in middle). Rendering as an Area? Maybe, modify osmarender to use the SVG masking feature
• Add/move/delete tags/markers on lines. Need to adjust the position of markers on lines, if they not appear where they are wanted. Possible solution: "tags:yes/no/indicated/unlessindicated"

yes - as normal

no - not at all

indicated - tags on nodes with tag:yes

unlessindicated - tags on all nodes except tag:no

• Can not do line tags with varying length (e.g impassable cliffs)
• A (large) erosion gully, has to be rendered as an area (can not do pointed ends nor varying line width)
• Path junctions (visible/indistinct)
• Path crossing with streams, bridge or not.
• Crossing points (on fences etc.) have to be done as a line now, want fixed-size crossing point (as node)?
• Firing range: Small rendering error (line behind arrow)

Working with other mapping software

An example for a proprietary mapping software sometimes used for orienteering maps is OCAD.

Comparison

OSM software pros

• Use of database allow for good collaborative mapmaking. Several people could edit and access the map data simultaneously.
• Use of database give revision history: who has changed something and when.
• Possibility to use map data with additional GIS applications. You can add touristical and name information about objects for example or use relations to link objects together.
• Objects on map have absolute positions (lat/long) obeying geodetic projection standards. Easy to merge maps.
• Open file format permits people to make new programs.
• Free software, you can make your own additions and many can contribute to the code.
• No licence cost, new (unexperienced) cartographers can download the software and try it.
• Most programs and the database work well in many operating systems (Windows, Linux, Mac OS...).
• Possible to combine ISOM, ISSOM, School maps, etc. in the same database and then render them for different purposes.
• ... .

OSM software cons

• The Editors are not (yet) fully WYSIWYG capable. The objects may look different in the editor than on the map. (i.e. use fine precision lines and points instead of map symbols)
• Probably not easy to use for course setting. However, have a look at the Purple Pen Free Software made for that purpose.
• Quite hard to render own map objects. (Usually not necessary, use Inkscape to add text, logos, pictures, etc. to your page layout.)
• ... ?

Converting Shapefiles

The easiest is to export your OCAD map as a shapefile and then convert that to the OSM file format. Shapefile export is only available in the professional edition of OCAD. If you only have the standard edition, you have to export as dxf file and then convert that to a shapefile, see further down.

By exporting to shapefile you should be able to get your features from OCAD converted to .osm (not tested). You will have to configure how key and values shall be translated. Please read shp2osm.

Here is also described how you transform your projection. This might be a bit of problem if the shapefile exportet from OCAD doesn't include correct information.

Converting dxf files

If you don't have OCAD Professional but only standard edition, you will have to export your map to dxf and then convert it to a shapefile. Note, you WILL lose information (what I can see, you don't get any information about the types of objects).

Use Grass to convert dxf to shapefiles.

Converting to OCAD

Not recommended. Feel free to try:

• http://code.google.com/p/osm2shp/
• ogr2ogr for projection conversion
• Load shapefile into OCAD.

Setting up a local database

To be able to cooperate on parts of your map privately until you publish the map after the competitions, or to add a layer that contains only temporary details, you can setup a local database and osm api. The current OSM database setup is called The Rails Port. Read install instructions there.

To merge data between databases use your editor to save the map data downloaded from a database server to a local .osm file, switch the server settings in the editor, open the .osm file and upload the data to that server.

• Do we have to remove database IDs from the .osm file?

IOF codes and their corresponding OSM map features

Compared to the set of IOF codes, openstreetmap knows more map features than IOF codes exist. OSM already provided tag definitions for quite a fraction of the IOF Codes. With some newer tags the OSM features cover the complete range of IOF Codes.

OSM Map Features

OSM map features consist of elements that are tagged with key=value pairs.

The basic elements can be nodes (single points), ways or areas. Ways consist of a number of ordered nodes, and areas are ways where the start and end node are the same. Read more about the basic elements on the Elements page.

Tagging refers to adding key=value pairs describing elements. It is not necessary for a map drawer to learn and and use tags directly, if the editor provides another way to define objects (with preset tags for example).

Generally osm tags should be named descriptively according to how someone would search for them, had he found something on the ground, classify with good [[Verifiability]|verifiability], and organized to optimize rendering for different purposes and when tags or values are missing/unsupported/combined/...). They are not optimized for human editing. That kind of optimization (like grouping, dependencies, easy switching, etc.) can be handled by editior programs.( syntactic conventions)

IOF codes (ISOM)

Please help in finding and documenting all osm tags belonging to IOF symbols.

The benefit is, that osm data can be rendered with IOF stylesheets,
and when mappers create objects by IOF codes/symbols in OSM Editors,
can be prompted to choose from the (more precise) set of OSM features.

The corresponding osm tags have not yet stabilized.

Remember, the general OSM rules, "map whats on the ground, not what should appear on the map" and Verifiability.

If you don't find whats on the groung listed here or on Map_Features, seach for existing tags with the wiki search and Taginfo. If you need, you could add Any_tags_you_like (refering to that page).

Introducing common tags for IOF mapping:

• ruins=yes states that the feature is deteriorated / unmaintained.

This tag is already in use and in Map Features

• foot=passable states that (barrier like) features are not a total barrier when on foot. (Default (without a tag) is foot=impassable.)

This is a proposed new value for the foot= key. A path up a cliff could be access=no (and even foot=no), still when the cliff is foot=passable, it should be mapped as such and appear as such on the IOF orienteering map.

• indistinct=yes states that the borderlines or position defined by the element is not visible as sharp as the map data may suggest.

This is a proposed new tag. On IOF maps many such elements will show up without an outline, so only a colour change is displayed on the map.

• runnability=* Can be 20%,60%,80%,100% and refers to the definition of the IOF standard (ISOM 2000 4.4).

This is a proposed new tag. On IOF maps the runability of forests/woods for example translates into shades of green.

• direction=* Can be [0-360] and states the direction of an asymetric feature, where 0 is north and counted clockwise.

This is a proposed new tag. On IOF maps vineyards for example are displayed with the distict direction of the rows, given this tag is available.

For way features that are not symmetric about the way (like a cliff) the direction tag is not necessary. The markings will always be TO THE RIGHT of the direction of the way. For example, going in the direction of a slope contour line, downwards should be to the right.

However, for nodes and areas which have a variable direction, like elongated knolls, caves or forests runnable in one direction, the direction needs to be taged. It is given in degrees (0-360) whith 0 degrees pointing north counting clockwise.

• barrier=earth_bank

This is a proposed new value (see below).

• still needed: tags for water wells (man_made=water_well?), boulder, boulder_field, boulder_cluster, stony_ground, bare_rock (all natural=?), orchard (landuse=?), distinct rides (linear break in forests without track or path), (arms) firing range, fodder racks and large roots (of fallen trees).

Orienteering maps often show positions for those.

• When mapping in the woods, remember to set disused=yes in some cases. For an old railway for example, so nobody thinks he could still catch the next train for a ride out there.

With ISOM2000 the IOF has categorized map symbols into the following groups:

Land Forms

Remember not to updload contours to the OSM map servers. Elevation model data has to be saved separately.

IOF Symbol Name	Value for iof= key notation	Element	IOF codes	Comment	Extra key=value pairs	Rendering example (not to scale)	corresponding osm tags	Photo
	contour		101, 102, 103	Height contours	type=normal/index/form. altitude=[meter] to specify height over sea
	slope_line		104	Draw slope line for node on a contour.
	?	?	105	Contour value (show on map)			show on contour line points with ele=* value
	earth_bank		106	Earth banks. For a small earth bank you could use a single node	size=normal/high (?)		barrier=earth_bank or man_made=embankment. For earth banks along both sides of a way also embankment=yes or cutting=yes. Optionaly: height=* so that the renderer can decide wether a slope is high or not. Should it be mapped as an area to define a varying length of the slope lines?
	earth_wall		107, 108	Earth walls	size=normal/small		barrier=earth_wall optionaly ruins=yes
	erosion_gully		109, 110	Erosion gully	size=normal/small. area=yes/no (for larger erosion gully)		way: barrier=ditch optionaly indistinct=yes
	NOT USED		111, 114	Larger knolls and depressions are shown by contours and slope lines
	small_knoll		112, 113	Knolls too small to be shown by contours.	elongated:yes/no. direction:[0-360] for direction of long side of elongated knoll.		node: barrier=earth_wall or historic=tumulus or historic=archaeological_site with site_type=tumulus optionaly: direction=* for elongated knolls
	small_depression		115	Small shallow natural depressions and hollows	depth=[meter]		barrier=ditch with indistinct=yes
	pit		116	Pits and holes with distinct steep sides.	depth=[meter]		barrier=ditch
	broken_ground		117	Broken ground	size=small/medium/large		area: barrier=ditch or barrier=earth_wall with area=yes optionaly: runnability=*
	special_landform		118	Special land form feature	Description:User Defined		(something you map appropriately and configure the renderer to show it as IOF118_special-landform)

Rock and boulders

natural=scree

IOF Symbol Name	Value for iof= key notation	Element	IOF codes	Comment	Extra key=value pairs	Rendering example (not to scale)	corresponding osm tags	Photo
	cliff		201, 203	Passable or impassable cliffs.	passable:yes/no. tags:yes/no. direction:[0-360] for nodes		natural=cliff barrier=retaining_wall waterway=dam optionaly: foot=passable
	rock_pillars		202	Rock pillars or gigantic boulders			natural=cliff area=yes
	rocky_pit		204	Rocky pit			barrier=ditch node together with natural=cliff or barrier=retaining_wall
	cave		205	Cave	direction=[0-360]	see rocky_pit	natural=cave_entrance
	boulder		206, 207	Boulders of different sizes	size=small/medium/large, height=[meter]		optionaly indistinct
	boulder_field		208	Part of a field of boulders	direction:[0-360], size=normal/large??
	boulder_cluster		209	A small distinct group of boulders so closely clustered together that they cannot be marked individually.	size=normal/large?
	stony_ground		210	Stony ground	size=small/medium/large		natural=scree optionally runability=*, alternative when area is not a scree, like a stony forest?
	? open_land, surface:sand		211	Open sandy ground			natural=beach, alternative when area is not a beach area=yes and surface=sand
	bare_rock		212	Bare rock			landuse=quarry alternative when area is not a quarry? natural=bare_rock tag?

Water and marsh

IOF Symbol Name	Value for iof= key notation	Element	IOF codes	Comment	Extra key=value pairs	Rendering example (not to scale)	corresponding osm tags	Photo
	water		301, 302, 304, 305?	Water areas (lakes, ponds, rivers)	bank_line:yes/no. passable:yes/no (issom)		natural=water (natural=land for islands within), waterway=dock , for large rivers use waterway=riverbank optionaly: foot=passable
	river		304	Smallest size for river, alternative or combined with water.	bank_line:yes/no. passable:yes/no?		waterway=river waterway=canal
	bank_line		301, 304	Bank lines to water areas (also see water)		See water	foot=passable removes bank line for waters
	watercourse		305, 306, 307	Crossable watercourses. Large watercourses could be combined with water.	size=large/small/minor, width=[meter]		waterway=river with foot=passable / waterway=stream or waterway=drain (medium) / the latter both optionaly with indistinct=yes.
	waterhole		303	Water-filled pit			node: barrier=ditch with natural=water
	narrow_marsh		308	A narrow marsh			way: natural=wetland or natural=mud
	marsh		309, 310, 311	Marsh that could be shown as an area	type=impassable/normal/indistinct		natural=wetland / with: foot=passable / with "indistinct" / same with nodes, natural=mud?
	well		312	Well			waterway=water_point possibly man_made=water_well older proposal
	spring		313	Source of a stream. When placed on the start of a watercourse, the direction is automatically oriented downstream	direction:[0-360]		barrier=ditch node with indistinct and natural=water / natural=spring node optionaly with a starting waterway
	special_water		314	Special water feature	Description:User Defined		amenity|fountain}, {{tag|amenity|drinking_water}, man_made=water_tower, man_made=watermill, man_made=reservoir_covered, ... (something you map appropriately and configure renderer to show it as IOF314_special-water)

Vegetation

IOF Symbol Name	Value for iof= key notation	Element	IOF codes	Comment	Extra key=value pairs	Rendering example (not to scale)	corresponding osm tags	Photo
	open_land		401, 402, 403, 404, 415(?)	Different types of open land	surface:normal/rough, trees:no/scattered, cultivated:yes/no(?)		open: natural=heath landuse=village_green landuse=recreation_ground leisure=park cultivated: landuse=farm rough: landuse=meadow natural=scrub natural=fell , (for scatered trees also tag forest/wood, see next)
	forest		405, 406, 408, 410, 411	Forests with different running speed. Normal (white) forest is normally not needed to tag	running:easy/slow/ difficult/ very_difficult/ impassable. one_direction:yes/no, direction:[0-360]		natural=wood or landuse=forest shade according to runnablity=*, impassable also: barrier=hedge (node, way or area with area=yes) all optional: direction=* and wood=* stating the (wood) vegetation type in an area (coniferous/deciduous/mixed).
	undergrowth		407, 409	An area of dense undergrowth but otherwise good visibility	running:slow/difficult		barrier=hedge with area=yes, foot=passable and runnablity=*
	orchard		412	Land planted with fruit trees or bushes.	direction:[0-360]
	vineyard		413	Vineyard	direction=[0-360]		landuse=vineyard
	? boundary		414, 416, 417(??)	Different type of boundaries between areas	type=distinct_cultivation/ distinct_vegetation/ indistinct_vegetation(?)		Marking an area or way indistinct=yes states it has a less sharp/visible vegetation boundary (may remove an outline shown). (A *way* taged natural=wood landuse=forest or landuse=farm and area=no may state a corresponding single (open loop) vegetation boundary?)
	special_vegetation		418, 419, 420	Special vegetation feature	Description:User Defined. display=cross/circle/dot		example could be a natural=tree (something you map appropriately and configure the renderer to show it as IOFxxx_special-vegetation_x/o)

Man-made features

There is a page about mapping Hiking paths.

General note: highway=footway highway=cycleway and highway=bridleway are shortcuts for highway=path + defined access=* tags i.e. foot=designated, bicycle=designated or horse=designated tags.

IOF Symbol Name	Value for iof= key notation	Element	IOF codes	Comment	Extra key=value pairs	Rendering example (not to scale)	corresponding osm tags	Photo
	road		501, 502, 503, 504, 505	Roads suitable for vehicles	type=motorway/major/ minor/narrow/track. area=yes/no. construction:yes/no.		501 motorway: highway=motorway, highway=trunk 502 major road: highway=primary, highway=secondary 503 minor road: highway=motorway_link, highway=trunk_link, highway=primary_link highway=residential highway=living_street highway=bus_guideway 504 road: highway=unclassified, highway=service, highway=track with tracktype=grade1 505 vehicle track: highway=track with tracktype=grade2, highway=bridleway(highway=footway, highway=cycleway, cycleway=track (if distinct way, not part of a larger road) Optionaly: width=* (or est_width=*), and highway=construction for roads in construction. (Maybe some rules using surface= or Proposed_features/surface_unification could be usefull to improve appropriate rendering.)
	path		506, 507, 508	Paths	type=large/small/indistinct. area=yes/no, urban=yes/no (for issom unpaved footpath)		506 footpath: highway=track with tracktype=grade3 and lower, highway=path with trail_visibility=excellent 506 small path: highway=path with trail_visibility=good and trail_visibility=intermediate 507 less distinct path: highway=path with trail_visibility=bad, and trail_visibility=horrible (consider adding sac_scale=* classification for hiking paths: Approved_features/Hiking)
	narrow_ride		509	A distinct ride
	??	?	510, 511	Whether a junction easily could be seen in competition speed	?
Footbridge	bridge		512	A footbridge with no path leading to it. The direction is automatically oriented if on a watercourse	direction:[0-360]		A waterway node with bridge=* level -1 below other features and ( foot=designated or foot=forestry or foot=passable (perpendicular crossing) / A (trail) way with bridge=* and level=(above other features) (angled crossings lige regular)
Crossing point with / without bridge	bridge:yes		513, 514	Whether a path over a watercourse have a bridge over it or not.			use level=* and bridge=* or highway=ford appropriately
	Railway	Railway	515		type=rail/tram		railway=* or railway=tram
	power_line		516, 517	Powerline	size=normal/major?. For nodes on line: pylon:yes/no.	Major powerlines?	power=line major lines: voltage=* >= 110000V?, cables=* >=5? also: aerialway=cable_car aerialway=gondola aerialway=chair_lift aerialway=drag_lift
	power_pylon		517	Pylon on a major powerline	?	See power_line	power=tower
	tunnel		518	A way under roads, railways, etc. which may be used by the runner. This symbol is used whether or not the tunnel has a track leading to it. (maybe smallest as node on road?)	part:extent/opening/edge. width=[meter].?		tunnel=yes bridge=* both used together with layer=*
	stone_wall		519, 520, 521	Walls made of stone	size=normal/ruined/high.		barrier=wall, also historic=city_wall optionaly: ruins=yes, foot=passable
	wall		519.1, 521.1	Walls (issom)	passable: yes/no		barrier=wall, also historic=city_wall optionaly: foot=passable
	fence		522, 523, 524	Fences	size=normal/ruined/high		barrier=fence optionaly: foot=passable, ruins=yes
Crossing point	crossing_point	?	525	All ways through or over high fences or walls must be indicated.			barrier=gate barrier=entrance barrier=stile barrier=sally_port
	building		526	Buildings	For nodes: direction:[0-360]		building=* power=station power=sub_station aerialway=station amenity=shelter tourism=alpine_hut tourism=chalet
	canopy		526.2	Canopy (issom)	For nodes: direction:[0-360]
	pillar		526.3	Pillar (issom)	?
	settlement		527	Houses and gardens and other built up areas.	How to indicate alternative rendering?		leisure=playground leisure=garden landuse=farmyard, landuse=allotments, landuse=residential [[Key:|]]=sports_centre leisure=track leisure=water_park leisure=miniature_golf and maybe a couple more ...
	permanent_out_of_bounds		528	Permanently forbidden	boundary:yes/no		access=no, access=private, foot=no, foot=private optionaly indistinct
	boundary		528	Boundary	type=permanently_forbidden	see permanent_out_of_bounds
	paved_area		529	An area of hard standing used for parking or other purposes.	? urban=yes/no (issom)		amenity=parking highway=pedestrian highway=services junction=roundabout amenity=ferry_terminal amenity=bus_station ...
	boundary (edge? / step?)		529.1	issom	type=edge/step urban=yes/no ?
	ruin		530	Ruin	?solid_line=yes/no?		building=* with ruins=yes
	firing_range		531	Firing range (usually way with two nodes). target at end of line.	?
	grave		532	A distinct grave.	?		amenity=grave_yard landuse=cemetery
	pipeline		533, 534	Pipelines	passable:yes/no		man_made=pipeline optionaly: foot=passable
	tower		535, 536	Tower	size=high/small		amenity=hunting_stand, man_made=tower (also min. required: tower:type=*) man_made=water_tower man_made=lighthouse
	cairn		537	Cairn, memorial stone or boundary stone			man_made=survey_point historic=memorial
	fodder_rack		538	A fodder rack which is free standing or built on to a tree.
	special_manmade		539, 540	Special man-made feature	Description:User Defined. display=cross/circle.		could be a kiln/platform? (Meilerplateu), barrier=bollard barrier=cycle_barrier barrier=cattle_grid barrier=toll_booth amenity=bench amenity=emergency_phone amenity=telephone amenity=waste_basket amenity=* amenity=grit_bin amenity=signpost (or tourism=information with information=guidepost)(something you map appropriately and configure the renderer to show it as IOFxxx_speciaal-man-made_x/o)

Technical symbols

(Not implemented yet)

Overprinting symbols

This refers to objects and markings that may be only valid temporarily during the competition. Like refreshment points, out-of-bound areas, etc. and the "off road" route for the competitor that connects the start point with control points and the finish.

(Not implemented, see Comparison for an alternative.)

• Orienteering does contains a tag definition for permanent control markers, but it looks as it is used differently (see tagwatch for GB and Scandinavia).

Discipline specific

The IOF has additionaly defiened some discipline specific codes and symbols.

Sprint Orienteering (ISSOM)

TODO

No major differences compared to ISOM, additional special features noted below.

Water: passable:yes/no foot=passable
Unpaved footpath: Use issom:path, type=large. If want to show area, use area=yes. urban=yes/no

highway=steps highway=pedestrian (ways)

Ski Orienteering (ISSKIOM)

TODO

MTB Orienteering (ISMTBOM)

TODO

Links and Contacts

IOF mapping with osm has previously been documented outside of the osm wiki at como.oxtract.se.

Many thanks go to David Svantesson who provided the osm community with osmarender enhancements to make it capable of rendering IOF symbols to implement the first OSM IOFmapping possibilities.

Any comments, testing reports, usage (and usage reports) and help is greatly appreciated.

Contacts:

• David is reachable by email as david at oxtract.se
• Other osm users interested in orienteering maps include Ollie, Thomas Wood, luchs, Mila, Wbski...
• Mailinglist: orienteering@ is in the process of being created.

If you are interested in IOF mapping, we suggest you put this wiki page to your watch list. (tab on top)