Upstreams of land improvement systems

Open data API in a single place

Provided by Maa-amet

Get early access to Upstreams of land improvement systems API!

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

Dataset information

Country of origin
Updated
Created
Available languages
English
Keywords
maaparandussüsteemi eesvool, maaparandussüsteem, eesvool
Quality scoring

Dataset description

Spatial shapes of the upstreams of all buildings of land improvement systems (areas of the regulated network) entered in the Register of Land Improvement Systems (MSR) together with a selection of basic attribute data (the code of the land improvement system to which the forward current belongs, the code of the structure of the land improvement system to which the forward current belongs, the name of the structure to which the forward current belongs, the number of the part of the forward current, etc.). The upstreams are in the MSR as the “facilities” of the building of the land improvement system, i.e. they belong to a building of a land improvement system and they have the code of the land improvement system and the code of the construction work attached to that building. A land improvement building is a part of a land improvement system that is put into service at once. One building of a land improvement system includes one or more parts of the forward current. Each part of the land improvement system has a unique code, which consists of the code of the land improvement system to which the forestream part belongs, the code of the building to which the forestream part belongs and the number of the forestream part of the order. Thus, the unique code of the foreground part is the system code+the building code+part no. The upstreams are generally less than 10 km² with a catchment area. The spatial shapes of the upstreams of the buildings of land improvement systems, together with a selection of basic attribute data, shall be disclosed: 1) The Agricultural and Food Board’s land improvement map application (https://athena.agri.ee/connect/analyst/mobile/#/main?mapcfg=%2FAnalyst%2FNamedProjects%2Fmaaparandus_avalik&lang=et). This is the current state of the MSR’s public GIS data. The layer in it is called “Land Repair Systems Front Flows”. 2) The Land Board X-GIS 2 map application “land improvement systems” (https://xgis.maaamet.ee/xgis2/page/app/maaparandus). It updates data based on MSR at least 2 times a year, in spring and autumn. The name of the layer of open front currents in it is “Ahead of the Land Repair Building”. The pre-flows of the collector are on the layer “Manifold drainage of the Land Repair Building” together with the parts of the common currents maintained by the state in the collector. The first stream can be distinguished by the land improvement system code – the code does not end with four zeros. 3) in the public view of the Land Improvement Systems Register (https://portaal.agri.ee/avalik/#/maaparandus/msr/systeemi-otsing). This is the current state of the MSR’s public GIS data. In the public view of the MSR, all the public attributes of the construction works of land improvement systems (front flows are structures). The name of the layer in the map window is “Ahead currents of land improvement systems”. 4) on the map of restrictions of the Land Board (https://kitsendused.maaamet.ee/#/avalik and). They update data based on MSR at least 2 times a year, in spring and autumn. The keeping/collection of data on the upstreams of land improvement systems arises from the Land Improvement Act, the statutes of the register of land improvement systems.
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