Skip to content

Add Herne Hill Velodrome as a shared route, both ways round - #6

Merged
RalfLeonFasler merged 2 commits into
OpenBikeNet:mainfrom
pepperstm:herne-hill-450
Nov 15, 2026
Merged

RalfLeonFasler merged 2 commits into
OpenBikeNet:mainfrom
pepperstm:herne-hill-450

Conversation

@pepperstm

Copy link
Copy Markdown
Contributor

What and why

A second shared route: Herne Hill Velodrome in south London, the outdoor track that opened in 1891, hosted the track events of the 1948 Olympics and is still raced on today.

velodrome-250 is the right first route, since every app can build it the same way. Herne Hill adds a real place. For apps like VeloPopuli that build their world from a GPS track (map data, buildings, terrain), the GPX puts riders on the actual track, with the real park and houses round it. Apps that draw their own track can treat it as a flat 450 m loop, same as the 250.

Files

  • routes/herne-hill-450.json: flat, closed, 450 m, ridden anticlockwise as in track racing. The club gives the track as 450 m, and the profile is flat like velodrome-250's.
  • routes/herne-hill-450-clockwise.json: the same track and the same start/finish line, ridden the other way.
  • routes/herne-hill-450.gpx and routes/herne-hill-450-clockwise.gpx: written by the new tool, like velodrome-250.gpx. Each is 450 m on your 6378.1 km sphere to within a millimetre and ends on its first point. The clockwise track is the same points in reverse.
  • tools/herne_hill_gpx.py: follows velodrome_gpx.py closely, with the same scaling loop and the same output, deterministic byte for byte. It takes clockwise as an argument for the second track.

Why clockwise is a route of its own

Riders are placed by their distance from the line. If both directions shared one route ID, a rider going clockwise at 100 m would be shown 100 m along the anticlockwise way: in the wrong place and riding head-on into everyone. A separate ID keeps each direction to itself, and an app can offer the choice simply by picking one route or the other.

How the track was made

The track is an oval of two straights and two semicircles, ridden anticlockwise. I fitted its centre, direction and bend radius (45.3 m) to the inside edge of the track in OpenStreetMap (relation 2524096). The oval sits within 0.6 m of that edge on average and 1.4 m at most. The inside edge in OSM measures 447 m, which matches the official 450 m well.

I used a fitted shape rather than copying the OSM outline on purpose. OSM data is ODbL, and this repo is CC BY / MIT, so only those few numbers come from the map, with a credit to OpenStreetMap contributors in the GPX.

The GPX points have no elevation. The track is flat, and apps with terrain data can use their own ground height. (velodrome-250.gpx uses 0, which is fine for a made-up place but would put a real one at sea level.)

The start/finish line

It's where the real one is: on the home straight, just north of the pavilion at the south end of the stands, where aerial imagery shows the white line across the track.

Not sure about

  • The IDs. herne-hill-450 follows the pattern of velodrome-250, and -clockwise is spelt out rather than -cw so it reads clearly. Happy to change either.
  • A convention for direction. If more tracks or loops follow, it might be worth a line in the spec saying a reversed route is a new ID with a -clockwise (or -reverse) suffix. I've left the spec alone here.

Checks

python3 tools/validate.py passes.

herne-hill-450: the 450 m outdoor track at Herne Hill, London, flat and closed,
ridden anticlockwise as in track racing. herne-hill-450-clockwise is the same
track and start/finish line the other way round, as a route of its own so
riders going opposite ways are never on the same route.

The GPX tracks are an oval at the real location, with its centre, direction
and bend radius fitted to the track's outline in OpenStreetMap, so apps that
build their world from a GPS track can draw the real surroundings.
pepperstm added a commit to pepperstm/velopopuli that referenced this pull request Nov 12, 2026
## What

Herne Hill Velodrome as a built-in track: the 450 m outdoor track in
south London, at its real place, ridden in laps. It's on the home screen
as "Herne Hill Velodrome", and ride setup asks which way round:
anticlockwise as raced, or clockwise.

**Builds on #68 (laps)**, now merged.

## The track

- The route is the measuring line, exactly 450 m from the finish line.
That's on the home straight just north of the pavilion, as on the aerial
photos. It's the same oval as OpenBikeNet's `herne-hill-450`
(OpenBikeNet/protocol#6), so riders from other apps line up.
- Banked 7° on the straights, rising to 26° in the bends. Riders lean
with it.
- Painted with the light-blue côte d'azur, the black, red and blue
lines, the finish line, the 200 m line and the pursuit lines. The paint
stays on the inside whichever way you ride.
- A galvanised railing on a kerb round the outside, plain-coloured
boards along the straights (no real brands), and floodlights with arms
over the track.

## The grounds

- The pavilion: brick below, cedar above with the glazed club room,
seating steps up to the terrace, dark columns, the wave roof curling
over at the back, and the striped loop emblem on the south wall. No
Olympic rings.
- North of it: the bleachers, the club's containers, the white canopy on
three masts, paving and a car park.
- In the middle: the junior track, the hard standing, the path in, and
the small shelter.
- The ground is laid level and kept clear of trees and map buildings.
Houses, roads and the railway round it come from the map as usual. No
START/FINISH arches or village signs.

## Checked

- `npm run check` passes, with 6 new tests: lap length and start point,
both directions, banking, the track look, no race barriers, level ground
and an empty infield.
- Checked a live preview in demo mode on both renderers, riding each way
round (`VP_SMOKE_ROUTE=herne-hill` or `herne-hill-clockwise`).
- Not yet ridden with a trainer.

## Not sure about

- The buildings are sized from OpenStreetMap and photos, so they're
close but not surveyed.
- The track is drawn round the measuring line, so it sits a few metres
inside the real one. The buildings are placed by their distance from the
drawn edge, so they still stand as close to it as they really do.
@RalfLeonFasler

Copy link
Copy Markdown
Contributor

Thanks a lot for this, and welcome! I like the idea of a real place as a shared route, and the fit to the OSM outline is very close (I compared it: within 0.63 m of the inside edge on average). The start line next to the pavilion matches the map too.

Keeping the clockwise variant is fine with me. This is more about presence and riding together than strict track rules, so having both directions is nice.

A few small things you may want to fix up, none of them blocking:

  • The README still only mentions tools/velodrome_gpx.py as the tool that writes GPX tracks; it could mention tools/herne_hill_gpx.py too.
  • The script's docstring says the inside edge fits "within 0.7 m on average", the PR description says 0.6 m (I get 0.63 m).
  • Most of herne_hill_gpx.py repeats velodrome_gpx.py (haversine, scaling, GPX output). A small shared helper could be nice at some point, but that can also come later.

…ring

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@RalfLeonFasler
RalfLeonFasler merged commit b14ba4d into OpenBikeNet:main Nov 15, 2026
1 check passed
RalfLeonFasler added a commit to OpenBikeNet/server that referenced this pull request Nov 15, 2026
Adds herne-hill-450 and herne-hill-450-clockwise (OpenBikeNet/protocol#6),
so the server accepts riders on them instead of answering unknown_route.

Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants