Parse image GPS EXIF

Image metadata often stores a location as four separate GPS EXIF tags rather than as familiar decimal coordinates. This parser accepts the latitude and longitude degrees, minutes, and seconds arrays together with their reference letters, validates the raw values, and returns signed decimal latitude and longitude. It gives developers, archivists, investigators, and photo workflow teams a small deterministic conversion step that can sit directly after an EXIF reader. North and east become positive values, while south and west become negative values.

Map the raw GPS EXIF tags to the input fields

EXIF represents a photographed location using GPSLatitude, GPSLatitudeRef, GPSLongitude, and GPSLongitudeRef. The first and third tags usually arrive from an EXIF library as three numeric values in degrees, minutes, and seconds order. Send those arrays as latitude and longitude.

For example, a camera may report latitude values of forty, twenty-six, and forty-six point eight with an N reference, plus longitude values of seventy-nine, fifty-eight, and fifty-six point four with a W reference. Do not insert a negative sign into the DMS arrays: the reference tag supplies the sign. Lowercase references are normalized to uppercase, which helps when metadata libraries vary in presentation.

Each array must have exactly three finite numbers. Minutes and seconds must both be at least zero and less than sixty. Latitude degrees cannot exceed ninety, longitude degrees cannot exceed one hundred eighty, and a coordinate exactly on either maximum must have zero minutes and seconds.

These checks distinguish valid raw EXIF coordinates from malformed metadata before the result enters a map, database, or geospatial index. The tool expects already extracted tags; it does not decode an uploaded image itself, so pair it with the EXIF reader used in your application.

Understand the conversion and reference validation

For each axis, the parser computes a magnitude by adding degrees, minutes divided by sixty, and seconds divided by thirty-six hundred. It then applies the direction encoded by the corresponding reference. N keeps latitude positive and S makes latitude negative.

E keeps longitude positive and W makes longitude negative. Reference validation is intentionally strict. A latitude reference must be N or S, and a longitude reference must be E or W.

The response includes normalized reference letters and the original validated DMS arrays alongside the two decimal numbers, making it easy to audit a batch conversion. All operations are deterministic arithmetic with no network request, clock, random input, or external model.

Use decimal coordinates safely in photo workflows

Once converted, latitude and longitude can be written to GeoJSON, shown on a map, indexed for proximity search, or compared with location records from another system. Keep the pair together and preserve its axis order: this response names latitude first and longitude second, while some geometry formats represent a point as longitude followed by latitude. Retaining the normalized references and DMS arrays can make migrations easier to review, especially when a collection contains images from both hemispheres.

Treat missing or invalid tags as data-quality events instead of replacing them with zero, because zero latitude and zero longitude is a real point in the Gulf of Guinea. The parser also rejects non-finite values, incomplete arrays, out-of-range components, and impossible values beyond the poles or antimeridian. It does not verify that the camera truly occupied the reported position, account for GPS datum differences, or inspect privacy implications.

Before publishing photos, consider whether exposing precise coordinates is appropriate; GPS metadata can reveal homes, workplaces, or sensitive natural sites.