Instrument 02 · Area

Area from UTM eastings, local X/Y or latitude and longitude

Paste the boundary in the coordinates you actually have — UTM eastings and northings with a zone and hemisphere, a local X/Y grid, or WGS 84 longitude and latitude in decimal or DMS — and Geodesia returns the grid, geodesic and ground surfaces, with every leg and the closure checked.

Area instrument Client-side execution CSV · JSON · PDF

Polygon Area & Coordinate Engine workspace

Polygon areaWGS 84Client-side
Loading polygon engine…

Loading polygon engine…

Overview

The instrument accepts the three coordinate forms a parcel actually arrives in. A local X/Y list in metres is a grid with no geographic reference, so it can only give a planar grid result. UTM eastings and northings are a real projection on WGS 84: enter the zone and hemisphere, and the instrument can recover longitude and latitude from the grid, which is what makes the geodesic and ground surfaces possible. WGS 84 longitude and latitude, in decimal degrees or degrees-minutes-seconds and written longitude first, arrive without a grid at all; Geodesia projects the ring into the UTM zone of its centroid so the grid surface exists, then computes the geodesic surface directly from the geographic coordinates.

Three surfaces are computed because they answer different questions. The grid surface is the Gaussian shoelace area on projected metres: it is what a UTM-based plan, GIS layer or CAD drawing sees, and it carries the distortion of the projection. The geodesic surface is Karney’s ellipsoidal area on WGS 84: it is projection-free, and it is the right figure when the boundary is defined by latitude and longitude. The ground surface divides the grid values by the combined scale factor — area by CSF², distance by CSF — and is the area on the ground at the mean elevation you enter. Local X/Y has only the first surface, because metres with an arbitrary origin cannot be related to the ellipsoid or to ground height.

Which figure to quote depends on how the boundary is defined and what the figure is for. A ground area is usually the one that matches a measurement taken on the ground; a grid area is the one that reconciles with a UTM plan or GIS layer; a boundary supplied as latitude and longitude is naturally quoted as a geodesic area. In geographic mode the UTM zone is derived automatically from the ring’s centroid, and both the zone and whether it was derived are shown in the diagnostics; in UTM mode you supply the zone and hemisphere yourself. Either way one zone has to span essentially the whole parcel: near a zone edge the projection scale is at its largest and the grid area drifts from the ellipsoid by a couple of parts in a thousand, and a ring that straddles two zones cannot be projected correctly in one.

Technical specification

Reference systems
Local X/Y (m) · UTM E/N with zone 1–60 and hemisphere · WGS 84 Lon, Lat decimal or DMS
Datum and ellipsoid
WGS 84 · a = 6 378 137 m · 1/f = 298.257223563 · b = 6 356 752.314 245 m; local X/Y carries no datum
UTM parameters
Zone 1–60 · hemisphere N/S · false easting 500 000 m · false northing 10 000 000 m (south) · k₀ = 0.9996 · Krüger order-6 transverse Mercator series
Surfaces
Grid (Gaussian shoelace on projected metres) · geodesic (Karney on WGS 84) · ground (grid ÷ CSF² area, grid ÷ CSF distance)
Outputs
Area and perimeter per surface · per-leg grid, geodesic and ground distance with grid bearing and azimuth · centroid · closure · k, EF and CSF · hectares and acres
Exports
CSV · JSON geodesia.report/v1 · A4 PDF field report · ISO-8601 UTC timestamp
Rounding and limits
Display rounding only (areas 0.01 m², distances 0.001 m, bearings 0.01°, scale factors 8 dp) · one zone per ring, with zone-edge distortion · self-intersection flagged, not repaired · geographic input is Lon, Lat, decimal or DMS

Runs entirely in the browser tab. Nothing you paste or drop is uploaded anywhere.

Capabilities

What Area does

01

Three reference systems

Work in the coordinates the plan, instrument or GIS actually uses: local X/Y in metres, UTM eastings and northings with a zone from 1 to 60 and a hemisphere, or WGS 84 longitude and latitude in decimal degrees or DMS. The mode sets what is available — local X/Y gives the grid surface only, while UTM and geographic input enable the geodesic and ground surfaces.

02

Paste, type, drop a file or digitise on the map

Paste a coordinate list — one pair per line, separated by commas, tabs, spaces or semicolons — type rows into the vertex table, drop a CSV, TXT, TSV or XLSX sheet with a header row naming the coordinate columns, or in geographic mode click the map in ring order and the longitude and latitude are written into the table. Editing, reordering or deleting a row re-closes the ring; for UTM input the map is a spatial check, with the grid ring projected to longitude and latitude rather than digitised.

03

White coordinate sheet for projected data

Projected rings are drawn on a white graph-paper sheet with metre ticks and labelled axes, numbered vertices, per-leg distance labels, a north arrow, a scale bar, the centroid and an area/perimeter annotation. Metres per pixel are equal on both axes, so the plot cannot stretch the parcel the way a resized picture would.

04

Per-leg vector table

Every leg is tabulated with its grid distance, geodesic distance, ground distance, grid bearing and WGS 84 forward azimuth, including the auto-closing leg from the last vertex to the first and a totals row for each perimeter. Grid bearings are clockwise from grid north; azimuths are measured from true north on the ellipsoid.

05

Combined scale factor, shown not assumed

The ground surface reports CSF = k · EF with k = k₀(1 + x²/2R²) and EF = a/(a+h), plus the mean elevation and both components, so the correction can be checked rather than trusted. A surveyed CSF can override the estimate; the override is range-checked and labelled as user-supplied in the diagnostics, with the projection scale factor and elevation factor left visible.

06

Ring diagnostics and validation

The instrument rejects fewer than three vertices, duplicate consecutive coordinates and a simple ring whose area is zero, checks UTM eastings and northings against their plausible ranges, and warns when geographic columns look swapped so they can be flipped in one action. A self-intersecting ring is measured and flagged as a bow-tie instead of being silently repaired, and the closure leg from the last vertex to the first is reported in metres.

Procedure

Working the instrument

The workspace is designed so a field measurement can become a filed report without leaving the tab: enter, verify, read, export.

01

Choose the reference system

Decide whether the boundary is defined on a local X/Y grid, in UTM eastings and northings, or in WGS 84 longitude and latitude, then pick that mode. Switching reference system keeps the vertex set: the same numbers are read in the new system and any row that cannot be parsed is flagged in the table rather than silently discarded, so check the columns after a switch and clear or correct anything that no longer fits.

02

Enter the ring in order

Paste one coordinate pair per line, type them into the table, drop a coordinate sheet (CSV/TXT/TSV/XLSX with a header row), or digitise on the map in geographic mode. Geographic input is longitude then latitude, decimal or DMS; UTM input needs the zone and hemisphere set in the reference panel, and the map is only a check. The ring closes itself from the last vertex back to the first, so do not repeat the first vertex.

03

Turn on the surfaces you need

The grid surface is always produced. The geodesic surface is on by default for UTM and geographic input and can be switched off; the ground surface is opt-in and asks for a mean elevation, with an optional surveyed CSF override. Local X/Y has no geographic reference, so only the grid surface is available and the interface says so.

04

Run the computation and read the diagnostics

Run the computation once the vertices and options are set. The diagnostics block reports the closure leg, the UTM zone and whether it was derived, the grid and geographic centroids, the projection scale factor k, the elevation factor and the CSF. Warnings — a self-intersection, a suspected column swap — are printed with the result, and map or projection problems are called out where they arise, not hidden.

05

Read the surfaces, then export

The surface cards give area and perimeter in square metres with hectares and acres alongside; the leg table carries the per-leg figures. The CSV records the legs and carries the surface figures in its header lines, the JSON is the full verification document with the surfaces you enabled and the parameters, and the PDF is a filed report with the method and timestamp attached.

Method statement

How it is computed

The formula behind every headline figure, stated plainly enough to check by hand.

01 · Gaussian shoelace on the projected grid

A_grid = ½ · |Σ(xᵢ · yᵢ₊₁ − xᵢ₊₁ · yᵢ)|

Planar area in square metres for the closed ring on projected coordinates — UTM eastings and northings, or a local X/Y grid. The ring is translated to its first vertex before the cross products accumulate, which keeps double precision intact when eastings run to hundreds of thousands of metres. This is the area in the plane of the projection, not on the ellipsoid: it includes the projection’s scale distortion and is the figure a UTM plan or GIS layer reports. A self-crossing ring still returns a shoelace sum, but that sum is algebraic and the result is flagged as self-intersecting rather than treated as a parcel area.

02 · Geodesic area on the WGS 84 ellipsoid

A_geodesic = R_q² · Σ ε (Karney geodesic series, WGS 84)

Each pair of vertices is joined by the inverse geodesic on the WGS 84 ellipsoid and the ring is evaluated as an ellipsoidal polygon; Karney’s method reduces the computation to series on the auxiliary sphere and is accurate to floating-point round-off. R_q is the authalic radius — the radius of the sphere with the same surface area as the ellipsoid — derived from a = 6 378 137 m and 1/f = 298.257223563 rather than assumed as 6 371 km. This surface has no projection scale and no zone, which is why it is the one to quote when a boundary is defined by latitude and longitude.

03 · Combined scale factor and the ground surface

CSF = k · EF · k = k₀(1 + x²/(2R²)) · EF = a/(a + h) · A_ground = A_grid / CSF²

k is the transverse Mercator scale factor at the parcel, k₀ = 0.9996, x = meanE − 500 000 m is the mean distance of the ring from the central meridian, and R = √(M·N) at the centroid latitude, with M the meridional and N the prime-vertical radius of curvature. EF is the elevation factor: a is the ellipsoid semi-major axis and h the mean ellipsoidal height you enter. Ground distance is grid distance divided by CSF, and ground area is grid area divided by CSF². A CSF from project control replaces the estimate; the interface labels it as a user override, and the projection scale factor and elevation factor remain visible so the number can be audited.

Geodesic computations use WGS 84 with the defining constants a = 6 378 137 m and 1/f = 298.257223563. Planar computations treat input as a grid in metres with no implied projection.
Calculations are carried at double precision and rounded only for display. Each export records the parameters and the rounding applied, so a reviewer can re-check every filed figure from the numbers in the report.
Open the instrument

Questions

Area questions

Grid, geodesic or ground — which area do I quote?

Quote the surface that matches the coordinate basis and the question being asked. If the parcel is defined in UTM and the figure has to reconcile with a UTM plan, a GIS layer or a CAD drawing, the grid area is the one those systems will show. If the boundary is defined by latitude and longitude, or the parcel crosses a zone, quote the geodesic area: it is on the ellipsoid and has no projection scale. If the area is to represent the land as measured on the ground, quote the ground area, which divides the grid figure by CSF² using the distance from the central meridian and the mean elevation. The three are legitimately different, and a report should name which one it is quoting.

Why does my UTM area differ from the geodesic area?

The UTM grid is a projection, so every distance on it is the ellipsoidal distance multiplied by the scale factor k. At the central meridian k = 0.9996, which makes the grid area about 0.08 per cent smaller than the ellipsoidal area; 300 km from the meridian k is about 1.0007 and the grid area is about 0.14 per cent larger. The geodesic surface measures on the ellipsoid directly, so it has none of that distortion. Elevation is a separate term: at 1 000 m the elevation factor a/(a+h) is about 0.99984, which makes the ground area about 0.03 per cent larger than the ellipsoidal area before the projection is considered. That is why the instrument shows the projection scale factor and the elevation factor instead of a single unexplained correction.

How is the CSF estimated, and when should I override it?

The estimate combines the projection scale factor with the elevation factor. k = k₀(1 + x²/2R²) uses x, the mean easting of the ring minus the 500 000 m false easting, and R = √(M·N) at the centroid latitude; EF = a/(a+h) uses the mean ellipsoidal height you enter, which is zero if you leave the field at zero. Their product is the CSF: ground distance = grid ÷ CSF, ground area = grid ÷ CSF². Override it when project control supplies a CSF from the survey adjustment or the project specification, or when a single scale and a single elevation cannot represent the parcel. The override accepts a factor strictly between 0.5 and 2, replaces the estimate in both the results and the exports, and is labelled as user-supplied; the estimate is a working figure, not a substitute for project control.

Can I paste UTM coordinates from Google Earth or a total station?

Yes, in UTM mode: paste one easting/northing pair per line, in that order, and set the zone and hemisphere once in the reference panel rather than including them in the paste. Google Earth reports UTM with a zone number and a latitude band letter — use the zone number and the N or S hemisphere, not the band letter. Total station exports may be UTM or a local site grid: if the instrument used a local grid, choose Local X/Y instead, because mislabelled eastings will produce a valid-looking but wrong area. Check the datum too — the calculator assumes WGS 84, and the ranges it validates (easting 0–1 000 000 m, northing 0–10 000 000 m) will catch a northing pasted into the easting column, but not a datum mismatch.

What if my parcel crosses a UTM zone boundary?

A UTM ring belongs to one zone, and the instrument does not stitch zones. In geographic mode it derives a zone from the centroid and projects the whole ring into that zone, which is fine for a parcel that straddles the boundary only slightly but increasingly wrong as the ring extends into the neighbouring zone, because the projection scale grows with distance from the central meridian. For a boundary that genuinely spans two zones, quote the geodesic surface, which has no zone, or split the parcel at the boundary and compute each part in its own zone; the ground surface from a single zone is likewise an approximation for such a parcel.

How is a self-intersecting ring reported?

The ring is tested for crossing edges once the vertices are valid and before the surfaces are read. A crossing ring is neither rejected nor silently repaired: the result is flagged self-intersecting, a red notice explains that the boundary crosses itself in a bow-tie, and the grid, geodesic and ground figures are still displayed for diagnosis because a surveyor needs to see what was computed. The displayed area of a crossed ring is an algebraic shoelace sum, not a planimetric parcel area, so it must not be quoted; the fix is to reorder or move the crossing vertices and compute again. The plot and the leg table usually show where the order went wrong.

Continue

Every figure here is a surface claim, so the instrument names the surface and shows the correction behind it: the grid figure on the projection, the geodesic figure on the ellipsoid, and the ground figure with its projection scale factor and elevation factor in view. Nothing is computed on a server, so the coordinates you paste stay in the browser tab, and the CSV, JSON or PDF can be filed beside the survey with the method, the zone where one applies and a UTC timestamp attached.