Landforms worth separating on a farm map

Which landform differences genuinely change how you observe and record a block?

Separate two areas onto different map units when they differ in slope, aspect, elevation or landform in a way that changes what you would write down, sample or walk past. If the difference does not change a decision, a note or a route, it belongs inside one unit rather than splitting your map into near-identical pieces.

The practical test is behavioural: would you describe these two places differently, sample them separately, or expect them to respond differently over a season? If yes, they deserve separate lines. If the only difference is a boundary you inherited from someone else, that boundary can wait.

Why does drawing too many boundaries cause problems later?

Every boundary you draw has to be maintained. Lines on a map are promises that someone will keep naming, noting and re-checking what sits on either side. Each extra unit multiplies the rows in your resource chart, the cells in your spreadsheet and the chances that two people record the same paddock under different names.

A useful farm plan resource notes that maps can get cluttered and that, in hard copy, you need enough copies to keep each one readable; digital layers can be separated instead (https://beeflambnz.com/sites/default/files/2026-06/Intro-overview.pdf). That advice points at a real trade-off. Detail is only worth carrying if the detail survives everyday use.

A land management unit, in this publication's sense, is a mapped area you can name, describe, walk to and revisit. That is a deliberate choice about how to organise the land, not a survey result.

Which landform differences usually earn their own line?

The following are the differences that most often change how a block is observed and recorded. Each one is a reason to look more carefully, not an automatic instruction to split.

Difference	Why it may change how you record a block	Worth its own line when
Slope	Affects how you walk, sample and describe ground cover	You would sample or describe the two areas differently
Aspect	Changes exposure through the day and season	You expect different timing or condition notes
Elevation	Changes the seasonal pattern you observe	Your notes would be dated or worded differently
Landform type	Steep land, terraces and river flats behave as different places	You would name and describe them separately
Erosion or hazard features	Change where you look and what you watch	You already keep a monitoring note about it
Water pathways	Change how water moves across a block	You follow or sample the pathway deliberately

Slope and aspect are both listed in farm mapping guidance as features worth identifying where they exceed a small threshold (https://beeflambnz.com/sites/default/files/2026-06/Intro-overview.pdf). Landforms, elevation and erosion-prone areas appear in the same feature list. The list is a starting inventory, not a rule about how many units a farm should have.

Aspect is often the difference people overlook. Two neighbouring faces can sit at the same elevation and slope yet dry, green up or hold condition on a different timetable. If your notes for one would be misleading for the other, they are not the same unit for record-keeping purposes.

Elevation matters in a similar way. A block that sits higher often has a different season rather than just a different view, and a record that does not distinguish the two will be hard to interpret later.

When should two similar areas stay as one unit?

Keep them together when the difference does not change anything you would write or decide. A gentle break in slope that you cross without thinking does not need a line. A small rise that changes how you sample or move through the block does.

A short decision checklist:

1. Would I describe these two areas differently in a field note? If no, treat them as one unit.
2. Would I sample, count or photograph them separately? If no, treat them as one unit.
3. Would I expect them to differ over a season in a way I would record? If no, treat them as one unit.
4. Would a second person name them separately without being told? If no, treat them as one unit.
5. Could I explain the boundary to someone standing on it? If no, reconsider the split.

This keeps the map aligned with how the land is actually worked. It also makes the unit names easier to hand on, because each name describes something a person can see.

The general principle behind land management units is that they exist to be identified, named and described on a resource chart, then assessed for strengths, weaknesses, opportunities and conditions of use (https://beeflambnz.com/sites/default/files/2026-06/Intro-overview.pdf). A unit that cannot carry that description is not pulling its weight.

How do separated landforms connect to naming and the resource chart?

Once a landform difference earns its own line, it needs a name that a stranger could follow. Names built from position and form tend to age better than names built from a person, a stock class or a temporary use.

The resource chart is where the separation pays off. Each row describes one unit: how it sits, how it is used, and what is worth watching. If two rows would read almost identically, that is a signal to merge them. If one row has to hold two different descriptions, that is a signal to split it.

This is also where landform choice and record structure meet. Separating blocks is not an end in itself; it exists so that the notes, totals and comparisons on top of the map mean something. For a fuller picture of how units are defined and named, see What counts as a land management unit and Naming units so others can follow.

How do you check the boundaries you first drew?

Take the map to the ground. Walk the boundary you drew and ask whether it is where you would actually stop and change what you are doing. Boundaries drawn at a desk tend to follow convenient shapes; boundaries walked on the ground tend to follow the land.

Where the map and the ground disagree, record the correction with a date. A short dated note is more useful than a redrawn line with no explanation. Guidance on working through a farm plan describes it as a living document that gets reviewed and revised over time, with information already held from councils, fertiliser companies or previous workshops often useful as a starting point (https://beeflambnz.com/sites/default/files/2026-06/Intro-overview.pdf). That framing supports editing a boundary rather than defending the first version.

Comparing a fresh walk against the drawn line is covered further in Checking a map against the ground.

What does separating landforms change in practice?

It changes what you can honestly compare. Records only support useful comparison when the areas being compared are genuinely alike in the ways that matter. A well-separated map makes seasonal notes, totals and photo comparisons more interpretable, because each record refers to a consistent piece of ground.

It also changes how a spreadsheet behaves. A tidy unit list means each row is a real place rather than a vague region, and sorting or filtering the rows keeps its meaning. More on structuring those records sits in Building a resource chart.

A spreadsheet workbook built around a worked example of stock reconciliation shows how updates flow through a small number of consistent rows rather than a sprawling, ambiguous list (https://beeflambnz.com/sites/default/files/2026-06/Computing-for-Farmers-Workshop.pdf). The same logic applies to land units: a stable, well-chosen set of rows is easier to update than a tangled one.

The aim is not the finest possible map. It is a map whose lines each do a job, so the observing and recording that follows stays clear.