How Remap ranks Washington DC's routes

Every route on these pages was built by Remap. For this edition, we surveyed 20,837 routes across 1,755 distributed starting points in Washington DC.

What constitutes a good route

We judge route quality based on these factors:

  • the breadth the route encapsulates from the starting point
  • how sinuous the roads are
  • how many intersections and traffic lights there are
  • how much natural scenery is visible
  • how much noise and traffic is exposed to the rider or runner

Overall a good route brings you back to your start location without repeating roads twice to get there.

How routes are ranked

Firstly, a route's shape determines if it gets ranked at all. Once that gate has been satisfied, we look to the amount of natural scenery the roads and trails travel through.

A route is ranked at a distance only when it is within 10% of it: a 5 km run is between 4.5 and 5.5 km.

Scenery carries the most weight in the routes we rank. Specifically we look at how long is the longest uninterrupted stretch of nature, and how much of it passes a beautiful viewpoint.

Only scenery earns points. Traffic and stops take points  from the final score away.

MeasureRunsRides
Through natureShare of the route through parks, forests and along rivers or the coast, or beside a park of 10 ha or more. A street that only runs alongside a smaller park, or along a canal, counts a quarter.16%25%
ViewsShare of the route on streets and paths that pass within 200 m of a viewpoint.36%35%
Longest nature stretchThe longest uninterrupted stretch through nature, expressed as a share of the entire route.48%40%

Traffic and stops

Remap has unique traffic and noise insights into your outdoor network and as such is able to shape routes intelligently based on this data. Our experience shows that for all of the outdoor activities our community participates in, the less traffic, noise and intersections the better.

Where concrete data is lacking, Remap estimates how busy every road is with a machine learning model trained on traffic counts.

Traffic stress

We follow the traffic stress levels study developed by transport researchers Mekuria, Furth and Nixon, using each road's type, speed limit and cycling infrastructure.

A road is stressful at level 3 or above. This generally means main roads, unless they are signed at 40 km/h or less, and side streets signed above 50 km/h.

For runs, we avoid routing alongside adjacent stressful roads.

For rides, a separated cycleway is never considered stressful. Painted cycle lanes on smaller main roads are also considered low stress up to 50 km/h.

Stops

These constitute:

  • traffic lights
  • busy roads that must be crossed or joined
  • stop signs
  • give way signs
  • road barriers

If there are multiple stopping signals in close vicinity, they are collapsed into a single signal. For instance, crossing both sides of a divided road counts as a single stop.

How the penalties work

Traffic stress is deducted in proportion to the distance travelled: every 10% of route length in stressful traffic removes 10% of the scenery score.

Each stop also carries an expected time penalty, based on the time normally taken to cover a kilometre. The two penalties are added together, with a floor of zero, which means a route can lose all of its scenery score, but never more than that.

  • For runs, each stop costs 16 seconds of the 360 seconds a kilometre takes.
  • For rides, each stop costs 12 seconds of the 138 seconds a kilometre takes.

Example: how traffic and stops affect a route

Runs
Scenery score80 points
Route8 km, 48 minutes
Stressful traffic10% of the length
Stops9 stops, 144 s waiting: 5% of the time
Scenery score left68 points
80 × (1 − 0.10 − 0.05) = 68
Rides
Scenery score80 points
Route26 km, 60 minutes
Stressful traffic10% of the length
Stops15 stops, 180 s waiting: 5% of the time
Scenery score left68 points
80 × (1 − 0.10 − 0.05) = 68

How the best compare

To show how much better Remap's routes are, we compare them with typical routes generated from residential streets across the city.

Typical routes vs. Remap's best

Each row in the comparison tables shows one part of the route score, expressed as a percentage.

Typical is the median score across all routes generated from residential streets across the city.

Remap's best is the median score of the routes featured in our rankings: the best run in each district, and the best ride from each starting point at each distance.

Scenery lost to traffic and stops shows how much of a route's scenery score is lost due to traffic and stops. Lower is better.

Comparing like with like

Route scores vary with distance, so we compare routes of the same length wherever possible.

For runs, the summary rows above the distance breakdown compare the 5 km routes featured on these pages with typical 5 km runs. The individual rows compare routes of the same distance: 5 and 15 km. Typical is the median score of all runs we generated at that distance from our test starting points, including those not featured on these pages.

For rides, the summary rows compare the 20 km routes featured on these pages with typical rides. We use 20 km because it's closest to the median length of a typical ride (22 km). The individual rows compare routes of the same distance: 20, 60 and 100 km. Typical is the median score of all rides we generated at that distance from our test starting points, including those not featured on these pages.

Runs
MeasureTypicalRemap's best
Through nature20%76%
Views0%0%
Longest nature stretch12%71%
Climbing78%100%
Scenery lost to traffic and stops8%2%
Overall score8%42%
5 km runs8%42%
15 km runs11%43%
Rides
MeasureTypicalRemap's best
Through nature25%54%
Views0%8%
Longest nature stretch12%36%
Climbing67%43%
Scenery lost to traffic and stops38%22%
Overall score7%24%
20 km rides9%24%
60 km rides5%12%
100 km rides4%8%

A consistent sample across the city

Washington DC is divided into 791 squares, each 500 m across, and 606 of them contain a residential street. In each of those, the starting point is on the residential street closest to the square's centre.

Up to 200 of these starting points are then chosen, spread evenly across the city.

Every city is sampled the same way, however many stations it has.

From each starting point, Remap generated one 5 km run and one ride, and every route it generated was kept: 1,731 runs and 2,222 rides in Washington DC.

A representative range of ride distances

People don't ride the same distance every time, so these sample rides vary in length.

Every city uses the same spread of distances:

  • half are shorter than 22 km
  • none are shorter than 8 km or longer than 120 km
  • neighbouring starting points receive different distances to ensure short and long rides are spread across the city

In Washington DC, these rides range from 8 to 120 km. Half of these rides fall between 14 and 34 km, with a median of 22 km.

The rides featured on these pages are 20, 60 and 100 km. Each distance is ranked separately.

Where the routes start

Runs

We found that public transport stops give the best spread of starting points: rail, metro and tram stations, bus and ferry stations, and bus stops in districts with few rail, metro or tram stops.

Starting points cover every district, with up to 10 in each.

Each candidate stop gets a short test run, and the stops with the highest scoring test runs become the starting points for the routes on these pages.

Districts follow the areas Washington DC is divided into, as mapped in OpenStreetMap.

Starting points kept in each part of Washington DC
DistrictStations triedStarting points kept
Ward 2133
Ward 532510
Ward 11349
Ward 6245
Ward 730610
Ward 32389
Ward 42219
Ward 82946

Rides

The city is divided into 3 km squares and we select one candidate starting point in each. Rail and metro stations are prioritised, followed by tram stops, other stations and finally bus stops. When several qualify, we choose the one closest to the centre of the square.

Each of these 27 candidates gets a 20 km test ride. The 26 highest scoring in Washington DC are ridden at 20, 60 and 100 km.

At each distance we show up to 5 of the city's best rides, at most one per starting point. A ride is left out as a near-duplicate when it and a better one share 80% of either one's roads. We have a total of 13 starting points.

After dark runs

We consider a run well lit if street lighting is recorded in OpenStreetMap along at least 60% of its length. Sections without recorded lighting count as unlit. We only report a route's lighting when lighting information is available for at least 75% of its length.

In Washington DC, OpenStreetMap has lighting information, lit or unlit, along 7% of the combined length of the runs we ranked; the rest has none. We show after dark runs only where that covers at least 50%. There are none this month.

How long a route takes

Estimated times assume a steady pace of 6 minutes per km running and 26 km/h cycling. Your actual time will depend on your pace.

We run this report every month

Every month, we regenerate the routes using the latest available map data and recalculate the rankings. As the map changes, so can the best routes in each district.

This is Washington DC's first edition, so there are no previous results to compare yet.

This edition

Generated 15 November 2026 by engine 99b44253a, map data version 14, foot line catalog 16, cycle line catalog 16: 2,217 requests, 20,837 routes, of which 2,435 ranked, from 1,555 stations screened.

See where today takes you

Choose your starting point. We’ll find the adventure.