Skip to content

Python: remove stale comment about timestamp units in the spec #50

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
sanderroosendaal merged 1 commit into from
Oct 23, 2026
Merged

Python: remove stale comment about timestamp units in the spec #50

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 0 additions & 2 deletions python/src/rowing_data/constants.py
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -21,8 +21,6 @@
APPLICATION_ID: bytes = APPLICATION_UUID.bytes

# Garmin FIT timestamps count seconds from 1989-12-31 00:00:00 UTC.
# Native `timestamp` uses this epoch (seconds), despite the draft table saying
# milliseconds — that wording is a FIT-profile mismatch, not a second epoch.
FIT_EPOCH_UNIX = 631065600

# Native FIT field scales: physical = raw / scale (FIT profile convention).
Expand Down
Loading