The cycle commuter who relies on Google Maps for routing usually ends up on the same fast, traffic-heavy roads as cars. The cyclist who knows their city well takes a parallel route one street over, quieter, more pleasant, often the same length, dramatically less stressful.
This article is about how to build that local knowledge yourself, for whichever city you ride in.
The principle: cyclists prioritise differently than drivers
Cars optimise for speed and travel time. Cyclists should optimise for traffic volume, road surface quality, lighting, and gradient. These are different routes most of the time.
A typical car-optimal route goes along arterials with traffic lights, broad lanes, and continuous flow. A typical cyclist-optimal route goes along parallel residential streets, through parks, along canal towpaths, and across pedestrianised squares. The cyclist route is usually slightly longer in distance but similar in time, with a fraction of the stress.
The mapping methods
Several tools and methods help build a personal route map:
1. Dedicated cycling map apps
Several apps now provide genuine cycling-optimised routing rather than car routing with cycling annotations. Komoot, Bikemap, and Cyclemeter are well-regarded for European cities. Strava’s heatmap shows where actual cyclists ride, which reveals routes that pure algorithms miss.
Google Maps now has a cycling mode that is improving but still tends to favour fast routes. Use it as a starting point but verify against dedicated cycling tools.
2. The local cycling community
Most cities have active cycling communities that publish suggested commuting routes. Look for: the local cycling campaign group (Cycling UK, Cyclists’ Touring Club, equivalent), bicycle co-op websites, Reddit communities for your city (“r/londoncycling,” etc.).
Posted routes from real local cyclists are often more useful than algorithmic routes because they encode knowledge about pothole-heavy stretches, dangerous junctions, and pleasant detours that algorithms don’t see.
3. Weekend exploration
The single best mapping method is also the slowest: pick a destination, ride to it on a quiet Sunday, and note what worked and what didn’t. Document your routes in a personal map (a paper notebook or a digital tool like Komoot’s collections).
After three months of weekend explorations, you will have a personal route library covering most of the places you commonly need to go. This local knowledge compounds: knowing one good quiet route through a neighbourhood usually reveals several adjacent good routes.
The features of a good route
What to look for when scouting routes:
- Low traffic volume. Residential streets, especially low-traffic neighbourhoods, are dramatically more pleasant than arterials.
- Continuous infrastructure. A cycle lane that suddenly ends after 200 metres is worse than a quiet street with no lane at all.
- Good road surface. Smooth tarmac is fast and comfortable; potholed roads are slow and dangerous.
- Manageable gradient. Slight uphills and flats are fine; steep hills add time and effort. An algorithm route might take a fast downhill that you have to climb home.
- Greenery and views. Routes through parks, along rivers, past historic buildings make the journey actively pleasant.
- Adequate lighting at night. Some lovely day routes become threatening in winter darkness; have alternative night routes.
The signature routes worth memorising
Most cyclists develop three to five “signature routes” they use repeatedly:
- The work commute (the one you do most often).
- The grocery shop route (often involves a slightly different end-point).
- The crosstown route (for friends, restaurants, evening events).
- The weekend pleasure route (for fun rides, not necessarily efficient).
- The bad-weather backup route (the safest, most-sheltered version).
Knowing these five routes by heart means you can leave the house without consulting a map for 80 percent of your cycling. Mental capacity that was going to navigation can go to enjoying the ride.
Junction-by-junction knowledge
Beyond route mapping, the next level is junction-by-junction knowledge: which specific junctions on your routes are dangerous, when, and why. The dangerous left-turn from a busy arterial. The right-turn that needs a two-stage approach. The roundabout where cyclists are routinely cut up.
For each dangerous junction, develop a personal protocol: take the lane, signal earlier, wait for a gap rather than rushing through, dismount and use the pedestrian crossing if necessary. This level of detail takes a year to develop but reduces close calls to almost zero.
Related: Going Car-Free in a City: An Honest, Year-One Account
The seasonal adjustment
Cycle routes change by season. A route that goes through a leafy park is glorious in May and a wet leaf-covered hazard in November. A canal towpath that’s well-used in summer becomes deserted and potentially unsafe in winter darkness. The good cyclist has a summer route and a winter route, often quite different, both well-tested.
Document this in your personal route map. Note which routes you use when. The seasonal swap becomes automatic by year two.
Related: Getting to the Airport Sustainably (and Affordably)
The route as community
The deeper effect of knowing your city well by bike is that you start to know your city well as a place. You notice which streets have the best independent coffee, which corners get afternoon sun, which routes pass the most interesting graffiti. The city you cycle through is denser with information than the city you drive through or transit through.
After a year of cycling commutes, most riders report knowing their city dramatically better than they did before, not as an explicit goal but as a side effect of the route-mapping work. That knowledge is one of the underrated benefits of cycling: not just transport, but a more intimate relationship with the place you live.
Related: Is a Monthly Transit Pass Actually Worth It? The Honest Math
The commute at a glance
| Key point | What it means in practice |
|---|---|
| Low traffic volume | Residential streets, especially low-traffic neighbourhoods, are dramatically more pleasant than arterials. |
| Continuous infrastructure | A cycle lane that suddenly ends after 200 metres is worse than a quiet street with no lane at all. |
| Good road surface | Smooth tarmac is fast and comfortable; potholed roads are slow and dangerous. |
| Manageable gradient | Slight uphills and flats are fine; steep hills add time and effort. An algorithm route might take a fast downhill that you have to climb hom |
| Greenery and views | Routes through parks, along rivers, past historic buildings make the journey actively pleasant. |
What an experienced household looks like
It is worth being honest about what good practice in this area looks like after several years of attention. It is not a magazine-perfect lifestyle. The bins are sorted but not labelled in artisan calligraphy. The pantry has a small set of jars rather than a coordinated wall display. The flat smells like whatever was cooked, not like a perfumed lobby. The energy bill is lower than the neighbourhood average but the household still has a TV, a kettle, and a freezer.
What is different is the defaults. The reusable bag is genuinely in the everyday bag. The thermostat is genuinely scheduled. The food in the fridge is genuinely used before being wasted. The shopping is genuinely planned rather than improvised. None of this requires the household to think harder about sustainability than the average household; it requires the defaults to have been set once and then left alone. The mental load of good practice is, in the long run, significantly lower than the mental load of constantly negotiating with disposable habits.
Sources and further reading
Frequently asked questions
For routing, yes. Dedicated cycling apps (Komoot, Bikemap) optimise for cycling-relevant factors that Google Maps doesn't fully capture. For navigation while riding, Google Maps is fine.
Roughly three months to know your main routes well; six months to know the city by bike. The investment is enjoyable rather than tedious if approached as exploration.
Varies hugely by city and park. Some are fine; some are not. Stick to well-used routes after dark, even if they are slightly longer.
Yes, it reveals where local cyclists actually ride, which is often more useful than algorithmic suggestions. Heavily-used streets on Strava are usually good cycling routes; quiet streets may be hidden gems or actually dangerous.
