Data Standard 2.0

The IOF Data Standards is a definition of an XML based format for interchange of data among the IT systems involved in organising an orienteering event. The Data Standards were introduced in 2002 and were the output of an IOF Interface Standards Project, lead by the IT Commission, and with participation by all the major interested parties.

Version 2.0.3

This is the first official version of the standard, dated 2002. This is the first standard that is widely implemented by software developers including the two EKT system, Emit and Sport Ident.

The changes from version 1.0 includes:
A total rewrite of nearly all elements.
Instead of having several Document Type Declaration (DTD) files each holding a small part of the standard and depending on each other the DTD is now assembled in a single file.
A number of messages, i.e. specification of the lists to be send from one software element to another, have been made. There still are some messages missing and they will be developed concurrently with demand for them.

Some example files of the messages to exchange have been made. Please read the comments in the DTD file for further information.

IOFdata (zip)
IOFdata (txt)

Example files


This list is used to exchange event information for a number of events, e.g. fixtures.

EventList_example These are actual events from the Danish fixtures of March 2002.

ClubListThis list is used to exchange information of a number of clubs, e.g. contact addresses and bank accounts. This could be used by a national club register.



This list is used to exchange non-event specific information on a number of Competitors. This could be used by a national competitor register.


EntryListThis list is used to send entries from a single club to an organizer of an event.


A normal entry list.


A normal entry list using teams for a relay.


An entry list with all information that possibly can be included. Only one entry is in the file.


The same as Example 3 but with a team entry for a relay.


This list is used for the start list of an event. In fact it could be put on WWW using XSLT (XML Style Language Transformation).


A normal start list.


A normal start list for a relay.


This list is used for the result list of an event. In fact it could be put on WWW using XSLT (XML Style Language Transformation).

A result list comes in three types:

  1. complete
    This is a complete list including all competitors. It should only be used after the event.
  2. snapshot
    This is also a complete list including all competitors but some may not have started yet, others may still be out running. It is a snapshot of the current standing.
  3. delta
    This is a file containing only the changes since the last file was sent. It is also a snapshot.

The latter two types are intended to be used for “real time” results during the event. The first type is for the final standing after the event.


A result list using competitor IDs. This should only be used if the reciever uses the same competitor database and uses the same IDs.
The list is also a “snapshot” result file.


A result list also using competitor IDs. It looks much the same as Example 1 but this is a “delta” result file. Only the changes since the last file was sent are included.


A relay result list also using competitor IDs. It is a “snapshot” file just as Example 1.


These data contains courses and controls including starting points and finish controls. This defines all the control and course information. It is typically exchanged between the course setting software and the event software for this to be able to perform punch checking. The data also contains information about the position of the controls on the map so it can be used by map printing software.


An ordinary event. In fact this is “real” data from Spring Cup.


A relay event. This is also “real” data from Spring Cup. Beware, it is a quite big file.

DownloadYou can download the DTD and example files in one package here:

IOFdata-2.0.3.tar IOFdata203


Message Standard

Although the Data Standard describes the information involved in an orienteering event it is not well suited as a standard for the information sent between systems.

The Message Standard should identify the different systems involved in an orienteering event and describe what data (“messages”) that should be send between the systems. Version 2.0 of the standard identifies some of the messages needed.

At the Oslo seminar in October 1998 the following structure was found:

Version 2.0 defines some of these messages:

1: EventList.
2: ClubList.
3: CompetitorList.
4 (Partly 5 and 6): EntryList.
9, Partly 8: CourseData, ClassData.
14, 17: ResultList.

|| Print page ||
  • Search

  • IOF Main Sponsor

    IOF Main Sponsor

    Nokian Tyres

  • IOF Sponsors

    IOF Sponsors

    BML Print

  • World Championships

  • Nokian Tyres World Orienteering Championships 2018
    4-11 August 2018

  • World Trail Orienteering Championships 2018
    4-11 August 2018

  • World Mountain Bike Orienteering Championships 2018
    5-13 August 2018

  • Other Upcoming Events

  • North American Orienteering Championships 2018
    17-24 August 2018

  • Orienteering World Cup Round 3
    31 August - 2 September 2018

  • MTB Orienteering World Cup FInal 2018
    21-23 September 2018

  • Orienteering World Cup Final 2018
    4-7 October 2018

  • IOF Partners

  • International Olympic Committee

  • ARISF_logos_05

    Association of IOC Recognised International Sport Federations

  • International World Games Association

  • International Masters Games Association

  • Global Association of International Sports Federations

  • World Anti-Doping Agency

  • International University Sports Federation (FISU)

  • Conseil International du Sport Militaire (CISM)

  • European University Sports Association

  • International School Sport Federation