Bauflächennutzung Vorarlberg 2001

Open data API in a single place

Provided by Land Vorarlberg

Get early access to Bauflächennutzung Vorarlberg 2001 API!

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

Dataset information

Catalog

Land Vorarlberg catalog

Country of origin

Austria

Updated

NaN.NaN.NaN NaN:NaN

Created

NaN.NaN.NaN

Available languages

English

Keywords

raumplanung, bauflaeche

Datasource

Official portal for European data link

Quality scoring

Dataset description

Die Bauflächennutzung 2001 Vorarlbergs stellt den tatsächlich bebauten Teil eines Grundstücks dar, welches als Baufläche (BK, BW, BM, BB) gewidmet wurde. Dieser Teil ergibt sich aus der Differenz von Grundstücksfläche minus ungenutzter Fläche und wurde anhand des Orthofotos 2001 per Hand herausgearbeitet. Dabei wird zwischen genutzt, schlecht genutzt (z.B. Parkplatz) und ungenutzt unterschieden. Wichtige Felder und Datentypen der Attributtabelle: AREA (double) Fläche des Polygons/der Parzelle BELEGUNG (string) beschreibt die tatsächliche Nutzung FW (string) Flächenwidmung - Signatur FW (string) Flächenwidmung - Text STAND (string) Stand der Daten Datenquelle: bauflaechennutzung_2001.shp

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