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 were asked to improve the copy function of events. The duplication feature now offers separate options for transferring route- and participant information. For groups and stages, you can also decide whether the copy should belong to the same group as the original event.

With the copy function, you use your previous tracking maps as a template and save time when initializing a new tracking map. The duplicate feature is available in the advanced settings of your tracking map.

Our leaderboard and live results solution is used for many of our long-distance events such as ultra trails, endurance cycling, or even rowing. We now made the processing of geo-locations to results more flexible, robust, and stand-alone. 

It might happen that a gps device does not send coordinates from the beginning of the race. From now on the later coordinates are considered in the leaderboard for calculating subsequent split points, and the splits before are just ignored. That way spectators get more live information from our leaderboard. 

Check the leaderboard from Ringvaart Regatta, a 100 km rowing race: https://racemap.com/timing/ringvaart-regatta-2023

Additionally, there is the option to manually enter results.  

Find all the information about our effortless live rank and real-time scoring in the documentation: https://docs.racemap.com/how-to-use-live-tracking/gps-timing

The track chart shows all geo points of a specific device with the recorded- and received time. Track chart highlights delays like when the GPS tracker sends packages from memory, which can indicate problems in mobile reception. 

We were asked to integrate the watchdog command for our PRO GPS tracker in the tracker management. The watchdog regularly reboots the tracking device regardless of a connection to the tracker management. You can now select the watchdog command in our message modal.

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.  

We massively enhanced the search in our documentation. Faster information speeds you up while working on Racemap tracking platform. Simply tell what you want, or ask a question. AI scans our documentation and gives you a simple, semantic answer - with clickable references if you want to dive deeper. Just give it a try and drop your feedback.

You access the AI search in our documentation (https://docs.racemap.com/) with the Lens option.

We integrated the Pengsent FM03E GPS Tracker into our tracking platform. You can now use this tracker type for live tracking on Racemap. 

Check the list of various devices that protocol is supported in Racemap: https://docs.racemap.com/hardware-for-live-tracking

To increase your flexibility when applying GPS trackers at sports events we developed the "close after"-parameter for messages. Now, there are three options on how the message interacts with the device which is remotely connected to our tracker management (https://racemap.com/admin/trackers/).

• Before "planned at"-time the message is not sent to the device. 
• Within "planned at"- and "close after"-time the message is sent to the device, as early as the device is connected to the tracker management.
• The message that can't be sent until "close after" becomes inactive (timeout) and won't be sent anymore. The new parameter for messages prevents unintentional "shut down"-commands that could not be sent in time.