Building Blocks · World · Chapter 2 of 7 · 4 min read

Real heights

The climbs are the part of a route your legs remember, so the heights have to be right. The heights in a GPX file often aren't.

What is wrong with recorded heights

A bike computer gets height in one of two ways. GPS height is less accurate than GPS position, and it jumps about. A barometer is smooth, but it measures air pressure, and pressure changes with the weather: over a four-hour ride the same road can come out many metres higher at the end than at the start.

The result is that devices disagree. Menaspà and colleagues put several bike computers on the same mountain climb and through the same 138 km event. Devices of one brand agreed with each other, but two brands differed by as much as 3% in total climbing, and switching on one brand's own height correction changed the total by 5 to 10%.

For a ride outdoors that is a detail. On a trainer it decides the resistance under your feet. A spike in the file becomes a wall that isn't there.

Heights from the ground itself

So BlockRide looks the heights up. When a route is prepared, it fetches open terrain data for the land under the route and takes the height of the road from that. The data is put together from public surveys of the Earth's surface, among them the Shuttle Radar Topography Mission, which mapped most of the planet's land from orbit in 2000, and finer national and European surveys where they exist.

These heights replace the ones in your file. Barometer drift and GPS noise no longer shape the climbs, and a file with no heights at all gets real ones. The menu tells you how far off the file was.

Where the file knows better

A terrain model describes the ground. A road doesn't always sit on the ground. On a bridge it is above it, in a tunnel below it, and in a cutting the model may still show the hill that was dug away.

BlockRide looks for these places: stretches where the terrain says steep and your recording says steady. There it keeps the shape from the file, and lines it up with the terrain at both ends so there is no step.

The land around the road

The same data builds the landscape. Close to the road, the hills and valleys are the real ones, eased onto the road's edge so the two meet cleanly. Further off, the game draws the real ridgelines as hazy shapes beyond the fog, so a valley road is framed by the mountains that are really there.

Mountain roads need one more thing. On a hillside of hairpins, two legs of the same road run side by side at different heights. The ground between them can't belong to both, so the lower road keeps its level and the upper one stands on a retaining wall.

How good is the data?

Good, and not perfect. The radar mission was built to be within 16 m in absolute height nine times out of ten, and the mission's own assessment, described by Farr and colleagues, found it did better than that. What matters for a climb is the change in height along the road, and an error that lifts a whole hillside by a few metres doesn't change that. Even so, the model is a grid, and a narrow road cut into a steep slope can sit between its points. That is one more reason the game smooths what it reads.

If the terrain data can't be reached, the route is built from the heights in your file, and you can ask for the lookup again later.

Your route is not sent to anyone for this. The game asks blockride.cc for squares of terrain, and BlockRide's server fetches them from the public archive. The archive sees which squares were asked for and nothing about who is riding.