0

When getting CreateionDate of PHAsset, the time returned is in UTC format. In order to display it correctly, so as to meet user's expectation that e.g. captured image of sunset was in the evening hours, not in the middle of night or day (depending on time-zone shift to UTC), the application needs to format the UTC date-Time by considering the timezone of the photo location.

I wrote a code, which handles this, and it works ok, but only for pictures which have geolocation and were taken with the iPhone camera, which is "aware" of time zone and so the UTC time it sets is correct. However if I open an image (asset) from PhotoLibrary which was taken with a camera not being "aware" of timezone concept (it only has a local time clock, which needs to be shifted when traveling to another timezone), than such a photo creation date refers to a non-UTC time (I guess that PhotoKit tries to derive UTC time of a photo - based on current for importing process local time shift against UTC-time - of the device used for importing).

If picture has geolocation, and the Creation Time is really UTC, I can derive timezone, and based on it I can format correctly UTC time to local time (of moment when picture was being taken). If the picture does not have geolocation, then I can't, despite the asset creation time is really UTC - User for some images may want to clear geolocation. Then I'm left with incorrect creation time (it is UTC but I don't know for which time zone I should format it)

The question is - how can I diffrentiate PHAsset's CreationDate - to know whether the value is, or is not time-zone "aware"? And, when knowing this, how to shift to proper timezone (to display local time of taking the picture), when there is no geolocation ?

The iOS and Mac Photos Application displaying images from Photo Library seem to deal with this problem fine, as these display for these legacy photos just the EXIF date-time (what is ok, as long as the legacy camera had its local time correctly set to local time upon traveling, what can be assumed).

So, based on what does Photos App pick either [ready to display Exif Date] or [UTC Asset Creation Date] ?

Michal.Jan008
  • 135
  • 11

1 Answers1

1

All pictures get a creation date of "now" based on the device's current idea of the current local time and the device's current timezone when the picture is taken or saved. Any device can have the wrong time or timezone so there's never any guarantee the picture's timestamp is accurate at all.

As for showing a picture's creation date in local time, you have only a few possible options. Use these in the following order to get the best result:

  • The picture has metadata (EXIF) that stores the date in local time. No conversion would be necessary.
  • The picture has metadata with the picture's GPS location. The coordinates can be used to work out the timezone of the picture and UTC timestamps can be adjusted.
  • None of that is available and the timestamp can only be shown in UTC or current local time (which may have nothing to do with where the picture was really taken).

Note that showing UTC time is always correct and unambiguous. Of course being able to show the picture's local time, when possible, can be more useful.

In short, first look at the picture's metadata for its local timestamp. Use that if it exists since that is in local time. See How to get original (EXIF?) creation date/time of PHAsset? for examples.

If you can't get the local creation time from the metadata, fallback to GPS adjustments or simply showing in UTC or current local time.

HangarRash
  • 7,314
  • 5
  • 5
  • 32
  • The first option (picking time-taken of from EXIF) was the very first approach I'd used, but when I learned that user may adjust creation date, which does not get stored back to exif, I had to change my algorithm, so as to get PhotoAsset Creation date attribute first (as this is seems to be updated when changing photo's date-time). I wish I could read the EXIF-stored taken data, but I would have to be sure first, that the user has not adjusted the photo taken date. Is there any way to ask PhotoKit to get information that the EXIF date-time has not been overridden by user? – Michal.Jan008 Jan 16 '23 at 07:41
  • If a user changes the EXIF photo date then that's the date the user wants. Why ignore it? The PhotoAsset creation date is based on the file attributes, not the EXIF data. The file creation date is probably the least accurate date you could possibly choose. Always use the EXIF date if it exists. – HangarRash Jan 16 '23 at 16:35
  • User cannot change EXIF photo date (of image imported to Photo Library). If one alters photo taken date using e.g. Photos application - it is *not* the EXIF data that gets changed, but Assets's CreationDate. – Michal.Jan008 Jan 16 '23 at 16:43