Check/Test/Fix timezone handling against gpx-files #1
Labels
No Label
No Milestone
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: Commander1024/radiation-tagger#1
Loading…
Reference in New Issue
Block a user
No description provided.
Delete Branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
I had problems matching timezone_aware gpx tracks to images, that were taken in the local timezone of the foreign country.
Have to create/fake testdata first, though.
Maybe, gpx files aren't even timezone-aware, but astimezone() is definitively the wrong pytz function make naive times tz-aware. Have to use localize() instead.
Probably fixed timezone issue in
3642d64505
. Needs proper testing, though. Acutally all timezones are localtime, but gpxpy seems to assume utc, which caused the offset in the first place.