-
-
Notifications
You must be signed in to change notification settings - Fork 110
add support for icloud takeouts #822
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
supports albums and original creation dates. request copy of your data from: https://privacy.apple.com
defer file.Close() | ||
|
||
reader := csv.NewReader(file) | ||
records, err := reader.ReadAll() |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Can't be the file too huge to be read in memory?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looking at my own icloud takeout I see a lot of "Photo Details - n.csv" files. Non of them has more than 1500 lines. Its not clear to me what logic they apply for the splitting of the files but none of them are too big.
Nice proposal. IPhones are generating file name like IMG_1234.JPG. Inevitably we will have another IMG_1234.JPG. |
I dont know how they handle duplicates but looking at my own takeout it's a flat structure. Every asset (image & video) is in "Photos/", no subdirectories. So names must be unique |
I have seen many examples of duplicates names produced by the same iphone in the same year. The Photo details files contains a hash code for each photo. So, it could have duplicate names, and probably no duplicated checksum. Anyway, the albums files mention only the image name... not the checksum... We can chat directly on discord @simulot |
supports albums and original creation dates.
request copy of your data from: https://privacy.apple.com