Picking a running route in a city you do not know

You arrive in the evening and you want to run before breakfast. A map you have never used, a hotel address, and no idea which side of the river people run on. The decision gets made from written information. The question is which written information is worth anything.

What you can judge before you get there

Four fields decide most of it.

How far the route is, whether it returns to where it started, what it is made of, and how many corners it contains. Those four can be read without seeing the place. The view and the atmosphere cannot, and neither changes what happens at seven in the morning.

• Distance tells you the shape of the morning, but only once you know whether the route closes on itself.
• Loop or line tells you whether the number in the listing is the number you run.
• Surface decides shoes.
• Corner count tells you how much attention the route demands while you are on the wrong time zone.

Anything gated has hours. A fifth field is missing from almost every route listing: whether you can get in. NYC311 states that Central Park "is open from 6 AM to 1 AM" (NYC311, fetched 2 August 2026), which rules out a five o'clock start for anyone whose body clock is six time zones behind.

Loop or line, and why it decides your morning

A loop returns you to your starting point. A line does not, and that flag changes the arithmetic more than distance does.

The catch? An eight kilometre line is a sixteen kilometre morning unless you have a plan for the far end.

In the published route data, Central Park Full Loop is 9.89 km and returns to its start. Hudson River Greenway is 8.12 km and does not. Seine Left Bank Quays is 3.45 km and does not, which makes it a short out and back, not a short run.

Read the flag rather than the name. Stanley Park Seawall appears as 7.97 km that does not return to its start, even though the seawall is known as a circuit, because the published shape stops where it stops. Waterfront paths are the common case, and most of them are lines: waterfront running routes.

1. Out and back. Doubles the distance, and the second half is navigation you have already done.
2. One way, then walk back. Good when the far end sits nearer your hotel than the start did.
3. One way, then transit back. Check the service runs at the hour you will finish.

Corner count as a proxy for attention required

Corners are where you get lost.

Distance is where you get tired. In a city you do not know, the corner count is the more useful of the two, and it is the field you are least likely to be given.

It is also not proportional to length. In the published route data, Central Park Full Loop carries two turn instructions across 9.89 km. Thames Path South Bank carries nine across 3.76 km. Hyde Park and Kensington Gardens carries thirteen across 6.76 km.

Runflake computes the turn instructions for each route from that route's own shape, with its own turn detector, before the route is published. They are not written by hand and not taken from a navigation provider. A bend becomes a turn only when the direction of travel changes by at least 55 degrees measured 35 m before and after the point, and the same 55 degrees still holds when the bend is re-measured over a wider 56 m window.

So a corner in this sense is a geometric event, not a landmark. A long sweeping bend you would never call a turn does not count. A short dogleg around a building does. Read the count as attention load, not as a description of the place. For what those counts feel like on the road, start with city running routes with turn cues.

Surface, and the words apps use for it

Two values. The published route data calls a route paved or mixed, and nothing else. Of the eighteen routes in the set, two are labelled mixed: Richmond Park Tamsin Trail and Crissy Field to the Golden Gate. The rest are paved.

Narrow vocabulary, and narrow is honest. Mixed does not tell you the proportion or where the change happens. It says nothing about what the surface does after rain. It tells you not to arrive with only the shoes that need tarmac.

Plan for the coarser label.

Travel writing offers adjectives instead. Beautiful, historic. A local secret. None of those are measurements and none are checkable before you go. Plan off the label that came from data.

Starting from a hotel rather than a trailhead

A published route starts where the route starts. Your hotel is somewhere else, and the gap between the two is part of your morning whether you planned for it or not.

Most bad first runs in a new city are the connector, not the route.

1. Measure the connector the night beforeWork out how far the route's start is from the door. Under a kilometre is a warm-up. Three kilometres is a second run you did not intend.
2. Walk it rather than run itWalking gives you the junction sequence in reverse for the way home, at a speed where you can read street names.
3. Confirm the entrance and the hoursGated parks close. Check the authority that runs the park, not a listing site, for the day you are running.
4. Decide the return before you startOn a line route, the way back is a decision for fresh legs and a full battery, not for the far end in the dark.

Jet lag does the damage here. The hour you feel like running is often earlier than the hour the city opens for it.

What to do when the route data runs out

Two routes in the published set carry no turn instructions at all: Seine Left Bank Quays and Gyeongui Line Forest Park. That is not a hole in the data. A path that never changes direction by enough to count produces no instructions, and the useful thing is to say so out loud.

The distinction matters on the road. "This course has no turn guidance. Follow the route on the map." means the route has no corners worth announcing. "Turn guidance could not be loaded for this course, so this run has no turn cues." means something failed. The first is information. The second is a reason to keep the map open.

Curated route geometry here comes from OpenStreetMap, credited to OpenStreetMap contributors under the Open Database License, which the project describes as data you are free to copy, distribute, transmit and adapt as long as you credit OpenStreetMap and its contributors (OpenStreetMap copyright page, fetched 2 August 2026). The same page notes that inclusion implies no warranty from the original provider. A path can exist on the ground and be missing from the extract, or sit in the extract and have been fenced off since.

What you want from software at that point is plain speech about what it does and does not know. Leave the route and the run keeps recording while you are told the size of the gap: "You are {N} {unit} off the route. Keep running. Guidance resumes when you are back on it." That is a report, not a rescue.

There is no rerouting and no arrow pointing back, so finding your way to the line is your job.

Three other silences are worth knowing before you rely on any of it. Run the course backwards and the cues switch off instead of flipping over: "You are running this course in reverse, so turn cues are off." At the start of a course run nothing is announced until 60 m of forward progress has been seen, and until then the screen says "Working out which way you are running." And if the route itself does not arrive, the run does not begin as a course run at all: the countdown holds on "Loading the course", then says "Runflake needs the route to follow it, and it did not arrive. Nothing has been recorded yet." with Try again or Skip course. That last one is worth planning around in a hotel with poor signal, because the route is fetched at the moment you start.

Your own fallback should be as plain. Screenshot the map before you leave the room. Note one bailout point where you already know the way back, and one landmark tall enough to see from most of the route.

Running somewhere you cannot read the signs

Direction is the local rule you are most likely to break. The Chiyoda City Tourism Association states that everyone runs the Imperial Palace loop counterclockwise, that one lap is roughly 5 kilometres, and that the course is not for runners alone, because bikes and pedestrians use it too (Visit Chiyoda, fetched 2 August 2026). The same page describes "no running areas" at the main sightseeing spots because they get very crowded, and names Nijubashi Bridge as one. None of that is signposted in a language you can read at six in the morning, and all of it is knowable the night before.

Turn instructions derived for one direction are not simply reversible, because a bear left and a U-turn are not simple mirror images, and a wrong instruction at a junction is worse than silence. That is the stated reasoning behind switching the cues off in reverse. Nothing is guessed at. Running against the local flow costs you the etiquette and the guidance at once. For a loop where the convention is documented and the shape is published, see the Tokyo Imperial Palace run, which measures 5.07 km in the route data.

Four habits carry across any city where you cannot read the signage. Run the direction the other runners are going. Keep to the side people pass on. Give way to pedestrians on a shared footway. Look up at every crossing instead of at your watch.