- Status New
- Percent Complete
- Task Type Feature Request
- Category Backend / Core
- Assigned To No-one
- Operating System All
- Severity Low
- Priority Very Low
- Reported Version 2.36
- Due in Version Undecided
-
Due Date
Undecided
- Votes
- Private
FS#393 - Use GPS timestamp when importing, if present.
If we have a GPS tag, the odds are its timestamp is going to be more accurate than what the camera thinks.
Unfortunately, the GPS timestamp is reported in UTC. All dates in PO are stored sans timezone, but the odds are that you're not in GMT. So we'd need to add some sort of local time zone setting and convert the date/times as appropriate.
Loading...
Available keyboard shortcuts
- Alt + ⇧ Shift + l Login Dialog / Logout
- Alt + ⇧ Shift + a Add new task
- Alt + ⇧ Shift + m My searches
- Alt + ⇧ Shift + t focus taskid search
Tasklist
- o open selected task
- j move cursor down
- k move cursor up
Task Details
- n Next task
- p Previous task
- Alt + ⇧ Shift + e ↵ Enter Edit this task
- Alt + ⇧ Shift + w watch task
- Alt + ⇧ Shift + y Close Task
Task Editing
- Alt + ⇧ Shift + s save task
* add preference for time zone into PO on a per-user basis
* alter all DB fields to include timezone -- what to do about existing timestamps?
* can PGSQL do auto-tz conversion for display purposes?