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
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
her photos in the Piwigo web GUI, so it really seemed necessary to fix the
images "in place" on the Piwigo server. The first problem with that is that
as you upload photos to the server, they are assigned unique filenames on
-disk based on the upload date and time plus a random has, and the original
+disk based on the upload date and time plus a random hash, and the original
filename becomes just an element of metadata in the Piwigo database. Piwigo
scans the Exif data at image import time and stuffs the database with a
number of useful values from there, including the image creation time that is
photos in the resulting set, and performed action "synchronize metadata". All
the selected image files were rescanned, the database got updated...
-Voila!
-
+Voila! Happy wife!