Buildings (buildings)

Open data API in a single place

Provided by Maa-amet

Get early access to Buildings (buildings) API!

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

Dataset information

Catalog

Maa-amet catalog

Country of origin

Estonia

Updated

Created

Available languages

English

Keywords

hoone, Baltic States, Latvia, ehitatav hoone, Estonia, Leedu, Lithuania, regio, eluhoone, rajatis, Eesti, Läti, kõrvalhoone, ehitis, vare, tööstushoone

Datasource

Official portal for European data link

Quality scoring

Dataset description

The REGIO database contains spatial shapes of buildings with additional information about buildings. In the areas of Estonia, Latvia and Lithuania, buildings have been mapped throughout the country. The spatial shapes of the buildings are related to addresses. In addition, the spatial shapes of Estonian buildings have an additional purpose of use, whereas one building may have several uses. The buildings database contains footprints of buildings. The data covers the whole territory of all three Baltic States. Footprints of buildings are related to addresses. In addition, the building footprints in Estonia have a purpose of use attached to them as additional information, whereas one building can have several purposes of use.

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