Skip to content

feat(scheduling): backlog rows can name a day GPX and camera UTC offset - #46

Merged
joepetjr merged 1 commit into
mainfrom
feat/backlog-day-gpx
Oct 24, 2026
Merged

joepetjr merged 1 commit into
mainfrom
feat/backlog-day-gpx

Conversation

@joepetjr

Copy link
Copy Markdown
Contributor

What

drive_backlog.yaml rows may carry day_gpx (a whole-day GPX track) and camera_utc_offset_hours (the hours the camera clock runs from UTC). backlog.load reads both; backlog-next prints both ("" / null when unset).

Why

The video pipeline's generic ingest locates footage with no GPS of its own by slicing a day track per file on the camera clock (drive --day-gpx --camera-utc-offset-hours). The backlog had no field for either, so those drives (the 2025-09 Ireland days) could not launch from it and were run by hand.

Rules

  • Both or neither: a track with no offset would be sliced on the wrong clock and land hours off with no error.
  • The offset is a number (not a bool) from -14 to 14.

Tests

tests/scheduling/test_backlog.py (row carries both; rows without have ""/None; five refusals) and tests/scheduling/test_cli.py (backlog-next output). Red before the change (7 failed), green after: 60 passed.

Footage with no GPS of its own (Insta360 on the 2025-09 Ireland trip) is located from a whole-day track, sliced per file on the camera clock. The backlog had no field for either, so those drives could not launch from it. day_gpx and camera_utc_offset_hours are required together: a track sliced on the wrong clock lands hours off without any error.
@joepetjr
joepetjr merged commit 5da8207 into main Oct 24, 2026
4 checks passed
@joepetjr
joepetjr deleted the feat/backlog-day-gpx branch October 24, 2026 19:07
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant