Our latest update focuses on making the RACEMAP tracking platform more intuitive, consistent, and technically robust. Here’s what’s new: 

📋 Tracker management: Clear connectivity state

We’ve integrated our SIM provider data directly into the tracker management and show connectivity through two separate indicators:

• CON column: Socket connectivity of the GPS tracker with the RACEMAP server
• NET column: Network registration of our SIM cards 

Important: NET is not transmitted by the GPS tracker itself—it comes directly from our SIM provider, adding redundancy. This is especially useful when a device cannot establish a socket connection, but the GSM modem is still registered in the network. In such cases, the tracker can still be reached via SMS (supported in RACEMAP tracker management).

This removes ambiguity and makes diagnosing GPS tracker status much more straightforward. 

Additional improvements:

• New dedicated NET column
• Simplified CON to show socket status only
• Replaced the online icon with a server icon for clarity
• Removed the cell tower icon from signal strength
• Improved column order and overall table consistency 

Read all about our dashboard to work with many GPS trackers in our documentation: https://docs.racemap.com/tracker-management

🔄 Player reload functionality (auto & manual) 

Keeping event data in the tracking map up-to-date is now much smoother—whether it’s DSQ dots disappearing or participant colors updating automatically. Activate the auto-reload feature in the visualization settings of your events. 

Auto-reload (default ON) refreshes:

• Participants, tracks, and colors
• Starter and track names
• POIs and metadata

Reload button is shown in the tracking map when auto-reload is disabled

Rendering improvements in the interactive race visualization:

• Viewport position is preserved after reload
• More accurate visual updates via sprite hashing

This feature ensures your player reflects real-time changes without requiring a page refresh.

⚙️ Current API improvements

We’ve continued refining the current API to improve accuracy, performance, reliability, and transparency. It now handles sparse data scenarios much better—such as endurance events with infrequent position updates every five minutes—making it an even more powerful tool for video production teams.

Core updates:

• More reliable speed calculation, especially with limited or missing geopoints
• Fixed inconsistencies in gap and average calculations
• Improved handling of shadow tracks
• Added extrapolated parameters including gap support
• Introduced participantId-based gap queries for unified comparisons 
• Simplified query parameters introducing Average Speed Window and Result Time 

Read more in our documentation, including live data samples: https://docs.racemap.com/api/current

If you’d like to test the latest API improvements with real event data from your RACEMAP library, reach out. We set up a 24/7 live event based on your real data for hands-on testing. 

🌍 Extended language support

The RACEMAP tracking app and white-label apps now also support:

• 🇵🇱 Polish
• 🇹🇷 Turkish 

All information about RACEMAP lightweight tracking app solutions: https://docs.racemap.com/apps/tracking

You can now connect any external location source to RACEMAP using the new HTTP tracker. 

HTTP trackers make it easy to forward positioning data from third-party systems directly to RACEMAP. Instead of connecting a physical device, you create a virtual tracker that receives location updates through a simple HTTP endpoint. 

With HTTP trackers, RACEMAP acts as the visualization and location processing platform, while your existing systems continue to provide the position data. This solution gives you a flexible way to integrate existing tracking systems with your RACEMAP project. 

Typical Use Cases

HTTP trackers are useful when location data already exists somewhere else and you want to display or process it in RACEMAP.

• Broadcast production systems, for example using the built-in GPS receivers in TV camera motorbikes during live sports coverage. If positions are already decoded within the broadcast workflow (e.g. from airplane uplink), they can be forwarded directly to RACEMAP.
• Public data sources, such as transportation networks publishing live positions of buses or trains.
• Marine tracking feeds where positions are already available via an API.
• GPS tracking platforms that collect positions from multiple devices.
• Fleet management systems used by support vehicles, logistics teams, or safety crews.
• Custom mobile apps or IoT devices sending their own coordinates.

Learn More

For step-by-step instructions on creating an HTTP tracker and sending coordinates, see our documentation: https://docs.racemap.com/gps-devices/http-tracker

We’re excited to share our recent improvements & new features in RACEMAP, designed to give our users more flexibility, clarity, and control over live tracking and event management. 

Interactive Elevation Chart Component

Our new Interactive Elevation Chart component is now available. It allows you to:

• Visualize the course elevation profile
• Track real-time positions of athletes
• Highlight important Points of Interest

The chart is fully customizable via URL parameters, making it easy to integrate into video productions, live broadcasts, or custom dashboards. 

This component was developed based on feedback from our advanced users during the February RACEMAP Masterclass Workshop and represents the first outcome from that collaboration.

🎯 Try the live demo: https://racemap.com/elevation-chart/61a2055b10cacc0001302283/#selected=632c5f976d787758a9e66d40&color=00ff00&elevation.showProgress=true

📄 Documentation: https://docs.racemap.com/live-tracking/profile 

Tag-Based Filtering for Generic Imports

You can now filter participant synchronization in the Generic Import based on tags. 

• Import only specific subsets of starters
• Align Generic Import logic with the race result import filter
• Address previous import issues and revamp the participant configuration component

This improvement ensures more precise and reliable imports, saving time when managing large events and complex datasets. 

Knots as a New Speed Unit

A customer working with water events was asking for knots as a new speed unit. 

• Renamed unit → unitType to separate from external APIs and make it explicit
• Added preview for the unit system
• Updated distance markers in the player
  

Join our workshop on methods and systems to work with live GPS data for races: Feb 10–12, 2026 · Dresden.

Reserve my spot

We’re hosting a three-day workshop focused on practical workflows for using real-time location data at complex sports events. You’ll learn how to build stronger services, improve operations, and reduce risks — and you’ll leave with solutions you can directly offer to your clients.

Attendees can also unlock up to €5,000 in Safemap savings. Seats are limited. Register for €125/seat.

All details about our workshop: https://go.racemap.com/workshop-26 

Upgrade your skills, expand your services, and strengthen your business:

• Practice with real data & demos: Work hands-on with live GPS streams, API integrations, and Safemap setups — guided by experts.
• Win new business: Develop ready-to-sell live-tracking and safety solutions that directly expand your service portfolio.
• Grow your network: Connect with experienced operators, exchange proven workflows, and discover faster, smarter ways to run events successfully.

Two months ago, we shipped the rebuilt participants table to give you a faster, cleaner way to manage athletes and their devices. Great to see it in use. Thanks for the feedback that helped shape the next enhancements.

Download a single participant’s recorded GPX track

You can now download the recorded GPX for a single participant straight from the participants table without the need to unpack the file. You can also download the GPX files from multiple participants. 

Synchronization: Handling abandoned participants

When you remove a participant in your external system (registration/timekeeping), we call those entries "abandoned" participants. We added a synchronization setting that defines how RACEMAP treats such cases during import/sync from your external system. 

Default behavior: RACEMAP retains the most recent information about abandoned participants - they remain in RACEMAP but will no longer be synchronized. Use this setting to choose the behavior that fits your workflow (keep the last snapshot or clear the participant). 

https://docs.racemap.com/api-import-and-export-data

We’re excited about the new enhancement for our interactive tracking map. We have added the startNumber argument to select specific participants. Just like: https://racemap.com/player/100KmDuathlon2018#selectedStartNumber=001,053

With this feature, you can automatically compose individual URLs for the tracking map to target specific participants without the effort to querry RACEMAP API for the participant id. 

More about URL parameters in our documentation: https://docs.racemap.com/how-to-use-live-tracking/iframe#url-parameters

We’ve added an API endpoint to simplify your workflow. You can now generate tracking keys on demand via API.

https://racemap.com/api/events/:eventId/actions/generate_starter_keys?count=10

Replace :eventId with the id of your event. Set count parameter to the number of needed keys - for example, count=11 to generate 11 keys. Call this route multiple times to generate more keys whenever needed. 

Use Case

This feature is especially useful when selling live tracking access through an online registration platform. You can now fully automate the key generation- and distribution process, reducing manual work and improving the user experience. Use this enhancement to integrate live tracking deeply into your registration or event management systems. 

All details in our documentation: https://docs.racemap.com/how-to-use-live-tracking/tab-keys#apis-related-to-keys 

Let us know how you’re using this enhancement.  We’re always keen to learn from your workflows!

Good news for Wiclax users! We're excited to announce the integration of RACEMAP GPS live data into Wiclax race scoring & timing software. With this powerful integration, Wiclax users can now:

• Query passings of GPS devices at geofences using on our times API 
• Track live locations through our current API 
• Access pre-processed geo data via our ranks API

This means more flexible, real-time insights for your events and competitions. A huge thank you to Mickael from Chrono consult for his invaluable support on this project and many thanks to Wiclax team for their innovation and collaboration.

For all the integration details, check out the new section in our documentation: https://docs.racemap.com/integrations/wiclax

Discover more about Wiclax here: https://www.wiclax.com/

We’ve launched our latest Geo API, providing all geo elements - the shadow track, lines, splits, and points of interest for a specific event. This enhances data exchange with third-party applications and enables seamless automation, keeping your operations updated with the latest event data.

• Automated Video Production – Instantly update the race track in your tracking map settings, making the latest data dynamically available for live broadcasts. 
• Third-Party Integrations – Easily synchronize geo elements with external platforms to improve event tracking, visualization, and analysis.

We’d love to hear how you’re using the new API! Share your feedback so we can continue fine-tuning it to meet your needs. Explore the full documentation: https://docs.racemap.com/data-api/geo-elements 

Tobias Däubner from [db]netsoft asked for additional parameters in our API to be able to always show the devices on the racecourse - rather than near it ;-)

We've now added two parameters to our current API:

lngSt and latSt – The current longitude and latitude of the device, precisely pinned on the shadowtrack. Our algorithm processes raw location data and projects it onto the shadowtrack.

Explore all available parameters in the RACEMAP API documentation: https://docs.racemap.com/data-api/current.