You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The image create time recorded in the exif data is all too often wrong. We should have an option to fix that. It should be fixed in the index only, not in the image file, since we want to stick with the principle to access the image files read only.
The most common causes of faulty create time in the image file include:
camera clock being set wrong during taking the image,
camera set to wrong time zone or wrong daylight saving time setting, which may be considered a special case of the previous bullet.
We might implement this adding some --fix-date command line option, taking an offset as argument, to the create subcommand of the CLI and/or adding a new fix subcommand to the CLI.
We probably should implement #7 first and this one on top of it.
The text was updated successfully, but these errors were encountered:
Not sure about this one: it turns out that once we have implemented #7, these kind of issues can be relatively easy fixed using the photoidx API in an interactive Python shell. It might be as easy as:
On the other hand, given the variety of possible errors that may occur in practice, it might be challenging to come up with a CLI suitable to cover all cases in an efficient way. I tend to to give that interactive Python shell a try as a user interface and wait and see how it performs in practice.
The image create time recorded in the exif data is all too often wrong. We should have an option to fix that. It should be fixed in the index only, not in the image file, since we want to stick with the principle to access the image files read only.
The most common causes of faulty create time in the image file include:
We might implement this adding some
--fix-date
command line option, taking an offset as argument, to thecreate
subcommand of the CLI and/or adding a newfix
subcommand to the CLI.We probably should implement #7 first and this one on top of it.
The text was updated successfully, but these errors were encountered: