Racemap Settings & Pricing

Racemap settings and pricing for predictive live tracking with data from timekeeping.

1st step: Create one tracking map for each contest of your event.

Every section / step to create a tracking map provides an extra paragraph with settings and hints for predictive tracking.

How does Prediction work?

Hardware

decoder reads considered for prediction only, when

  • time setting in race|result 11 is as UTC format

  • tracking map and race|result 11 settings with corresponding date

  • set start time in race|result 11 within time frame (> start time, < end time) of corresponding tracking map in Racemap

  • consideration of Loop Box reads

  • The pings our system receives from race|result 11 contain the location of the hardware. There is no need to define the location of Track Boxes, Decoders and Loop Boxes in racemap.

  • The hardware location is automatically projected to the appropriate location on the shadowtrack.

  • One Track Box can assign several locations on the same shadowtrack eg. in loops. That means this box produces more data for the prediction.

Rules for Visualisation

  • Participants appear in live visualisation with 2nd ping. Eg. when algorithm receives the start detections with no delay, the markers show up at the 1st Track Box which is placed 0.5 - 1 km from the start.

  • In replay participants show up directly from the start location.

  • auto recalculation of the replay when event is finished

Algorithm & Prediction

  • Track boxes within 30 m distance to the shadowtrack are projected on the track. If your box is located 35 m from the track the algorithm will ignore the pings from this box.

  • One track box can detect pings for several contests (shadowtracks) at the same time. The algorithm assigns the pings to the correct shadowtrack, as algorithm knows from data import which transponder belongs to which contest.

  • Extrapolation of average speed until algorithm receives ping from next box position

  • Fitting of extrapolated speed depending on gap between virtual (dot in map) and real participant

  • As track boxes does not detect every transponder, virtual marker in the map goes on moving over the location of following boxes.

  • Pings from moving boxes (eg. on car of race director or on a boat) are taken into account of real-time prediction.

  • You have to set speed values of sections / splits in the shadowtrack tab. That values are taken into account to improve the prediction e.g. for triathlons.

  • Maximum filter: pings with a two times faster average speed than your set speed value of the section are ignored.

  • Minimum filter: pings with a 0.1 slower average speed than your set speed value of the section are ignored.

Automated System Checks

Features that support you to check the settings of hardware (Track Boxes, Decoders, Loop Boxes), of r|r 11 and of Racemap some days before the event.

  • Show Hardware Feature: monitor incomming pings and location of hardware

  • System Test: sending emulated Pings to r|r 11 and when your forwarding settings in r|r 11 are correct, r|r forwards ping back to Racemap

Pricing for Predictive Tracking

We do not charge tests and training of predictive tracking.

  • Test: We are open supporting tests, when we need the data to improve our prediction algorithm or when we are uncertain if the prediction will be good. Just get in touch and we decide if your event is a test for us.

  • Training: We also support you in training the predictive tracking. Just set-up your training maps for Monday, Tuesday and Wednesday (working days). We will delete training maps after a couple of days. Predictive maps with the purpose of "training" which run on other days will be charged according to our pricing.

Mandatory: Prediction & Pageviews

The pricing for predictive tracking is fair and considers the number of participants and the spectators in two separate parameters. Our fair pricing allows cheap live tracking for small events.

  • Number Transponders in one tracking map our algorithm calculates the location for and

  • Daily Pageviews of all tracking maps (contests) for an event (bandwidth). Pageviews are monitored and tracked with Google Analytics.

Prediction

Number of Transponders

Price each Race Day

base rate - including 100 transponders

25 EUR

specific price - 101 to 250 transponders

+ 0,25 EUR/transponder

specific price - 251 to 10.000 transponders

+ 0,12 EUR/transponder

specific price - from 10.001st transponder

+ 0,10 EUR/transponder

example:

  • price of a contest with 85 participants is 25,00 EUR

  • price of a contest with 10.009 participants: 1.233,40 EUR =

    250 * 0,25 EUR + (10.000 - 250) * 0,12 EUR + (10.009 - 10.000) * 0,10 EUR

Daily Pageviews

Bandwidth: Daily Pageviews of all Tracking Maps for an Event

Price each Race Day

Basic: up to 5.000 pageviews

0 EUR

Standard: up to 25.000 pageviews

250 EUR

Pro: unlimited pageviews

500 EUR

example: event with two contests lasting three days

Day

Pageviews

Contest 1

Pageviews

Contest 2

Sum Daily Pageviews

Resulting

Bandwidth

1st

1.800

2.553

4.353

Basic: 0 EUR

2nd

2.335

4.905

7.240

Standard: 250 EUR

3rd

4.780

10.220

15.000

Standard: 250 EUR

Price for bandwidth for the total event is 500 EUR = 0 EUR + 250 EUR + 250 EUR.

Options: Sponsor Logo & Export API

example: contest with 10.009 participants

  • price for prediction: 1.233,40 EUR

  • additional price for sponsor logo: 616,70 EUR = 0,5 * 1.233,40 EUR

Export API