Past the RACE|RESULT event ID or the URL of the Racemap access file. The API checks the access and provides feedback. Select the contests to sync specific participants. The initial import can take up to 1 min.
Multi-stage events with one participant file in RACE|RESULT: To prevent overwriting start and finish times in finished stages with data from the running stage, remove the synchronization for finished stages eg. delete the contest in the API.
Add Track Boxes in the tracking map to display the location of your hardware. That way you can coordinate your staff the race ground.
Import of participants with transponder ID, only: To import a participant to Racemap, Simple API must provide the parameters: ID, RaceNr, Transponder1, Firstname, Contest and Visibility. If one parameter is missing the participant won't be pulled to Racemap.
RACE|RESULT Knowledge Base - Simple API to pull data from RACE|RESULT: https://www.raceresult.com/en/support/kb.php?id=8165-Racemap
UTC format of “Start:” and “Finish:” ISO 8601 https://en.wikipedia.org/wiki/ISO_8601
Transponder fields with transponder number to enable data import into Racemap
Option 1: insert Chip-Codes to every participant: fill in “Transponder1” in field "Transponder1" (default)
Option 2: match participants with chipfile: fill in "TransponderInChipFile" in field "Transponder1"
Parameters displayed in participant list of tracking map:
RaceNr
Firstname
Lastname
(Club) - optional in brackets
color of markers
Simple API » Racemap Access » Custom field to import keys or color into your Racemap event: [Color]&";"&[TrackingKey]
Visibility of participants in tracking map, in case of "not Predictive Tracking": To show a participant in the map, Simple API must provide: ID, RaceNr, Transponder1, Firstname, Contest, Visibility and Tracking Key. Participants without a key are not displayed.
Assign keys to participants: Main Window » Participants Data » User Defined Fields
field "TrackingKey":
switch([Bib]>0 AND [Bib]<=500;[TrackingKey_1];[Bib]>500 AND [Bib]<=1000;[TrackingKey_2]; ... ;[Bib]>xxxx AND [Bib]<=xxxx;[TrackingKey_n]);"")
field "TrackingKey_1":
up to 500keys fit into one user defined field
for more participants set up a 2nd field "TrackingKey_2"
insert keys in this format choose([Bib];"xxxxxx";"xxxxxx";"xxxxxx")
Checkbox:
Main Window » Participants Data » Additional Fields
add checkbox field such as "Agree to live tracking"
field "TrackingKey":
iif[AYN1]=1;switch([Bib]>0 AND [Bib]<=500;[TrackingKey_1];[Bib]>500 AND [Bib]<=1000;[TrackingKey_2]; ... ;[Bib]>xxxx AND [Bib]<=xxxx;[TrackingKey_n]);"")
"iff[AYN1]=1"-function: whether participant checked Live Tracking ("AYN1" - "Additional Yes/No Field" 1 - "Agree to Live-Tracking") if yes: one Tracking Key is joint with participant
With the color parameter, you define specific colors for the markers in your tracking map.
color to be defined as color hex code
Main Window » Participant Data » User Defined Fields
"translate"-function: set the first color ("#F2F2F2") for female and the second color ("#000000") for male
translate([gender];"#F2F2F2";"#000000")
"switch"-function. In this example there are two contests ("Contest1" and "Contest2"). With "ContestName" in [brackets] you get the contest name. If ContestName of a participant is equal to "Contest1" the color is "#F2F2F2". If ContestName is equal to "Contest2" the color will be "#04B404".
switch([ContestName]="Contest1";"#F2F2F2";[ContestName]="Contest2";"#04B404")