The spatial data set “Estonian Topography Database — Hydrography” includes the real-world phenomena of the Estonian Topography Database (ETAK) “Water Collections and Hydrographic Facilities”, which are classified as classes of phenomena: sea, standing water bodies, watercourses, shoreline, hydrographic facilities, culverts; as well as the landforms of the reality model group ‘surface fashion’, whose attribute surface form type values are raw material and waterfall.
The attributes of the sight class standing water bodies shall be: name of standing water body, unofficial name of standing water body, type of standing water body.
The attributes of a visual class of watercourses are: name of the watercourse, unofficial name of the watercourse, type of watercourse, width of the watercourse, type of watercourse axis, status of the watercourse axis, flow direction.
Visual class shore line attributes: shore type, delimiting water body type, poured into administrative boundary.
Visual grade hydrographic facilities attributes are: type of hydrographatic facility.
The clerical attributes of the visual class are: the culprit type.
There are no sea attributes in the visual class.
The foundation and maintenance of the Estonian topography database is based on the “Basic Regulation of the Estonian Topography Database” and “The procedure for the capture of topographic data and topographic phenomena of general significance”.
The main data sources are: data or derivatives obtained by aerial photography and laser scanning, including orthophotographs; data transmitted by holders of information in the course of data exchange; details of the surveys carried out by the controller; data from other surveys and surveys, including from public databases and other sources.
Build on reliable and scalable technology
FAQ
Frequently Asked Questions
Some basic informations about API Store ®.
Operation and development of APIs are currently fully funded by company Apitalks and its usage is for free.
Yes, you can.
All important information such as time of last update, license and other information are in response of each API call.
In case of major update that would not be compatible with previous version of API, we keep for 30 days both versions so you will have enough time to transfer to new version. We will inform you about the changes in advance by e-mail.