Area from coordinates

Paste corner coordinates — a simple list, CSV, KML, GPX or GeoJSON. You get the area, perimeter and the length of every side, calculated the same way as the Land Measure app.

One “latitude, longitude” per line (DD, DMM or DMS), or paste CSV / KML / GPX / GeoJSON.

Paste coordinates to see the area.

Show on map

How it works

The tool reads your text, works out the format, and joins the points in order. For a closed area it computes the polygon’s area on a sphere of radius 6,371,000 m by adding the spherical excess of the triangles fanned out from the first corner; the perimeter is the sum of great-circle (haversine) distances between consecutive corners, plus the closing side. These are the same formulas, with the same Earth radius, as the Land Measure app — so the same corners give the same numbers here and on your phone.

Side length (haversine): h = sin²(Δφ/2) + cos φ₁ · cos φ₂ · sin²(Δλ/2) d = 2R · atan2(√h, √(1−h)) R = 6,371,000 m Area: sum of spherical excess E of triangles (P₁, Pᵢ, Pᵢ₊₁), × R²

Why not the familiar shoelace formula? Degrees of longitude shrink toward the poles, so treating latitude and longitude as flat x/y numbers distorts the shape. The spherical method needs no projection and works anywhere, including plots that cross the 180° meridian. Our guide how to calculate area from GPS coordinates compares the methods in detail.

Accepted input

FormatExampleOrder
List (decimal degrees)41.88, -93.62lat, lon
List (DMS / DMM)41°52′48″N, 93°37′12″Wlat, lon
CSV with headername,latitude,longitudeby column name
KML<coordinates>-93.62,41.88,0 …lon,lat[,alt]
GPX<trkpt lat="41.88" lon="-93.62">attributes
GeoJSON[[-93.62, 41.88], …][lon, lat]

Polygons with holes are measured by their outer boundary only, and the tool says so. For the differences between these formats, see KML vs GPX vs GeoJSON. To convert a single coordinate between notations, use the coordinate converter.

Worked example

The example (press Load example) is a field near Ames, Iowa with corners at 41.88000, −93.62000 · 41.88000, −93.61400 · 41.87550, −93.61400 · 41.87550, −93.62000. Its area is 248,565 m² = 24.86 ha = 61.42 acres and its perimeter 1,994.26 m. The north and south sides are about 496.7 m long, the east and west sides about 500.4 m.

Frequently asked questions

What coordinate formats can I paste?

One point per line as “latitude, longitude” in decimal degrees (41.88, -93.62), decimal minutes (N 41 52.8, W 93 37.2) or degrees-minutes-seconds (41°52′48″N, 93°37′12″W) — the same formats the Land Measure app accepts. You can also paste CSV with latitude and longitude columns, KML (anything with <coordinates>), GPX track or route points, or GeoJSON.

Does the order of the points matter?

Yes. Points are joined in the order given, and the last point joins back to the first. List the corners as you would walk around the boundary. If sides cross, the tool warns you because the area isn’t meaningful.

Do I need to repeat the first point at the end?

No, but it doesn’t hurt: a repeated closing point (as in KML and GeoJSON polygons) is ignored.

GeoJSON gives a different area when I swap the numbers. Why?

GeoJSON stores positions as [longitude, latitude], the opposite of the usual “lat, lon” order in a list. The tool reads GeoJSON in its own order and plain lists as latitude first. If your list is longitude-first, add a CSV header like lon,lat on the first line.

Are my coordinates sent anywhere?

No. Everything is calculated in your browser. The coordinates only appear in the page address so the link can be shared; nothing is sent to a server.