Vector geospatial data version management method
By dividing vector geospatial data into point, line, and surface elements with version and availability tracking, the method addresses inefficiencies in current systems, enabling real-time updates and three-dimensional management.
Patent Information
- Application Number
- CN202411309814.3
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Filing Date
- 2024-09-19
- Publication Date
- 2024-12-20
AI Technical Summary
Current vector geospatial data management systems face issues with poor timeliness, inefficient management of historical data, and lack of three-dimensional capabilities, particularly in managing the life cycle of point, line, and surface elements.
A method that divides vector geospatial data into point, line, and surface elements, each with unique fields for coordinate, code, and version values, and includes version management and availability fields to track edits and deletions, enabling real-time data updates and three-dimensional data management.
Enhances data management efficiency by allowing real-time updates and historical data preservation, supporting near-real-time map data releases and efficient three-dimensional data organization.
Abstract
Description
Technical Field
[0001] The invention relates to a vector geographic space data version management method, belonging to the technical field of space data management. Background Art
[0002] Vector geospatial data is an important infrastructure for the construction of geographic information systems. With the continuous collection and improvement of national basic geographic information data, the acquisition of geographic information data is no longer a problem. However, how to efficiently manage the massive amount of geographic information data obtained in different periods and update the geographic information data in an orderly manner has become a new bottleneck in the GIS field. At present, a commonly used method for updating vector geospatial data is to carry out periodicity, that is, to compile and process the newly collected data on the basis of the original data in a period of one year (which may be longer or shorter), and finally publish it as a new version of map data. However, this is far from meeting the requirements of emergency rescue, civil navigation and other applications for the currentness of map data. At the same time, different versions of map data are managed by file names and other methods, which is very inefficient. ArcGIS SDE and other tool software have the function of managing vector geospatial data versions, but such tools manage in units of data tables and cannot achieve version management of the entire life cycle of any point, line, or surface element. At the same time, ArcGIS SDE and other software tools also have the problem of being inconvenient for local operation. In addition, the existing mainstream vector spatial data formats such as shapefile and geojson basically only express geographic spatial data in plane coordinates, but lack elevation coordinates, which also causes inconvenience in the organization and management of three-dimensional spatial data.
[0003] Therefore, the current management of three-dimensional vector geographic spatial data has problems such as poor timeliness, large amounts of historical data accumulated but unable to be applied, and low management efficiency. Summary of the invention
[0004] The purpose of the present invention is to provide a vector geospatial data version management method to solve the problem of low management efficiency in the current vector geospatial data version management process.
[0005] In order to solve the above technical problems, the present invention provides a vector geospatial data version management method, which comprises the following steps: The vector geographic spatial data is divided into three elements: point, line and surface. The point element is used to describe an independent point target or a point on a line or surface, and is provided with fields of coordinate value, unique point code value and version value; the line element is used to describe a linear object, and is provided with fields of unique line code value and version value; the surface element is used to describe a surface object, and is provided with fields of unique surface code value and version value; the field of version value is used to manage the number of times the element has been edited, modified and approved; Version management is performed on each feature constituting vector geospatial data based on the version value of the version value field in each feature.
[0006] Furthermore, when a line element or a surface element is edited and modified and approved, the version value of the element is changed, and at the same time, the version value of the edited point elements among the point elements constituting the element is changed; When a point feature is edited and approved, the version value of the point feature is changed, and the version values of the line and surface features containing the point feature are also changed.
[0007] Furthermore, corresponding "Is it available" fields are provided in point features, line features, and surface features, for implementing the management of element deletion and approval.
[0008] Furthermore, when an element is deleted and approved, the value of the "Is Available" field of the element is marked as "No" and is still stored in the corresponding location; when an element is not deleted and approved, the value of the "Is Available" field of the element is marked as "Yes".
[0009] Furthermore, when the number of point elements whose "Is Available" field value is marked as "Yes" among the point elements constituting a line element is less than or equal to one, the value of the "Is Available" field of the line element is marked as "No"; otherwise, the point elements whose "Is Available" field value is marked as "No" among the point elements constituting the line element are deleted, and the value of the "Is Available" field of the line element remains "Yes".
[0010] Furthermore, when the number of points constituting a surface element is less than three or the surface element is deleted and approved, the visible field of the surface element is set to "No"; when the surface element is deleted and approved, the visible field of the point elements on the surface element is modified to "No".
[0011] Furthermore, when a component whose value of the "Is Available" field is marked as "No" needs to be reused, the value of the "Is Available" field of the component is modified to "Yes".
[0012] Furthermore, when the user wants the latest data, the method selects the latest version and data corresponding to elements that have not been deleted and approved from the vector geospatial data according to the version value field and the "Availability" field.
[0013] Furthermore, both point elements and line elements are provided with corresponding elevation fields for managing the elevation value of the element.
[0014] Furthermore, the element is also provided with a corresponding attribute value field for correspondingly describing the name and type of the element.
[0015] The beneficial effects of the present invention are as follows: as an improved invention, the present invention divides vector geographic spatial data into three elements: points, lines, and surfaces, wherein the point element is provided with fields for coordinate values, unique point code values, and version values; the line element is provided with fields for unique line code values and version values; the surface element is provided with fields for unique surface code values and version values; wherein the field for version value is used to manage the number of times the element has been edited, modified, and approved. The present invention can achieve unified management of all vector geographic spatial data by dividing vector geographic spatial data into three elements: points, lines, and surfaces. At the same time, a version value field is added to each element to record the number of times the element has been edited, modified, and approved. It can clearly record changes in vector geographic spatial data elements. By managing the version of any vector geographic spatial data element, the efficiency of version management is improved, and the real-time release of any appropriate amount of spatial data is achieved, making user-side data nearly real-time and current. DETAILED DESCRIPTION
[0016] The specific implementation process of the present invention is described in detail below.
[0017] The present invention divides vector geographic spatial data into three elements: points, lines and surfaces, wherein the point elements are provided with fields of coordinate values, unique point code values and version values; the line elements are provided with fields of unique line code values and version values; the surface elements are provided with fields of unique surface code values and version values; the field of version values is used to manage the number of times an element has been edited, modified and approved.
[0018] The first element of vector geographic spatial data is a point. A point is used to define an independent point target, such as a street lamp, electric pole, store, tree, etc. When representing an independent point target, a point should usually have attribute information, such as name, type, etc. It can also be used as a basic element of a line element or a surface element, and a line or surface target is composed of multiple point elements; if it is not an independent target, such as just a point on a line or a point on a surface, it may not have an attribute value. Since spatial data may be edited and modified, it is also necessary to describe the number of times the point element has been edited and modified and reviewed. Therefore, the metadata fields used by the present invention to describe point elements include coordinate value fields, code value fields, and version value fields, and attribute fields can be added as needed.
[0019] Line features are the second element, 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 feature are arranged in order in the data file. These point features define the shape of the line feature by connecting them in sequence when they are represented, and also express the direction of the line feature. The point features that make up the line feature usually do not have attribute information, but special points can also have attribute information, such as stations in roads and sluices in rivers. For any line, it should at least have a code value, and the attribute value can also be set according to actual conditions. The attribute value is generally used to indicate the name and type of the line. Line feature data is organized using line code values and code index values of line point features, or using line feature code values, attribute values, and code index values of line points. When the last point feature in a line feature is the same as the first point feature, it means that the line feature is a closed line, such as a roundabout; otherwise, it is an open line. When two line features intersect in the same plane, the two line features must share the same point feature, such as a road intersection; when the two lines do not intersect in the same plane, they do not share the same point. Since spatial data may be edited and modified, it is also necessary to describe the number of times the line element has been edited and modified and reviewed. Therefore, the metadata field used to describe the line element in the present invention includes a coded value field and a version value field, and the attribute field can be added as needed.
[0020] As the third type of element, the surface element is used to describe surface 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 element are arranged in sequence in the data file. These point elements define the shape of the surface element by connecting lines in sequence when representing, and also express the direction of the surface element. The point elements that make up the surface element usually do not have attribute information, but special point elements can also have attribute information, such as the entrance of the park. For any surface element, it should at least have a coding value, and usually also have attribute information, such as name, type, etc. Therefore, 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. The last point element of the surface element must be the same point element as the first point element. Therefore, the metadata field used by the present invention to describe the surface element includes a coding value field and a version value field, and the attribute field can be added as needed.
[0021] 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 an element refers to adding 1 to the current version value of the element. For example, when a user first creates a vector geographic spatial element 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. By setting the above-mentioned version value field, the present invention can perform version management on each element constituting the vector geographic spatial data. For example, a user can find the desired version of data through the version value field, such as the latest version. At the same time, the changes of any vector spatial data can be analyzed and traced.
[0022] In order to preserve historical data, that is, after a vector geographic space element (point, line or surface) 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 data, the present invention also sets corresponding "Is it available" fields in point elements, line elements and surface elements, which are used to realize the management of elements being deleted and approved. When an element is deleted and approved, the element 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 element as "no"; when an element is not deleted and approved, the value of the "Is it available" field of the element is marked as "yes". When an element 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 element to "yes". When using the "Availability" field to manage data, if the number of point features whose "Availability" field value is marked as "Yes" in the point features that make up the line feature is less than or equal to 1, it means that the remaining point features cannot constitute a point feature. At this time, the value of the "Availability" field of the line feature is marked as "No"; otherwise, the point features whose "Availability" field value is marked as "No" in the line feature are deleted, and the value of the "Availability" field of the line feature remains "Yes". When there are less than 3 points that make up the area feature, or the area feature is deleted and approved, the area feature visibility field needs to be set to "No"; when the area feature is deleted and approved, the area feature visibility field is set to "No", and the point feature visibility field on the area feature is also changed to "No".
[0023] In order not to affect the application on the user side, for example, when the user needs to perform rendering operations on spatial vector data, in order to avoid the influence of elements whose value of the "Is Available" field is marked as "No", the present invention can use this field to filter out elements whose value of the "Is Available" field is marked as "No".
[0024] In addition, currently vector geographic spatial data mainly refers to two-dimensional data. In order to expand vector geographic spatial data, the present invention also provides corresponding elevation fields for both point elements and line elements to manage the elevation value of the element, and has expanded the original two-dimensional expression of vector geographic spatial data to three dimensions. The "elevation" in the present invention refers to the absolute elevation value with the 1985 National Elevation Datum as the reference surface, in meters. Since elevation only acts on points and lines, not on surfaces, that is, in a vector map, a surface is still a plane composed of the same plane points with an elevation of 0, corresponding elevation fields are only provided for point elements and line elements.
[0025] 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 in the file, 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 element, line element, or surface element is modified or deleted, the code value of the point element, line element, or surface element is still only owned by the point element, line element, or surface element, and is no longer used by other point elements, line elements, or surface elements. By giving point elements, line elements, and surface elements a unique code throughout their life cycle, it is possible to uniquely identify all vector geographic spatial data elements, which is convenient for data maintenance, tracing, and merging.
[0026] Points, lines, and surfaces are organized in the file by arranging point data first, then line data, and finally surface data. The order of arrangement of each element in each type of data is arranged in sequence according to the size of the encoding 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 applied to the expression of various attribute information and can store non-relational data.
[0027] In order to better illustrate the implementation process and effect of the present invention, the vector geographic spatial data version management of the present invention is now described in conjunction with specific three-dimensional vector spatial data.
[0028] <Point code="1" latitude="30.430000" longitude="121.390000" elevation="10.48" version value="1" is available="yes"> <Attribute key="Name" value="Bakery" / > <Attribute key="Type" value="Store" / > < / Point> <Point code="1" latitude="30.430000" longitude="121.390000" elevation="10.48" version value="2" is available="yes"> <Attribute key="Name" value="Stationery Store" / > <Attribute key="Type" value="Store" / > < / Point> <Point code="1" latitude="30.430000" longitude="121.390002" elevation="10.48" version value="3" is available="yes"> <Attribute key="Name" value="Stationery Store" / > <Attribute key="Type" value="Store" / > < / Point> <Point code="4" latitude="26.410000" longitude="124.430000" elevation="12.35" version value="1" is available="yes"> < / Point> <Point code="4" latitude="26.410000" longitude="124.430000" elevation="12.35" version value="2" is available="no"> < / Point> <Point code="7" latitude="26.410001" longitude="124.430000" elevation="22.11" version value="1" is available="yes"> < / Point> <Point code="7" latitude="26.410001" longitude="124.430000" elevation="22.11" version value="2" is available="no"> < / Point> <Point code="14" latitude="26.410002" longitude="124.430002" elevation="41.17" version value="1" is available="yes"> < / Point> <Point code="14" latitude="26.410002" longitude="124.430002" elevation="41.17" version value="3" is available="no"> < / Point> <Point code="19" latitude="26.420000" longitude="124.450000" elevation="19.10" version value="1" is available="yes"> < / Point> <Point code="123" latitude="26.420003" longitude="124.450000" elevation="34.35" version value="1" is available="yes"> < / Point> <Point code="1456" latitude="26.420000" longitude="124.450003" elevation="52.74" version value="1" is available="yes"> < / Point> <Point code="1456" latitude="26.420000" longitude="124.450003" elevation="52.74" version value="2" is available="no"> < / Point> <Point code="1567" latitude="26.420003" longitude="124.450003" elevation="46.36" version value="1" is available="yes"> < / Point> <Line code="1456" version value="1" is available="yes"> <Node code index="4" / > <Node code index="7" / > <Node code index="14" / > <Attribute key="road" value="sidewalk" / > < / Line> <Line code="1456" version value="2" is available="no"> <Node code index="4" / > <Node code index="7" / > <Node code index="14" / > <Attribute key="road" value="sidewalk" / > < / Line> <Face code="19" version value="1" is available="yes"> <Node encoding index="19" / > <Node encoding index="123" / > <Node encoding index="1456" / > <Node encoding index="1567" / > <Node encoding index="19" / > <Attribute key="Building" value="Office Building" / > < / Face> <Face encoding="19" version value="2" is available="Yes"> <Node encoding index="19" / > <Node encoding index="123" / > <Node encoding index="1456" / > <Node encoding index="1567" / > <Node encoding index="19" / > <Attribute key="Building" value="Office Building" / > < / Face> Through the above examples, the changes in any vector geospatial data element of this data can be clearly understood.
[0029] In this example, after the user creates a point feature with the encoding of 1, two modifications are made to it. For the first time, the value of the "Name" key in the attribute key-value pair of this point feature is modified to "Stationery Store", so its version value needs to be modified to 2, and whether it is visible remains "Yes"; for the second time, the longitude value of this point feature is modified, so its version value needs to be modified to 3, and whether it is visible remains "Yes".
[0030] After the user creates the point features with the encodings of 4, 7, and 14, each of them is modified once, that is, these three point features are deleted. Therefore, the version values of these three point features are all modified to 2, and whether they are visible is modified to "No"; at the same time, since the line feature with the encoding of 1456 is composed of these three point features, and these three point features are all deleted, resulting in the deletion of this line feature as well. Therefore, the version value of this line feature needs to be modified to 2, and whether it is visible is modified to "No". In fact, even if only two of these point features are deleted, since one point feature cannot form a line feature, this line feature will also be deleted.
[0031] After creating the point feature coded as 1456, the user modified it once, that is, deleted the point feature, so the version value of the point feature was changed to 2, and the visibility was changed to "No"; at the same time, because the created area feature coded as 19 contained the point feature, the point feature was deleted and the area feature was modified at the same time, so the version value of the area feature also needed to be changed to 2. Since the remaining 3 point features can still constitute the area feature, the visibility field of the area feature is still "Yes". If there are less than 3 points on the area feature, the visibility field of the area feature needs to be changed to "No".
[0032] It can also be seen from the above examples that the modification or deletion of point, line and surface elements does not change their coding values. On the other hand, it is convenient to manage different versions of the elements corresponding to the coding values through the coding values.
[0033] In the above data, the point feature coded as 1 retains the latest version of data with version 3; because the "visible" field is no, the point features coded as 4, 7, 14 and their constituent line features coded as 1456 are not retained; similarly, because the "visible" field of the point feature coded as 1456 is no, the point is not retained, and the area data coded as 19 containing the point feature is retained after deleting the point. When the editing user edits any point, line, or area feature and passes the review, the data manager can publish the latest version of the data to the front end in real time, realizing near real-time map data updates.
Claims
1. A vector geospatial data version management method, characterized in that: The method comprises the following steps: The vector geographic spatial data is divided into three elements: point, line and surface. The point element is used to describe an independent point target or a point on a line or surface, and is provided with fields of coordinate value, unique point code value and version value; the line element is used to describe a linear object, and is provided with fields of unique line code value and version value; the surface element is used to describe a surface object, and is provided with fields of unique surface code value and version value; the field of version value is used to manage the number of times the element has been edited, modified and approved; Version management is performed on each feature constituting vector geospatial data based on the version value of the version value field in each feature.
2. The vector geospatial data version management method according to claim 1, characterized in that: When a line feature or a surface feature is edited and modified and approved, the version value of the feature is changed, and at the same time, the version value of the edited point features that constitute the feature is changed; When a point feature is edited and approved, the version value of the point feature is changed, and the version values of the line and surface features containing the point feature are also changed.
3. The vector geospatial data version management method according to claim 1, characterized in that: Corresponding "Is it available" fields are set in point features, line features, and surface features to manage the deletion and approval of features.
4. The vector geospatial data version management method according to claim 3, characterized in that: When an element is deleted and approved, the value of the "Is Available" field of the element is marked as "No" and is still stored in the corresponding location; when an element is not deleted and approved, the value of the "Is Available" field of the element is marked as "Yes".
5. The vector geospatial data version management method according to claim 3, characterized in that: When there are less than or equal to one point features whose "Is Available" field value is marked as "Yes" among the point features constituting a line feature, the value of the "Is Available" field of the line feature is marked as "No"; otherwise, the point features whose "Is Available" field value is marked as "No" among the point features constituting the line feature are deleted, and the value of the "Is Available" field of the line feature remains "Yes".
6. The vector geospatial data version management method according to claim 3, characterized in that: When the number of points that make up a surface feature is less than 3 or the surface feature is deleted and approved, the visible field of the surface feature is set to "No"; when the surface feature is deleted and approved, the visible field of the point features on the surface feature is changed to "No".
7. The vector geospatial data version management method according to claim 4, characterized in that: When a feature whose "Availability" field value is marked as "No" needs to be reused, the value of the "Availability" field of the feature is changed to "Yes".
8. The vector geospatial data version management method according to claim 3, characterized in that: When the user wants the latest data, this method selects the latest version and the data corresponding to the elements that have not been deleted and approved from the vector geospatial data according to the version value field and the "Availability" field.
9. The vector geospatial data version management method according to any one of claims 1 to 8, characterized in that: Both point features and line features are set with corresponding elevation fields to manage the elevation value of the feature.
10. The vector geospatial data version management method according to claim 1, characterized in that: The element is also provided with a corresponding attribute value field for correspondingly describing the name and type of the element.