Understanding Differences Between WGS84 & UTM-K Coordinate Systems

When you copy coordinates from a mobile map app, you get familiar latitude and longitude numbers like 37.5665, 126.9780. Yet when you download official government spatial datasets or municipal facility registries in South Korea, the coordinate columns often contain large six- and seven-digit numbers like 953901, 1952032. Both pairs point to the exact same spot—Seoul City Hall—but they are expressed in different Coordinate Reference Systems (CRS). Mixing them up without proper transformation plots your markers in the middle of the ocean. This article compares the two coordinate systems you will encounter most often in Korean location services—WGS84 (EPSG:4326) and UTM-K (EPSG:5179)—with concrete conversion examples and common developer pitfalls.

1. Two Foundational Concepts: Datum & Projection

Reference Ellipsoid and Geodetic Datum

Because centrifugal force from Earth's rotation causes the equator to bulge outward, Earth's equatorial radius (~6,378.1 km) is about 21.4 km longer than its polar radius (~6,356.8 km). Geodesy approximates this oblate shape mathematically using a smooth reference ellipsoid, and combines the ellipsoid with an anchor origin and orientation relative to Earth's crust/center of mass to define a geodetic datum.

Geographic CRS vs. Projected CRS

• Geographic Coordinate System: Expresses positions on the 3D ellipsoid surface using angular measurements—latitude ($\phi$) and longitude ($\lambda$) in degrees.
• Projected Coordinate System: Mathematically flattens the curved ellipsoid onto a 2D plane and expresses positions as linear $(X, Y)$ distances in meters from a defined origin. Planar meter coordinates make Euclidean distance and area calculations straightforward, though every projection introduces controlled distortion (covered in detail in Map Projections & the KMA LCC Grid).

2. WGS84 (EPSG:4326): The Global Standard for GPS & Web APIs

WGS84 (World Geodetic System 1984) is the global geocentric datum maintained for the GPS satellite constellation. Its origin sits at Earth's center of mass, and it is the universal default used by the browser HTML5 Geolocation API, iOS/Android location services, and the GeoJSON specification (RFC 7946). In GIS software and coordinate libraries like PROJ, standard WGS84 latitude/longitude is identified by the code EPSG:4326.

Taking Seoul City Hall as an example:

• Decimal Degrees (DD): Latitude 37.5665° N, Longitude 126.9780° E
• Degrees, Minutes, Seconds (DMS): 37° 33′ 59.4″ N, 126° 58′ 40.8″ E

While 1° of latitude corresponds to roughly 111 km everywhere on Earth, the east-west distance of 1° of longitude shrinks with the cosine of latitude ($\cos(\phi)$)—measuring about 88 km at Seoul's latitude (37.5° N) and 0 km at the poles. Consequently, you can never compute real-world distance by simply taking $\sqrt{\Delta\text{lat}^2 + \Delta\text{lon}^2}$ in degrees.

How Much Precision Does Each Decimal Place Represent?

Knowing the ground resolution of decimal degrees helps you choose the right database column precision and avoid storing meaningless noise:

Decimal Places	Degree Increment	Approx. Ground Distance (Latitude)
2 decimal places	0.01°	~1.11 km (neighborhood scale)
3 decimal places	0.001°	~111 m (city block scale)
4 decimal places	0.0001°	~11.1 m (building / street width)
5 decimal places	0.00001°	~1.11 m (consumer GPS limit)

Because smartphone GPS accuracy is typically 3 to 15 meters outdoors, storing more than 5 or 6 decimal places in a standard web application rarely reflects real physical precision.

3. UTM-K (EPSG:5179): Korea's Unified Planar Coordinate System

The international Universal Transverse Mercator (UTM) system slices the globe into sixty 6°-wide longitudinal zones. Unfortunately, the Korean peninsula straddles the seam right down 126° E—splitting the country between UTM Zone 51N (120°–126° E) and UTM Zone 52N (126°–132° E). To avoid stitching two separate coordinate zones across nationwide maps, South Korea defined a single nationwide planar coordinate system centered on the peninsula: UTM-K, officially registered as KGD2002 / Unified CS (EPSG:5179).

When we transform Seoul City Hall (37.5665° N, 126.9780° E) into EPSG:5179, we get approximately Easting $X = 953,900\text{ m}$, Northing $Y = 1,952,030\text{ m}$. Subtracting the false origin (`1,000,000`, `2,000,000`) immediately tells us that Seoul City Hall sits roughly 46.1 km west (`-46,100 m`) and 48.0 km south (`-47,970 m`) of the (38° N, 127.5° E) central origin.

4. How Different Are the WGS84 and GRS80 Ellipsoids?

Prior to the 2000s, older Korean maps used the Tokyo Datum based on the 1841 Bessel ellipsoid—which is offset from modern GPS coordinates by roughly 300 to 400 meters! Modern Korean standards (KGD2002) switched to the GRS80 ellipsoid, whose semi-major axis (`6,378,137.0 m`) is identical to WGS84 and whose polar semi-minor axis differs by only 0.1 millimeters. For consumer web maps, weather apps, and public facility locators, WGS84 and GRS80 ellipsoid surfaces agree within centimeters. However, if a legacy dataset uses the old Bessel ellipsoid (such as EPSG:5174), you must apply a 7-parameter Helmert or grid shift transformation or your pins will land 350 meters away.

Transforming Coordinates Reliably in Code

Rather than hand-coding series expansions for Transverse Mercator ellipsoidal equations, always use battle-tested libraries such as PROJ (`proj4js` in JavaScript/TypeScript, `pyproj` in Python, or PostGIS `ST_Transform`) with explicit EPSG codes (`EPSG:4326` ↔ `EPSG:5179`), and sanity-check your output against known landmarks like Seoul City Hall.

5. Side-by-Side Summary

Attribute	WGS84 (EPSG:4326)	UTM-K (EPSG:5179)
CRS Type	Geographic (3D Spherical/Ellipsoidal Angles)	Projected (2D Planar Cartesian Grid)
Unit of Measure	Degrees (°)	Meters (m)
Reference Ellipsoid	WGS84	GRS80
Coverage Area	Worldwide	South Korea (Nationwide Single Zone)
Primary Use Cases	GPS receivers, HTML5 Geolocation, Web Map SDKs	National GIS databases, Government Open Data portals

6. Five Common Mistakes When Working with Coordinates

• Swapping `[latitude, longitude]` and `[longitude, latitude]`: Everyday conversation and Google Maps URLs use `(lat, lon)`, whereas GeoJSON, PostGIS `ST_MakePoint(x, y)`, and `proj4` strictly expect `[longitude, latitude]` (`[X, Y]`). For South Korea, latitude is always in the `33–38` range and longitude is in the `124–131` range.
• Confusing Surveying $(X, Y)$ with Mathematical $(X, Y)$: In Korean civil surveying standards, $X$ traditionally denotes Northing (vertical) and $Y$ denotes Easting (horizontal)—the exact opposite of computer graphics and GIS software! Always verify whether a government CSV column labeled `X` holds a `950,000` (Easting) or `1,950,000` (Northing) value.
• Storing raw numbers without recording the EPSG code: Korea uses multiple planar projections (`EPSG:5179` UTM-K, `EPSG:5186` Central Belt 2010, `EPSG:5174` legacy Bessel). Always document the CRS alongside the data.
• Measuring ground distance directly in Web Mercator (`EPSG:3857`): Web map tiles use `EPSG:3857`, which stretches distances by $\sec(\phi)$—inflating distances around Seoul by ~1.26×. Use `EPSG:5179` or the Haversine/geodesic formula for true distance.

7. Summary

WGS84 (`EPSG:4326`) represents global positions as angular latitude/longitude degrees, while UTM-K (`EPSG:5179`) projects the Korean peninsula onto a single meter-based plane with a false origin of `(1,000,000, 2,000,000)`. Keeping EPSG codes, axis order (`lon, lat` vs `lat, lon`), and datum definitions explicit prevents every common coordinate bug.

To see how HereWeather obtains your device's WGS84 coordinates and converts them into the Korea Meteorological Administration's 5 km forecast grid, read our companion articles on HTML5 Geolocation API Accuracy Limits and Map Projections & the KMA LCC Grid.

References

• EPSG:5179 - Korea 2000 / Unified CS (UTM-K)
• EPSG:4326 - World Geodetic System 1984 (WGS84)
• National Geographic Information Institute (NGII) of Korea