The route at a glance

The desktop planner now tells you what a route holds before you ride it. A briefing under the route planner sums it up badge by badge, the stop list gives every leg its own figures, and the elevation profile and the map point at the same place from either side.

What the route holds

The route briefing has one badge per thing a rider asks about a route, in a fixed order. Gates and access comes first: closed, in doubt and passable gates, bollards and toll booths. When anything is closed or in doubt it is drawn as loudly as the unpaved share, because a locked gate ends a ride sooner than gravel does. When the route could not be checked on some leg, the badge says Not checked. It never says "none" for a gate list nobody read.

Then come the surface (the unpaved share), the steep stretches (how many kilometres are over 10 %, how much of that is unpaved, and the steepest grade with its place), single track when there is any, and rider reports. The reports badge lists the closures the router met and what other riders reported along the line: hazards, gates and rated stretches, plus your own reports. It reads the same reports the map's layer shows, cell by cell along the route. As everywhere else, they are told and never routed on: the server's route does the avoiding.

Each badge has an eye. It lights that badge's stretches and places on the map: orange bands under the route line for the steep parts, rings on the gates, and several kinds at once if you like. A badge also opens to a list, and each item fits the map to its place and puts the profile's marker there.

The stop list now gives each leg its own figures: distance, climbing, unpaved share and time. The legs' climbs add up to the climb the profile states, so the two never quote different numbers for the same ride.

One cursor for the profile and the map

The profile used to be a fixed 120-pixel picture stretched to fit its box: taller widgets did not grow it, and its labels were distorted. It is now drawn at the size of its widget, beside the map or docked under it, and drawn again when you resize it.

Pointing works both ways now. Point at the profile and the place is pinned on the map. Point at the route line on the map and the profile's marker moves there. A card at the point gives the distance, the height, the slope, the surface, the posted limit and the time it takes to get there. The time comes from the routing engine's own timing, so a slow gravel climb takes its real share of the ride. A switch in the profile's title bar hides the card. From the keyboard, P gives the profile the focus and the arrow keys walk along the route.

Weather on the profile's own axis

The forecast along the route has moved from the route planner into the profile. Set a departure, press Compute, and the weather at each place, at the time you reach it, lines up under the profile. The ice stretches and the "leaving later clears the ice" hint came along. Once a forecast is in, the card at the point gives the clock time of arrival and the weather there.

The line that wasn't there

Testing the map hover turned up an older problem: on the hybrid basemap, which is the default, the computed route was not drawn at all. That basemap lays the streets of an open vector style over satellite imagery, and the overlay brought its own font server. That server has no Open Sans, which is the font of the route's direction arrows. When one range of font glyphs fails to load, MapLibre drops every tile of the layer's source, so the arrows took the route line and its casing with them. Nothing failed in the console. The hybrid basemap now keeps our own font endpoint, which serves both font families, and a test pins that.

Dig deeper: the desktop client, The route at a glance.