01
Named formulas, printed with the result
Each instrument states the method that produced each figure — Gaussian shoelace, Karney geodesic series, inverse geodesic distance — instead of hiding it behind a black box.
Spatial instruments · WGS 84
Elevation cross-sections, parcel areas from survey coordinates and cadastral unit conversion — evaluated on the WGS 84 ellipsoid, exported as CSV, JSON or a PDF field report. No account, no upload, no server-side compute.
Karney geodesics Gaussian shoelace UTM 1–60 · CSF ground area pdf-lib reports
Workspace
Terrain Profile opens by default. Switch instruments without losing what you have already measured — each tab holds its own state for the session.
Click the map to set A, then B. Prefer typing? Coordinates accept decimal degrees or DMS.
e.g. -1.2864
e.g. 36.8172
20–200 samples
Elevations are fetched in batches of 100 from the Geodesia edge service first, then Open-Meteo, and cached for this session. A failed lookup never discards your input.
No profile computed yet
Set two points on the map, draw a route, or upload a table with distance and elevation columns. Metrics appear here as soon as the profile is sampled.
No profile yet. Pick two points on the map, draw a route or upload a CSV with distance and elevation columns.
No station data
Stations appear once a line, route or uploaded table has been sampled.
Ecosystem · App directory
Geodesia is the hub for a set of decoupled, single-purpose spatial applications. Each runs on its own subdomain, keeps its own release cadence, and is launched from here.
Showing 3 of 3 applications.
Terrain profiles, polygon area and closure, and land-unit conversion in one client-side workspace.
WGS 84 geodesic inverse (Karney) · hand-rolled SVG profile chart · CSV / JSON / PDF reports
AI crop-suitability analysis (published as Land IQ) over browser-local Cloud-Optimized GeoTIFFs, clipped to a drawn parcel.
COGs read in the browser · polygon clipping · no raster upload · suitability scoring
Thesis methodology flowchart generator for research protocols, exporting publication-ready diagrams.
LaTeX / TikZ · Word DOCX · Mermaid · deterministic layout
Method statement
Every figure is derived from a named, published formula, and every report states which one produced which result. Nothing is approximated silently.
Planar area · Gaussian shoelace
A = ½ · |Σi (xi·yi+1 − xi+1·yi)|
The trapezoid form of the shoelace formula, evaluated on vertices in metres. It is exact for the numbers as drawn on a planar grid, independent of ring orientation, and is the correct check against a CAD parcel or a printed plan.
Ground area · WGS 84 geodesic
Aellipsoid = Σ Δλ · (2·E + sin α1 + sin α2) · b²/2
Polygon area on the ellipsoid using Karney’s series (GeographicLib). Legs are measured as inverse geodesic distances with forward and back azimuths, so the result is the area on the ground rather than on a projection. A spherical approximation is not adequate at cadastral scale; it is deliberately not offered.
Projected grid · UTM & combined scale factor
k = k0 · (1 + x²/(2R²)) · CSF = k · a/(a + h) · Aground = Agrid / CSF²
UTM eastings and northings from any zone (1–60, hemisphere-aware) are measured on the projected grid. The combined scale factor comes from the parcel’s distance to the central meridian (x) and the mean elevation (h), or from a survey-supplied value; ground area is the grid area divided by CSF², which is why the figure on a plan and the figure on the ground are not the same hectare.
Elevation profile statistics
Δsi = si+1 − si · grade % = 100 · Δh/Δs · gain = Σ max(0, Δh)
Stations are sampled along the geodesic at a fixed interval, so distance accumulates on the ellipsoid rather than in degrees. Climb and descent are separate accumulations of the positive and negative elevation differences; gradient is derived per segment and the maximum reported with the station where it occurs.
Instruments in this build
01
Each instrument states the method that produced each figure — Gaussian shoelace, Karney geodesic series, inverse geodesic distance — instead of hiding it behind a black box.
02
No upload endpoint exists. Coordinates and dropped files are read with the File API and evaluated in the tab.
03
CSV, JSON (geodesia.report/v1) and a PDF field report carrying parameters, method and an ISO-8601 timestamp.
04
Every method statement and feature breakdown is real HTML in the first response — no hydration wait before the text you came for.
05
Real labels on every input, focus rings that survive the dark theme, chart sampling by arrow key, and a manual coordinate path for every map action.
06
Geodesia is the hub for Land IQ and MethodFlow; each runs on its own subdomain and keeps its own cadence.
Questions
Short answers to the questions that decide whether a browser instrument is usable in real work. Anything unanswered: [email protected].
Yes to both: every instrument is free to use and there is no account, sign-in or email gate. The tools run entirely in the browser tab, so there is no usage limit to meter and nothing to subscribe to.
Nowhere. Coordinates you paste, files you drop and results you compute stay in the browser tab — there is no upload step and no analytics or tracking script on the site. Two lookups do leave the device by design: map tiles from OpenStreetMap and elevation samples from the Open-Meteo elevation endpoint. Everything else, including all arithmetic, is local.
Geodesic calculations use WGS 84 with the defining constants a = 6 378 137 m and 1/f = 298.257223563. UTM coordinates are handled on WGS 84 transverse Mercator for any zone 1–60 in either hemisphere (false easting 500 000 m, false northing 10 000 000 m south, k0 = 0.9996), and local X/Y input is treated as a planar grid in metres with no implied projection.
They answer different questions, so all three are printed. The grid area is the shoelace result on the projected coordinates — the figure that matches a plan, a CAD parcel or a UTM schedule. The geodesic area is the area on the ellipsoid and is the right figure for any statement about the land itself. The ground area divides the grid area by the combined scale factor squared (CSF = k · a/(a + h)), which is the figure a surveyor quotes after projection and elevation are removed. The difference between them is diagnostic: if it is larger than you expect, the projection or elevation assumption is wrong.
Yes — switch the reference system to UTM, set the zone and hemisphere, and paste easting, northing pairs one per line (CSV, tabs, or a spreadsheet paste all work). The tool measures the grid area and perimeter from those numbers directly, converts them to WGS 84 to add the geodesic and ground surfaces, and plots the ring on a coordinate sheet so a transposed pair or a missing corner is visible. Keep the whole parcel inside one zone: crossing a zone boundary puts the ring on two projections and the grid area stops being meaningful.
It accumulates geodesic distance between sampled stations along your line, differences the sampled elevations to get climb and descent, then derives gradient and a slope classification from each station-to-station segment. You get total distance, gain, descent, net change, minimum and maximum elevation, mean elevation, average and maximum gradient, and a station table that every headline figure can be traced back to. Elevations come from the Geodesia edge elevation service, with Open-Meteo as the fallback, so a survey sheet you upload is always the more authoritative source.
Three artefacts per computation: a CSV of the raw and computed stations, a JSON verification document under the geodesia.report/v1 schema carrying the method statement and timestamp, and a PDF field report typeset client-side with pdf-lib. All three carry the tool name, parameters and an ISO-8601 timestamp so a reviewer can reproduce the result.
No, and it does not claim to be. It is a planning, verification and coursework instrument: excellent for checking a computed figure, reconciling a deed area, or sanity-checking a consultant’s schedule — but only a licensed surveyor’s adjudicated survey can define a boundary.
Once a page has loaded, all computation works without a network connection. Two features degrade gracefully offline: the map basemap needs tiles, and elevation sampling needs the elevation endpoint. In both cases the tools stay usable through manual coordinate entry and CSV/XLSX upload.
Start
Elevation cross-sections from two map clicks, a drawn route or an uploaded survey sheet, with climb, descent, gradient and slope class.
Parcel area from UTM, X/Y or lat/long: grid, geodesic and ground surfaces, per-leg checks, closure and a full unit breakdown.
Every land unit at once — metric, imperial and Kenyan cadastral/agricultural — with exact factors and a dimensions helper.