GISela Coordinate Reprojection
Convert GeoJSON, KML, GPX, CSV or shapefiles between WGS 84, UTM, LV95, British Grid and more.
How it works
Reprojects vector data between coordinate systems with GISela’s own projection maths: WGS 84, ETRS89, Web Mercator, every UTM zone, ETRS89-LAEA, German Gauss–Krüger zones, Swiss LV95/LV03 and the British National Grid. Reads the coordinate system from .prj files and GeoJSON, and shows sample coordinates before and after.
- The data is read into WGS 84 longitude/latitude, then projected to the target system. Readers: GeoJSON (also the old “crs” member), TopoJSON (arcs decoded with the transform), KML/KMZ, GPX, CSV with coordinate or WKT columns, WKT and zipped shapefiles with .prj detection by EPSG authority, name or Transverse Mercator parameters.
- Transverse Mercator (UTM, Gauss–Krüger, British National Grid) uses Karney’s 6th-order Krüger series on the system’s own ellipsoid; ETRS89-LAEA uses the ellipsoidal Lambert azimuthal equal-area formulas of IOGP Guidance Note 7-2; LV95/LV03 use swisstopo’s rigorous oblique Mercator formulas; Web Mercator uses the spherical formulas on the WGS 84 radius.
- Datum changes (OSGB 1936, DHDN, CH1903/CH1903+) go through geocentric coordinates with a published 7-parameter Helmert transformation. ETRS89 is treated as equal to WGS 84 (well under 1 m in Europe).
- Outputs are rounded to 8 decimals for degrees and 3 decimals (millimetres) for metres.
Helmert datum shifts are good to about 1–5 m. For survey work use the national grid transformations (OSTN15, BeTA2007, FINELTRA).
Sources
- Transverse Mercator with an accuracy of a few nanometers (Karney 2011) (Journal of Geodesy 85)
- IOGP Geomatics Guidance Note 7-2: Coordinate conversions and transformations including formulas (IOGP)
- Formulas and constants for the calculation of the Swiss conformal cylindrical projection and for the transformation between coordinate systems (swisstopo)
- A guide to coordinate systems in Great Britain (Ordnance Survey)
- RFC 7946: The GeoJSON Format (IETF)
Part of GISela
-
GISela Browser GIS
A GIS in your browser: layers, attribute tables, styling, analysis and print layouts.
How to convert coordinates between WGS 84, UTM, LV95, British National Grid and Gauss–Krüger
Reproject GeoJSON, KML, GPX, CSV, WKT or TopoJSON from one coordinate system to another — with the datum shift named and a sample of converted points to check.
What it is for
Coordinates only mean something together with their coordinate system. A GPS gives longitude and latitude in WGS 84; a Swiss survey delivers LV95 metres (EPSG:2056), British data the National Grid (EPSG:27700), German data Gauss–Krüger or ETRS89 / UTM. This tool converts a whole file from one system to another and returns it as GeoJSON, CSV or WKT.
It reads GeoJSON (also with the older crs member), TopoJSON, KML/KMZ, GPX, CSV with coordinate columns or a WKT column, and WKT lines. The source system comes from the file where it can (crs member) or from the code you give. The same converter runs in the GISela app when you import and export layers.
Worked example
The second example converts five bus stops given in LV95 as a CSV with the columns stop;E;N;boardings. The first row is Bus Seefeld;2643240;1219692;640. With Coordinate system of the data set to 2056 and Convert to WGS 84, the tool reports:
Coordinates were converted from CH1903+ / LV95 (EPSG:2056) to WGS 84.
The sample table shows Bus Seefeld at 8.00850538° E, 47.12680389° N. Going the other way, the first example takes seven tram stops in WGS 84 to LV95: the stop Weiher at 7.992° E, 47.1215° N becomes E 2,641,991.811, N 1,219,093.400. The result also names the datum shift: a 7-parameter Helmert transformation from swisstopo, with a note that grid-based national transformations can differ by a few metres.
The third example takes the town's district polygons to ETRS89-LAEA (EPSG:3035), the equal-area system for European statistics: the first corner becomes E 4,168,367.201, N 2,669,452.313.
How to read the result
- From / To — the systems that were used, by name and EPSG code. Check From: a wrong source system is the most common mistake.
- Sample — the first converted points with input, WGS 84 and output values. Compare one with a known point.
- Datum — how the datum was changed. Projections are exact to the millimetre; the datum shift is good to about 1–5 m.
- Download — one file per layer (a GPX file can contain waypoints and tracks).
Tips and common mistakes
- Easting first. CSV columns are read as x = easting/longitude and y = northing/latitude. Columns named
lat/lon,E/N,x/y,easting/northingare found automatically. - Big numbers in "auto" mode. If the data is in metres but no system is given, the tool warns that the file is probably in a projected coordinate system — give its code and run it again.
- GeoJSON in a projected system is written with the old
crsmember. RFC 7946 only allows WGS 84, so some programs ignore it; prefer CSV or a shapefile for projected output. - UTM zones. Type the code under Or another EPSG code: 326xx for northern zones, 327xx for southern, 258xx for ETRS89.
- ETRS89 is treated as identical to WGS 84 — the difference is well under a metre in Europe today.
FAQ
Which coordinate systems are supported?
WGS 84, Web Mercator, all WGS 84 and ETRS89 UTM zones, ETRS89-LAEA, Gauss–Krüger zones 2 to 5 (DHDN), Swiss LV95 and LV03, and the British National Grid. Other codes are refused with a list of the supported ones.
How accurate is it?
The projection formulas (Krüger series to sixth order, IOGP and swisstopo formulas) agree with the official worked examples to the millimetre. Datum shifts use the published seven-parameter sets, which are good to one to a few metres; national grid files such as OSTN15 or NTv2 are not included.
Is my file uploaded?
In the GISela app nothing leaves the browser. Through this tool page or the API, the file is sent to the UsefulWeb server, converted in memory and not stored.
Guide last updated:
For scripts and AI agents
- JSON API:
POST https://giselareproject.usefulweb.app/api/v1/calculate(same calculation as this page) - Interface description: OpenAPI 3.1 · AI guide: llms.txt
- MCP server (Streamable HTTP):
https://giselareproject.usefulweb.app/mcp· tool namegisela_reproject
Example request
curl -s -X POST https://giselareproject.usefulweb.app/api/v1/calculate \
-H 'content-type: application/json' \
-d '{…see OpenAPI examples…}'