You can make a difference in the Apple Support Community!

When you sign up with your Apple Account, you can provide valuable feedback to other community members by upvoting helpful replies and User Tips.

Looks like no one’s replied in a while. To start the conversation again, simply ask a new question.

Metadata in different time zones - nightmare

I am very annoyed about this very apparent bug in Photos.


On the Mac version, you click the Get info button to check the date and time of a particular photo and it will display the correct time of when the picture was taken. It might be the case though that you are consolidating pictures from a particular 'event' from different people/sources and this always worked very well for me in iPhoto - pictures would be sorted correctly by date. Please note, I am talking about pictures that have been taken outside your usual timezone (i.e. on holidays abroad)


Importing those very same pictures now into Photos, very often (not always) yields in pictures being sorted incorrectly. Although, pictures from different sources have the correct date, they are being sorted based on my home timezone. I then obviously checked under Image -> Adjust Time,Date the embedded timezone of those pictures. Again, both pictures have the same timezone selected. There is no fix to this. Doesn't matter if I am changing the timezone or manually change entries, it will simply not sort the pictures correctly.


Photos on iOS will always display the time of my own home zone above any picture I have taken and sort it based on that. This is consistent with the Mac version in terms of sorting but iOS actually does give a bit of insight of why it is sorting pictures incorrectly.


Photos on iCloud.com is another story and it very often displays in 'moments' very different metadata about time, date locations and gets it very wrong.


I think there is a inconsistency in the Photo app or in the Photo Cloud library in general that causes this problem. I know that while Photo was in beta on icloud.com many people reported that pictures would display Cupertinos time zone for any picture they have taken.


I am not sure this can be easily fixed because it doesn't seem to be just a case of how the different Photo app interpret metadata. It might already be the case that Photos have been damaged when I imported them manually into the Photos app. That would mean re-importing and adjusting of thousands of photos for me which were in perfect order beforehand.


What is your experience?

Posted on Apr 17, 2015 7:26 AM

Reply
42 replies

Apr 25, 2016 5:27 AM in response to Erik Coremans

There are occasions when iPhone images don't have GPS information and it's a problem that's really annoying me.


If you take the picture through iMessage (for example), the resulting picture saved to the camera roll is missing the following metadata. MAKE, MODEL and LOCATION.


Why this occurs, I have no idea. The original photo is stored to the camera roll while the optimised version, sent via iMessage, still has this information attached.

Apr 25, 2016 7:11 AM in response to Apple Iceman

Apple Iceman wrote:


There are occasions when iPhone images don't have GPS information and it's a problem that's really annoying me.


If you take the picture through iMessage (for example), the resulting picture saved to the camera roll is missing the following metadata. MAKE, MODEL and LOCATION.


Why this occurs, I have no idea. The original photo is stored to the camera roll while the optimised version, sent via iMessage, still has this information attached.

Ok - but it is not at all clear why you posted this in the Photos for Mac user to user forum - it seems to have nothing to do with photos and no one here can change anything - can you explain your reasoning please or ask a technical question abut Photos for the Mac that the users here can hep with?


LN

Apr 25, 2016 8:17 AM in response to LarryHN

Ok - but it is not at all clear why you posted this in the Photos for Mac user to user forum - it seems to have nothing to do with photos and no one here can change anything - can you explain your reasoning please or ask a technical question abut Photos for the Mac that the users here can hep with?


We're talking about timezone (and location) information when importing into Photos. I've had this problem before where I couldn't understand why some of my photos taken with my iPhone didn't have timezone information. It was a long process to discover where the fault lay.


The original post included references to Photos and iCloud. Bugs in the iPhone comes across to the Photos app which is advertised as the Mac software for your photos. iPhone included.

Apr 25, 2016 8:39 AM in response to Apple Iceman

We're talking about timezone (and location) information when importing into Photos. I've had this problem before where I couldn't understand why some of my photos taken with my iPhone didn't have timezone information. It was a long process to discover where the fault lay.

Photos for Mac is still handling imports from the iPhone frequently wrong.


Other iPhone and iPad photos that will give incorrect location data and capture times are the still images, that come with iPhone videos. They are frequently imported with the wrong timezone and appear in different moments than the videos they belong to.


Also, if I sync photos with iTunes to my iPad and edit them on the iPad, My Photo Stream will sync them back without GPS and with an incorrect time zone.

And lastly, if my iPhone and Mac cannot connect to Wi-Fi and I have to import the recent photos using a USB connection, and accidentally import an older photo that has been downloaded from iCloud Photo Library, this iCloud download will also have missing metadata and an incorrect capture time.

May 14, 2016 4:49 PM in response to Erik Coremans

Erik Coremans wrote:



2. I have in my holiday 2015 album, 3 different kind of photos :

- taken with Canon camera - while under GPS coverage

- taken with the same Canon camera - while NOT under GPS coverage (poor or no signal at time of photo)

- taken with iPhone6 camera

The pictures which were under GPS coverage, do not have the phenomena of adapting the time zone to the time zone of your computer during import. These pictures have the correct time zone.




Eric,

I am struggling with the same dilemma, as I attempt to import/process several hundred photos taken on a recent vacation trip. I've come to the same conclusion that you have re pictures taken with no GPS coverage.

Here's what I think is happening:

- if a picture imported into Photos has legitimate GPS tags (lat & long), Photos will use the GPS info to determine a "Closest City", and from that, the timezone in which it thinks the picture was taken. It then adds the derived timezone info to the metadata for that picture. That timezone is then used when Photos determines how to order pictures in the Moments timeline.

- if a picture does not have GPS tags (perhaps the GPS receiver in the camera was turned off), Photos is unable to determine a "Closest City". Nor can it infer the timezone in which the picture was taken. If that's the case, it assigns the nearest city to the Mac when the import was done as Closest City (using OSX Location Services). It also appears to assign the picture with the system timezone in effect on the Mac when the import was performed. If/when that happens, the picture will be sorted in the Moments timeline hours away from where it should be.

- I've encountered an additional scenario. Sometimes, my camera (a Lumix ZS-40) will store out-of-bounds lat/long values in the EXIF. This happens when the camera does not have good GPS coverage (i.e. inadequate GPS signals from >3 satellites). In that situation, the Lumix also records the value "Void" in the GPSStatus tag in the EXIF, declaring that the GPS values are no good. It appears that Photos ignores the value in the GPSStatus tag. When it imports such a picture, I've observed that it assigns no Closest City (a blank). It seems to assign a timezone of GMT to such a picture. When such a picture gets placed in the Moments timeline, it will also be out of order.


As for images originating on an iPhone, I've found that iOS treats pictures taken on my iPhone differently from screenshots. Pictures may or may not have correct GPS tags (depending on if/how the iPhone was able to determine location when the picture was taken). An iPhone may use GPS satellite signals, and/or cell tower info, and/or WiFi base station info to infer location. The location info embedded in an iPhone picture may or may not be accurate. On the other hand, I've observed that screenshots captured on the iPhone don't have any embedded location/GPS metadata. I've noticed that Photos assigns the location and timezone that the Mac has when a screenshot is imported into Photos.


One 'fix' for this mess is to assign correct GPS tags to all pictures before they are imported into Photos. In your case, this means assigning location info to any pictures taken on your Canon when it had no GPS coverage. Geo-coding can be done using a 3rd party program such as HoudahGeo. That's what I'm using. Once that's done. you can import all the geo-tagged pictures into Photos, which will then assign a consistent location-based time zone to every picture.


As Léonie points out, this all gets much more complicated when images transit through iCloud, get synced via PhotoStream, are transferred via USB, and/or are migrated using carrier pigeon.

May 14, 2016 11:11 PM in response to D.R.C.

As Léonie points out, this all gets much more complicated when images transit through iCloud, get synced via PhotoStream, are transferred via USB, and/or are migrated using carrier pigeon.

And if the GPS data are embedded in the original Master image files before importing the GPS will survive the journey through iCloud. It is really worth it to get the locations embedded in the originals. It makes it easier to move photos between Photos Libraries as well.

May 15, 2016 2:00 AM in response to D.R.C.

On the other hand, I've observed that screenshots captured on the iPhone don't have any embedded location/GPS metadata. I've noticed that Photos assigns the location and timezone that the Mac has when a screenshot is imported into Photos.


It's not only screenshots. It appears to be all photos not taken directly through the built in camera app, as I described in Re: Metadata in different time zones - nightmare.


User uploaded file


Above is a screenshot of Image Capture, showing two photos taken on my iPhone, ready to be imported. The top photo was taken through iMessage, the bottom through the Camera App. There are a couple of things worth mentioning.


  • Both images were taken with a valid GPS signal. Top image has more than location stripped.
  • The filenames indicate that the top picture was taken before the bottom picture. Correct.
  • The times indicate that the top picture was taken after the bottom picture. Incorrect.
  • The top picture has adopted the current timezone on the iPhone (+9) and not the Mac, which is still on the timezone when both pictures were taken (+2).
  • The photos appear in the correct order in Moments on the iPhone with the second picture's time adjusted showing as (+9).


I reported this bug and had an email conversation with a guy in the Photos section. It ran out of steam when it was determined to be an iPhone issue. That the products work hand in hand was conveniently forgotten.


One has to ask two questions. Why strip this information in the first place? Secondly if it is stripped, or there is no valid location information on the phone, use the timezone on the phone/camera when the photo was taken through TimeZoneOffset Exif data field.


Moments is an integral part of Apple's photo strategy, this is basic stuff that should have been thought through.

Jun 10, 2016 1:59 AM in response to rikscha

I just went on a trip. I have an iPhone 6s Plus / Nokia Lumia 950 XL / Samsung S6.

I copied all my images to one folder (I use a Windows 10 computer). Below are the naming conventions of files not taken at the same time:

20160526_194646.jpg Android

WP_20160520_09_43_22_Pro.jpg Windows

20160526_091035396_iOS.jpg iOS


What I found with iOS was, the image filename is taken in GMT.


So being that my trip was 10 hours off of GMT, I would need to script out the renaming of the files to adjust for the 10 hour difference.

so this image 20160526_091035396_iOS.jpg iOS says it was taken on 2016/05/26 _ 09:10:35:396


that reads 9:10:35 AM. The last 3 numbers in Bold (396) maybe the millisecond but I didn't confirm that.


should look more like:

20160526_191035_iOS.jpg (I removed the last 3 since I don't take pictures that quickly.


The problem still is, because my flight to my tripe was with layovers in 2 more time zones, I need to identify the images that were taken in different time zones to ensure I don't adjust 10 hours on a time zone that was different.


If people are taking photos with devices (like phones) that update time automatically from cell phone providers, this would not be an issue if the images were not saved in GMT. 😟


but I can also see the issue where, if you had an old digital camera, the images would all have been saved in the original time zone (Since most people don't change the time on their cameras while traveling).


I'm sure the different platforms (Windows/Apple/Google) will not agree on a standard between them to say, filenames should all be like:

YearMonthDay_HourMinuteSecond_Platform (and potentially millisecond)


but if you know the difference for iOS and you rename all your photos to be a similar naming convention your images will sort properly.


The downside here is, while the platforms are not using a similar convention if you receive more photos, let's say the event was a wedding and person 5 decides to send you their complete images, you then have to go through the exercise again, to ensure you have images named chronologically correct.

Sep 16, 2016 9:41 PM in response to OMG-Really

Bump.


Has anyone yet found a convenient way to fix this sort of thing? I've got a mix of pictures from three different sources - my iPhone, my digital camera, and a friend's digital camera. All were "correctly" set for local date settings, in this case west coast North America. In Photos for El Capitan, they all display the correct "local" time when the photo was taken (although in Photos for iOS 10, they display the incorrect time). However, all the photos taken with the iPhone SE are time-shifted to match what the time was in my "home" time zone (East Asia) and wind up massively out of order (about 15 hours later). This is really messing up Moments and the automated slideshows that, while a nice feature of iOS 10, have made this bug more annoying.


I'm hoping something will improve in Sierra in a few days, but is there any relatively easy way to do this now? I'm wondering about somehow getting the photos off my iPhone and on to my desktop without going through the Photos app, but I'm not sure if that's even possible. (That'd also be a good way to give the photos useful file names, but I guess it might kill the Live Photos feature.)

Dec 28, 2016 2:28 AM in response to Lost in Asia

This has been bugging me for ages too since working on my vacation photos a couple of months back. But I've finally out how to fix it. I've documented it on my blog here: https://www.atpeaz.com/fix-photos-out-of-chronological-order-in-albums/ (so that I remember). But essentially, it's to use the Photos app's Adjust Date and Time feature to change the timezone WITHOUT changing the date and time itself.

Metadata in different time zones - nightmare

Welcome to Apple Support Community
A forum where Apple customers help each other with their products. Get started with your Apple Account.