Other timing system
Predictive live tracking with reads from any timing system.
There are two possibilities RACEMAP receives data from a timekeeping software.
Recommended: Reads (detections) include the reader's location.
Reads without the location. In that case, the readers' locations must be set in RACEMAP.
Request
URL https://racemap.com/services/trackping/api/v1/timing_input/pings
Method POST
Timing API token: We have to create your timing API token to let you send data to the endpoint. Contact info@racemap.com.
Reads object
timingId
Unique ID of the reader
"XF32098"
or "_8nx7uoyun"
timingName
*
Name of reader in timing software
"5K-split"
or "Start II"
chipId
Transponder ID
"RRPing_ZDKAR32"
or "RRPing_70761"
or "HH32098"
timestamp
"2023-11-09T16:35:05.248Z"
lat
Latitude of the reader
51.5074
lng
Longitude of the reader
13.7276
(*) Optional parameter without impact on processing the reads in RACEMAP.
timingId
without impact on processing the data in Racemap.
Response
If everything is correct the HTTP code 200 is returned.
Set readers' locations
Case 2, if reads are sent without coordinates: Virtually define the locations of your readers in the map settings of your tracking map.
Upload the race track.
Set this track as the shadowtrack of the race.
Create a split representing the location of your reader at the race.
Check "Timekeeping"
Provide the unique
timingId
in the field "IDs of Timing Systems" of the split. You can add multipletimingId
to a split, if you use multiple readers at the same location.
Note: If a single reader is used for multiple detections (e.g., timing a lap race at 5K and 10K), enter its location only once. There's no need to add the reader multiple times.
Last updated