From: Bdale Garbee Date: Fri, 24 Jan 2020 09:16:28 +0000 (-0700) Subject: more text X-Git-Url: https://git.gag.com/?p=web%2Fgag.com;a=commitdiff_plain;h=225b518a01a4f2e9fa2162f184457c71e2332058 more text --- diff --git a/bdale/blog/posts/Digital_Photo_Creation_Dates.mdwn b/bdale/blog/posts/Digital_Photo_Creation_Dates.mdwn index 170ab08..beaaf06 100644 --- a/bdale/blog/posts/Digital_Photo_Creation_Dates.mdwn +++ b/bdale/blog/posts/Digital_Photo_Creation_Dates.mdwn @@ -5,7 +5,7 @@ I learned something new yesterday, that probably shouldn't have shocked me as much as it did. For legacy reasons, the "creation time" in the [Exif](https://en.wikipedia.org/wiki/Exif) metadata attached to digital camera pictures is not expressed in absolute time, but rather in some -arbitrary express of "local" time! This caused me to spend a long evening +arbitrary expression of "local" time! This caused me to spend a long evening learning how to twiddle Exif data, and then how to convince [Piwigo](https://piwigo.org/) to use the updated metadata. In case I or someone else need to do this in the future, it seems worth taking the time @@ -83,6 +83,12 @@ plus 4 time zones from home to where the photos were taken. And the remaining was originally set by hand, and drift of the camera's clock in the many months since then. +I thought briefly about hacking Piwigo to use the GPS time stamps, but quickly +realized that wouldn't actually solve the problem, since they're in UTC and +the pictures from our phone cameras were all using local time. There's +probably a solution lurking there somewhere, but just fixing up the times in +the photo files that were wrong seemed like an easier path forward. + A Google search or two later, and I found [jhead](https://www.sentex.ca/~mwandel/jhead/), which fortunately was already packaged for Debian. It makes changing Exif