Other timing system

Predictive live tracking with any timing system.

There are two possibilities RACEMAP receives data from a timekeeping software.

1. Recommended: The reads (detections) include the reader's location.

2. The reads don't include locations. In that case, the readers' locations must be set in RACEMAP map settings.

Reads object

Field	Description	Sample
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	Timestamp in UTC when the reader detects the transponder	"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.

1. Reads with locations

timingId without impact on processing the data in Racemap.

POST https://racemap.com/services/trackping/api/v1/timing_input/pings
Content-Type: application/json
api-token: 6J7PDXOO
[
  {
    "timingId": "XF32098",
    "timingName": "Start",
    "chipId": "HH32097",
    "timestamp": "2023-11-09T16:31:07.248Z",
    "lat": 51.5074,
    "lng": 13.7386
  },
  {
    "timingId": "XF32099",
    "timingName": "Start II",
    "chipId": "HH32098",
    "timestamp": "2023-11-09T16:31:05.248Z",
    "lat": 51.5074,
    "lng": 13.7386
  },
  {
    "timingId": "XF32100",
    "chipId": "HH32099",
    "timestamp": "2023-11-09T16:32:04.248Z",
    "lat": 51.5074,
    "lng": 13.7386
  },
  {
    "timingId": "XF34568",
    "chipId": "HH32099",
    "timestamp": "2023-11-09T16:35:03.248Z",
    "lat": 51.5074,
    "lng": 13.7386
  },
  {
    "timingId": "XF36549",
    "timingName": "Finish",
    "chipId": "HH32099",
    "timestamp": "2023-11-09T16:38:02.248Z",
    "lat": 51.5074,
    "lng": 13.7386
  }
]

2. Reads without locations

timingId is addressed to a specific location that has to be set up in RACEMAP map settings.

POST https://racemap.com/services/trackping/api/v1/timing_input/pings
Content-Type: application/json
api-token: 6J7PDXOO
[
  {
    "timingId": "XF32098",
    "timingName": "Start",
    "chipId": "TPTest_HH32097",
    "timestamp": "2023-11-09T16:31:07.248Z"
  },
  {
    "timingId": "XF32099",
    "timingName": "Start II",
    "chipId": "TPTest_HH32098",
    "timestamp": "2023-11-09T16:31:01.248Z"
  },
  {
    "timingId": "XF32100",
    "chipId": "TPTest_HH32099",
    "timestamp": "2023-11-09T16:35:04.248Z"
  },
  {
    "timingId": "XF33718",
    "chipId": "TPTest_HH32099",
    "timestamp": "2023-11-09T16:36:03.248Z"
  },
  {
    "timingId": "XF34329",
    "timingName": "Finish",
    "chipId": "TPTest_HH32099",
    "timestamp": "2023-11-09T16:39:02.248Z"
  }
]

Response

If everything is correct the HTTP code 200 is returned.

Timing API token: We have to create your specific timing API token in your Racemap account. Please contact [e-mail].

Set readers' locations (case 2) if reads don't include coordinates: In map settings of your tracking map.

• 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 multiple timingId to a split. In case you use multiple readers at the same location.

Split "CP-1" with the unique split id U078