Vector geospatial data relation description method

Abstract

The invention relates to a vector geographic spatial data relation description method, and belongs to the technical field of spatial data management. According to the method, a relation description data structure comprising relation coding values, relation coordinate values, at least two members and role attributes of each member is constructed, relation data is described by utilizing the structure, and the relation coordinate values are used for describing coordinates displayed in a map or positions where text letters appear. The role attributes are used for describing spatial semantics or other business attribute relations of members in the relations, and the members are point elements, line elements, surface elements or relation data in the vector geographic space data. It can be seen that by means of the constructed relation description data structure, the relation between the geographic entities can be described, the vector geographic space data are made to carry semantic information, the relevance between the vector geographic space data can be described more clearly, and relevance analysis of the geographic space data is facilitated.

Description

Technical Field

[0001] The invention relates to a method for describing the relationship between vector geographic spatial data, and belongs to the technical field of spatial data management. Background Art

[0002] In the field of geographic information, vector geospatial data has emerged in a variety of data formats, such as shapefile, geojson, kml, geopackage, etc. However, these data formats can usually only represent and store geospatial entity data such as points, lines, and surfaces, but cannot represent various relationships between geospatial entities, such as orientation relationships, topological relationships, upstream and downstream relationships, and even business relationships. Space is the basic dimension of objective things and the essential attribute of geographic data. If there are only spatial entities but no spatial relationships, it is impossible to understand the interactions of the objective world. Summary of the invention

[0003] The purpose of the present invention is to provide a method for describing the relationship between vector geographic spatial data, so as to solve the problem that the relationship between vector geographic spatial data is difficult to describe at present.

[0004] In order to solve the above technical problems, the present invention provides a method for describing the relationship between vector geographic spatial data, which method comprises: A relationship description data structure is constructed and the vector geographic spatial data relationship is described according to the structure. The relationship description data structure includes a relationship code value, a relationship coordinate value, at least two members, and a role attribute of each member. The relationship coordinate value is used to describe the coordinates of the relationship displayed in the map or the position where the text annotation appears. The role attribute is used to describe the spatial semantics or other business attribute relationships of the members in the relationship. The members are point elements, line elements, surface elements or relationship data in the vector geographic spatial data; point elements are used to describe independent point targets or points on lines and surfaces, line elements are used to describe linear objects, and surface elements are used to describe surface objects.

[0005] Furthermore, point features are provided with fields for point coordinate values ​​and point code values, line features are provided with fields for line code values, and surface features are provided with fields for surface code values; point features are organized in the form of point coordinate values ​​and point code values, line features are organized in the form of line code values ​​and code index values ​​of points on the line, and surface features are organized in the form of surface code values ​​and code index values ​​of point features on the surface; members in the relationship description data structure are described using the code values ​​of the members.

[0006] Furthermore, the relationship description data structure also includes relationship attributes for describing the name and type of the relationship.

[0007] Furthermore, the relationship description data structure also includes a relationship "Is it available" field, which is used to implement the management of relationship deletion and approval. When a relationship is deleted and approved, the relationship is also stored in the corresponding position, and the value of the relationship "Is it available" field is marked as "no".

[0008] Furthermore, the point elements, line elements and / or area elements are also provided with corresponding attribute values ​​for correspondingly describing the names and types of the point elements, line elements and area elements.

[0009] Furthermore, each of the elements is provided with a version value field for recording the number of times the element has been edited, modified and approved.

[0010] Furthermore, the relationship description data structure is provided with a version value field for recording the number of times the relationship and the elements in the relationship have been edited, modified and approved.

[0011] Furthermore, the relationship code value starts from 1, and the corresponding relationship code value increases by 1 for each additional relationship description.

[0012] Furthermore, the relationship encoding value is for the entire life cycle, and each relationship encoding value only describes the corresponding relationship.

[0013] The beneficial effects of the present invention are as follows: as an improved invention, the present invention constructs a relationship description data structure including relationship code values, relationship coordinate values, at least two members and role attributes of each member, and uses the structure to describe relationship data, wherein the relationship coordinate values ​​are used to describe the coordinates of the relationship displayed in the map or the location where the text annotation appears, and the role attributes are used to describe the spatial semantics or other business attribute relationships of the members in the relationship, and the members are point elements, line elements, surface elements or relationship data in vector geographic spatial data. It can be seen that by using the relationship description data structure constructed as shown, the present invention can realize the description of the relationship between geographic entities, so that the vector geographic spatial data has semantic information, can more clearly describe the correlation between low-description vector geographic spatial data, and is helpful for the correlation analysis of geographic spatial data. BRIEF DESCRIPTION OF THE DRAWINGS

[0014] Figure 1 It is a schematic diagram of the relationship between vector geographic spatial data that needs to be described in the embodiments of the present invention. DETAILED DESCRIPTION

[0015] The specific implementation process of the present invention is described in detail below with reference to the accompanying drawings.

[0016] The present invention constructs a relationship description data structure including a relationship code value, a relationship coordinate value, at least two members and a role attribute of each member, and uses the structure to describe the relationship data, wherein the relationship coordinate value is used to describe the coordinates of the relationship displayed in a map or the position where a text annotation appears, the role attribute is used to describe the spatial semantics or other business attribute relationships of the members in the relationship, and the members are point elements, line elements, surface elements or relationship data in vector geographic spatial data.

[0017] For any piece of relationship description data, its composition includes relationship code value, relationship coordinate value, at least two members and role attributes of each member. The role attribute of each member is used to describe the spatial semantics or other business attribute relationship of the member in the relationship. The relationship coordinate value indicates the position where the icon or text annotation of the relationship displayed in the map appears. It is a virtual position defined by the user and can generally be selected at the average position of the members constituting the relationship. Members can be point, line, surface or relationship data types. For example, two points, a point and a line, a surface and a relationship can all constitute a piece of relationship description data. In addition, relationship description data usually also has attribute information to describe the name and type of the relationship.

[0018] The vector geographic spatial data relationship description method of the present invention is used to describe the members constituting the relationship and the relationship between the members, wherein the members can be point elements, line elements, surface elements or relationship data, so the members constituting the relationship are now introduced.

[0019] Point feature points are used to define independent point targets, such as street lights, electric poles, shops, trees, etc. When representing independent point targets, points should usually have attribute information, such as name, type, etc. They can also be used as basic elements of line features or surface features, and multiple point features form line or surface targets; if they are not independent targets, such as just points on a line or a surface, they may not have attribute values. Therefore, the metadata fields used to describe point features in the present invention include coordinate value fields and coded value fields, and attribute fields can be added as needed.

[0020] Line features are used to describe linear objects on the ground, such as roads and rivers. Line features are composed of two or more point features. The point features that make up the line features are arranged in sequence in the data file. These point features are defined by connecting lines in sequence when they are represented, and the direction of the line features is also expressed. For any line, it should at least have a coding value, and the attribute value can also be set according to the actual situation. The attribute value is generally used to indicate the name, type, etc. of the line. Line feature data is organized using line coding values ​​and coding index values ​​of point features on the line, or using line feature coding values, attribute values, and coding index values ​​of points on the line. Therefore, the metadata field used by the present invention to describe line features includes a coding value field, and attribute fields can be added as needed.

[0021] Area elements are used to describe planar objects on the ground, such as parks, lakes, forests, etc. A surface is composed of three or more non-collinear point elements. The point elements that make up the surface elements are arranged in sequence in the data file. These point elements define the shape of the surface elements by connecting them in sequence when they are represented, and also express the direction of the surface elements. The surface element data is organized using the surface coding value and the coding index value of the point elements on the surface, or using the surface coding value, attribute value, and the coding index value of the points on the surface. Therefore, the metadata field used by the present invention to describe the surface elements includes a coding value field and a version value field, and the attribute field can be added as needed.

[0022] In this embodiment, the code values ​​of point elements, line elements, and surface elements can all start from 1. For each additional point, line, or surface, the code value of the point, line, or surface element increases by 1. Each point element code value, line element code value, and surface element code value are unique, that is, each point element has only one point element code value, each line element has only one line element code value, and each surface element has only one surface element code value. This code value will always accompany the entire life cycle of the point, line, or surface. After the information of the point, line, or surface element is modified or deleted, the code value of the point, line, or surface element is still only owned by the point, line, or surface element, and is no longer used by other point, line, or surface elements. The relationship code value is consistent with the point, line, and surface, and all start from 1. For each additional relationship description in the file, the code value of the relationship description increases by 1. This code value will always accompany the entire life cycle of the relationship description. After the information of the relationship description is modified or deleted, the code value of the relationship description is still only owned by the relationship description, and is no longer used by other relationship descriptions.

[0023] In order to retain historical data, that is, after a relationship description data is deleted, it can still be retained in the database on the server side, so as to facilitate the tracing of the history of the relationship data, the constructed relationship description data structure is also provided with a corresponding "Is it available" field, which is used to realize the management of relationship descriptions that have been deleted and approved. When a relationship description data is deleted and approved, the relationship description data is not deleted from the server side, but is still stored in the corresponding position. It only needs to mark the value of the "Is it available" field of the relationship description data as "no"; when a relationship description data is not deleted and approved, the value of the "Is it available" field of the relationship description data is marked as "yes". When a relationship description data whose value of the "Is it available" field is marked as "no" needs to be reused, it only needs to modify the value of the "Is it available" field of the relationship description data to "yes".

[0024] In order to timely understand the changes of each element in the relationship, each element is provided with a version value field to record the number of times the element has been edited, modified and approved; the relationship is also provided with a version value field. When a line element or a surface element is edited, modified and approved, the version value of the element is changed, and at the same time, the version value of the edited and modified point element in the point element constituting the element is changed; when a point element is edited, modified and approved, the version value of the point element is changed, and at the same time, the version value of the line and surface elements containing the point element is changed. The change of the version value of the element refers to adding 1 to the current version value of the element. For example, when a user creates a vector geographic spatial element for the first time and it is approved by the server, this embodiment assigns the version value of the element to 1; when a user modifies or deletes a vector geographic spatial element and it is approved by the server, the version value of the element is increased by 1 on the original basis, that is, it becomes 2. When any element in the relationship is modified, or the attribute information of the relationship itself is modified, and then uploaded to the server, its version value will change, and each change will also increase by 1. By setting the above version value field, the present invention can perform version management on each element constituting vector geographic spatial data.

[0025] The relationship description is organized in the file after the point, line, and surface data. The order of each element in the relationship description data is arranged in sequence according to the size of the code value. The point, line, and surface are organized in the file by arranging the point data first, then the line data, and finally the surface data. The order of each element in each type of data is arranged in sequence according to the size of the code value. The attribute information of points, lines, and surfaces is stored in the form of key-value pairs. A point, line, and surface can have multiple attribute information, that is, multiple key-value pairs. Storing the attribute values ​​of points, lines, and surfaces in the form of key-value pairs can be used to express a variety of attribute information and can store non-relational data.

[0026] To better illustrate the implementation process and effects of the present invention, the description of the vector geospatial data relationship of the present invention is now described in conjunction with specific three-dimensional vector space data. This vector space data is as follows Figure 1 as shown

[0027] <Node encoding="25369" isAvailable="yes" latitude="39.90622415642" longitude="116.31518214673" elevation="34.35" versionValue="1" / > <Node encoding="25370" isAvailable="yes" latitude="39.90622004139" longitude="116.31628989905" elevation="34.35" versionValue="1" / > <Node encoding="25371" isAvailable="yes" latitude="39.90622209891" longitude="116.31727426976" elevation="34.35" versionValue="1" / > <Node encoding="25373" isAvailable="yes" latitude="39.90606984296" longitude="116.3172876808" elevation="34.35" versionValue="1" / > <Node encoding="25374" isAvailable="yes" latitude="39.90607601551" longitude="116.31629526347" elevation="34.35" versionValue="1" / > <Node encoding="25375" isAvailable="yes" latitude="39.90609453314" longitude="116.31518482894" elevation="34.35" versionValue="1" / > <Node encoding="25393" isAvailable="yes" latitude="39.90633731939" longitude="116.31572931737" elevation="34.35" versionValue="1"> <Attribute key="name" value="Museum Station" / > <Attribute key="type" value="Bus Stop" / > < / Node> <Node encoding="25426" isAvailable="yes" latitude="39.90616037202" longitude="116.31518483095" elevation="34.35" versionValue="1"> <Attribute key="name" value="Traffic Light" / > <Attribute key="Type" value="Signal Light" / > < / Node> <Node code="25453" available="Yes" latitude="39.90634966443" longitude="116.31613433093" elevation="34.35" versionValue="1" / > <Node code="25454" available="Yes" latitude="39.90626736412" longitude="116.31613969535" elevation="34.35" versionValue="1" / > <Node code="25455" available="Yes" latitude="39.90626736412" longitude="116.31630599231" elevation="34.35" versionValue="1" / > <Node code="25456" available="Yes" latitude="39.90634966443" longitude="116.31630062789" elevation="34.35" versionValue="1" / > <Line code="865" available="Yes"> <Node codeIndex="25369" / > <Node codeIndex="25370" / > <Node codeIndex="25371" / > <Attribute key="Highway" value="Expressway" / > <Attribute key="Name" value="Fuxing Road" / > <Attribute key="Direction" value="Downward" / > < / Line> <Line code="867" available="Yes"> <Node codeIndex="25373" / > <Node codeIndex="25374" / > <Node codeIndex="25375" / > <Attribute key="Highway" value="Expressway" / > <Attribute key="Name" value="Fuxing Road" / > <Attribute key="Direction" value="Upward" / > < / Line> <Face code="979" available="Yes"> <Node coding index="25453" / > <Node coding index="25454" / > <Node coding index="25455" / > <Node coding index="25456" / > <Node coding index="25453" / > <Attribute key="Name" value="Fuxing Road Gas Station" / > <Attribute key="Type" value="Building" / > < / Face> <Relationship coding="63" isAvailable="Yes" latitude="39.9061954" longitude="116.3162068" elevation="0"> <Member type="Line" coding index="865" role="Road" / > <Member type="Line" coding index="867" role="Road" / > <Attribute key="Name" value="Fuxing Road (Two-way)" / > <Attribute key="Type" value="Road" / > <Attribute key="Route" value="Expressway" / > < / Relationship> <Relationship coding="91" isAvailable="Yes" latitude="39.9061954" longitude="116.3162068" elevation="0"> <Member type="Relationship" coding index="63" role="Road" / > <Member type="Node" coding index="25393" role="Platform" / > <Member type="Node" coding index="25426" role="Traffic Signal" / > <Member type="Face" coding index="979" role="Building" / > <Attribute key="Name" value="Fuxing Road and Its Ancillary Facilities" / > <Attribute key="Type" value="Road and Its Ancillary Facilities" / > < / Relationship> The above relationship describes a relationship coded as "91", the relationship type is "road and its ancillary facilities", the name is "Fuxing Road and its ancillary facilities", and the relationship has 4 "members", namely a "relationship" type data coded as "63" and "role" as "road", two "node" type data coded as "25393" and "25426" and "roles" as "platform" and "signal light", and a "surface" type data coded as "979" and "building". Among them, the "relationship" type data coded as 63 has a relationship type of "road" and contains two "members", namely two expressways in different directions coded as "865" and "867". Through this relationship description, the relationship between the road and the surrounding facilities can be directly read from the relationship and its member data, such as the road is a two-way road, there is a gas station and a bus stop next to the road, and there is a traffic light at the left end of the road, etc. These relationship descriptions are difficult to display and express in the usual vector space data format.

Claims

1. A method for describing the relationship between vector geographic spatial data, characterized in that: The method includes: A relationship description data structure is constructed and the vector geographic spatial data relationship is described according to the structure. The relationship description data structure includes a relationship code value, a relationship coordinate value, at least two members, and a role attribute of each member. The relationship coordinate value is used to describe the coordinates of the relationship displayed in the map or the position where the text annotation appears. The role attribute is used to describe the spatial semantics or other business attribute relationships of the members in the relationship. The members are point elements, line elements, surface elements or relationship data in the vector geographic spatial data; point elements are used to describe independent point targets or points on lines and surfaces, line elements are used to describe linear objects, and surface elements are used to describe surface objects.

2. The method for describing the relationship between vector geographic spatial data according to claim 1, characterized in that: Point features are set with fields for point coordinate values ​​and point code values, line features are set with fields for line code values, and surface features are set with fields for surface code values; point features are organized in the form of point coordinate values ​​and point code values, line features are organized in the form of line code values ​​and code index values ​​of points on the line, and surface features are organized in the form of surface code values ​​and code index values ​​of point features on the surface; members in the relationship description data structure are described using the code values ​​of the members.

3. The method for describing the relationship between vector geographic spatial data according to claim 1, characterized in that: The relationship description data structure also includes relationship attributes, which are used to describe the name and type of the relationship.

4. The method for describing the relationship between vector geographic spatial data according to claim 1, characterized in that: The relationship description data structure also includes a relationship "Is it available" field, which is used to manage the relationship being deleted and approved. When a relationship is deleted and approved, the relationship is also stored in the corresponding position, and the value of the relationship "Is it available" field is marked as "no".

5. The method for describing the relationship between vector geographic spatial data according to claim 2, characterized in that: Point features, line features and / or area features are also provided with corresponding attribute values ​​for correspondingly describing the names and types of the point features, line features and area features.

6. The method for describing the relationship between vector geographic spatial data according to claim 2, characterized in that: Each of the elements is provided with a version value field for recording the number of times the element has been edited, modified and approved.

7. The method for describing the relationship between vector geographic spatial data according to claim 1, characterized in that: The relationship description data structure is provided with a version value field for recording the number of times the relationship and the elements in the relationship have been edited, modified and approved.

8. The method for describing the relationship between vector geographic spatial data according to claim 1, characterized in that: The relationship code value starts from 1, and the corresponding relationship code value increases by 1 for each additional relationship description.

9. The method for describing the relationship between vector geographic spatial data according to claim 8, characterized in that: The relationship encoding value is for the entire life cycle, and each relationship encoding value only describes the corresponding relationship.

Images