Skip to content
from the airport.

Submitting a route

This site is built on measurements. Every drive time was produced by a routing engine or driven, terminal door to town centre. Every coordinate names its source. Every page carries the date it was last checked. A route you submit enters the site the same way or not at all — and this page exists so that when we say no, you can see it was the rules that said it.

What a route is

One path a traveller actually makes: from an airport to the place they came for, or between two destinations people pair on the same trip.

The destination is a place. The test: would a traveller with no relationship to any business still make this drive? The ski hill passes — it is the reason for the trip. A town, a park, a trailhead, a ferry terminal all pass. A cabin, a restaurant, a shop — anyone's front door, including our clients' — does not.

That rule is not a limitation on operators; it is what makes a route worth linking to. A route ends at the town, so it serves every operator in that town. We will not build anyone a private road — the public road helps you and your neighbours.

Listing is not recommending

Route pages do carry businesses — where you could sleep at the end of the drive, where the map records food along it — and that is not a hole in the rule above. A business cannot be the reason for a drive. A business can be a fact about one.

Those blocks carry no stars, no prices, no opinions and no opening hours, and they are never "all of them" or "the good ones". They come from OpenStreetMap, they are measured to a distance, and that distance is the only thing they claim. The headline is the gap — the longest stretch of road with nothing mapped on it — because that is the fact a traveller can plan around and a directory cannot give them.

So we list, and we never rank. A place appears on a route page because open map data records it within two kilometres of the driven line, and it appears in the order you pass it — not because it is good, not because it paid, and not because we like it. Choosing dinner is still someone else's job: a town's own site can carry the phone numbers and the opening hours we deliberately refuse to publish. Nobody can buy a place in our lists, because we do not compile them: the open data does, and anyone can correct it.

What we need from you

Not measurements — verifying is our job, and we re-measure everything regardless of what is submitted. What we need is the case:

What gets a route accepted

What gets one declined

A decline comes with the nearest route we would accept, where one exists — we cannot route to your door, but a route to your town may well clear the bar, and it serves you along with everyone else there.

What acceptance means

An accepted route becomes ours editorially. We write the page, we maintain it on our verification cycle, and we change it when the road or the facts change — including in ways a submitter might not prefer. Credit for the suggestion is given if you want it. We accept what clears the bar, as capacity allows.

Acceptance cannot be bought. Sponsorship can fund the research and writing of a route — and where it does, the page says so — but it cannot buy a yes. Sponsors see no draft and approve no copy. No invoice of any kind moves a route past these rules.

Routes and directions are different things

We also build private door-to-door directions for accommodation operators' own booking pages — the last leg from the public road to a guest's actual destination. Those are directions, not routes: they are made for a guest who has already booked, they carry no recommendation, and they never appear on this site. This site's routes are never for sale, and its pages end at places.

How to submit

Email us the case — the origin, the destination, and why travellers make the drive. We read everything; we accept what clears the bar; and if it does not, we will tell you which line it fell at.