When providing live tracking for events & races in a scalable manner our users work with APIs to import and export participants' information and GPS devices. We now refactored our generic import. We flattened nested objects and now provide to import RACE RESULT lists. 

Read all about our generic import in the documentation: https://docs.racemap.com/api-import-and-export-data/import-basics/metadata-api

We enhanced our leaderboard solution to show more accurate results. If the synchronization of participants' data includes start- and finish times these values are used in our leaderboard with higher priority than processed start- and finish times from GPS data. This feature lets flexibly combine start and finish detections from a timing system with intermediate splits by GPS data in the same leaderboard. 

Read about synchronizing participants' data and about our leaderboard in the documentation: 

• https://docs.racemap.com/api-import-and-export-data/import-basics 
• https://docs.racemap.com/how-to-use-live-tracking/gps-timing

We aim to speed up processes when working with GPS trackers and to prevent support issues. 

Now our tracker page shows participant's name & bib number and the event name. That way you deploy GPS trackers at the race ground and through the QR code participants swiftly self-check that they have received the correct device. 

Additional useful information on the tracker page about battery, last location, GPS fix, and reception with the mobile network. The easy interaction with end users enables seamless workflows when you deploy many GPS devices at a race.  

The generic import now provides a detailed error description if it fails for specific entries. Read all about flexibly import & synchronize participants' & devices' information through the generic import feature: https://docs.racemap.com/api-import-and-export-data/import-basics/metadata-api 

Predictive tracking processes sporadic detections from a timing system and shows a race visualization in real-time. The participant markers move smoothly in the interactive map. Prediction enables an effortless live forecast of all participants and is a scalable tracking solution for mass events.

For RACE RESULT timers we developed new tests and auto-checks. Now, our prediction dashboard provides clearer feedback on settings & on forwarded data. We support the timekeeper even more effectively and prevent unintentional mistakes when setting up the event before and while live-tracking a race.

• Auto-check, if forwarding to Racemap is set in track box settings, 
• Auto-test, if forwarding to Racemap is working, 
• Display the locations and the mapping of the track boxes and
• Import and sync participant data 

Our users spend less time docu reading but do more and better live tracking. More about predictive live tracking in our documentation: https://docs.racemap.com/predictive-tracking-with-data-from-timekeeping

Our grabber is a handy tool to poll our live data API and directly show race data in real-time in a browser tab. Use this solution to seamlessly provide real-time participant data such as speed, distance to go, or gap for your video productions. No coding skills needed.

With the new version of the grabber, you can now set 

• Multiple deviceIds respectively startNumbers to show specific participants only. (Instead of showing all participants or only one.)
• The number of devices in lead showLeaders eg. in order to show data of the five leaders only. 

Download files and all information about our grabber tools to easily extract live data from our API are summarized in our documentation: https://docs.racemap.com/data-api/grabber.

There are many users that manage the participant information in RACE RESULT 12. Racemap provides an interface to import & sync participants with your tracking map, easily. Using the synchronization feature you just need to update only one source of participants' data. 

We now reworked this modal and added some enhancements. 

• Showing the list of contests corresponding to the event id.
• Select each contest separately to sync with the tracking map.
• Showing the time of the last synchronization.
• Parsing the raw data file and showing an overview such as the number of participants with transponder id.

Read all about the import of participants from RACE RESULT into your tracking map in our documentation https://docs.racemap.com/api-import-and-export-data/import-basics/metadata-import-via-rr.

We enhanced the list with the Participants Data in the event settings. The style is cleaner, the list loads much faster and you are able to work more efficiently. The two major improvements are 

• The list flexibly spreads to full display size and
• The menu shows the number of entries.

We added the option to preset filters for the visualization. When setting the "none" status as the default filter, the tracking map will initially hide participants with a DSQ or DNF status tag. Spectators watching the visualization can adjust the filter in the tracking map, also.

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