Collective currents maintained by the State

Open data API in a single place

Provided by Maa-amet

Get early access to Collective currents maintained by the State API!

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

Dataset information

Country of origin
Updated
Created
Available languages
English
Keywords
riigieesvoolud, riigi poolt korrashoitavad ühiseesvoolud
Quality scoring

Dataset description

Spatial forms of all common recipient currents maintained by the state (hereinafter the state artificial recipient) entered in the register of land improvement systems (MSR) together with the main attributes (code of the land improvement system, code of the building of the land improvement system, name of the building, number of the part of the state artificial recipient, name of the watercourse of the state artificial recipient, etc.). The state precedents have been established by Government of the Republic Order No 274 "List of common precedents maintained by the state in order" (adopted on 1 November 2018). State forerunners are in the MSR as buildings of the land improvement system. They have a unique code according to the respective instructions. In the MSR, the national antecedents set out in an order of the Government of the Republic are divided into sections (by means of the building code and part No of the national antecedent) according to the county border and whether it is a part of the national antecedent in the collector. The national forerunners generally have a catchment area of more than 10 km2. The GIS data of state presidencies shall be disclosed: 1) in the Land Improvement Map Application of the Agriculture and Food Board (https://athena.agri.ee/connect/analyst/mobile/#/main?mapcfg=%2FAnalyst%2FNamedProjects%2Fmaaparandus_public&lang=en). This is a snapshot of MSR's public GIS data. The name of the layer in it is "Collective currents maintained by the state". 2) in the Land Board's X-GIS 2 map application "Land improvement systems" (https://xgis.maaamet.ee/xgis2/page/app/land improvement). It has the same data as in the MSR, but with a delay of about 2 hours. The name of the layer of open state precedents in this map application is "Common Precedents Held in Order by the State". 3) in the public view of the register of land improvement systems (https://portaal.agri.ee/apublic/#/land improvement/msr/system-search). This is a snapshot of MSR's public GIS data. The public view of the register of land improvement systems contains all the public attributes concerning the construction works of land improvement systems. The name of the layer in the map window is "Common currents maintained by the state". 4) on the Land Board's restrictions map (https://kitsendused.maaamet.ee/#/public and https://xgis.maaamet.ee/xgis2/page/app/limitations). They update data based on MSR at least 2 times a year, in spring and autumn. 5) in the corresponding WFS (https://metadata.geoportaal.ee/geonetwork/srv/est/catalog.search#/metadata/d8fd5b03-1dfd-49e7-bdc-6fbe558bb1db) and WMS (https://metadata.geoportaal.ee/geonetwork/srv/est/catalog.search#/metadata/209ae929-fb8f-41b0-ac36-0f5a7c2d34a3) services described in the spatial data catalogue. The keeping/collection of data on the state precedents of land improvement systems arises from the Land Improvement Act, the statutes of the register of land improvement systems and the aforementioned Government of the Republic Order No 274.
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