Calculated, or just looked up? Two very different kinds of “noise data”

Two different things both get called “noise data”

If you've shopped around for property risk data, you'll have seen noise show up as one line among many — flood, radon, landfill, coal mining, noise — in a general-purpose property-data API, usually priced by the call, a penny or two at a time. It's easy to assume all of these noise fields are doing the same job. They aren't.

Some of them are a government noise-zone label, looked up for a location and returned as-is. Some of them are the output of an actual acoustic calculation, run for that specific property. Both are legitimate uses of “noise data” — but they answer different questions, and they're worth telling apart before you decide which one you need.

What a general-purpose property-data API actually returns

Homedata, a UK property-data API aimed at conveyancers and portfolio buyers, is a useful example because it says plainly what its noise field is. Its own site lists “Defra road and rail noise zones” as one of the free tools alongside flood, radon, landfill, coal mining, air quality and invasive plants — “property-level” risk flags, sold on a pure pay-as-you-go basis (100 tokens for £1, with the noise/environmental-risk field costing a single token per call — no subscription, no minimum).

That's a fair, honestly-described product: a government-published noise zone, returned for a location, at a commodity price. For screening hundreds of addresses at once for a rough flag, that's often exactly the right tool, which is part of why AcoustaPLOT's own bulk address-checking tool offers a cheap data-only tier too — a plain band, nothing more, for exactly this kind of first pass. The question is what you're actually being told when the field comes back, and what happens when you need more than a flag.

Where that government data comes from, and its own stated limits

The underlying dataset — Defra's Strategic Noise Maps — is a real, credible, nationally important resource: large-scale modelling of road and rail noise across England, republished roughly every five years as part of the UK's environmental noise reporting obligations. It's genuinely useful, and AcoustaPLOT uses it too (see below).

But it is, by its own nature, a periodic national exercise, not a bespoke calculation for one building. As our own guide to reading a Defra noise map explains, it's modelled rather than measured, published in five-decibel bands rather than a precise figure, and coverage itself is a real limitation — a blank area on the map doesn't necessarily mean a quiet street, it can just mean that stretch of road wasn't included in that round's mapping. A tool that simply passes that zone label through can only ever be as current, as precise, and as complete as the underlying map it's reading from.

What AcoustaPLOT's Noise Risk Screening actually does with the same starting point

To be fair to the comparison, AcoustaPLOT's own Screening report also uses Defra's Strategic Noise Maps — as a primary source, wherever they have coverage for a property. The difference is what happens next, not whether Defra gets used at all.

Where Defra has coverage, AcoustaPLOT converts the banded result into an actual Lden and Lnight figure in decibels, not just a zone label, states an explicit accuracy range on every result, names the dominant noise source, and — where a property is affected by both a road and a railway — correctly combines the two exposures by logarithmic energy addition rather than just reporting whichever is louder. Where Defra has no coverage at all, AcoustaPLOT doesn't return a blank: it calculates the level directly, using the UK's Calculation of Road Traffic Noise (CRTN, 1988) method applied to real Department for Transport traffic-count data for that road. Every figure is tied to a named, citable standard — see our Methodology and Standards pages — rather than a bare number with no stated basis.

Why the price difference reflects a different product, not just a markup

AcoustaPLOT's Noise Risk Screening is £34.99 — a long way from a penny-per-call property-data field, and it should be: it's a different kind of product. A one-off calculated figure with a stated accuracy range is more expensive to produce than passing through a government label, and Screening is also the entry point to a ladder a bare data field simply has no equivalent of at any price — a £99 Insight Report, a £349 Acoustic Barrier Design that physically models a real garden fence to ISO 9613-2 and recommends an actual height, a £499 Complete Property Noise Report, up to a £750 Whole-Site Desktop Study for a whole development.

Put plainly: a property-data API answers “is there a flagged noise zone here?” as one line among dozens of unrelated checks. AcoustaPLOT answers “what is the noise level at this specific property, how confident are we, and — if it's a problem — what do I do about it?” as a dedicated noise-assessment product, with an escalation path built in. Which one represents better value for money depends entirely on which of those two questions you're actually asking.

When a bare data field is the right call — and when it isn't

None of this makes a cheap data-only field the wrong tool to reach for — for a first-pass screen across a large portfolio, it often is the right one, which is why we offer a comparable data-only tier ourselves for bulk checking. It stops being the right tool the moment the question changes from “should we look closer at this one” to “what exactly is the risk here, and what would fix it” — at that point, a government zone label was never going to be able to answer either question, because it was never calculated against this specific property in the first place.