What is a Track? How TurfZones defines tracks

A track is a continuous sequence of zone activity by a single player. We build tracks from your TURF events (takeovers and assists), ordered by time, and split them when there's a long gap in activity.

What gets included

• Event types: Takeovers and assists are both part of a track
• Order: Events are sorted in strict chronological order
• Zone count: The track's zone count equals the number of events in the track (takeovers + assists)
• Points: Total points = sum of points from all events in the track

In the fullscreen track viewer, both the list and the map include all events (takeovers + assists). Other views may visually distinguish event types for clarity.

When a track starts and ends

• Start: The first event after a gap of more than 60 minutes, or the first event inside your selected time range
• End: The last event before a gap of more than 60 minutes, or the last event within your selected time range
• In progress: A track is marked "in progress" when its last event was within the last 30 minutes
• Date filters: Tracks respect the analytics time window you choose (e.g., last 24h). This can create partial tracks at the edges of the range

How splitting/merging works

• Split rule: A gap strictly greater than 60 minutes between consecutive events starts a new track
• Merge rule: Any events with ≤ 60 minutes between them belong to the same track
• Assists-only: Tracks can be made entirely of assists (that’s valid)
• Same-zone repeats: Multiple events at the same zone count separately if they happen within the 60-minute window

Examples

• 18:00 takeover → 18:45 assist → 19:30 takeover (45 min gaps): one track
• 18:00 takeover → 19:05 takeover (65 min gap): split into two tracks

Map rendering

• Path: The line connects zone coordinates in event order using straight segments
• Not GPS: We do not reconstruct your exact traveled path; it’s an event-to-event visualization, so lines may cross water or buildings
• Markers: Start and end are marked; assists use a distinct icon

Metrics we show per track

• Duration: From first to last event time in the track
• Zone count: Total events (takeovers + assists)
• Total points: Sum across events in the track
• Collaboration stats (enhanced tracks): number of assists, assist ratio, assist partners

Why your track might look different than your ride/run

• Event-based: We only know when you took/assisted zones, not your continuous GPS
• Straight lines: Route lines are visual connectors, not navigated paths
• Time windows: Applying a date filter can cut tracks at the start/end

FAQs

• Why did my track split? There’s a gap of more than 60 minutes between two consecutive events, or a time filter boundary
• Why does the zone count differ from what I expected? We count all events (takeovers + assists). Some lists may hide assists for readability
• Can I change the 60-minute threshold? Not at the moment; it’s fixed to keep analytics consistent
• Can a track be only assists? Yes. Assists can start/end a track and form a full track
• Does distance matter? No. Tracks are determined purely by time gaps, not how far apart zones are

Saving and sharing tracks

You can save any track (name and describe it) and find it later under My Insights. Saved tracks include their event list and summary metrics and can be shared with teams if you choose.