Instrument 01 · Elevation

Elevation cross-sections from a line, a route, or a survey sheet

Drop two points on the map, draw the alignment you actually intend to build, or load the levels you already reduced — Geodesia samples the ground along that line and returns a cross-section with climb, descent, gradient and slope classification, every figure traceable to a station.

Profile instrument Client-side execution CSV · JSON · PDF

Terrain Profile workspace

Terrain profileWGS 84Client-side

Elevation source

Map or manual

Click the map to set A, then B. Prefer typing? Coordinates accept decimal degrees or DMS.

e.g. -1.2864

e.g. 36.8172

Sampling

20–200 samples

Smoothingmoving average

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.

Map

WGS 84 basemap

Basemap: Geodesia edge cache — loading tiles…

Loading basemap…
No endpointsClick to set A

Click A, then B. The profile samples the WGS 84 geodesic between them. Keyboard alternative: type coordinates in the panel.

Profile metrics

Awaiting 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.

Category thresholds · flat < 2% · gentle < 5% · rolling < 10% · hilly < 20%
Elevation profile

No profile yet. Pick two points on the map, draw a route or upload a CSV with distance and elevation columns.

Station table

No data

No station data

Stations appear once a line, route or uploaded table has been sampled.

Overview

A terrain profile is a one-dimensional reading of a two-dimensional surface. The instrument samples ground elevation at a fixed interval along your line, accumulates the horizontal distance geodesically on the WGS 84 ellipsoid, and differences consecutive elevations to separate climb from descent. The result is a cross-section you can read at a glance and a station table you can audit line by line.

Three input paths exist because profiles are made at three different stages of a job. Two map clicks answer a route question before a site visit — is this saddle better than that one, and by how much? A drawn route follows the alignment of a pipeline, access track or transmission line, including its bends. Uploading a CSV, TXT or XLSX file is the survey path: your reduced levels are authoritative, and the instrument should not silently replace them with a public elevation surface.

Distance is the part most profile tools get wrong. Sampling at a constant spacing in degrees gives station intervals that vary with latitude, and a rhumb-line chord is not the line a contractor measures. Geodesia solves the inverse geodesic problem between stations, so the cumulative chainage is the distance on the ellipsoid, and the bearing reported for each leg is the forward azimuth at that station.

Technical specification

Input modes
Two map points · drawn route · CSV / TXT / XLSX
File columns
chainage + elevation, or latitude + longitude + elevation
Distance method
Inverse geodesic, WGS 84 ellipsoid
Sampling
Fixed spacing along the line, stations capped for legibility
Elevation source
Supplied in file, or sampled through the Geodesia edge elevation service (Open-Meteo fallback)
Statistics
Distance · gain · descent · net · min · max · mean · grade
Exports
CSV · JSON (geodesia.report/v1) · PDF field report
Limits
Elevation surface resolution, not vegetation or canopy height

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

Capabilities

What Profile does

01

Two-point geodesic line

Click a start and an end point; the line drawn is the geodesic between them, and the chainage reported is the inverse geodesic distance on WGS 84 — not a degree-fraction approximation.

02

Drawn routes with bends

Add vertices to follow a pipeline, track or river alignment. Each leg is sampled independently and the chainage accumulates across vertices, so a route profile reads as one continuous section.

03

Survey sheet ingestion

Upload CSV, TXT or XLSX with chainage and elevation, or latitude, longitude and elevation. Columns are detected by name and confirmed in the interface before anything is computed.

04

Climb and descent, counted separately

Elevation gain is the sum of positive differences between consecutive stations, descent the sum of negative ones. Net change is start minus end, so a there-and-back route correctly reports both numbers rather than a misleading zero.

05

Gradient per segment, and where it peaks

Every station pair carries a run, rise, percent grade and angle in degrees. The maximum grade is reported with the station it occurs at, which is what decides a switchback or a culvert.

06

Cross-section you can interrogate

Hover the chart for a pinned readout at the nearest station, or step station by station with the arrow keys. The same samples feed the table, the CSV and the PDF report.

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 source of truth

If the elevations come from a survey, upload them — reduced levels are authoritative. If the question is a reconnaissance one, use the map. Both paths produce identical stations, identical statistics and identical exports.

02

Trace the line

In map mode, place two points for a straight alignment, or draw a route vertex by vertex. Coordinates can also be typed or pasted directly when the map is unavailable or the line is specified in a table.

03

Read the profile before the numbers

Look at the cross-section first: where the summit sits, whether the descent is longer than the climb, and whether any station is an obvious outlier. Then check the station table and the gradient column against it.

04

Export with the method attached

CSV carries the stations, JSON carries the verification envelope with parameters and timestamp, and the PDF is a field-report page with the profile chart, statistics and station table together.

Method statement

How it is computed

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

01 · Chainage from the inverse geodesic

s₁₂ = inverse geodesic (φ₁, λ₁, φ₂, λ₂) on WGS 84

Consecutive stations are sampled at a fixed interval along the line; each pair is solved with the inverse geodesic problem (Karney), which also yields the forward azimuth used as the leg bearing. Chainage is the running sum of those distances, in metres.

02 · Climb, descent and net change

Δhᵢ = hᵢ₊₁ − hᵢ · gain = Σ max(0, Δh) · descent = Σ max(0, −Δh) · net = hₙ − h₀

Differences are taken between consecutive samples after optional moving-average smoothing. Net change is the endpoint difference; because gain and descent are separate accumulations, gain − descent equals net for any profile, which is a useful self-check.

03 · Gradient and slope classification

grade % = 100 · Δh / Δs · angle° = atan(Δh / Δs) · 180/π

Run is the geodesic distance between stations and rise the elevation difference, so grade is dimensionless and comparable between a 50 m and a 5 km section. The maximum grade over the profile identifies the classification band: flat, gentle, rolling, hilly or steep.

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

Profile questions

Where does the elevation come from, and how accurate is it?

In map mode the elevations come from the Geodesia edge elevation service, which returns a global digital elevation model value at each coordinate and falls back to Open-Meteo if the edge service cannot answer. That is a bare-earth surface at a horizontal resolution of tens of metres, so it will not represent a cutting, a bridge deck or a hedge, and it should not be quoted as survey accuracy. The background map is served through the Geodesia edge tile cache — Thunderforest topo styling with data © OpenStreetMap contributors, and automatic fallback providers if the edge service is unreachable — and changing the basemap has no effect on the elevations or the profile. In upload mode the elevations are yours, and the statistics are only as good as the levels in the file.

Why is the line on the map slightly curved?

Because it is a geodesic. Between two points on an ellipsoid the shortest path is not a straight line in latitude/longitude space, and over a few hundred metres the difference is invisible while over tens of kilometres it is not. Chainage follows the geodesic, so the profile and the drawn line agree with each other and with the ground.

Can I use my own levelled survey instead of the elevation service?

Yes, and for any real design question you should. Upload CSV, TXT or XLSX with a chainage column and an elevation column — reduced levels, spot levels or a level-book extract all work — and the instrument uses only your numbers. No elevation request is made, and the profile is exactly your survey.

How many stations are sampled, and can I change the spacing?

The sampling interval is fixed by the instrument so that a 200 m section and a 20 km section are both legible, and the number of stations is capped. The station table lists every sample used, so the spacing is visible in the chainage column rather than hidden. For a survey-driven profile the stations are your rows, not resampled points.

Why does elevation gain not equal the net change?

Because a profile that rises and falls again has both climb and descent. Net change is end minus start; gain sums every positive difference and descent sums every negative one. On an out-and-back route the net is zero while the gain and descent figures are large and both correct — which is exactly the distinction that matters for effort, drainage and vehicle performance.

Can this profile a route with bends, such as a pipeline or access track?

Yes — switch to route mode and add vertices instead of just two endpoints. Each leg is sampled geodesically, chainage accumulates across the vertices, and the bearing column reports the leg azimuth at each station, so the table reads like a set-out schedule rather than a single straight section.

What is the maximum line length it will handle?

There is no hard geographic limit; the practical constraint is the number of elevation samples requested, which is batched. For very long alignments, work section by section and export each, or upload the profile as tabular data, which bypasses sampling entirely.

Continue

A profile is a claim about the ground, so the instrument is built to show its working: the station table is the evidence, the method statement is the reasoning, and the export carries both with a timestamp. If an elevation looks wrong, the sample is visible and can be corrected or replaced — which is the only defensible way for a browser tool to present terrain data.