Cartographic model 1:500 000 Vector - administrative boundaries cut-off date 01.01.2022

Open data API in a single place

Provided by Federal Ministry of Agriculture, Regions and Tourism (BMLRT)

Get early access to Cartographic model 1:500 000 Vector - administrative boundaries cut-off date 01.01.2022 API!

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

Dataset information

Catalog

Federal Ministry of Agriculture, Regions and Tourism (BMLRT) catalog

Country of origin

Austria

Updated

Created

2022.05.16

Available languages

English

Keywords

Vektorkarten, Digitale Landkarten, INSPIRE, AT.BEV

Datasource

Official portal for European data link

Quality scoring

Dataset description

This data set corresponds to the outlines of the administrative districts of the object area boundaries of the KM500-V. The cartographic model 1:500 000 - vector (KM500-V) contains the scale-related generalized vector data of the topographic overview map of Austria on a scale of 1:500 000. The KM500-V is divided into the object areas terrain representation, waters, borders (state, state and district borders), settlements (signatures and geographical names), vegetation and traffic. Reference date = creation date: The data for this day is the most up-to-date database of the BEV. This is not the same as the date of recording or surveying.

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