Code Lists

Platform: 🖥️ Desktop only

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

Why Code Lists Are Used

A code list maps the visible code on a control flag (e.g., "31") to the device's internal technical code (e.g., "131"). The system uses this mapping to match punches to the correct controls 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 the XML file's control codes to the correct device codes.

Tip: If your event's control codes and device codes are the same, a code list is not needed.

Creating a Code List

  1. Open Code Lists from the main menu.
  2. Click Add code list.
  3. Enter a Code list name to identify the list.
  4. For each mapping, fill in:
    • Control code — The code visible to participants (can be a number or string).
    • Device codes — The device's internal codes. If a control has multiple devices, enter codes separated by commas (e.g., 32,33,34).
  5. Click Save code list when done.

Editing a Code List

Open an existing code list from the Code Lists page, make changes to the name, control codes, or device codes, and click Save code list.

Deleting a Code List

Open the code list you want to delete and click Delete code list. You'll be asked to confirm before deletion.

Importing Codes from a CSV File

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 Read codes from CSV file.
  3. Select your CSV file. The codes are populated from the file.

The CSV format has no header row. Each row contains a control code and one or more device codes:

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

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

You can download a sample file from the code list page.

Multiple Device Codes Per Control Code

A single control code can have multiple device codes — common when a control has multiple devices. Enter the device codes separated by commas in the Device codes field.

Putting It Together: Preparing Codes for a Forest Event

The course setter sends a CSV file with control-to-device mappings. You open Code Lists, create a new list with the event name, and import the CSV. All mappings appear immediately. Later, when you import IOF XML course data, Navisport uses this code list to map control codes to the correct device codes — results are calculated correctly from the very first chip read.