Leaderboard
Easy timing solution with live rank & real-time scoring. Results from virtual splits & participants' location data, no timing hardware needed. For virtual races, permanent timing, & regular events
Interactive leaderboard from real-time geolocations
Check interactive leaderboard: results of Damloop Home Edition with 2,000+ participants: racemap.com/timing/dam-tot-damloop-home-edition-10em_2020
*/ranks API
*/times API
to pull the data from a specific leaderboard
all detections from geofences (raw data) to process in your timekeeping system
Overview
Useful information and data in the leaderboard:
- (live) rank,
- DNF, DNS, DSQ,
- race number,
- name and
- finish- and split results.
Customize your leaderboard and select elements:
- progress with current distance,
- link to tracking map with the selected participant,
- live status showing if a participant is currently active,
- team challenge with overall target distance for all contributed distances in your leaderboard, sample https://racemap.com/timing/virtual-race
Settings in the leaderboard
- Start times: timestamp from start location,
- Delta times: duration to previous split and
- Upload activity: for participants to import recorded activities.
Test event for a virtual race: "Easy QR Code Run" with passcode 6G615L
Flexible application
Activities from anytime and from everywhere
Processing results from virtual splits or geofences and geolocations of each participant. Leaderboard compares any activities, flexibly.
anytime
everywhere
net results: difference from start timestamp, independent from if participants start
- anytime, like a virtual race or a permanent timing OR
- at nearly the same time, like a regular event
- without race track like a virtual race, participants provide activities from everywhere OR
- participants move on given course from start- to finish location, like a regular event
Features and advantages
- effortless results: with virtual splits or with checkpoints and with geolocations of participants, no timing hardware, no rfid tags
- flexible results: adjust settings (add a new split, move start location, etc.) of a running event or even of a past event, refresh results with new parameters within seconds
- effortless proof of activity: athletes contribute activities using any device
- scales to the largest events with 2,000+ participants
- specific URL for each leaderboard
Processing geolocation data in leaderboard
- net results: difference from start timestamp
- live rank: 10sec auto-update
- results of 1sec accuracy
feature
without race track (virtual race)
athletes run on given track (shadowtrack)
mapping of geolocations
-
within 50 m distance to shadowtrack
detection of start
FIRST geolocation within event time
LAST geolocation at location of start within event time
detection of finish/ split
if device covers the distance of finish/ split
FIRST geolocation at location of finish/ split
target
distance (needed duration is calculated) OR duration (achieved distance)
distance = length of shadowtrack (duration is calculated)
speed filter
segments with too high velocity (depending on 
type of sport) not considered
-
segmentation
participants contribute multiple activities to accumulate the total activity (Monday workout + Wednesday training etc.)
no segmentation: participants provide activities from start to finish corresponding to shadowtrack
segmentation
with keys (add-on): sum up activities (Racemap App + upload) to total activity
segmentation
if total activity > target, detection of finish from the fastest segment corresponding to target
segmentation
breaks without geolocations (duration & distance between two locations) are ignored eg. stop recording activity or rest between two activities
Evaluation participant status (DSQ, DNF, DNS) if geolocations do not fit the required distance within event time. The status is displayed in the leaderboard in the "Rank" column.
feature
without race track (virtual race)
athletes run on given track (shadowtrack)
DSQ: disqualified
-
first geolocation of device is more than 500 m behind location of start on shadowtrack
DNF: did not finish
does not reach target
last geolocation of device does not reach the location of finish on shadowtrack
DNS: did not start
no geolocation received
no geolocation mapped on shadowtrack
Accuracy
Comparison of leaderboard against professional timing solution at 100km-Duathlon, extensive description of this project in our blog.
comparison shows:
- leaderboard provides results from geolocations and virtual splits with low effort, no timekeeping system needed
- same sequence in scoring with leaderboard and with professional timing solution
- accuracy depending on tracking interval of GPS device, deviation < 1 min
Best practice
Leaderboard without given track (virtual race)
Virtual challenge with a global activity map and a Leaderboard for individual workouts
Connect athletes from where they are and compare their activities in a leaderboard. Participants contribute their exercises at anytime and from everywhere. The virtual race provides a leaderboard to compare individual workouts of every participant and a tracking map showing the current location and the replay to verify specific activities.
Evidence of activity with geolocation data regardless of time, location and segments
- From everywhere e.g. a participant in Norway and another athlete in Germany feed their activities into the same event.
- Participants provide their activities at anytime within the start- and end time of the virtual race.
- Participants accumulate activities, e.g. 5k on Monday and another 8k on Wednesday.
Leaderboard for regular event with given route
Prevent unintentional start- and finish timestamps
If participants wait before starting their race and the GPS device already sends locations close to the start split, then "start" detection can be triggered too early. To prevent unintentional reads of start and finish just move the location of the start split 100 m along the shadowtrack (100 m behind real start area). finish split: 100 m before real finish area.
Ensure 1st mapping from (virtual) start split
For detecting "start" the location of the (real) start area has to be mapped to the (virtual) start split on the shadowtrack. If the 1st location from a device is closer to lap three then this device is mapped to lap 3 and not to the start split.
shadowtrack too close to start area causes problems with mapping
Last modified 4d ago
Copy link