GIS Tools - Area Calculator

What Is a Polygon Area Calculator?

A polygon area calculator computes the surface area enclosed by a polygon's boundary. In GIS this is one of the most frequently requested measurements — farmers want field sizes, planners want parcel areas, conservationists want habitat extent, foresters want compartment sizes, and regulators want flood footprints in hectares. The challenge is that Earth is curved, so there are two very different ways to compute area: planar (treat the polygon as flat, use its projected coordinates) and geodesic (account for Earth's curvature using an ellipsoidal model).

Planar area is fast and simple — apply the shoelace formula to the vertex coordinates in a projected CRS like UTM or State Plane and you get square meters directly. But the result depends entirely on the projection you chose. Web Mercator, for example, grossly inflates area toward the poles, making Greenland appear 14 times larger than it really is. Equal-area projections (Albers, Mollweide, LAEA) are designed specifically to preserve area, so planar measurement in those CRSs is trustworthy.

Geodesic area is the rigorous answer. It computes the actual area on the WGS84 ellipsoid using algorithms like those in Turf.js turf.area(), PostGIS ST_Area(geography), or GeographicLib's geodesic polygon. This is what QGIS uses for its ellipsoidal area field and what ArcGIS calls "geodesic area." Our calculator returns both measurements side-by-side so you can see the difference, understand the projection effect, and pick the one that matches your downstream reporting standards. Everything runs in the browser — no uploads, no install, complete privacy for proprietary parcel data.

How Area Calculation Works

The Shoelace Formula

For a simple polygon with vertices (x₁,y₁), (x₂,y₂), ..., (xₙ,yₙ) in a planar CRS, the signed area is A = ½ |Σ (xᵢ · yᵢ₊₁ − xᵢ₊₁ · yᵢ)|. This is the "shoelace" or surveyor's formula. It is O(n), exact for simple polygons, and handles holes by subtracting the interior ring areas. This is what's used inside desktop GIS for planar area.

Geodesic Area on the Ellipsoid

For geographic coordinates on WGS84, the surface is curved, so the shoelace formula gives nonsense. Instead, you sum signed "spherical excess" contributions of each edge relative to a reference parallel. Modern geodesic algorithms (Karney, Danielsen) extend this to the ellipsoid with sub-ppm accuracy — a 100 km² polygon is computed to within a square meter. That's what Turf.js and PostGIS geography type use under the hood.

Handling Holes and Multipolygons

A polygon with a hole subtracts the hole's area from the outer ring's area. A MultiPolygon sums the areas of each part. The calculator handles these cases automatically for any GeoJSON Polygon or MultiPolygon feature.

Winding Order

GeoJSON RFC 7946 specifies that outer rings should be counter-clockwise and inner rings clockwise. Many files violate this. The calculator handles either convention, but for maximum compatibility downstream, run the GeoJSON Validator & Fixer afterward.

Key Parameters and Options

Input Data

Paste a single polygon as GeoJSON, drop a file of polygons, or input coordinates as WKT. The calculator accepts Polygon, MultiPolygon, and FeatureCollection inputs.

Calculation Method

Choose geodesic (default, ellipsoidal, rigorous) or planar (fast, requires an appropriate projection). For a mixed view, "both" reports geodesic and planar side by side.

Output Units

Square meters, square kilometers, hectares, acres, square feet, square miles, or square nautical miles.

Summary Statistics

For batch inputs the calculator can also report total, mean, min, max, and a histogram of polygon sizes — useful for inventory reports and parcel analysis.

Practical Applications

Land Management and Cadastre

Municipal governments, land registries, and cadastre agencies use area measurement for taxation, parcel description, and land transfer. A tiny error in a planar measurement on a poorly-chosen projection can compound across millions of parcels into meaningful revenue differences. Geodesic area gives a defensible, projection-independent answer.

Agriculture and Precision Farming

Farmers use area calculators to quantify field sizes, compute fertilizer and seed requirements, and submit claims for subsidies. Precision agriculture platforms bill by hectare, so a consistent, standards-compliant measurement is critical. The calculator supports hectares and acres natively and reports both geodesic and projected area so farmers can cross-check against legacy records.

Environmental Science and Conservation

Habitat mapping, wetlands inventories, protected area reporting, and deforestation monitoring all depend on accurate area statistics. IUCN and CBD reporting standards typically expect ellipsoidal area. Researchers can drop a GeoJSON of habitat polygons into the calculator and get total protected extent in a specified unit ready for publication.

Urban Planning and Zoning

Planners need to compute zone areas, impervious surface footprints, park and open space percentages, and buildable area after subtracting setbacks. Area calculations drive density caps, floor-area-ratio controls, and comprehensive plan metrics. A quick in-browser tool is ideal for spot-checking a development proposal.

Disaster Response and Damage Assessment

After a flood, wildfire, or earthquake, responders digitize the affected area and need a total in square kilometers or hectares for press releases and FEMA submissions. The area calculator can process a drawn polygon in seconds, before the data has even left the field tablet.

Forestry

Forest compartments, harvest blocks, and fire perimeters all rely on consistent area measurement. Forestry GIS typically stores data in a regional projection with an equal-area property; the calculator honors this and also provides a cross-check in geodesic square kilometers.

Mining and Resource Extraction

Mine leases, claim boundaries, and environmental impact areas all need auditable area figures. Regulatory bodies generally accept either geodesic or equal-area planar results, but require transparency about which was used. The calculator labels each output accordingly.

Step-by-Step Workflow in gis.tools

Open the Area Calculator in your browser.
Drop a GeoJSON, WKT, or shapefile containing one or more polygons.
The tool detects the coordinate reference system and polygon count, and reports a warning if the CRS is unsuitable for planar measurement.
Pick the calculation method (geodesic, planar, or both) and output units.
Click Calculate. Per-feature area appears in a table alongside summary statistics.
Export results as CSV or a GeoJSON with a new area attribute on each feature.
For deeper analysis, route the data through Column Statistics or Graduated Styling to visualize area distribution.

Worked Example

A conservation analyst has digitized 240 wetland polygons across a state and needs total protected wetland hectares for an annual report. She drops the GeoJSON into the Area Calculator, picks geodesic and hectares, and in under a second gets a per-wetland table plus a total of 18,427.3 ha. She spot-checks three large polygons against the state's official tabular records and they match within 0.1% — the expected accuracy for ellipsoidal polygon area. She exports the CSV, adds a percentage-of-total column in a spreadsheet, and the report is done by lunch. No wetland data ever left her laptop.

Common Pitfalls and Gotchas

Planar area on Web Mercator: The most common mistake. Web Mercator inflates area dramatically away from the equator. Always use geodesic or reproject to an equal-area CRS first.
Ignoring holes: A polygon with an inner ring should subtract the hole's area. If you see suspiciously high totals, check for missing holes.
Ring winding: Some tools flip sign based on winding direction. If you see negative areas, check the GeoJSON Validator & Fixer.
Self-intersecting polygons: A bowtie polygon has ambiguous area. Repair it with Geometry Repair before calculating.
Mixing units: Double-check whether downstream consumers expect hectares, acres, or square kilometers.
Datum mismatches: Geodesic calculations assume WGS84. For legacy datums the discrepancy is usually negligible (<0.1%), but be aware.
Very small polygons: Near the numerical precision limit (a few square millimeters on WGS84), geodesic formulas can introduce artifacts. Use planar math at engineering scales.
Invalid polygons: Missing closing vertex, duplicate vertices, or unclosed rings can all confuse the calculator.

Tips for Best Results

Use geodesic for any cross-regional or continental calculation.
Use an equal-area projection (Albers, Mollweide, EPSG:6933 NSIDC EASE-Grid) for planar work where consistency matters more than speed.
Always label outputs with both the method (geodesic/planar) and the units (ha, km², acres).
Validate polygons before calculating — sliver polygons and self-intersections corrupt totals.
For very large polygons that cross a UTM zone boundary, prefer geodesic over forced-zone planar math.
Cross-check a few results against a second tool (QGIS ellipsoidal area, PostGIS ST_Area(geography)) for peace of mind.

Comparison with Other GIS Approaches

QGIS's $area field calculator, ArcGIS Pro's Calculate Geometry tool, PostGIS ST_Area, Turf.js turf.area(), and GeoPandas gdf.to_crs(...).area all do the same job. Our browser tool matches their output for standard cases. The desktop and database tools scale better for millions of polygons; the browser tool is faster for ad-hoc checks and respects data privacy for sensitive parcels.

Performance Considerations

Geodesic area is ~1 microsecond per vertex on modern hardware. A FeatureCollection with 100,000 polygons averaging 50 vertices each processes in a few seconds. The memory bottleneck is JSON parsing; files beyond 500 MB become impractical.

Data Privacy and Browser-Based Processing

Parcel boundaries, habitat data, and survey polygons are often sensitive. The calculator never uploads them — everything is computed locally in JavaScript. Close the tab and the data is gone. No server logs, no telemetry, no third-party analytics.

Related GIS Concepts

Geodesic area: the true area on the ellipsoid, computed by integrating across the surface.
Equal-area projection: a projection designed so planar area equals geodesic area within its region of validity.
Signed area: the shoelace formula returns a signed value that depends on vertex winding; absolute value gives the actual area.
Green's theorem: the mathematical basis of the shoelace formula, generalized to closed curves in the plane.
Spherical excess: the amount by which the sum of a spherical polygon's angles exceeds the planar sum, proportional to its area.

Frequently Asked Questions

How do I calculate the area of a polygon in square meters?

Drop a GeoJSON polygon into the Area Calculator, pick geodesic method and square meters as the unit. The tool returns the result instantly.

What's the difference between geodesic and planar area?

Geodesic area accounts for Earth's curvature and is projection-independent. Planar area applies the shoelace formula to projected coordinates and depends on the CRS. For small polygons in an equal-area CRS they agree; for large polygons in Web Mercator they diverge badly.

Can I calculate area for a polygon with holes?

Yes — the calculator handles inner rings correctly, subtracting hole area from outer ring area.

What units are supported?

Square meters, square kilometers, hectares, acres, square feet, square miles, and square nautical miles.

Is hectares the same as acres?

No. 1 hectare = 10,000 m². 1 acre ≈ 4,046.86 m². 1 ha ≈ 2.471 acres.

About Area Calculation