Historic Landscape Change

Blog·

Tithe map vs historic OS map for tracing field boundary loss

When a boundary loss claim lands on your desk for a conservation area review, the instinct is to reach for whatever map is oldest. That's not always the right instinct. Tithe maps and the historic OS series answer different questions, and conflating them is how you end up citing a boundary that was never surveyed to the accuracy you're assuming.

What a tithe map actually shows you

Tithe maps were drawn parish by parish from the late 1830s through the 1850s, mostly to work out who owed what under the Tithe Commutation Act. They're a land-use and ownership record first, a topographic survey a distant second. Scale varies between parishes, the surveyor's skill varies more, and the apportionment schedule that goes with the map is often the more reliable part of the pair. For a parish that enclosed late, the tithe map might show the new post-enclosure field pattern already in place. For one that enclosed earlier or never went through parliamentary enclosure at all, you're looking at strip fields or ancient closes that the OS First Edition will later record as already lost.

This is where an enclosure map comparison earns its keep. Enclosure awards and their accompanying maps, where they survive, predate the tithe survey by anywhere from a few years to several decades. Set an enclosure map against a tithe map for the same parish and you can sometimes catch the actual moment of boundary rationalisation: open-field strips consolidated into the rectilinear blocks that still show up in the landscape today. Plenty of parishes enclosed by agreement rather than Act, so no map was ever filed, and that leaves gaps you can't fill from this pair alone. Where an enclosure map does survive for your parish, it gives you an earliest fixed point for that site, and only that site.

Where the historic OS series does a better job

The First Edition County Series (mostly surveyed 1840s to 1890s depending on county, revised again around the turn of the century) is a different animal. It was built on a national triangulation, so boundary lines are positioned with a consistency no tithe surveyor was working to. For tracing field boundary attrition evidence, the OS series is the stronger backbone: 1st edition, 2nd edition (1890s-1900s), and the inter-war revisions give you three or four fixed, comparably accurate snapshots across roughly a century. Overlay those and genuine boundary removal, as opposed to a surveyor's slightly wandering pen line, becomes something you can actually defend in a committee report.

The catch is georeferencing. Tithe maps in particular distort unevenly across a sheet, so rectifying one against modern mapping means accepting a margin of error that the OS sheets don't carry. Good practice is to treat the tithe map as qualitative evidence of what was there and roughly where, and lean on the OS editions for anything you need to measure.

The gap neither map series closes

Here's the practical problem for a conservation review: the last reliable OS County Series revision for most areas sits somewhere in the 1930s to 1950s. Post-war agricultural intensification, the hedgerow grubbing-out that ran through the 1960s and 70s, and the field amalgamation that came with it all happened in the gap between that last paper revision and whatever satellite or aerial baseline you're working from now. That's seventy, eighty years of attrition with no mapped record in between, which is exactly the period a committee usually wants evidence for.

That gap is what wartime and mid-century aerial sorties can fill, once they're orthorectified and set against a recent high-res pass. Historic Landscape Change does that rectification work so a site or conservation area gets a decadal comparison stretching from those mid-century flights up to the present, bridging the exact stretch where the map series goes quiet.

If a boundary loss case needs that mid-century evidence and not just the paper trail, it's worth seeing what the site can pull for your area.

Start a pilot

← Back to the blog