Customers using our */current API to feed TV graphics with real-time location data asked for gap values in relation to a specific reference device. Advantage: The reference device can be selected and flexibly changed during a running event. 

So we developed the new gapAverage parameter. gapAverage provides the duration in seconds to reach the current location of the reference device. The prediction is calculated with the average speed of the reference device on the leg between its current location to another device.

• The gapAverage value can be calculated only for devices behind the reference device.
• gapAverage fluctuates less than gap calculated with small values of currentSpeedDuration query.

Read all about the */current data feed and find many samples to test your APIs in our documentation: https://docs.racemap.com/data-api/current#optional-query-parameters

You can now work with our new API and feed your own application with live data from sports events. The */distance data feed provides real-time geolocations and the two new parameters distance & bearing between one defined reference device and all the other devices in the event.

For maximum stability and minimum delay data in this API is calculated independent of a shadowtrack, there is no pendency on mapping.  

• Test our sample API of a running event: https://racemap.com/api/data/v1/61a21210e5d45d000199f7d9/distance?deviceId=61a2122f181c0a0ff7b53765 
• Read all about our new */distance data feed in our documentation: https://docs.racemap.com/data-api/distance

We've added the ability to trim the */current data feed with each call, directly. Therefore we added three parameters

• liveDelay: The duration in seconds from when a location is recorded until this location is provided in the API.
• currentSpeedDuration: The previous duration in seconds to average the speed value.
• interpolation: true or false

Using these parameters you can call */current API with different settings for the same event. Like one call with no interpolation and a minimum live Delay to access the latest data. And another call of the same data feed with interpolation and smoothly changing values.

Find all information about the options to call the */current data feed in our documentation: https://docs.racemap.com/data-api/current#optional-query-parameters

We refactored our API for passings at virtual checkpoints. Now the data feed provides the distance between the locations of detection and of timekeeping point for each read. Especially timekeepers flexibly use the */times API to enrich their results data.

distanceToSplit

All information about our */times API in the documentation: https://docs.racemap.com/data-api/times

We added the option to open the */participants API in the participants section of each event. 

Using this API you can call specific parameters and integrate live tracking into your services seamlessly. That way you can identify those participants who have not yet redeemed their tracking keys and send them an email reminder with your mailing solution and provide a convenient race experience.

Read all information about */participants API in our documentation: https://docs.racemap.com/data-api/participants

Due to the usage of our data feeds for various 3rd party applications such as TV graphics or live dashboards we were asked to add parameters in the */current API. Two new parameters:

• eta - Estimated time of arrival is the duration to reach the finish. The prediction is based on the measured speed.
• gap - Is the duration to reach the current location of the leader. The prediction is based on the measured speed. 

Our documentation provides all information and samples about our data feed:  https://docs.racemap.com/data-api/current

You can now adjust the size of geofences for virtual detections. Just provide the needed value in meters in the data feed settings of your event.

More about our API for reads and detections: https://docs.racemap.com/data-api/times

Our data feeds are used for 3rd party applications such as timing software. We improved the data feed for specific timekeeping points and added two parameters

• name of timekeeping in Racemap and 
• distance in m of the detection from geolocation of timekeeping point

All information about */times/id data feed in our documentation https://docs.racemap.com/data-api/times#reads-at-specific-virtual-timekeeping-point