According to the Law of Ukraine "On Regulation of Urban Development" of February 17, 2011 N 3038-VI urban planning documentation is developed as a geospatial profile data set (GPDS) in a single system of classification and coding. The core of such a classification and coding system in accordance with world experience and international standards should be a register of objects (catalog of object classes, their properties and relationships (hereinafter Catalog)), which in modern geographic information projects of different countries is created according to international standard ISO19110 :Methodology for feature cataloguing. The catalog of objects should permeate the whole process from the formation of requirements for documentation and support of its release from the GPDS to its further use in GIS and other cadastral and geoinformation areas, including as part of the data quality assessment system.
Maine text
The catalog of objects classes of the urban-planning cadastre is the unified system of classification defining structure of objects, system of coding and classification of attributes for realization of the conceptual model of data sets of urban-planning documentation. According to the requirements of ISO 19110, all classes, attributes, associations, roles of associations of objects included in the catalog are identified by the name and description in natural language, which are unique within the catalog. In electronic catalog, the names should be submitted on the basis of a certain system of classification and coding, ie in a formalized form sufficient to convert the data into a form suitable for use in DBMS and GIS. A feature of the catalog of objects classes of the urban cadastre, in contrast to the usual data sets, is to ensure the implementation of the mechanism of multivariate representation of objects in their life cycle (existing, prospective, archival).
Compilation of the catalog of objects classes for GPDS urban planing documentation was carried out on the basis of the principle of the maximum generalization of the objects which are included in its structure on their basic urban-planning properties. In the process of creating and filling the catalog, the requirements to the components of the database of urban cadastre, defined in [1], [2], [3], [5] and other regulations, as well as the classification of localities used in the design of urban planing documantation were taken into account. The Catalog is based on the system of coding groups of objects according to the scheme defined in the List: <group code> <subgroup code><class code>.A total of 20 groups have been identified in the draft of Catalog, of which 19 are defined by the List, and 1 group, “General System Indicators”, has been introduced for system tables (for example, Legislation, Regulations, etc.). The catalog was supplemented by a set of classes that define the generalized indicators of urban cadastre objects of the local level according to [1 - 3] and other classes of objects that were not covered by the List (for example, waste heaps, center development directions, treatment facilities, etc.). The purpose of creating and using an electronic catalog is to improve the quality and efficiency of data use at all stages of creation, maintenance and use of geospatial databases of urban cadastre in various GIS programs (Fig. 1).
For example, at the stage of data collection and creation of appropriate sets of geospatial data, the catalog of object classes regulates their structure and composition, sets the rules of topological relationships between objects. At the stage of using geospatial data sets, the object catalog defines the rules for ensuring the semantic, domain, spatial integrity of the data and models the behavior of urban cadastre objects. The electronic catalog is important for assessing the quality of geospatial data sets, as it provides an information base for programs to test the compliance of sets with the data classification and coding systems defined in the catalog and the domains of attribute values.
Implementation of the relational database model of the catalog gives significant advantages: simultaneous access to geospatial data of many users, standard means of data storage and recovery and the ability to work in client-server mode, providing representation of geospatial data in new abstract data types, compatibility of different applications by data formats and methods of access to them.
The database of the catalog of objects classes of urban cadastre consists of the following main sections (Fig. 2): Register of catalogs, Metadata catalogs, Register of object groups, Register of object classes, registry of object class attribute, Register of classifiers (List of classifiers and their content), Register of associations between object classes, Register of topology rules, Register of operations on classes, — and contains documentation and definitions of all its components.
For each class in the catalog database describes the associations of objects (table "Register of Associations", Fig. 2), the registration of which is defined as "mandatory". Object associations define the spatial and non-spatial relationships between classes.Each association has a unique code, which is formed as a concatenation of the object class code, the relationship of which is described, the code of the communication object class and the association number in the classifier: <association code>:=<target object type code>< object type code for the association><role code>. For example, the association between the classes of residential buildings and oil, gas and product pipelines is registered in the catalog with the code 11010004030507, where 110100 — class code "Residential buildings", 040305 — class code "Buildings on oil, gas and product pipelines", 07 — role code of the object of the class "Residential buildings" in the association "associated with".
For each object class in the catalog database, operations on classes whose registration is defined as "additional" are described. Class operations define a set of valid states and transitions between objects when performing geometric operations on them. Operations on classes set the rules for controlling the process of converting the value of one attribute into the value of the attributes of one, two or more spatial objects, when the original spatial object is divided, combined, changed. Operations define the functional relationship between object class attributes and aim to provide semantic integrity constraints and, as a result, attribute data quality control. Each operation has a unique code, which is formed as a concatenation of the code of the main attribute of the object class (for which the operation is defined) and the operation number in the classifier: <operation code>:=<the target class code of the object ><target attribute code><operation code>. The operation defined for the attribute "Land area" when performing the merger of two parcels, registered in the catalog with the code 1601031401, where 16010314 — attribute code "Land area" for 371 uban cadastre catalog, 01 — transaction code "Sum of values, aggregation" according to the classifier of operations. Topology rules, as a means of controlling the spatial relationships between objects and classes of spatial objects, are defined in the catalog at the level of: object (type of object localization: point, line, polygon); a set of object classes (topological relationships between object classes). Object-level topology rules are defined as a matrix of acceptable spatial localization types for each class (for example, the table "Register of relations class - type of spatial localization", Fig. 2). Object class set topology rules aim to ensure the integrity of spatial data and are a set of requirements that define the spatial relationships of one or more classes of spatial objects (for example, the table "Register of topological relations" in Figure 2). Each topology rule has a unique code, which is formed as a concatenation of the type code of the first and second objects of topological relations with certain types of localization and the code of the topology rule (according to the classifier of topological rules): <topology rule code >:=<code type of the first object ><code type of the first object ><topology rule code>. The topology rule to describe the relationship between the classes of topological relations "Residential buildings" and "Land" is registered in the catalog by code 1101003160103302, where 1101003 — class code "Residential buildings, polygon", 1601033 — class code "Land plots, polygon", 02 — topology rule code "must match" according to the appropriate classifier.
A separate part of the electronic catalog is a set of functions defined in SQL (Structured Query Language), which implement links between sections of the catalog of objects, provide automatic formation of the data set structure in the ORDBMS environment adding new attributes to tables) on the basis of changes to the directory, implement the catalog-defined "object behavior", control the integrity of the data. The graphical interface of the electronic catalog is organized on the basis of integration of database and GIS technologies with the use of open source software DBMS PostgreSQL and GIS QGIS, which provides comfortable cataloging by the user.