RACE RESULT import
Synchronize participants data through Simple API.
Last updated
Synchronize participants data through Simple API.
Last updated
Go to participants settings in your Racemap event and open the import/export tab. Past the RACE RESULT event id or the URL of the access file. Racemap checks the access and provides feedback. Select the contests for synchronization with Racemap.
Multi-stage events with one participant file in RACE RESULT: To prevent overwriting start- and finish reads in finished stages with data from the running stage, deactivate the synchronization in finished stages.
In order to let Racemap query participant data go to Main Window, Simple API, and select Racemap access.
Simple API must provide the parameters:
ID
in Id field
Contest
If Id
or Contest
parameter are missing the participant won't be pulled to Racemap.
ID
must be unique within each contest.
ID
is the identifier to address participant information in RACEMAP when synchronizing with RACE RESULT.
A new ID
creates a new entry in RACEMAP.
If one ID
is removed then the corresponding entry is deleted in RACEMAP.
Timestamps in Start- and Finish field in UTC format: ISO 8601 https://en.wikipedia.org/wiki/ISO_8601
The fields Age, Sex, Club, Nationality, and Status are imported as tags into RACEMAP participant list.
Parameters of the simple API displayed in tracking map: RaceNr
, Firstname
, Lastname
, Status
, Age
, Sex
, Club
and Nationality
.
Adapt the Transponder1 field for the transponder id of passive- (Bib
) or active timing (Transponder1
) or use the TransponderInChipFile
argument.
When conducting predictive tracking, you can hide participants from visualization depending on their status. The if function in the Transponder1 field removes the transponder id of participants with DNS, DSQ, or DNF status.
Prediction: Passings from timekeeping for live extrapolation of participants' location and speed.
Use the custom field in the simple API to flexibly import
[Color] to specify markers in the visualization with different colors,
[Key] to enable live tracking with Racemap App,
[IMEI] ids of GPS trackers,
[APPID] and
[TAGS] additional tags to filter participants in the visualization and in the leaderboard.
Go to Main Window, Participants Data, User Defined Fields to define the arguments in the custom field.
The color parameter sets various colors of the markers in the tracking map and needs to be defined as color hex code.
Color depending on contests: Switch function in user defined fields. If Contest.Name of a participant is "Gravel" then color is "#F2F2F2". If Contest.Name is "MTB"color is "#04B404".
Color depending on gender: Translate function in user defined fields: Set the first color ("#F2F2F2") for female and the second color ("#000000") for male.
Online registration with live tracking through Racemap App for every participant. Keys enable Racemap App for live tracking of a specific event.
Assign keys to participants.
The switch function in the Key field assigns one key to every participant.
Choose function in Key_1 field:
Paste keys from Racemap of the corresponding Racemap event.
choose([Bib];"xxxxxx";"yyyyyy";"zzzzzz";...)
Up to 500 keys fit in one user defined field.
For more than 500 participants in the contest set up a second field Key_2 and so on.
choose([Bib]-500;"XXXXXX";"YYYYYY";"ZZZZZZ";...)
Online registration with optional live tracking through Racemap App e.g. when the event wants to sell live tracking. Go to Main Window, Participants Data, Additional Fields, and add a checkbox "App".
If function in Key field: If the participant checks "Agree to live tracking with Racemap App" one key is assigned to this participant.
You own GPS trackers or you have rented trackers for an event. You can assign the devices to participants in RACE RESULT, directly. That way the participants data and the tracker information are synchronized with your event in RACEMAP.
A) Automatically assign GPS trackers to participants according to their bib numbers
Prepare your GPS trackers with labels of the bib numbers beforehand.
Go to Main Window, Participants Data, User Defined Fields, and add the field IMEI
. Paste the bib number that is labled on the tracker and the corresponding IMEI number of the device.
The code sample inserts five GPS devices with bib numbers into RACE RESULT.
B) Use the friendly name to manually add a specific GPS tracker to a participant
RACEMAP devices come labeled with a friendly name of six letters. You might use your GPS trackers with your own label system.
Go to Main Window, Participants Data, User Defined Fields, and add the field IMEI
. Paste the friendly name of the tracker and the corresponding IMEI number.
The code sample inserts five GPS devices with its friendly names into RACE RESULT.
Go to Main Window, Participants Data, Additional Fields, and add the field Tracker
.
Go to participants and paste the friendly name to address a specifc tracker to the participant. The IMEI of this device will be synchronized through the simple API with the RACEMAP event.
C) Online registration with optional live tracking with RACEMAP App or with GPS tracker.
Go to Main Window, Participants Data, Additional Fields, and add the checkbox App
and add a second checkbox Tracker
.
Key
and Key_1
fields are similar to the sample above.
If
function in IMEI
field: If the participant checks "Live Tracking GPS Tracker" one IMEI is assigned to this participant.
Choose
function in IMEI_1
field, past the IMEI numbers from the GPS devices.
For live tracking with RACEMAP App of an event with stages it can be useful to assign the App-Id to the participant information in RACE RESULT. Before the 1st stage, the participants redeem their keys in RACEMAP App. The specific App-Id of one participant becomes known and can be queried with the starters API. This way you can import the participant information including the App-Id for the subsequent stages.
A participant in RACEMAP, which already has an App-Id, can't get another device id (like a different App-Id, IMEI, or Transponder-Id). It is not possible to delete, refresh, or overwrite an App-Id of a participant through the RACE RESULT import.
To address a different device id you have to import the same participant information with a new import id, which creates a new participant on RACEMAP side.
Synchronize additional information about categories such as sponsor, mixed team, ... in order to filter participants in the visualization and in the leaderboard. Go to Main Window, Participants Data, Additional Fields, and add the test fields "Team" and "Sponsor".
Argument in TAGS field of the user defined fields in order to insert the two tags team and sponsor of the participant.
Participants reach the checkpoint before the cut-off time and continue on the white course.
RACE RESULT settings with three contests - grey, white and black:
User defined field for sorting participants during the event from grey contest to white or to black depending on detections at the checkpoint.
Racemap settings:
create a tracking map with the white course (shadowtrack) and synchronize participants from grey and white contests
create another map with the black course and synchronize participants from grey and black contests
create a group and add the white map
Description of the process:
From the start, all participants are calculated on the white- and on the black shadowtrack. That means each participant is shown twice - in the white and the black map.
At the cut-off time the participants in the white (black) contest are synchronized with the white (black) map. That means each participant is visible in either the white or the black map.
Now, add the black map to the group map. That way spectators continue streaming the same group with the new sorting of participants.
To select a contest in the RACE RESULT import at least one participant needs to be assigned to this contest. That means at the beginning you need to add one participant in the white and the black contest. This one participant does not need to have a transponder Id.
cut-off | grey | white | black |
---|---|---|---|
until cut-off time
all participants
no participant
no participant
from cut-off time
no participant
participants with detection at checkpoint
participants without detection at checkpoint