Racemap Racemap updates logo

Racemap updates

Stay tuned to Racemap live tracking platform: new features, enhancements, and resolved issues

Subscribe to Updates

Labels

  • All Posts
  • enhancement
  • bug fix
  • apps
  • visualization
  • monitor
  • leaderboard
  • API
  • prediction
  • keys
  • GPS tracker
  • Participants Data
  • Tracker Management

Jump to Month

  • January 2023
  • November 2022
  • October 2022
  • September 2022
  • August 2022
  • July 2022
  • June 2022
  • May 2022
  • April 2022
  • March 2022
  • February 2022
  • January 2022
  • December 2021
  • November 2021
  • October 2021
  • September 2021
  • August 2021
  • July 2021
  • June 2021
  • May 2021
  • April 2021
  • March 2021
  • February 2021
  • January 2021
  • December 2020
  • November 2020
  • October 2020
  • September 2020
Powered️ byAnnounceKit

Create yours, for free!

API
a week ago

Spotter app released

Since last season we provide small HTML apps that make live data from endurance races easily usable for video productions such as TV overlays. The spotter is our latest release. For example, this tool feeds the speaker with real-time information from anywhere on the race course. 

Easy usage for everybody: No coding skills needed, working in any browser tab:
  • Just define up to three different spots (distance from the start location in m). 
  • The table sorts participants within the sensitive range (rangeBeforeSpot and rangeAfterSpot) coming closer to the spot. 

Do you have specific requirements for the spotter app? Just drop a comment.

All information about our handy tools to easily extract live data from our */current-API can be found in our documentation: https://docs.racemap.com/data-api/grabber

enhancementAPI
2 months ago

Improved basic grabber and drafting tool

For a couple of months now, we are providing the grabber to pull real-time data from endurance races and make the data usable for live productions such as video broadcasting. Time for an update. 

We now added the new parameters gap, gapAverage, gapChase and gapDistance to the grabber. Additionally, there can be set a refDeviceId or a refStartNumber to flexibly define the reference device for the gap calculations. 

Furthermore, the drafting- and related penalty discussion at triathlons let us develop a prototype of a drafting tool. The tool evaluates the distance between participants and monitors if participants move in the draft zone.

All information about our handy tools to easily extract live data from our */current-API can be found in our documentation article: https://docs.racemap.com/data-api/grabber  

API
2 months ago

Current API updated

The current API processes real-time geolocation data for TV graphics & overlays, speed monitoring, gap time calculation, and any other 3rd party application that needs live data from sports events. We now added three parameters to the API: 

  • speedRaw: Average speed in [m/s] is calculated with the interpolated raw coordinates. 
  • gapChase: Duration in [s] to reach the current location of the leader respectively of the reference device. Prediction with the speed of the chaser. 
  • gapDistance: Distance in [m] to reach the current location of the leader respectively of the reference device.  

With this update, the startNumber is a query parameter and the leader is the reference for the calculation of gapAverage, gap, gapChase, and gapDistance by default.

Read all about our current API and find live samples to test with your applications in our documentation: https://docs.racemap.com/data-api/current

enhancementvisualizationmonitorleaderboardAPI
2 months ago

Parameters added to adjust the mapping

We've added parameters to flexibly adjust the mapping algorithm to the specific needs of your event: 

  • Max. mapping distance
  • Max. and Min speed for speedfilter

This will allow for more accurate mapping, and we are sure it will be a helpful addition for your event. Access the mapping parameters in the "Danger Zone" of the advanced settings of your event.

The mapping impacts all functions and features in Racemap that calculate the relation of the devices' locations to the shadowtrack. Which are visualization, leaderboard, monitor, */ranks & */current API.

How does the mapping work? GPS devices send their geo data to a specific tracking map. The mapping calculates the device's location on the shadowtrack. The algorithm takes into account the device's current coordinates and its previous location on the track. Mapping considers laps and assumes that a device moves onwards (and not backward) on the track.

enhancementAPI
3 months ago

Tool to show live data in the browser

Since we are providing live geodata through APIs two years ago, we have been asked for a handy tool to extract specific values such as speed, distance to go, gap or away from track etc. 

In most cases, a TV production has no time to develop or adapt their solution feeding the overlay with live data from our API. Now you can use our handy and flexible grabber tool to directly display specific live data in a browser tab. We are looking forward to learning more about your use cases and how you are going to apply this solution.

Read more about this solution in our documentation: https://docs.racemap.com/data-api/grabber

enhancementAPIParticipants Data
3 months ago

Participants import reworked

We reworked the participants section in the settings of each tracking map. Now, it is much clearer how to import respectively synchronize Participants Data with CSV files or from hosted (recommended) sources such as RACE RESULT or your own server.  

  • To better control the import you can switch on & -off the synchronization from a hosted source. 
  • The synchronization stops calling the hosted source three days after the end time of the tracking map, automatically. 
  • You can synchronize participant data from different sources with the same tracking map. 
  • You can automatically call the participant data in your tracking map from the given API endpoint, also. 
  • You can import participants from RACE RESULT without a transponder code. We removed the requirement for transponder1 field.

Read more about the import of participants' data in our documentation https://docs.racemap.com/api-import-and-export-data

API
a year ago

New gap duration for reference device

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

API
a year ago

*/distance data feed

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
API
a year ago

Settings to call */current data feed

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

API
a year ago

*/times API with distance to split

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