
For a map table, export signed Composite latitude and longitude rather than assuming raw EXIF coordinate magnitudes include their hemisphere signs. Then check the receiving system's axis order and missing-value policy. Numeric output alone does not prevent a western location from being placed in the east.
Inspect magnitudes and reference directions
Read the actual metadata with groups visible:
exiftool -a -G1 -s "-GPS*" sample.jpg
EXIF stores the coordinate magnitude and hemisphere reference separately. The Composite tag reference lists latitude and longitude derived from those pairs.
Do not discard an S or W reference just because a spreadsheet column expects a number.
Export the intended derived values
For a photo with supported EXIF GPS data, a proposed read-only CSV request is:
exiftool -csv -n -FileName -Composite:GPSLatitude -Composite:GPSLongitude sample.jpg
Save the text through an appropriate text-output route. Inspect the CSV header and the actual selected fields rather than silently renaming a different value to “latitude.”
The application coordinate-format documentation describes numeric extraction. Explicit Composite selection makes the hemisphere dependency clear for this EXIF-based task.
If the file contains only another location representation, inspect that format's fields instead of assuming this exact query covers every movie or image.
Test known hemispheres and column order
Use an authorized sample whose approximate location and hemisphere are independently known. Confirm negative latitude for south and negative longitude for west where applicable.
A hypothetical coordinate pair can be arithmetically valid in the wrong order. The table may say latitude then longitude, while a receiving GIS interface expects x then y. Follow the receiver's documented column assignment; do not infer it from the word “coordinates.”
Also test a file with no location. Do not replace a missing coordinate with zero, which is a real position rather than a universal missing-data marker.
Keep extraction separate from geotagging
This table reports stored or derived coordinates; it does not write a new position or prove where the photograph was taken. If the source coordinates are doubtful, investigate tracklog time matching before exporting a larger table.
For public use, apply the location-data sharing review. A technically correct table can expose a private route.
The proposed acceptance artifact is an identified source-to-row table with correct signs, known column order and explicit missing values. No map import or coordinate extraction was tested here. Retain the source group and conversion choices so another person can reproduce the numeric interpretation.
Related tasks
- Lightroom GPX Auto-Tagging Misses Photos: Check the Tracklog Time Offset
- How Do I Check a Photo for Location Metadata Before Sharing It?
Sources and scope
- ExifTool Application Documentation: Application -n numeric extraction and coordinate-format behavior; CSV output field selection. Composite namespace is selected explicitly for coordinates derived from EXIF magnitude/reference pairs.
- Composite Tags: Composite GPSLatitude and GPSLongitude derive from coordinate/reference-direction pairs, unlike unsigned EXIF magnitudes.
Official-documentation synthesis researched on 23 October 2026 (Asia/Shanghai). Readable official deep-page text was obtained through public search; direct ExifTool fetches may return HTTP 403. No configuration, file edit, coordinate export or geotagging test was executed. Namespaces, paths, ASCII trial text, coordinates, dates and thresholds are explicitly illustrative. This article relies on the readable Composite and application documentation; forum attribution is omitted because a direct forum capture was an unavailable-page placeholder. The separately retained public web forum cache is not needed for the cited recipe. Exact installed-version and receiving-system behavior require the stated acceptance checks.
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.