Understanding GIS Coordinate Systems (EPSG) — 4326 vs. Local Projections, Explained
Coordinate systems are the single most common sticking point when people first work with GIS. "I opened a Shapefile and the data showed up somewhere off the coast of Africa," or "the area calculation looks way off" — 90% of the time, the root cause is the coordinate system. Building GISDirect and hearing from users, this is by far the most frequent topic. So let's get the concept solid.
Why do we need a coordinate system at all?
The Earth is round; a map is flat. To represent a point on that curved surface with two numbers, you need an agreed-upon reference for how you're measuring it. That agreement is the coordinate reference system (CRS). The same physical location can produce completely different numbers depending on which CRS you use to express it.
Coordinate systems fall into two broad families.
1. Geographic coordinate systems (latitude/longitude)
These keep the Earth's curved shape and express location as latitude and longitude, in degrees. The most common is EPSG:4326 (WGS84) — the same coordinate system GPS and Google Maps use. City Hall in Seoul sits at roughly latitude 37.566, longitude 126.978. It works anywhere on Earth, but because the unit is "degrees," it's not directly suited to measuring distance or area — the real-world distance covered by one degree changes depending on where you are.
2. Projected coordinate systems (meters)
These "unroll" the curved Earth onto a flat plane using a specific projection method, and express location in meters. In Korea, the most common are EPSG:5186 (Korea Central Belt TM) and UTM-K (EPSG:5179). Coordinates come out as large meter values, like "200000, 500000." If you need to measure distance or area accurately, you need a projected coordinate system like these.
What is an EPSG code?
There are thousands of coordinate systems in use worldwide, and describing each one in words every time isn't practical — so each was assigned an internationally recognized number. That's the EPSG code. The ones you'll actually run into most often:
| EPSG | Name | Unit | Typical use |
|---|---|---|---|
| 4326 | WGS84 (lat/lon) | degrees | GPS, web maps, data interchange |
| 3857 | Web Mercator | m | Google/web map tiles |
| 5186 | Korea Central Belt TM | m | Korean cadastral/survey data |
| 5179 | Korea UTM-K | m | Korean national mapping standard |
| 32652 | UTM Zone 52N | m | Satellite imagery (eastern Korea) |
"My data is in the wrong place" — a practical diagnosis
A Shapefile isn't actually a single file — it's a bundle of several. Among them, the .prj file carries the coordinate system definition. Here are the most common ways things go wrong:
- Missing .prj file: the software doesn't know the coordinate system and has to guess — positions end up wrong. Explicitly specifying the data's actual coordinate system fixes this.
- Meter coordinates read as lat/lon: reading "200000, 500000" as latitude/longitude puts the point off the edge of the Earth. The reverse mistake happens too.
- Axis order (lon/lat vs. lat/lon): some datasets store x/y in swapped order, which can flip a location to entirely the wrong side of a country.
Quick diagnostic: look at the raw numbers. If they're small decimals roughly between -180 and 180, it's likely lat/lon (4326). If they're large numbers in the hundreds of thousands, it's a meter-based projected CRS. Getting just this distinction right solves half of these problems.
Handling coordinate systems in the browser
Automatic coordinate system detection was one of the things I cared about most while building GISDirect — there's no reason a working professional should have to memorize EPSG codes. When you upload a file, it looks at the .prj (if present) together with the coordinate range to estimate the CRS, then converts to 4326 for display on the map and to an appropriate meter-based CRS for calculations, automatically.
Summary
- Use latitude/longitude (EPSG:4326) to express location; use a meter-based projected CRS (5186, 5179, etc.) to measure distance and area.
- An EPSG code is just an internationally standardized number for a coordinate system. Knowing 4326, 3857, and 5186 covers most real-world cases.
- If your data looks misaligned, first check whether a
.prjfile exists and look at the magnitude of the coordinate numbers. - You don't need to master this yourself — let the tool detect and convert, and just understand the underlying idea.