GISela Area & Length
True area, perimeter and length of polygons and lines on the WGS 84 ellipsoid, per feature.
How it works
Measures every polygon and line of GeoJSON, KML, GPX, CSV/WKT or shapefile data on the WGS 84 ellipsoid with Karney’s geodesic algorithms — the same numbers as GISela’s measure tool and attribute fields. Holes are subtracted; results in metric or imperial units.
- Polygon area and perimeter: Karney’s geodesic polygon algorithm (edges are geodesics on WGS 84), outer rings minus holes. Line length: sum of geodesic distances (Karney inverse problem).
- Input in a projected coordinate system is first converted to WGS 84 longitude/latitude, so the result does not depend on the map projection.
- Units: 1 ha = 10,000 m², 1 acre = 4046.8564224 m², 1 mi = 1609.344 m, 1 ft = 0.3048 m.
Areas are on the ellipsoid surface (sea level), not along the terrain.
Sources
- Algorithms for geodesics (Karney 2013) (Journal of Geodesy 87)
- 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 measure the true area and length of polygons and lines
Get the area, perimeter and length of every feature — measured on the WGS 84 ellipsoid, in metric or imperial units — from GeoJSON, KML, GPX, CSV, WKT or shapefiles in any supported coordinate system.
What it is for
Areas and lengths measured on a flat web map are wrong, often badly: Web Mercator stretches areas by more than a factor of two at 47° north. This tool measures every polygon and line on the WGS 84 ellipsoid, the model of the Earth GPS uses, with Charles Karney's geodesic algorithms. It returns area and perimeter for polygons (holes subtracted), length for lines, and totals.
Use it to check the size of a parcel, a nature reserve or a district, the length of a route or a pipeline, or to compare what another program says. The GISela app uses the same functions for Analysis → Add area and length fields and the measure tool.
Worked example
The first example measures six district polygons of an invented town. The table lists, for example:
- Altstadt — 1.32 km² (1,320,464.07 m²), perimeter 4.606 km
- Bahnhof — 1.472 km², perimeter 4.872 km
- Seefeld — 1.153 km², perimeter 4.302 km
The totals are 8.174 km² of area and 28.091 km of perimeter.
The second example measures the town's tram line in imperial units: 2.31 mi (3,717.63 m). The third measures a WKT triangle, POLYGON ((8 47, 8.0132 47, 8.0066 47.0136, 8 47)): 75.893 ha with a perimeter of 4.19 km.
How to read the result
- Totals — number of features, total area, perimeter and length.
- Table — one row per feature with layer, name (from a name field when there is one), geometry type and the values in readable units. The raw values in m² and m are in the JSON result.
- Units — metric uses m², ha and km² by size and m or km; imperial uses ft², acres and mi², ft and mi.
Tips and common mistakes
- The coordinate system of the input matters only for reading it. Data in LV95, UTM or the British National Grid is converted to WGS 84 first and then measured, so the result is the true size on the ground, not the size on the projection.
- Lines between vertices are measured as geodesics — the shortest path on the ellipsoid. For short edges this is the same as a straight line on any good map.
- Holes count: a lake inside a park polygon is subtracted from its area.
- Self-intersecting polygons (a "bow tie") have no clear area; repair them first.
- Heights are ignored: a steep hiking trail is longer on the ground than its map length.
FAQ
Why is the area different in my desktop GIS?
Most desktop programs measure in the coordinate system of the layer. In an equal-area system you get the same result within a few square metres; in a conformal system such as UTM or Web Mercator the result can be off by a fraction of a percent up to a factor of two.
How accurate is it?
Karney's algorithms are exact to a few nanometres on the ellipsoid. The real uncertainty comes from the data: a vertex that is 1 m off moves the area by about 1 m times the length of its neighbouring edges.
Can I measure points?
Points have no area or length; the app's Add area and length fields gives them longitude and latitude instead.
Guide last updated:
For scripts and AI agents
- JSON API:
POST https://giselaarealength.usefulweb.app/api/v1/calculate(same calculation as this page) - Interface description: OpenAPI 3.1 · AI guide: llms.txt
- MCP server (Streamable HTTP):
https://giselaarealength.usefulweb.app/mcp· tool namegisela_area_length
Example request
curl -s -X POST https://giselaarealength.usefulweb.app/api/v1/calculate \
-H 'content-type: application/json' \
-d '{…see OpenAPI examples…}'