Repository navigation
A free browser-local Takeout sidecar/date checker — looking for real-export feedback #492
Replies: 1 comment 1 reply
|
I don't have a real-export result to report, but one small synthetic regression set may help the date report: conflicting filename and JSON dates, a valid leap day versus an invalid one, and I'd also separate a missing timezone from a confirmed UTC instant so a report doesn't label a same-photo/different-local-day case as a repairable date error without enough evidence. I maintain DateParser Kotlin. Its explicit date-order and invalid-input behavior offers comparison cases, not a Takeout/EXIF repair implementation. If that small corpus is useful for the checker, a repository star would be appreciated. |
Uh oh!
There was an error while loading. Please reload this page.
LaunchTrace Takeout Check is a small read-only prototype developed by Hongyang and an AI coding agent. This introduction is AI-assisted too. Sharing a companion experiment here, not an official GPTH feature.
It checks an extracted Google Photos Takeout folder in your browser and lists filename/JSON
photoTakenTimematches, unmatched sidecars, ambiguous filenames and conflicting dates. CSV, JSON and HTML reports are available. It reads filenames and JSON locally; it does not open photo contents, upload files or modify originals.Try it: https://launchtraceqa.com/check/ — a synthetic demo is available first. Desktop Chrome/Edge recommended. If you have an existing export, start with a small representative subfolder.
Limits: no EXIF checks, date repair or proof of export completeness. Truncated-name hints remain manual-review hints, not restored dates. It cannot fix every GPTH matching failure or replace GPTH/immich-go. Free, no account or payment required.
We are looking for independent real-export feedback: does the report reveal a useful unresolved case, or do existing free tools already cover it? Which step remains difficult? Approximate totals and a description of the problem are enough. Please do not post photos, reports, personal filenames, links to private exports or credentials. A synthetic example is fine if you want to illustrate a naming pattern.
This is an early prototype, not a claim of customer-tested reliability. If this category is unsuitable, we will withdraw the post rather than repeat it elsewhere in the repository.
All reactions