Location Data Converter (GPX, KML, CRS)
Convert between GPX, KML and GeoJSON, transform WGS84 and Korean TM / UTM-K coordinates, switch coordinate notations, and compute distance and bearing. Files and coordinates never leave this browser.
Location files often reveal where you live and work. This tool never uploads them — files are read and converted only inside this browser.
Open a file or paste its contents; the format is detected and converted. Waypoints, tracks/routes and polygons are supported.
One coordinate per line. For WGS84 use "37.5663, 126.9779" or "37°33'58.7"N 126°58'40.4"E"; for projected systems use "x y" in meters. Up to 2,000 lines.
Notations of the first coordinate
Korea 2000 (GRS80) and WGS84 differ by centimeters to decimeters and are treated as equal. Legacy Bessel-based TM (EPSG:5174 etc.) needs a 7-parameter transform and is not supported. Calculations use a transverse Mercator series (Krüger), checked at the origins and against an independent implementation.
Enter one latitude/longitude per line to get leg and total distances; with two points you also get bearings and the midpoint. Degree-minute-second notation works too.
| # | Distance | Bearing |
|---|
Distance is the geodesic on the WGS84 ellipsoid (Vincenty). Bearing is the initial bearing (north = 0°, clockwise); the midpoint is spherical.
Everything runs in this browser and nothing is stored. XML is read by our own parser that ignores DOCTYPE and external entities, so no external file is ever accessed.
FAQ
Is GPX time data lost?
Converting GPX to GeoJSON keeps track times in properties.times, and converting back to GPX restores them. KML has no such concept, so times are dropped there.
What happens to polygons in GPX?
GPX has no polygons, so outlines are exported as closed tracks. Holes become separate tracks.
Which coordinate system do Naver and Kakao use?
Naver Maps uses WGS84 lat/lon or UTM-K (EPSG:5179). Kakao Maps defaults to WGS84 lat/lon; legacy KATEC coordinates are not supported here.