Rail Noise - Lnight - England Round 2

Open data API in a single place

Provided by Department for Environment, Food and Rural Affairs

Get early access to Rail Noise - Lnight - England Round 2 API!

Let us know and we will figure it out for you.

Dataset information

Catalog

Department for Environment, Food and Rural Affairs catalog

Country of origin

United Kingdom

Updated

Created

Available languages

English

Keywords

Transport networks, noise exposure, environment

Datasource

Official portal for European data link

Quality scoring

Dataset description

Data indicating the level of noise according to the strategic noise mapping of rail sources within areas with a population of at least 100,000 people (agglomerations) and along Network Rail and HS1 traffic routes. Lnight indicates night time annual average noise level results in dB, where night is defined as 2300 - 0700. Noise levels are modeled on a 10m grid at a receptor height of 4m above ground, polygons are then produced by merging neighboring cells within the following noise classes: 70.0+ dB, 65.0-69.9 dB, 60.0-64.9 dB, 55.0-59.9 dB, 50-54.9 dB, <49.9 dB This data is a product of the strategic noise mapping analysis undertaken in 2012 to meet the requirements of the Environmental Noise Directive (Directive 2002/49/EC) and the Environmental Noise (England) Regulations 2006 (as amended). Attribution statement: © Crown Copyright

European data infrastructure with broad catalog discovery, free evaluation access and production-grade API options.

190K+

indexed dataset pages

countries and EU institutions

2019

API-first since

Free API quota

for evaluation and prototypes

SLA

history and push on production APIs

FAQ

Questions before production use

Practical answers on evaluation, licensing, freshness, versioning and support.

api.store is built and operated by Apitalks s.r.o. Company details and a direct contact path are linked in the footer for vendor checks and procurement review.

Yes. Selected APIs include a free API quota, so your team can validate coverage, freshness, response shape and workflow fit before asking for a production plan.

Often yes, but usage rights depend on the source license and dataset. We surface source, license and update metadata where available, and can help review terms before a production integration.

Maintained APIs include update metadata where available. For production integrations, we can add history, monitoring and push updates so changes are easier to detect and act on.

Production APIs can add SLA, stable identifiers, versioning support, history, push updates and direct support around the data your product or AI workflow depends on.

Didn't find the API you need?

Let us know and we will figure it out for you.

api.store Built by Apitalks

European data discovery with free evaluation access and production-grade API options.

About api.storePrivacy Terms of Service