more text

[web/gag.com] / bdale / blog / posts / Digital_Photo_Creation_Dates.mdwn

diff --git a/bdale/blog/posts/Digital_Photo_Creation_Dates.mdwn b/bdale/blog/posts/Digital_Photo_Creation_Dates.mdwn
index 170ab0864ddad8f1cf8315af2a7ddd4cf78b9a2b..beaaf0679efd9349ebc00e5421df332c49eabe04 100644 (file)
--- 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