TheLastGimbus/GooglePhotosTakeoutHelper

Files with paranthesis e.g. (1) have differently named JSON files and titles

rizz360 opened this issue · 8 comments

rizz360 commented

I have the following files:

  • IMG_4081(1).jpg
  • IMG_4081.JPG(1).json

Notice how not only the 'jpg' is uppercase for the json (fixed #46) but also the (1) is placed in the wrong location. To bring this one step further, this is the content of the json:

{
  "title": "IMG_4081.JPG",
  "description": "",
  "imageViews": "0",
  "creationTime": {
    "timestamp": "1432899863",
    "formatted": "May 29, 2015, 11:44:23 AM UTC"
  },
  ...
}

The title does not have the (1) at all. A big portion of my library has this issue. Is there something wrong with my export or is this yet another annoyance in takeouts?

To be clear, this happens with files that are not duplicates but probably just happened to have the same name upon upload.

Just look at this fun mess:
image

hump commented

Same issue here...

Final statistics:
Files copied to target folder: 6666
Removed duplicates: 0
Files for which we couldn't find json: 949

rizz360 commented

Since #60 has been merged, this can be closed.

TheLastGimbus commented

Hey @hump, I just pushed a release that should fix it - can you pip install -U ... and compare how many json not founds you have?

hump commented

my results with latest 2.2.0

Final statistics:
Files copied to target folder: 6666
Removed duplicates: 2
Files for which we couldn't find json: 896

e.g.:
image


{
  "title": "Datei_Aufnahmeblatt 4756-2b Hütteldorf, Dornbach.jpg",
  "description": "",
  "imageViews": "0",
  "creationTime": {
    "timestamp": "1514722370",
    "formatted": "31.12.2017, 12:12:50 UTC"
  },
  "modificationTime": {
    "timestamp": "1609432770",
    "formatted": "31.12.2020, 16:39:30 UTC"
  },
  "photoTakenTime": {
    "timestamp": "1244148605",
    "formatted": "04.06.2009, 20:50:05 UTC"
  },
  "geoData": {
    "latitude": 0.0,
    "longitude": 0.0,
    "altitude": 0.0,
    "latitudeSpan": 0.0,
    "longitudeSpan": 0.0
  },
  "geoDataExif": {
    "latitude": 0.0,
    "longitude": 0.0,
    "altitude": 0.0,
    "latitudeSpan": 0.0,
    "longitudeSpan": 0.0
  },
  "googlePhotosOrigin": {
    "mobileUpload": {
      "deviceFolder": {
        "localFolderName": ""
      },
      "deviceType": "ANDROID_TABLET"
    }
  }
}

BTW: nice progress bar with ETA :)

TheLastGimbus commented

Ookaay, so it did help some 🚀 ! For the rest, I tried looking, and some photos just literally have no exif at all, so there isn't much to do 😕

Edit for you edit: Like... you see what happens here 😖 there is no way for us to connect those two...

  • 👍1
hump commented

most images, which have no json, are edited images...

rizz360 commented

I also noticed that iOS live photos are all kinds of messed up. The moving part of the live photos is exported as a corrupted ...(1).heic with the same base name as the static image. Changing the extension to .mov makes it a playable video.

TheLastGimbus commented

I am seconds from filling a lawsuit at Google for not complaining at GDPR properly...