Vegetation

Open data API in a single place

Provided by Geodesy, Cartography and Cadastre Authority of Slovak Republic

Get early access to Vegetation API!

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

Dataset information

Catalog

Geodesy, Cartography and Cadastre Authority of Slovak Republic catalog

Country of origin

Slovakia

Updated

2021.12.06 00:00

Created

Available languages

English

Keywords

Zeleň, Orná pôda, Živý plot, Tráva, Strom, Vegetácia, Park, Vetrolam, Kroviny, Kosodrevina, Ker, Les, Ovocný sad, Úžitková zeleň, Byliny, Chmeľnica, Dreviny, Záhrada, Lesopark, Lúka, Porast, Rastlinstvo, Alej, Stromoradie, Pasienok, Vinica

Datasource

Official portal for European data link

Quality scoring

Dataset description

Dataset Vegetation contains selected classes of objects from the ZBGIS category of the same name, which interpret the plant cover of the earth's surface, natural or artificial cultures and stands. Includes object classes: Hops; Shrubs, thickets, forest; Meadow; Leakage; Arable land; Fruit orchard, garden; Tree; Grassland and scrubland; Useful greenery; Vineyard; Live fence, tree rows. Objects are represented by a vector spatial component and a descriptive component that contains qualitative and quantitative information defined in the Catalogue of Object Classes ZBGIS (KTO ZBGIS) available at www.geoportal.sk.

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