Residential buildings from address data (WMS)

Open data API in a single place

Provided by Maa-amet

Get early access to Residential buildings from address data (WMS) API!

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

Dataset information

Country of origin
Updated
Created
2023.08.01
Available languages
English
Keywords
MaRu wms, unikaalaadress, aadress, eluhoone, kasutusotstarve
Quality scoring

Dataset description

The purpose of the service is to provide information about Estonian residential buildings.Buildings with a unique address requirement in the Address Data System (ADS) are included, which, according to the Estonian Technical Register (EHR), have a residential purpose and have been mapped by the Estonian Topographic Database (ETAK). Spatial shapes of buildings can come from ETAK, EHR and ADS. The data comes from the Land Board. Usage codes used to identify residential buildings:11100 single apartments; 11101 private homes; 11102 terraced or double house sections (if there is a roof and entrance from the ground);11103 cottages, garden houses; 11200 residential buildings with two or more apartments;11210 residential buildings with two apartments; 11212 residential buildings with two apartments;11220 residential buildings with three or more apartments; 11221 terraced houses; 11222 other residential buildings with three or more apartments. The service includes fields: • ADS_OID – Address Object Identifier in the Address Data System. • EHR_GID – Part geometry identifier of the building in the Construction Register. • EHR_KOOD – unique building code created by the building register. • EHR_URL – link to the technical register. • ETAK_ID – unique identifier of the Estonian topography database for objects. • INFORMATION – The valid full address in textual form contains all parallel addresses. • LAHIAADRESS – The current Close Address in textual form contains all parallel addresses. • KAOS_KOOD – Purpose(s) of the building in code form. • INFORMATION – Use(s) of the building as text. • Unik – Unik address requirement.
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