they were shared with me or imported into the library by other means, and the source did not include a timestamp in the EXIF metadata) My guess is that these images originated from other sources (e.g. Whilst most of my images contained reasonable EXIF timestamps for the time they were taken (written by the phone's camera), a small number did not.Instead, Google's metadata comes out in the accompanying JSON files. EXIF / IPTC) in the image files is not updated if changes are made within Google Photos, for example if the dates are updated using the Google Photos UI. From what I can tell, the embedded metadata (e.g.For an image named IMG123.jpg, sometimes you get but sometimes it's just IMG123.json The naming convention for the JSON files seems inconsistent and has some interesting edge cases.In the case that the export was split across multiple zips, I'm not sure whether there is any guarantee that the images & JSON files will always be co-located within the same export The date based folders don't always contain perfect pairs of images and JSON files, sometimes you get JSON files without a corresponding image. ![]() The JSON sidecar files include, amongst other things, a useful photoTakenTime property. These folders contain a mixture of image files and JSON metadata files. Each zip contains folders for certain dates and/or album names.There are some interesting challenges to note here: populate the DateTimeOriginal field in the EXIF metadata if this field is not already setĪt the time of writing (October 2020), Google Takeout provides you with one or more zip files, structured in a way that is fairly unintuitive and tricky to make use of directly.Įxtracting the zip, you might find something similar to this:. ![]()
0 Comments
Leave a Reply. |