meshO Manager

Appearance

Exporting data ​

Audience: Event organisers sharing results and event data with federations, Eventor, other software, or the club.

What Manager can export, where each export lives, and what goes into the files.

What you can export, and where ​

Each export lives on the screen it belongs to:

WhatWhereFormats
ResultsResults → PublishIOF XML, JSON, PDF, print, upload to Eventor, a sheet on the splits printer
Start listStarts → Start list tab → ActionsIOF XML, JSON, CSV, PDF, print, upload to Eventor
Entry listCompetitors → Actions → Export entry listIOF XML, JSON, CSV
Start blocksCompetitors → Actions, or the class's Assign blocks dialogCSV, JSON
Bib numbersThe Actions menu of Allocate bib numbersCSV (one row per event, or one per person), JSON
Changes reportCompetitors → Actions → Changes report → ActionsPDF, CSV, JSON
Carnival standingsThe multi-stage event's Standings tab → ActionsCSV, PDF
Knock-out classificationThe knock-out competition's Classification tabCSV
A GPS trackTracking, beside each athlete unitGPX
Results, every few minutes, for another systemEvent details → Backup & export → Live exportIOF XML — one file overwritten each time, or a new file for each export
Live results onlineEvent details → Live results (liveresultat), and cloud syncSent straight there — see Publishing live results online
The whole eventThe event's card on the Events list → Backup eventA backup zip

IOF XML is the orienteering standard (version 3.0), read by Eventor, federation systems, WinSplits, SplitsBrowser, Livelox and other timing software. JSON is Orienteering JSON (OJSON), which carries everything the XML does and more. CSV opens in a spreadsheet.

There is no CSV of results. Results go out as IOF XML or JSON for other software, and as a PDF or print for people. The exceptions are a carnival's overall standings and a knock-out's classification, which both export as CSV (see Exporting a multi-stage event).

Every export is of the event as it stands at that moment. Exporting changes nothing in the event, and isn't recorded in its audit trail. The one exception is an upload to Eventor, which can save the event's Eventor link (below).

Results files ​

Publish → Export IOF XML…, Export JSON… and Upload to Eventor… on the Results screen produce the results file other systems keep. Before any of them, Manager checks that everyone in the classes you chose has a settled result. A file has to say what became of everybody who took part. See Settling everyone first, and What an exported results file contains for how each status is written.

The Publish options dialog then asks:

  • Classes — which classes go in. Everything is ticked to begin with.
  • Include DNS competitors — whether competitors marked DNS are in the file.
  • Countries — for the files only, when there's more than one (below).
  • Relay or individual — at an event with both, because a results file never mixes the two (see Relay events).
  • IOF XML options — for the IOF XML only: combined classes, and leaving out organisation ids (below).

Export PDF… and Print view… make a document for people rather than software, laid out like the Results screen. See Publishing the final results.

Splits ​

Both results files carry each competitor's split times: one per control, in course order, so split-analysis tools such as WinSplits, SplitsBrowser and Livelox can draw the race. The IOF XML gives them in whole seconds, as those tools expect; the JSON gives them to the millisecond, and says whether each came from the card or a radio control. Nothing has to be switched on.

Exporting one country's results ​

Publish → Export IOF XML and Publish → Export JSON open a dialog that, alongside the classes, asks which Countries to include. Everything starts selected, so the file carries every country unless you untick some — handy when a national federation wants only its own runners.

  • A competitor's country is their club's. A relay team goes by the team's own club, so a team is always exported whole.
  • No country covers competitors whose club has no country recorded (or has a dash, -, where the code would be), and competitors with no club at all.
  • Places are not renumbered. A runner who came fourth in the class is fourth in the file, whoever else was left out.
  • The list only appears when there is more than one choice — a single country plus No country counts. The PDF, Print and Upload to Eventor actions don't offer it: Eventor must get every runner in each class you upload, or it reads the rest as never having entered.

Each country shows with the code its clubs were given. If some clubs were given the IOC code (SUI) and others the ISO code (CHE), both appear — tick both.

Combining classes for the World Ranking (IOF XML) ​

The IOF asks a World Ranking event for a results file in which every class that ran a course is merged into one list and ordered — the ranking points are worked out over everyone on the course, not class by class. At a Middle where M21E and M20E run one course, and W21E and W20E another, that is two merged lists; at a sprint where M18A runs with them, three classes in each.

Publish → Export IOF XML has an IOF XML options line for this: click Change beside it. In the dialog that opens, either click Combine by course — each set of the classes in the export that ran the same course becomes one combined class — or click Add combined class and pick its classes yourself. Click Done, check the line in Publish options now lists your combined classes, and export as usual. Nothing is remembered: the next export starts again with nothing combined.

  • Each combined class is published once, with everyone in it ordered by time. Places and time behind are worked out across the combined list, so an M20E runner who beat half of M21E is placed among them.
  • Each combined class has a Class name, Class id and Course name. Left blank, the file uses its own: the class is named after its classes (M21E + M20E) with their ids joined (1+2), and the course after the class. Fill them in when the World Ranking event was set up with names of its own — Men, ME and so on. Two classes in one file can't have the same id; the dialog says so beside the field.
  • Nothing in the event changes. The classes stay separate everywhere else — on screen, in the JSON export, in the PDF and on Eventor. Export the ordinary file as well if anyone needs the classes apart.
  • Combine by course counts classes as running the same course when they were given the same courses on the Classes page; a class alone on its course is left as it is. Only individual classes can be combined — never relay classes — and a class can be in one combined class only.
  • Classes you leave ticked but that aren't combined are exported as normal alongside — untick them from Classes if the IOF wants the World Ranking classes only. Untick a class you combined and it simply drops out of its combined class.

Leaving out organisation ids ​

The same dialog has Leave out organisation ids. Each competitor's club is still named in the file, with its country; only the club's Eventor organisation number is left out (a club that isn't an Eventor organisation never has one in the file — see Club registry). That number means nothing to a system that numbers clubs its own way, such as the IOF World Ranking, which may otherwise try to match on it. A relay team's club keeps its id.

Uploading to Eventor ​

Results → Publish → Upload to Eventor… and Actions → Upload to Eventor on the start list send the results or the start list straight to Eventor, without saving a file. Both need Eventor set up in Settings → Eventor, with your organisation's API key.

  1. Choose the classes in Publish options, as for a file.
  2. Choose the Eventor event. An event created from Eventor, or one you've uploaded to before, already has it chosen. Otherwise, pick it from your organisation's events, and Manager remembers the choice as the event's Eventor link.
  3. Click Upload.

Things to know:

  • Eventor needs every runner in each class you send. That's why there's no Countries choice for an upload: a class with runners left out reads on Eventor as though they never entered.
  • Nothing is uploaded if Eventor is missing a class. If the Eventor event has no class for one you're sending, the upload stops and names the classes. Leave those out in Publish options, or add them to the event in Eventor, and upload again.
  • Corrections need another upload. Changing a result in Manager doesn't change what Eventor already has. Upload again once it's fixed.

Start lists ​

The start list goes out from Actions on the Start list tab of Starts: IOF XML, JSON, a CSV that Manager's own CSV entry import reads back, a PDF, a print view, and an upload to Eventor. All three files can be imported back into Manager. See The Start list tab and Uploading the start list to Eventor.

Exporting the entry list ​

Who has entered — as opposed to when they start or how they got on — is exported from the Competitors page: Actions → Export entry list, in IOF XML, OJSON or CSV. It's written up where the menu lives: see Exporting the entry list.

Two things worth knowing before you reach for it:

  • The export is always the whole event, never the filtered list you're looking at.
  • The CSV is designed to be edited and re-imported — though not every column comes back. The round-trip table says which do.

Exporting a multi-stage event ​

Both standings exports live on the Actions menu of the carnival's Standings tab, alongside Recompute.

Overall standings as CSV — Export CSV. One row per competitor, one column per stage, plus the total: the shape a prize-giving spreadsheet wants. A stage that didn't count is bracketed rather than blanked, and a provisional total keeps its *, so the file says what the screen said. Export one class or all of them.

Overall standings as PDF — Export PDF. The table laid out for printing or pinning up, matching whatever you have on screen: the class or combined view you have selected, and your Show and Times settings.

IOF XML per stage — export a stage's results as IOF XML the usual way. Because the event is a stage, the file also carries the stage's raceNumber and each competitor's overall standing after that stage as an IOF OverallResult. Every stage up to it has to be settled first — a runner left with no status on an earlier day holds the file up, and the export tells you who (see What an exported results file contains). That is the IOF standard's own answer to multi-stage results, so SplitsBrowser, Eventor and Livelox read it with no bespoke format. A standalone event's export is unchanged.

See Multi-stage events.

A knock-out competition's classification — Export CSV at the top of its Classification tab: one row per competitor with their overall place, and the place they took in each round. There is no total time, because a knock-out has none. Each round's own results export normally, as any event's do. See Knock-out competitions.

How a competitor is identified in an exported file ​

Every results, start-list and entry-list export — IOF XML, OJSON and Upload to Eventor alike — names each competitor by the identifiers they hold: their Eventor ID (your own competitor number) and their IOF ID. In IOF XML the competitor number comes first and the IOF ID follows it marked as the IOF's, so a system that reads only the first one still finds the number it always did. A competitor holding neither is exported by name alone. The CSV entry and start lists carry both as the Database Id and IOF Id columns, and all of them read both back when imported into Manager.

To fill in IOF IDs for a field that arrived without them, see Importing IOF IDs.

Exporting as OJSON ​

Everything Manager exports as IOF XML it also exports as OJSON — a published format with a JSON Schema, carrying the things the XML has no room for: split-time columns as data, a relay team's own result, whether a split came from a card or a radio, and millisecond precision. If you are writing something that reads a Manager event — a club results page, a spreadsheet pipeline, an app — that is the format to read.

See OJSON for the endpoints, the field reference and the schema.

GPS tracks ​

At an event with meshO athlete units, Tracking has a Download GPX track button beside each unit. It saves the route that unit recorded as a GPX file, which mapping and route-analysis software opens. See Tracking.

Keeping the event afterwards ​

An export is a copy for somebody else. To keep the event itself, take a backup: one zip holding everything, from the punches to the audit trail, that restores into Manager exactly as it was. Take one when the results are final and keep it somewhere other than the laptop. See Backup and restore.

Every card read is also kept on disk as its own file, whether or not you back up. See Card downloads are always kept twice.

If cloud sync is on, finishing the event also publishes it to the meshO cloud, where spectators can browse the results online (see Publishing to the meshO cloud).