Code Lists

Platform: 🖥️ Desktop only

See also: Classes, Courses & Maps, Import & Export

When you need this

Your event uses checkpoint markers where the printed code differs from the internal punch device code — for example, checkpoint "31" uses a device with code "131". A code list tells Navisport how to map between these two numbering systems so results are calculated correctly. You also need a code list when importing course data from IOF XML files that use control labels different from your punch device codes.

Why code lists exist

In orienteering events, the code printed on a checkpoint marker (e.g., "31") does not always match the internal technical code of the punch device (e.g., "131"). This happens because punch devices use their own numbering, which may differ from the checkpoint codes used in course planning. A code list bridges this gap so the system can correctly match punches to checkpoints and calculate results.

Code lists are also used during XML import — when you import course and class data from an IOF XML 3.0 file, the system uses the active code list to map control labels from the XML file to the correct punch codes.

Tip: If your event uses the same numbers for checkpoint codes and punch codes, you don't need a code list.

Creating a code list

You're setting up a new event and the course planner has provided a mapping between control codes and device codes:

  1. Open Code lists from the main menu.
  2. Click Add code list.
  3. Enter a Code list name to identify this list.
  4. For each mapping, fill in:
    • Checkpoint code — the code visible to participants (can be a number or text).
    • Punch codes — the internal device codes. If a checkpoint has multiple punch devices, enter the codes separated by commas (e.g. 32,33,34).
  5. Click Save code list when you are done.

Editing a code list

You need to correct a mapping or add new checkpoints. Open an existing code list from the Code lists page, make your changes to the name, checkpoint codes, or punch codes, and click Save code list.

Deleting a code list

A code list is no longer needed. Open the code list you want to remove and click Delete code list. You will be asked to confirm before the list is deleted.

Importing codes from a CSV file

The course planner has sent you a file with all the code mappings. Instead of entering codes manually, you can import them from a CSV file:

  1. Open a code list (or create a new one).
  2. Click Import codes from CSV file.
  3. Select your CSV file. The codes will be populated from the file.

The CSV format has no header row. Each row contains a checkpoint code followed by one or more punch codes. If a checkpoint has multiple punch devices, list all codes comma-separated on the same row.

31,131
32,132
33,133,134
34,135

In the example above, checkpoint 33 has two punch devices with codes 133 and 134.

An example CSV file is available for download on the code list page so you can see the expected format.

Multiple punch codes per checkpoint

A single checkpoint code can have multiple punch codes. This is common when a checkpoint has more than one punch device. Enter the punch codes separated by commas in the Punch codes field. For example, checkpoint code 31 might have punch codes 32,33,34.

Putting it together: preparing codes for a forest event

The course planner emails you a CSV file with control-to-device mappings. You open Code lists, create a new list named after the event, and import the CSV. All mappings appear instantly. Later, when you import the IOF XML course data, Navisport uses this code list to match control labels to the correct punch codes — results calculate correctly from the first card read.