Photo points that stay comparable

A comparable photo point stays comparable because three things are recorded before the first shutter click: an exact position, a camera setting, and what the frame is meant to show. Get those three on paper or in a spreadsheet, and a photo taken years later can be lined up with the first one rather than argued about.

Where should the photo point marker actually go?

Place the marker where the view answers a question you already ask about the land, not where the view happens to look pleasant. A marker near a gateway that shows a riparian strip, a slip-prone face, or a paddock boundary does more work than one aimed at a scenic ridge.

Start from the land unit you already manage. If the marker sits inside a named unit, its photos inherit that unit's history. The article What counts as a land management unit explains how to draw those boundaries so a marker lands inside one clear unit rather than straddling two.

What do I write on the marker so a stranger can find it?

Record enough that someone who has never walked the property can stand in the right spot and face the right way. At minimum:

• A unique photo point ID that matches the spreadsheet row.
• The grid reference or GPS coordinates of the camera position, not the subject.
• The bearing in degrees from the camera to the subject.
• The distance from camera to a named landmark in frame.
• The land unit name and the paddock or block name.
• The date of first capture and the initials of the person who set it.

Naming follows the same discipline as any other farm record. If your unit names are inconsistent, the marker will be too. Naming units so others can follow sets out a naming rule that survives staff changes.

Should every photo point use the same camera settings?

No, but every point should use settings you can repeat. Lock the zoom to the same focal length at each visit, keep the camera at the same height, and keep the same orientation to the landscape. A photo taken at eye height with the camera held vertically will not match one taken at chest height in landscape.

Write the settings on the record: focal length, camera height, orientation, and whether the frame was held to a fixed landmark in the foreground. If a phone is used, note the phone model, because lenses differ between models and a later visit on a different phone will produce a different field of view even from the same spot.

What belongs in the frame, and what should be left out?

Frame the question, not the farm. A photo point that tries to capture a whole hillside will show weather and cloud more than ground cover. A tighter frame on the feature you actually assess, such as a bank, a waterway edge, or a fence line, gives a comparison that still means something in five years.

The B+LNZ farm plan overview lists photo-point monitoring locations as a feature worth identifying on a farm map, alongside soil testing sites and water monitoring points [1]. That is a useful organising principle: a photo point is a monitoring site, so it should sit on the map next to the other monitoring sites rather than floating on its own.

One practical check: stand at the marker and ask what a photo of this scene would prove. If the answer is vague, move the marker until it is specific.

How do I keep the record comparable across seasons and staff?

A photo point record fails when the only person who can repeat it has left. The record needs to travel without its author, which means:

• One row per photo point per visit in a spreadsheet, with date, initials, file name, and any note about conditions.
• The original image stored with the same ID in the file name.
• A short field note written the same day, not reconstructed later.

Dating and signing a field note is the habit that keeps the record honest. A photo without a date and initials is a picture, not a record. The article Dating and signing a field note covers the minimum discipline.

One paper sheet and one spreadsheet works well here. The B+LNZ computing workbook shows the pattern of recording stock information in a simple table and using formula cells to total values [2]. The same simple structure works for photo point rows: the row is the record, the totals are not the point.

Comparison at a glance: strong versus weak photo point records

Element	Strong record	Weak record
Position	GPS of camera, bearing to subject	"Top of the hill"
Camera	Focal length, height, phone model	Not recorded
Frame	Named feature in view	Whole hillside
Naming	Tied to land unit and block	Standalone nickname
Date	Same day as capture	Added later from memory
Storage	ID in file name, one row per visit	Photos in a phone album

When should a photo point be retired or moved?

Retire a photo point when the feature it framed no longer exists, for example a fenceline removed or a waterway realigned. Do not quietly shift the marker to a new view and keep the old ID. Give the new location a new ID and note in the old row that the point was retired, with the date and reason.

The overview notes that a farm plan needs to be reviewed and revised over time to meet the demands of the farm [1]. Photo points follow the same logic. A retired point is still a record of what was monitored and when that monitoring stopped.

How do photo points connect to the rest of the farm map?

A photo point only earns its place when it is visible on the map alongside boundaries, land units, and water features. If the map is cluttered, the marker gets lost. The article Map layers versus map clutter sets out how to separate features into layers so monitoring sites stay readable.

Finally, the ground truth matters. A marker placed from a desk can end up inside scrub or on the wrong side of a fence. Walking the route and checking the position against the ground is the step that turns a plotted dot into a usable photo point. Checking a map against the ground describes that pass.

Done this way, a photo point is not a photograph. It is a repeatable measurement you can defend, with a position, a frame, and a date attached to it.