Zone de bruit d’une carte de bruit stratégique 2022 4ème échéance (données agrégées) - Type C et Indice Ld - Infrastructures ferroviaires

Open data API in a single place

Provided by DDT Haute-Marne

Get early access to Zone de bruit d’une carte de bruit stratégique 2022 4ème échéance (données agrégées) - Type C et Indice Ld - Infrastructures ferroviaires API!

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

Dataset information

Catalog

DDT Haute-Marne catalog

Country of origin

France

Updated

2022.05.03 22:00

Created

2022.05.16

Available languages

English

Keywords

environnement, nuisance-n-bruit, nuisance-bruit, bruit, donnees-ouvertes, zone-de-bruit, directive-2022-49-ce

Datasource

Official portal for European data link

Quality scoring

Dataset description

Les zones de bruit sont des éléments géométriques constitutifs de la carte de bruit stratégique. Pour les cartes de type A (CBSTYPE), chaque zone de bruit est généralement délimitée par 2 courbes isophones (Lden 55-60, 60-65, 65-70, 70-75 et Ln 50-55, 55-60, 60-65, 65-70) ou par la courbe isophone de limite inférieure (Lden >75, Ln > 70). Pour les cartes de type C (CBSTYPE), chaque zone de bruit est délimitée par la courbe isophone de limite inférieure (Lden > 68 ou 73, Ln > 62 ou 65). Standard de données COVADIS Bruit dans l’Environnement, version 1.1 – 8 juin 2017

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