
A movie's top-level location field and its timed GPS records are different metadata objects. Use ExifTool's supported embedded-record extraction when investigating a recorded route. A plain container summary can miss the timed samples even when the format contains them.
Decide whether you need a location or a track
A single coordinate describes one stored position. A sequence of time-associated samples can describe changing positions during a recording. Do not turn the first coordinate found in a movie into a claim about its entire route.
Keep the original local and authorized for inspection. A route can disclose more than a single photograph's location. The pre-share location review is useful context, but a still-image GPS check does not inspect every embedded video record.
Start with a grouped read of relevant fields:
exiftool -a -G1 -s "-GPS*" sample.mp4
Record what this ordinary read reports. Do not add a write assignment while investigating.
Read supported embedded records
For the same file, request:
exiftool -ee -a -G1 -s "-GPS*" sample.mp4
ExifTool's application documentation describes -ee as extraction from supported embedded documents or records. Support depends on the recording format and device data. Some sources require more extensive parsing documented under that option; do not assume the first setting covers every camera.
The official command examples also show extracting timed GPS values from supported video data. This supports an inspection route, not a guarantee that any MP4 or dashcam file contains GPS.
Inspect time associations before building a route
Look for repeated samples and their actual time fields. Keep each coordinate connected to its reported sample time and group. A flattened list of latitudes alone is not a validated track.
If preparing a text export, explicitly choose the fields and inspect missing values. Do not silently interpolate a new path merely because some records lack coordinates. Confirm the time basis before comparing a route to the visible action.
For a hypothetical driving clip, a useful check compares several recognizable route points with the corresponding recorded events. This is a proposed consistency check, not a tested recording or a guarantee of geographic accuracy.
Interpret an empty result conservatively
If no timed records appear, check the exact file format and documented parser support. The recorder might store telemetry in another companion file, omit it from this export or use an unsupported representation. “ExifTool did not report samples through this route” is more accurate than “the camera never recorded GPS.”
Likewise, visible embedded records do not mean a later editor preserves them. Stream and metadata handoff decisions remain separate.
The artifact for this task is a scoped timed-metadata report with source identity, extraction options and unresolved support limits. It is not newly geotagged media, proof of a person's whereabouts or a certified reconstruction of every moment in the recording.
Related tasks
- How Do I Check a Photo for Location Metadata Before Sharing It?
- How to Preserve or Set Metadata, Chapters, and Audio Language When Remuxing with FFmpeg
Sources and scope
- ExifTool Command-Line Examples (official repository): Official examples show binary ICC extraction to .icc and embedded GPS extraction with -ee.
- ExifTool Application Documentation: CSV identity uses SourceFile; list separators and append differ from scalar strings. The -o, -if, -b, -w, -struct and backup utility options have explicit scopes.
Documentation-based guidance researched on 23 October 2026 (Asia/Shanghai), with proposed checks rather than reported application tests. RawPedia and digiKam manual pages were opened or returned readable official body text. ExifTool official pages were readable through public search; direct PDF/XMP tag-reference fetches returned HTTP 403. Verify installed-version controls, metadata representations and receiving-reader behavior. Decorative cover assets do not depict software or a test result.
Prepared by Imagild Editorial, the company editorial team responsible for these guides. AI assisted research and drafting. This is documentation-based guidance with proposed examples, not a claim of hands-on testing or an independent product review. Report a correction.
Cover: Mariya Eskina / Pexels, Pexels License. This is an illustrative source photograph, not an application screenshot or a generated test result.