# Classical Race Map View (Predictive Tracking) The **Classical Race Map View** is the live-map dashboard for races that are configured for **Predictive Tracking** in **RUFUS Race Manager**. It gives operators a visual, real-time representation of how the race is evolving on the course. Instead of reading race progress only through tables and checkpoint data, you can now follow the event directly on the map. The map combines the configured course, mapped checkpoints, and projected participant positions to help you understand where the race is, how it is moving, and who is leading each part of it.

Classical Race Dashboard in Map View

## What is Predictive Tracking? **Predictive Tracking** is a live-race visualization system for **classical races**. It projects participant positions between mapped checkpoints using their latest valid split pace. This means the system can estimate where each participant is on the route even when they are currently between two physical timing points. The result is a more intuitive and spectator-friendly way to monitor race progress in real time. ## When is the map view available? The **Map View** is available for classical races that are properly prepared for Predictive Tracking. A race must have: * a valid mapped route * at least one mapped intermediate checkpoint These elements are configured in the **Course Designer**. If the race does not meet these requirements, Predictive Tracking will not be available. ## How to open the Map View During race operations, open the **Race Dashboard** and switch to **Live Map** view. Once enabled, the dashboard changes from the standard race control layout to a map-first live tracking view. ## What the map shows The Predictive Tracking map displays several layers of live race information. ### Race route The dashboard shows the configured course route for the selected race. This gives operators a clear visual reference of the race path and helps place all live activity in real course context. ### Mapped checkpoints All mapped checkpoints related to the race are shown on the route. These typically include: * **Start** * **Intermediate checkpoints** * **Finish** Each checkpoint helps define where participants are confirmed and how the system calculates projected positions between timing points. Checkpoint markers also show race progress information, including **crossed / pending counts**, helping operators quickly see how the field is moving through the course. ### Projected participant positions Participants are shown as live dots placed on the route. These dots are not random approximations. They are projected using the latest valid checkpoint data and the participant’s most recent pace between splits. This lets operators see a live representation of where the field is likely positioned at that moment on the course. ## Tracking modes The map supports different filtering modes so operators can focus on the part of the race that matters most. Available tracking modes include: * **Top 10 overall** * **Top 5 by gender** * **Age-group leaders** * **Race distribution** You can also add **extra selected bibs** on top of the active filter, making it possible to follow specific participants while keeping the broader race context visible. This is especially useful when monitoring favorites, team athletes, special guests, or participants under review. ## Participant details Clicking a participant on the map opens a pinned detail tooltip with additional race context.

Participant Details in Map View

Depending on the race state and available data, the tooltip can include: * bib / participant identifier * race time * current pace * distance to go * predictive finish time * last checkpoint * next checkpoint This gives you a quick operational summary for that participant without leaving the dashboard. ## Why projected positions matter Predictive Tracking helps operators understand the race between physical reads. In a traditional view, you only know where a participant was the last time they crossed a checkpoint. With Predictive Tracking, Race Manager uses that checkpoint data to estimate where the participant is now. This helps answer questions such as: * Where are the leaders right now? * How spread out is the race? * Who is approaching the next checkpoint? * How is the front of the race evolving? * Which participants should operators keep an eye on? It turns checkpoint timing into a live visual story. ## In simulation and live operation The Map View can be useful both during real live timing and during simulation or race testing. It helps operators validate that: * the route is mapped correctly * checkpoints are placed in the correct order * participant projections behave as expected * the race flow is visually understandable This makes it a valuable tool both for setup validation and for race-day monitoring. ## Predictive Tracking in participant management Predictive Tracking is not limited to the main dashboard. It also appears in the **Edit Participant** view, where Race Manager shows a focused mini-map snippet for the selected athlete. This gives operators additional spatial context while reviewing individual participant data. ## Best practices For the best Predictive Tracking experience: * make sure the course route is mapped accurately * place checkpoints carefully on the correct point of the route * include at least one valid intermediate checkpoint * verify that checkpoints follow the real course order * use map filters to reduce clutter during large races * pin selected bibs when you need to follow specific athletes ## Why it matters The Classical Race Map View adds a more modern, map-first layer to race operations. It helps timing teams understand where participants are, where they are headed, and how the race is developing in real time. For operators, that means better visibility and better context. For the event experience, it means race timing data becomes something much easier to interpret, explain, and share. --- # Agent Instructions: Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter: ``` GET https://help.runonrufus.com/rufus-race-manager/races/classical-race-map-view-predictive-tracking.md?ask= ``` The question should be specific, self-contained, and written in natural language. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.