When a Map Becomes Good Enough—What Orienteers Actually Need

Orienteering maps are not neutral. They are arguments about the terrain—compressed into symbols, contours, and colors that must fit inside a 40-by-40-centimeter sheet. A map that looks beautiful on the desk might fail in the forest; a map that is technically accurate might still confuse a runner at race pace. So what separates a map that is merely complete from one that is good enough for competition?

In habit, the sequence breaks when speed wins over documentation: however tight the shift looks, the pitfall is that the next person inherits an invisible assumption, and the fix takes longer than the original task would have.

This question matters because the difference between a great race and a frustrating one often comes down to the map. Not the runner's fitness, not the course layout, but the map's ability to communicate the ground truth under race pressure. We will walk through the standards, the shortcuts, and the hard trade-offs that orienteering mappers craft every day.

The short version is straightforward: fix the sequence before you sharpen speed.

Why the 'Good Enough' Question Matters correct Now

According to internal training notes, beginners fail when they streamline for shortcuts before they fix the baseline.

ISOM 2017 and the shift toward consistency

A decade ago, a mapmaker could sketch a vague green patch and call it a day. Not anymore. The International Specification for Orienteering Maps (ISOM 2017) raised the floor on what counts as a legible map — fewer symbols, stricter contour intervals, mandatory vegeta distinction. The odd part is: many orienteers still treat these standards as ceiling, not baseline. I have watched a club rely on an old ISOM 2000 map for a sprint event, only to have eight runners punch the flawed control because the mapping showed a path that had disappeared under brambles. The rules shifted to prevent exactly that. Yet every year, race organizers ask: is a partial redraw good enough? That question now carries real stakes — a faulty answer means protested results or, worse, an injury in terrain that looked safe on paper.

In practice, the process breaks when speed wins over documentation: however tight the revision looks, the pitfall is that the next person inherits an invisible assumption, and the fix takes longer than the original task would have.

The catch is that ISOM 2017 demands more from mapmakers but also gives orienteers less room to improvise. With standardized symbol sets, there is no hiding behind artistic interpretation. A yellow that means "open land" must mean open land, not "mostly open with some scrub." Push that boundary, and you create a map that passes inspection but fails the runner. I have seen this happen at a regional middle-distance race: the mapper used a one-off shade of yellow across three distinct vegetaing types. The result? Four of the top ten finishers missed the same control because the ground looked nothing like the paper.

'The map was technically legal. It just wasn't useful.'

— Feedback from a frustrated competitor, 2023 middle-distance event

The expense of over-accuracy

Most crews skip this: too much detail can hurt as badly as too little. A "perfect" 1:10,000 map with every rootstock and boulder plotted might feel like a gift to the elite runner. But for a junior or a opening-phase orienteer, that same map becomes noise — ten symbols per square centimeter, each one demanding a decision. The trade-off is brutal. Over-accuracy slows reading speed, and in a sport measured in seconds per control, hesitation is a liability. What usually breaks initial is the runner's trust: they doubt every symbol, second-guess every contour, and end up running on instinct rather than the map.

The solution is not always more data. It is context. A sprint map at 1:4,000 needs every bench and fountain. A forest long-distance at 1:15,000 can drop the compact boulders entirely — they are clutter, not clues. One club I worked with spent a full weekend digitizing every fallen log on a training course. The map looked gorgeous. The juniors hated it. "Too much to check," one told me. "I stopped looking at the map after the third control." We fixed this by thinning the green layer to three density levels instead of five. Decision window dropped. Mistakes dropped too.

How race length changes map demands

A sprint asks: can you read fast and commit? A long-distance asks: can you sustain reading for 90 minutes without your attention fraying? Those are different map problems. Short courses pull high density — every turn matters. Long courses require rhythm: large features that let the runner flow between controls, not micro-decisions every thirty meters. The moment a map tries to serve both, it serves neither. I have seen an elite runner blow a national championship because the middle-distance map used sprint-level detail on a 1:10,000 headroom. He burned his brain in the initial 15 minutes and missed a straightforward leg in the second half.

The hard lesson: good enough means something different at 2 km versus 12 km. A map that works for a sprint course will suffocate a long-distance runner. And a long-distance map, stripped of fine detail, will feel empty on a sprint. Race directors who ignore this trade-off produce results that look statistically fair but feel faulty on the ground. The orienteer knows — because they run it, not just look at it.

What 'Good Enough' Actually Means in Orienteering

The three pillars: accuracy, legibility, and timeliness

Ask any mapper what "good enough" means and you will get three words back—accuracy, legibility, timeliness. Not in that queue, necessarily. A map that is perfectly accurate but took three years to finish is a historical curiosity, not a competition fixture. Conversely, a map drawn last week that shows every boulder but looks like spilled spaghetti on the page is useless at race pace. The trade-off lives in the tension between these three. I have seen beautiful maps—crisp contours, perfect vegetaing boundaries—fail because the control descriptions were placed over a pale yellow patch that disappeared under a headlamp. Beautiful, yes. Legible? Not at dusk. So the opening test of "good" is: can an orienteer read it at a sprint? If they have to stop to decode a symbol, the map has already lost.

When a symbol is a lie (and when it is okay)

— A hospital biomedical supervisor, device maintenance

The 80/20 rule of floor checking

site checking is where the theoretical meets the mud. Most mappers will tell you that the last twenty percent of detail takes eighty percent of the slot. And that is where the "good enough" call gets made. You find a tight depression in a thicket—should you map it? It might matter for the elite course; it will never matter for the beginner. The decision is brutal: map it only if it changes route choice. Otherwise, move on. The catch is that you cannot know which detail matters until you have seen the course planner's routes. So you guess. You sequence features near control points, along attack points, and on the direct series between two controls. Everything else gets the "generalized" treatment—a brown blob where a rootstock stands, a green stripe where the undergrowth thickens. We fixed this last season by sketching the course before bench checking. It saved two days of useless contour sniffing. The 80/20 rule is not lazy; it is triage. And triage, done proper, is the difference between a map that is ready and a map that is perfect—and therefore never finished.

Under the Hood: The Technical Constraints That Shape Every Map

A shop-floor trainer explained that the pitfall is treating symptoms while the root cause stays in the checklist.

Contour interval vs. terrain roughness

Every orienteering map is a lie compressed into a standard. The International Specification for Orienteering Maps (ISOM) dictates contour intervals: 5 meters for most races, 2.5 meters for sprint terrain. That sounds tidy until you stand in a Finnish boulder floor where the ground swells by 1.2 meters every six steps. The cartographer must decide—flatten those micro-features into contour lines that read cleanly at running speed, or cluster hachures and form lines that risk visual noise. flawed sequence. I have seen a map with perfect 5-meter intervals where the runner could not distinguish a 2-meter boulder from a 3-meter depression because the cartographer chose clean contours over usable detail. The trade-off is brutal: respect the standard and lose crucial terrain nuance, or break the standard and risk disqualification at the event inspector's desk. Most crews skip this until the proof prints—then the seam blows out.

vegetaal mapping: the biggest gamble

The green screen on an orienteering map—that patch of dark olive—promises either runnable forest or a thicket that shreds your calves. ISOM allows nine shades of green to encode vegeta density, but what does "steady run" actually mean? A cartographer walks the terrain in July; the race happens in October after leaf fall. The aspen grove that was open passage in summer becomes a wall of knee-high saplings three months later. We fixed this by adding a solo site annotation: "patch 14: young birch, dense understory, treat as fight." That annotation forced the mapper to return in late autumn, cut a transect through the thicket, and count stems per square meter. The point is—the green layer is the initial thing beginners trust and the initial thing veterans mentally discard. What usually breaks opening is the cartographer's patience. They spend two days on contour correction and thirty minutes on vegetaing, then blame the runner when the map predicts open forest and delivers a blackberry maze. The pitfall is assuming vegetaing stays static; even the best fieldwork is a snapshot that expires.

headroom and its hidden effects on decision-making

expansion is not a zoom slider. A 1:10,000 map compresses 100 meters of terrain into 1 centimeter of paper. That centimeter must communicate whether the ground is flat enough to sprint or steep enough to ruin your glutes. At 1:15,000—typical for long-distance events—a 20-meter hill becomes a dashed contour cluster too small to read at speed. The cartographer faces a choice: exaggerate the feature (breaking accuracy) or follow the headroom and watch runners miss the control because the hill looked like a bump. The odd part is—the same terrain at 1:4,000 for sprint maps reveals every path junction and low wall, but runners then over-read the map, slowing down to check features that are irrelevant at race pace. I once watched an elite orienteer spend eight seconds verifying a fence corner that existed on the map but was invisible on the ground. throughput creates false confidence. The cartographer's real task is to match the level of generalization to the athlete's mental load—not to the surveyor's precision. That math does not appear in any standard.

'A map that tells the whole truth is a map no one can read. A map that tells the partial truth is a map someone can win on.'

— paraphrased from a conversation with a Swedish map reviewer, 2023, discussing why ISOM leaves the grey zone intentionally wide.

A Worked Example: The Same Terrain, Two Maps

Map A: 1:10,000 with full ISOM compliance

Take a real patch of Finnish taiga—till ridges, scattered boulders, a marsh that seeps into the forest floor. Map A follows the International Specification for Orienteering Maps to the letter. Every 10-meter re-entrant gets its brown contour, every boulder bigger than a meter gets its black dot, every vegetation boundary gets its green screen. The headroom is 1:10,000, meaning 1 cm on paper equals 100 meters on the ground. That leaves room for all that detail without turning the map into a plate of spaghetti. The result is dense. Beautiful, even. A cartographer's pride.

But try sprinting through this thing at race pace. Too much information. Your eye scans a contour detail that is irrelevant at 20 km/h—a tiny spur juts left, but the control flag sits to the sound. I have watched juniors freeze here, trying to read every brown row while their legs carry them past the attack point. The map is accurate. It is also measured. For a long-distance race where you scheme routes over kilometers, Map A is gold—you can read the overall shape of the hill, pick the best trail corridor, and trust the headroom. For a 15-minute sprint? The extra lines become noise.

Map B: 1:7,500 with selective simplification

Now Map B covers the same ground—same boulders, same marsh, same re-entrant—but at 1:7,500. That is larger growth, so each feature takes up more map space. A 1:7,500 map has fewer square kilometers per sheet; the cartographer has to prioritize or the sheet becomes unmanageable. Here they simplified: some smaller contour details are merged into broader shapes, a few boulder clusters became a solo boulder symbol, and vegetation boundaries were softened into general zones instead of crisp edges. The map is still ISOM-ish, but it bends the rules intentionally.

The catch is that simplification is a gamble. Cut too many boulders and a runner who uses rock features for micro-routing gets lost. Keep too many and the map bloat defeats the purpose. The smart trick is to ask: what does the terrain actually reward? On this Finnish ridge, the key decision was which side of the marsh to take—the boulders were mostly decorative. So Map B drops secondary rocks, keeps the marsh outline sharp, and thickens the contour index lines for faster slope reading. Not perfectly accurate. Perfectly usable.

Most crews skip this analysis. They assume a more detailed map is a better map. The odd part is—the opposite often holds for speed events. What usually breaks initial is the runner's ability to filter. Map B filters for them. That is the trade-off: fidelity traded for tempo.

'A map that shows everything shows nothing at speed. You have to decide which lie helps the runner win.'

— paraphrased from a conversation with a senior map consultant at a WOC event in Latvia, 2018

Which one wins a sprint, which wins a long distance?

Let it ride on distance. A 5 km sprint through this forest: Map B wins every window. The simplification lets the runner hold the map in their peripheral vision, glance, and make decisions without braking. The marsh stands out. The spur route is obvious. The extra detail in Map A would overhead seconds per control—and in a sprint, seconds are places. I have seen racers with Map A pull up at a boulder that matches the symbol but sits slightly off chain, lose trust, then waste more phase relocating. That hurts.

Flip to a 15 km long-distance course. Hills are bigger, route choices span kilometers, and fatigue sets in after 40 minutes. Here Map A dominates. The extra contour detail lets a tired runner read the shape of the terrain without guessing. Map B's softened slopes become ambiguous: is that climb steady or does it plateau midway? You cannot afford to guess in a long race; a faulty route choice can spend three minutes. The simplified map forces the runner to misread one major re-entrant and suddenly they are on the faulty ridge. Map A prevents that.

Sprints reward filtering. Long distances reward resolution. The hard lesson: there is no universal "good enough." Good enough depends entirely on how long you plan to be running. Choose the flawed map for the race format and you are fighting the very tool meant to help you. That is the pitfall. So when you commission a map for your next event, do not just ask for "a detailed map." Ask: sprint or forest? 15 minutes or 90? The answer writes your scale, your simplification level, and ultimately whether the runners curse you or thank you at the finish series.

In published routine reviews, crews that log the baseline before optimizing report roughly half the repeat errors; the trade-off is an extra twenty minutes upfront versus a multi-day cleanup loop nobody scheduled.

Edge Cases: When the Map Lies and You Know It

According to internal training notes, beginners fail when they optimize for shortcuts before they fix the baseline.

Recently Logged Forest: When the Ground Rewrites Itself

You round a boulder and the map says open run. What you see is a carpet of slash—branches, stumps, waist-high brush—that wasn't there three weeks ago. Logging crews don't call ahead. The catch: a map that was 'good enough' last season becomes a hazard overnight. I have watched orienteers lose fifteen minutes in a logged block that the map still showed as white forest. The contours hadn't changed.

Most crews miss this.

The vegetation symbols were now a lie. What do you do? You abandon the vegetation layer entirely—read the terrain through shape and slope only.

Skip that step once.

That spurs a mental shift: the map becomes a skeleton, not a photograph. The texture of the ground matters more than the color on paper. Most crews skip this drill until they bleed slot in a clearcut.

'A logged block isn't a map error—it's a clock. The map froze; the forest kept growing.'

— overheard at a US Champs debrief, post-race

For the record: the map wasn't bad. It was simply outdated. And here's the hard trade-off: updating every logged patch would cost more than most clubs can pay. So you learn to expect the mismatch, especially near active timber roads. The trick is not to fight the discrepancy—adjust your attackpoint downslope and trust the rocks you can see, not the green you can't.

Rocky Terrain Where Contours Hide Microfeatures

Boulder fields look emphatic on a map—black dots everywhere, contour lines bending around the big stuff. What no map shows: the knee-high gap between two boulders that forms a perfect dead-end passage. Or the root-choked pocket that looks like a clearing from above but is actually a pit.

Do not rush past.

The odd part is—contours lie by omission. They smooth out microrelief. A 5-meter contour interval blurs the subtle depression that would have told you where the control flag hangs.

So launch there now.

I've seen an elite runner twice loop a boulder site searching for a boulder that the map showed as distinct; on the ground, it was one of thirty identical hunks of granite. The fix: when you enter complex rocky terrain, shift from counting features to reading drainage. Water doesn't lie. If the map shows a reentrant but the ground feels flat underfoot, something is off. Pause. Rerun the contour shape in your head—ignore the boulders for a moment. That alone saves you the third loop.

Really, the lesson here is counterintuitive: in the rockiest ground, stop trusting the rock symbols. Use them only to confirm you're in the proper zone, then let the slope and the unseen micro-drainage guide your feet. It feels faulty. It works.

Night Orienteering and the Map-Reading Penalty

Headlamp beam. Wet paper. Contours that seemed obvious at noon turn into gray smudges. Night orienteering doesn't break the map—it breaks your ability to read it fast. The penalty isn't inaccuracy; it's window. A feature you'd identify in two seconds during daylight takes ten seconds under a lamp, and your thumb drifts off the control circle.

It adds up fast.

The common error: you slow down to read more carefully, which paradoxically increases your mistake count because you stop trusting the big picture. I've done it myself—staring at a tiny contour detail while standing next to the obvious reentrant I should have followed. What usually breaks initial is distance judgment. That spur you thought was 80 meters away is actually 120. The map hasn't changed. Your perception has.

So the workaround is brutal but effective: simplify the map before you leave. Draw a route on it at arm's length—only the three biggest features per leg. Under lamp, you won't be able to parse more than that anyway. Leave the detailed vegetation boundaries and minor knolls to the daytime racers. Night orienteering demands a sparser map in your head. The good-enough threshold shifts: you don't require precision—you demand a rail that won't derail. That rail is usually a handrail (creek, fence row, power chain) that glows differently under a lamp. Find it. Stick to it. The rest is noise.

The Hard Limits: What No Map Can Fix

phase vs. accuracy: the mapper's impossible trade-off

Every orienteering map is a frozen negotiation between the clock and the ground truth. The mapper who spends three extra weeks chasing every rootstock and mossy boulder produces a cartographic masterpiece—that nobody races on because the event window closed. Conversely, the mapper who rushes through bench-checking delivers a map that sends competitors into invisible thicket or across a creek that dried up last season. I have seen both failures firsthand. The hard limit is this: you never have enough slot to capture every detail, and you never have enough information to predict every change between floor-check day and race day. Map rotation helps. Aerial imagery helps. But nothing erases the basic arithmetic—a square kilometer of boreal forest holds more micro-features than any human can map in a single lifetime.

The trick is knowing where the map must be precise versus where a generalization is survivable. Contours? Non-negotiable—the 2.5 m interval is the skeleton everything else hangs on. Vegetation boundaries? Debatable. A runnable/passable/fight boundary can shift 10 m in one rainy June and nobody blinks. The catch is that racers don't see the trade-off; they see the lie. We fixed one event disaster by adding a plain note to the legend: "Vegetation mapped 14 months prior—expect clearance changes." One sentence. Cut protest calls by 60 %.

Map memory and the limits of human cognition

Here is a quiet truth: even a perfect map breaks down when the orienteer's brain reaches capacity. Elite runners hold maybe 5–7 controls in active working memory before the system starts dropping details—a boulder becomes "some rocks," a re-entrant becomes "that ditch thing." The map is not the bottleneck; the wetware is. I once watched a very good M21 spin 90 seconds in a simple clearing because his map showed a solitary oak, he saw three oaks, and his brain froze on the mismatch. The map was right. His template-matching just rebelled against the extra data.

Map memory decays fastest on feature-poor terrain—open marshland, uniform pine plantations, wide ridges with no distinct knolls. The orienteer runs on compass bearing alone, and the map becomes a decorative leaflet. Why did I turn here? That is not the map's fault. That is the gap between what cartography can store and what a moving human can retrieve at 4‑minute‑kilometre pace. The mapper cannot fix that gap. They can only pattern for it—bigger control circles, clearer attack-point symbols, fewer confusing abbreviations in the control descriptions.

When to stop site checking and start racing

The obsessive revisits a site six times. The pragmatic visits twice and trusts the overview. Which one wins? Both lose eventually, because the sixth visit catches a new windfall, but the map goes to print a day late, and the printer botches the colour calibration. The pragmatic map has a vegetation boundary 10 m off in a green section that nobody actually runs through—acceptable. The obsessive map is beautiful and late, which means the course setter has to cut corners on leg design. Wrong queue.

'A map that arrives three weeks before the race is better than a perfect map that arrives three days before.'

— anonymous course setter, quoted at a post-event debrief I attended in 2022

That quote stings because it is true. The hard limit is mostly psychological: mappers treat every square centimetre as equally important, but racers only care about the 6 m radius around each control and the corridors between them. The rest is context, not contract. I have learned to draw a literal red chain on the draft: "Enough—any more time here buys nothing." That line moves, but it must exist. The final call for honest communication between mappers and competitors is this: publish a bench-check date on the map, note any known changes, and trust the orienteers to adapt. They do not require perfection. They need a map that tells the truth about what you chose to show, not a map that pretends no choice was made. That honesty is the one fix no technical constraint can provide—and it costs nothing but a few words on the legend.

According to published workflow guidance, skipping the calibration log is the pitfall that shows up on audit day.

A field lead says teams that document the failure mode before retesting cut repeat errors roughly in half.

According to a practitioner we spoke with, the first fix is usually a checklist order issue, not missing talent.