#3356·dawarich

Tracks never terminate when GPS points arrive continuously

Author: mxzgithubCreated Aug 13, 2026Updated Sep 18, 2026

BEFORE OPENING AN ISSUE, MAKE SURE YOU READ THIS: https://github.com/Freika/dawarich/issues/1382

OS & Hardware Unraid 7.3.2, Docker Compose AMD 5900x, 128 GB RAM, ZFS storage

Version 1.12.1 Describe the bug Short: Basically, I am seeing a ghost of yesterdays Routes today, because the tracks are spanning over to much time.

Long: Track segmentation never terminates a track when GPS points arrive continuously, producing tracks spanning 12–36+ hours.

Example: Track #17757:

  • Duration: 35.9 h
  • Distance: 153,133 m
  • avg_speed: 4.26 km/h
  • Points in track: 1,814

An average of 4.26 km/h over 153 km is not a plausible movement profile, the track has absorbed long stationary periods (overnight) between actual journeys.

Point gap analysis within that track:

  • Median gap: 49 s
  • Max gap: 401 s
  • Gaps > 30 min: 0
  • Gaps > 60 min: 0

My setting minutes_between_routes is 30, but no gap ever exceeds 6.7 minutes, so the track never closes. The device reports position continuously, including while stationary.

Distribution across the whole library (28,562 tracks from 2,333,331 points, 2014–2026):

  • Median duration: 0.61 h (correct)
  • Tracks > 12 h: 3,300 (11.6 %)
  • Tracks > 24 h: 1,397 (4.9 %)

The majority segment correctly, so the logic works when gaps happen to occur. It just has no other way to end a track.

Expected behavior Tracks should end when movement stops, not only when a reporting gap occurs. No Overnight Tracks.

Logs No errors in Sidekiq logs during track generation.

Disclaimer Report write-up assisted by Claude Opus 5.