Home / Coordinates and Location Formats

How to Find the Coordinate System of a File or Dataset: The Digit Test and the EPSG Registry

Earth seen from space, continents against a dark backdrop

Photo: Zelch Csaba / Pexels

Every GIS professional inherits the same haunted file sooner or later: a spreadsheet, a shapefile, a CSV of points, thousands of coordinate pairs, and no note anywhere about what the numbers mean. Open it in software with the wrong assumption and the points land in the ocean, or in the wrong hemisphere, or, worst of all, almost in the right place, off by a distance small enough to survive review and large enough to matter. The good news is that coordinate systems leave fingerprints all over their numbers, and a short procedure, the one support teams at firms like Esri teach for exactly this case, identifies most files in minutes. This guide works that procedure in order, from the digit test you can do with your eyes to the registry lookup that names the system exactly. The tool above shows the friendly end of the spectrum: click a place and read a pair in degrees, the geographic form the first test looks for.

Interactive map

Coordinate Explorer: Read a Pair and Name Its System

Click a place and read the pair it reports. Small numbers with decimals are degrees in a geographic system; the digit test in this article starts from exactly that observation.

Decimal degrees40.689167, -74.044444
Latitude40.689167° N
Longitude74.044444° W
Degrees minutes seconds40° 41' 21.00" N, 74° 02' 40.00" W
Degrees decimal minutes40° 41.350' N, 74° 02.667' W
Plus code87G7MXQ4+M67

Map data © OpenStreetMap contributors. Coordinates are read from the map itself, in the WGS 84 system your phone uses.

Step One: The Extent Digit Test

Open the data and look at the largest absolute values in each column. The digits left of the decimal point sort nearly every file into its family at a glance. Geographic systems (latitude and longitude in decimal degrees) are bounded by the planet: longitude runs from minus 180 to 180 and latitude from minus 90 to 90, so you will never see more than three digits left of the decimal, and the values carry long decimal tails. Pairs like 40.689167, minus 74.044444 are geographic on sight. Projected systems measure in meters or feet from a local origin, so their coordinates are large: UTM eastings and northings, State Plane values, and national grid coordinates typically run six to eight digits left of the decimal, like 583,960 and 4,506,780. Local or engineering systems sit in between, often three to five digits, measured from a site origin that exists only in the project's documents. Read the extents first and write down the family before touching any software: degrees, projected, or local. Half of all identification work is finished in this one look, and it is the same instinct as reading a pair's shape in our coordinate notation guide, one level up.

Step Two: Units and Zone Logic

Within the projected family, narrow by magnitude and meaning. UTM (Universal Transverse Mercator) covers the Earth in 60 zones, each 6 degrees of longitude wide, and its coordinates obey strict ranges: eastings run roughly 100,000 to 900,000 meters (the zone's central meridian is assigned a false easting of 500,000) and northings run 0 to about 9,300,000 in the northern hemisphere. A pair like 583,960 E, 4,506,780 N is a UTM fingerprint; the zone is the remaining unknown, and it comes from geography: the file's subject matter sits in exactly one zone, and Zone 18N holds New York while Zone 30N holds London and Paris's longitude band. State Plane coordinates in the United States are in feet in many states (meters in some), which produces eastings that can exceed a million and a distinctive feel: values too big for UTM in a US dataset are State Plane until proven otherwise. National grids, Britain's OS grid and its cousins, carry their own ranges and often arrive as grid references rather than raw pairs, the subject of our grid reference guide. At this step you are not naming the system; you are building the shortlist the next steps confirm.

Step Three: Read the Files That Travel With the Data

Datasets rarely travel alone, and their companions confess. A shapefile's .prj file is a plain text declaration of the coordinate system in well known text; open it in any text editor and it names the projection, the datum, and the units outright. Our what is a shapefile guide explains the sidecar files, .prj included. GeoJSON is simpler: by specification its coordinates are longitude and latitude in WGS84 decimal degrees, always, so a .geojson file's system is known before you open it, a fact our GeoJSON guide states as the format's founding rule. Metadata files (.xml sidecars, README files, data dictionaries) from government and academic sources declare the system in their spatial reference sections. CSV files confess through their headers: columns named lat and lon, or x and y with a project name, or easting and northing, each narrowing the family. And the source is evidence: data downloaded from a national portal follows that portal's documented standard, and the download page, not the file, is where the declaration lives. Check the companions before the registry; the answer is usually already in the folder.

A vibrant view of Earth from space
A vibrant view of Earth from space

Step Four: Name It Exactly in the EPSG Registry

A family and a zone are not yet an identity. Coordinate systems are catalogued, with codes, in the EPSG registry, searchable at epsg.io, which holds more than 10,000 registered systems and is the industry's phone book. The codes you will meet constantly: EPSG:4326 is WGS84 geographic, the latitude and longitude of GPS and GeoJSON. EPSG:3857 is Web Mercator, the projection of web maps, whose coordinates are meters but distorted, a classic misidentification because its values look like a national grid's. EPSG:326xx and 327xx are the UTM zones, 326 for northern hemisphere zones 1 to 60 (32630 is Zone 30N) and 327 for southern. Search the registry by the place and the family your tests produced ("UTM 18N", "British National Grid" is EPSG:27700) and read the registry's extent and unit notes against your file's numbers. Software asks for these codes when you define a mystery file's system, and giving it the code, rather than a similar sounding name, is what makes the definition exact and repeatable. Our convert latitude and longitude to UTM guide shows the code family in action from the conversion side.

The Datum Trap: Same Projection, Wrong Century

The most dangerous misidentification is the near miss. Two files can share a projection, UTM Zone 18, say, and still disagree by tens to over a hundred meters because their datums differ: the datum is the model of the Earth's shape and position that the coordinates are anchored to. North America's working datums are NAD83 (current, aligned closely with WGS84 for most purposes) and NAD27 (the older survey, still present in historical data), and the shift between them across the continent runs from a few meters to well over 100 meters depending on location. A NAD27 file defined as NAD83 does not land in the ocean; it lands on the wrong parcel, the wrong side of the road, which is why datum errors survive casual checks. The digit test cannot save you here, because the numbers look identical in form. The defenses are provenance (know the data's era and source), the .prj and metadata (which name the datum explicitly), and suspicion of any dataset older than the mid 1980s that arrives without papers. When two layers disagree by a suspiciously uniform offset, think datum before you think error.

The Procedure, Compressed, and What to Do With a Local System

Compressed, the identification runs: read the extents and apply the digit test (three digits or fewer with long decimals means geographic degrees; six to eight means projected meters or feet; in between means local). Check the companions (.prj, metadata, headers, the source portal's documentation). Apply zone and unit logic to shortlist candidates. Confirm the exact identity and datum at epsg.io and record the EPSG code with the file forever. Then, and only then, tell your software what the file is, using the define projection operation, which labels the numbers without changing them, rather than a conversion, which changes them and will corrupt a mislabeled file further. The local system case deserves its honest paragraph: site grids from engineering and archaeology, with small coordinates and no registry entry, can only be identified from project documents or by control points, places whose real coordinates you know and can match to the file's pairs. Two or three control points let you build the bridge to a known system; zero control points means the file is a map of a private world, and the professional move is to say so rather than guess. Identification is a chain of evidence, and the chain's strength is that each link can be checked. When you state a file's system, state the evidence with it: extents, companions, code. The next inheritor of the file will thank you, and they are probably you, in eighteen months, having forgotten everything.

Related Guides

If this page answered part of the question, these coordinates guides cover the rest of the same ground:

Frequently Asked Questions

How can I tell if coordinates are latitude and longitude or a projected system?

Apply the digit test. Latitude and longitude in decimal degrees never exceed three digits left of the decimal point (longitude tops out at 180, latitude at 90) and carry long decimal fractions. Projected coordinates in meters or feet run to six, seven, or eight digits left of the decimal. The extents of the file settle the family at a glance.

What is an EPSG code and where do I look one up?

An EPSG code is the registry number of a coordinate system in the EPSG Geodetic Parameter Dataset, searchable at epsg.io, which catalogues more than 10,000 systems. EPSG:4326 is WGS84 latitude and longitude; EPSG:32630 is UTM Zone 30N. Software uses these codes to define a dataset's system exactly.

My file has a .prj sidecar. What does it tell me?

Everything, usually. The .prj file is a plain text declaration of the shapefile's coordinate system: projection, datum, and units in well known text format. Open it in a text editor and read it before any other test; it outranks inference from the numbers.

Two datasets in the same projection still do not line up. Why?

The classic cause is a datum mismatch: same projection, different datum, such as NAD27 versus NAD83 in North America, which shifts positions by a few meters to over 100 meters depending on location. Check each file's datum in its .prj or metadata. A uniform offset between layers is the signature.

What if the coordinates are small numbers that match no known system?

You likely have a local or site grid, measured from a project specific origin. Such systems are not in the EPSG registry. Identify them from project documentation or by control points: locations whose real world coordinates you know, matched against the file's pairs, which let you relate the local grid to a known system.

Photo credits: Zelch Csaba (Pexels); Zelch Csaba (Pexels). Photos are served from this site; follow the credit to the library page for the original.