Checking a Map Against the Ground: A Field Guide

A farm map is a working hypothesis about your property. It tells you where a boundary should be, where a fenceline sits and where water runs. The ground is the evidence. Checking a map against the ground is the simple discipline of walking the places you depend on and writing down where the paper and the paddock disagree.

The New Zealand farm planning guidance from Beef + Lamb New Zealand frames mapping as a step within a wider plan and notes that a base map over an aerial, satellite or topographic image is a useful starting point [beeflambnz.com/sites/default/files/2026-06/Intro-overview.pdf]. That is the map you carry. This article is about the walk that follows.

Why check a map against the ground at all?

Because maps age faster than land. A fenceline is moved, a culvert is replaced, a track is cut, a shelterbelt is felled, a water trough is shifted, and the map on the wall still shows the old arrangement. Older maps also inherit other people's scale and purpose: a regional council map or a fertiliser company map may show soil or contour at a broad scale rather than the paddock scale you manage at. The B+LNZ guidance is explicit that maps at the 1:50,000 and 1:63,360 regional scale are too coarse for farm management purposes, even though they are useful starting points [beeflambnz.com/sites/default/files/2026-06/Intro-overview.pdf].

A walk also catches what was never mapped: an unformed crossing, a wet-winter spring, a gate that no longer closes, a stub fence never removed. Each matters if the record is to be trusted by a future reader.

What should I carry and how should I mark it?

Carry the map, a pencil, a phone or camera, and something pocket-proof to write on. Print two copies if you can. Work in pencil so you can change your mind, and note the date and your name: an undated field note is nearly useless later, since you cannot tell whether the discrepancy was fixed.

Photograph anything you intend to change. A fence strainer, a gate, a culvert headwall, a trough, a broken marker. Take a wide shot that shows the surroundings and a close shot that shows the detail. If you plan to return to the same spot, note roughly where you stood, so the next photo is comparable. The article Photo points that stay comparable covers how to set those points so they stay useful across seasons rather than drifting into a loose collection of images.

How do I walk a boundary or fenceline properly?

Walk the line itself, not the paddock beside it, and stop wherever map and ground disagree. The differences are small but cumulative: a corner set back, a section following a different spur, a boundary along a stream that has shifted, a straight line that is really a surveyed dogleg.

At each stop, mark the map with a symbol that means "correct this", then write one sentence describing the difference. "Southwest corner of Middle Paddock set back about 20 metres to the old macrocarpas." A number and a landmark are more useful than an adjective. Repeat landmarks and unit names along the way, because a map that uses consistent names is one that others can follow. The article Naming units so others can follow explains why a stable naming scheme is the difference between a record and a riddle.

How do I handle water, tracks and other placed features?

Water and tracks are the features most likely to have changed and to cause problems if wrong. Note where a drain really ends, the true alignment of a race or track, and the location of troughs and stock water points you rely on.

A practical decision checklist for each feature is useful, because it keeps a walk consistent across visits and across people.

Feature	Check	Mark if wrong
Boundary	Line matches fence and legal line	Yes, with a note
Fenceline	Condition, alignment, gates	Yes
Track or race	Usable alignment, crossing points	Yes
Water, drain, trough	Position, direction of flow, endpoint	Yes
Shelterbelt and trees	Extent, gaps, renewal	Yes
Structures	Sheds, yards, crossings, bridges	Yes
Hazards and waste	Old dumps, dip sites, disposal areas	Yes, and keep the note

The B+LNZ farm mapping guidance lists farm infrastructure, land features, water features and monitoring sites among the things that may be worth identifying on a map, and it notes that many features exist, so a single crowded sheet is best split across copies or digital layers [beeflambnz.com/sites/default/files/2026-06/Intro-overview.pdf]. That advice is practical: a map that tries to show everything at once shows nothing clearly. The article Map layers versus map clutter is the companion piece to that decision.

What do I do with the corrections afterwards?

Back at the desk, with the walk still fresh, sort notes into three piles: fix now, check with someone, and interesting but not yet actionable. Update the map or the fenceline and boundary layer, and update the written description of any unit the walk touched, since a boundary change often changes what belongs in it.

The B+LNZ step outline places farm mapping before the identification of land management units, which is a sensible order: the boundary and features set the frame, and the units sit inside it [beeflambnz.com/sites/default/files/2026-06/Intro-overview.pdf]. If a walk changes a boundary or a fence in a way that splits or merges a block, the resource chart for that unit may need a quiet edit too. The article Building a resource chart shows how those records hang together.

How do I keep the record usable rather than ornamental?

Keep a running correction log. One line per change: date, what was found, what was corrected, who did it. A log is more honest than a tidy map, because it shows the map's history rather than pretending the map was always right.

Store the walk's photos with the date and the unit name in the filename or the caption, and keep the marked paper sheet for the season. When the season ends, archive it. A spreadsheet that holds the corrections should be simple enough to re-check later: one row per feature, sortable columns, no merged cells and no formulas that break when a row is inserted. The workbook guidance from B+LNZ's computing-for-farmers material is built around exactly that kind of plain spreadsheet work, and it treats sorting, filtering and basic formulas as ordinary tasks rather than advanced ones [beeflambnz.com/sites/default/files/2026-06/Computing-for-Farmers-Workshop.pdf].

How often should I walk the ground?

There is no single right answer, but there is a useful rhythm. Walk the whole boundary once a year, ideally in the same season so the comparison is fair. Walk the fencelines and tracks that carry the most stock more often, because they wear faster. Walk after any event that is likely to have changed something: a storm, a flood, a major fencing job, a new track, a change in lease or licence.

The B+LNZ introduction notes that keeping an eye on natural resources is a day to day part of managing a farm, alongside stock, pastures and finances, and that a plan does not have to be built all at once [beeflambnz.com/sites/default/files/2026-06/Intro-overview.pdf]. The same is true of correcting a map. One boundary and one fenceline, done properly, are worth more than a rushed sweep of the whole farm.

A map that matches the ground is not a decorative artefact. It is the shared reference that lets a new worker find a gate, lets a contractor understand where a track runs, and lets you plan the next fence with confidence. The walk is what keeps it true.