MGDB data extent and feature classes involved in automated update are defined.
The set of harmonisation points is created in MGDB where MGDB objects intersect or touch the harmonisation boundary (Fig.
The set of harmonisation points is revised by the UGDB manager who ascertains that all harmonisation points connect to the UGDB objects within allowed accuracy and that the attributes of each MGDB and corresponding UGDB object are compatible.
The AUS service is designed to as well ensure interoperability between the municipality geo-reference database MGDB and the surveyors' databases.
The prototype of procedures that select and move information from local surveyors' databases to MGDB (Fig.
Figure 6 shows data transformation model used by AUS for update of MGDB. Automatic procedures compare the AUS records with the database and detect objects that have been changed, deleted or newly added in comparison with the last database version.
However, full implementation of AUS requires not only technological solutions but also some adjustments of existing legal base: amended regulations of municipal geo-reference base data flows and specifications of geo-reference base data encoding for surveyors and MGDB managers.