RACE RESULT 12 has some built in tools for integrating your timing systems and data with third party tracking visualisation partners.
Tracx
For a Tracx App integration of your event file, you will need to grant the platform access to your event file. To do so, create a race result 14 API Key from your customer account (Account access / API keys) wihtout an expiry date.
Share the API Key with your Tracx contact person to make sure you have access to your RACE RESULT 14 events from the Tracx dashboard. Make sure the name of the race within Tracx matches exactly the name of the event in RACE RESULT 14. Another option is to give the race a Race Identifier. Please consult TRACX for further details.
Lastly, inform TRACX whether there are already participants in the event file. Everything else will be done automatically from the TRACX dashboard.
Racemap
Racemap can pull participant data directly from RACE RESULT 14 via the SimpleAPI feature explained below.
The software also controls forwarding of the timing data from Track Boxes, Decoders and Loop boxes to Racemap for them to use for the tracking visualisation.
Participant Data
To enable synchronisation of participant data between RACE RESULT 14 and racemap your event file will need to be hosted online, you can still work offline on the day with online forwarding enabled.
Navigate to the Main Window - Access Rights / Simple API and select a Simple API Type "RaceMap Access". This will by default populate the required data for RaceMap integration, ensure to hit the Save button in the top left to enable the API.
By default the API will send the "Transponder1" and "Transponder2" fields, If you are using a Chip File you will need to edit this to "TransponderInChipFile".
A Start and Finish result are defined, these 2 times are used by RaceMap to accurately show when the participant has started and finished.
It is unlikely you will need to change any other fields, you should consult with RaceMap before changing data if you are unsure how it will affect the integration.
To pull this data in to RaceMap, under the Participants tab enter the Event ID under Import from RACE RESULT 14, this will show a green tick if the API is enabled, and finally select the contest(s) which should be displayed on this visualisation. Here you can also set additional customer IDs which should be considered for this event.
If everything is set correctly then the Starter List will be automatically populated within a few minutes depending on the size of the list. Note: Your API MUST have data for: ID, RaceNr, Transponder1, Firstname, Contest and Visibility fields in order for the Starter list to be populated.
The starter list can also be entered / updated manually or imported via an Excel spreadsheet, an example is attached below. You must follow this template, in particular for the IMEI, device type and class fields.
TrackPing Forwarding
Track Boxes
To enable forwarding of Track Pings from Track Boxes to RaceMap you need to setup Track Box Configuration Rules in the Timing Module within the Systems menu. Read more about the settings for Track Box Configuration HERE, ensure that the Tracking Partner is set to RaceMap.
Within RaceMap it is also necessary to set your Customer ID in the Profile Settings page.
You do not have to show your Track Boxes on the map but it can be useful for monitoring them during the race. You can import them to your Starter List from an excel file based on the template below or manually enter them, the format of the data is important to ensure these are recognised correctly.
If you edit the Starters list manually using a phone or Tablet then you can set the Startnumber for Track boxes to an Icon using an Emoji keyboard, this can help to differentiate them from normal athletes on the course.
Decoders
Timing Data from decoders can also be forwarded to RaceMap, this should be setup via the Tracking Data Forwarding in the Timing Module.
RTRT
RTRT can work with data from all RACE RESULT Systems, you must first ensure to have the devices you plan to use added to your account by RTRT otherwise data will not be available. There are different methods for sending data to RTRT for different devices, you may need multiple setup.
Decoders
RTRT make use of the Client Mode which is available on decoders, which is configured through the decoder browser interface, this applies for both passive and active applications. Client mode allows RTRT to pull data directly from the decoder when it is online, and also offers some remote control of the decoder through their platform.
When using Loop Boxes you must also enable the option to use Loop ID in your RTRT setup, then assign the relevant Loop IDs. At this time stored data may not be handled well if it comes from an unexpected timing system.
To setup client mode for use with RTRT please contact RTRT directly to get the correct URL and port number for their servers, they have a guide for using client mode of race result decoders with their platform.
Track Boxes
To enable forwarding of Track Pings from Track Boxes to RTRT you need to setup Track Box Configuration Rules in the Timing Module within the Systems menu. Read more about the settings for Track Box Configuration HERE, ensure that the Tracking Partner is set to RTRT.
RTRT will handle Track Box data as timing data and will use the first/last time according to the rules in your setup.
USB Timing Box
Note: RTRT currently ignores USB Timing Box Data. Please speak to them before using this functionality.
Data from USB Timing Boxes can be forwarded to RTRT in the same way as Track Box data but requires a different setup.
Open Exporters + Tracking from the Timing Module, in here you can set up exporter rules for Tracking partners.
You should setup an exporter rule for each timing point which should be sent to RTRT, or select All Timing Points. For each exporter setup the name, timing points, destination and your race result customer ID.
Once setup you will see the Exporters in your Systems list in the Timing Module, you will need to click the green play button to start sending data to RTRT. When data comes in from the relevant Timing Point it will be automatically forwarded to RTRT immediately.
When using Loop Boxes you must also enable the option to use Loop ID in your RTRT setup, then assign the relevant Loop IDs. At this time stored data may not be handled well if it comes from an unexpected timing system.