Brandenburg Landscape Programme 2001

Open data API in a single place

Provided by Ministerium für Land- und Ernährungswirtschaft, Umwelt und Verbraucherschutz (MLEUV)

Get early access to Brandenburg Landscape Programme 2001 API!

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

Dataset information

Country of origin
Updated
2026.03.19 00:00
Created
2000.12.30
Available languages
English
Keywords
brandenburgisches-naturschutzgesetz-bbgnatschg, opendata, bboxbebb, gesetz-über-naturschutz-und-landschaftspflege-bundesnaturschutzgesetz---bnatschg, brandenburgisches-naturschutzausführungsgesetz-bbgnatschag
Quality scoring

Dataset description

The landscape programme was established in 2001. It contains guidelines, development objectives, conservation-related target concepts and the objectives for the natural regions of Brandenburg. The data includes: Map 2 - Development goals Map 3.1. - Protective property-related objectives: Species and habitat communities Map 3.2. - Protective property-related objectives: soil Map 3.3. - Protective property-related objectives: water Map 3.4. - Protective property-related objectives: Climate / air Map 3.5. - Protective property-related objectives: Landscape (continued 12/2022) Map 3.6. - Protective property-related objectives: recuperation Map 3.7. - Protective property-related objectives: Biotope network (draft) Legal basis: - Brandenburg Nature Conservation Act (BbgNatSchG) - since 2013 Federal Nature Conservation Act (BNatSchG) in conjunction with Brandenburg Nature Conservation Execution Act (BbgNatSchAG) The valid landscape programme was originally drawn up on the basis of the BbgNatSchG. This was replaced by the Brandenburg Implementation Act to the Federal Nature Conservation Act (Brandenburg Nature Conservation Implementation Act (BbgNatSchAG).
European data infrastructure with broad catalog discovery, free evaluation access and production-grade API options.
190K+
indexed dataset pages
32
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.

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

Copyright © 2026. Made by Apitalks