From this dialog, you can export course data as XML (eXtended Markup Language) format files.  The format has been specified in the IOF Interface Standards project, and you can find more information on the IOF home page at http://www.orienteering.org under the menu IOF / IT Commission / Interface Standards project.

The output from the dialog is a file which contains information on control locations, courses, and classes.  For each course is listed the classes that run the course, and the controls that the course visits.  Also, information on leg lengths is included.

This information can be imported into event administration software for easier punch checking.  Also, this information can be imported into various split time analysis programs.

When you click "Export", Condes will prompt you for a file name for the file to which the exported data should be saved.

File Type

Choose between "IOF Version 1.0" and "IOF Version 2.0".   IOF Version 2.0 is recommended.  IOF Version 1.0 is available only for backwards compatibility.

Encoding

Choose between "ISO-8859-1" and "UTF-8".  This is the character encoding of texts in the file.  UTF-8 is available only when Condes is running in Unicode mode, and is recommended, as this encoding can handle the 16-bit character values used by the Unicode standard.  ISO-8859-1 is the standard Windows character set, and files using this encoding may depend on the character set used on the computer that is used to generate the file.

Canvas (for control co-ordinates)

The "controls" section of the exported file contains co-ordinate pairs for each control.   These co-ordinates are in units of millimeters on the printed map. 

The exported file can contain only one set of co-ordinates for controls.

Therefore, for an event with multiple maps, it is important to choose the a canvas to use in order to get the correct set of co-ordinates for the controls.

Omit "CourseIDs"

Some event administration software packages depend on having a Course ID number associated with each course in the exported data.   If needed, Condes can include this number in the exported file - just make sure to uncheck this box.

Be aware that the Course ID number that Condes assigns to each course will follow the course through the lifetime of the event file. 

Pitfall:  If you rename a course to a different name, it will keep the existing Course ID number.  This will still happen, even when you rename a course, then create a new course with the old name.  When you then export, there will be a different Course ID associated with the name, because it is really a new course.  This is a potential pitfall, if the receiving event administration software expects a course with the same name always to keep the same Course ID number.

Relay

For relay, the file can contain Variations and/or Forks. 

Export variations

If you check this box, for each course the file will have a list of all course variations.  Each variation will be "a course" with all the controls on the course.

Export forks

If you check this box, for each course the file will have a description of the forks on the course.

Use relay XML format extensions

If you check this box, the section with forks will contain indications of the fork and branch limitations controlled by "leg forks" and "bind forks".  These indications are not part of the IOF standard format, and therefore the program that imports the XML file must support these extensions.

If you UNCHECK this box, Condes will - in the exported file - split relay courses that use "leg forks" and "bind forks" into separate courses for each relay leg, thus complying with the IOF standard format.

The Variations and Forks sections are used differently by different event administration software. 

Exporting Variations is the standard and recommended way of transferring relay courses.  This is supported for example by the Emit e-time software.

Exporting forks allows the importing event administration software to combine the forks into courses.   This feature is supported by OS2003 from Sport Software.

Be extremely careful if you choose to use "forks", as there is no guarantee that the event administration program will combine the forks into variations the same way as Condes does, and the naming of the resulting variations may also be different.  The risk is that there will be differences between the variations produced by Condes when printing the courses, and the variations generated by the event administration software. 

Please also note in particular that if you use OS2003 from Sport Software, you need to uncheck the "Use XML format extensions" box, since OE2003 does not support the format extensions.  As mentioned, Condes will then split each course that uses leg limitations (leg forks and bind forks) into separate courses for each relay leg.  Due to the restrictions in OE2003's relay support, this might confuse OE2003's combination validation, and you probably have to validate manually that combinations for each team are entered correctly.