Vector geographic element collaborative update management method, device and medium

Abstract

The invention relates to the technical field of geographic information systems, and discloses a vector geographic element collaborative updating management method and device and a medium, and the method comprises the steps: a user edits a vector, and generates GeoJSON Delta data; matching the GeoJSON Delta data with a baseline version, and carrying out automatic / manual conflict processing through an attribute rule or spatial topology analysis; after conflict processing is completed, the three-dimensional version tree is updated, and real-time synchronous storage is carried out. The method can be applied to the fields of land investigation, smart cities and the like, and solves the problems of version chaos, frequent conflicts and the like in traditional GIS data updating.

Description

Technical Field

[0001] The present invention relates to the technical field of geographic information systems, and in particular to a method, device and medium for collaborative updating management of vector geographic elements. Background Art

[0002] Currently, in the field of natural resources and land space planning, multiple departments (such as forestry, water conservancy, and environmental protection) need to collaboratively update land use data for the same area. For example, when the forestry department demarcates ecological protection zones, it needs to synchronize them to the land space planning platform in real time to avoid conflicts with the agricultural department's cultivated land red lines. In collaborative editing and processing updates, multi-person collaborative processing, version management, regional processing branch locking, and topological conflict warning detection are required. However, the current collaborative processing and update methods are relatively traditional, mainly using table-level locks for topological conflict detection and full backups for temporal version management. The overall efficiency is low, and the real-time processing efficiency is low.

[0003] Summarizing the existing GIS data collaborative update technology, the main defects are as follows: 1. Extensive version management: Traditional GIS uses full backup to store historical versions, resulting in explosive growth in storage space (for example, 100 edits generate 100 times the storage space).

[0004] 2. Delayed conflict detection: Existing systems often perform geometric overlap checks during the submission phase and are unable to provide real-time warnings of spatial topological conflicts (e.g., illegal intersections between roads and plots).

[0005] 3. Low collaboration efficiency: It lacks a branch-merge mechanism similar to Git, making it difficult to support parallel editing by large teams. Summary of the Invention

[0006] The purpose of the present invention is to propose a method, device and medium for collaborative update management of vector geographic elements to solve the technical problems of low efficiency and poor real-time performance in the current collaborative update of vector geographic elements.

[0007] Specifically, the present invention provides a method, device, and medium for collaborative update management of vector geographic elements, the method comprising the following steps: S1. The user edits the vector and generates GeoJSON Delta data. S2. Automatically / manually resolve conflicts between GeoJSON Delta data and the baseline version using attribute rules or spatial topology analysis. S3. After conflict resolution is completed, the three-dimensional version tree is updated and stored synchronously in real time.

[0008] A storage medium stores instructions and data for implementing a vector geographic element collaborative update management method.

[0009] A vector geographic element collaborative update management device comprises: a processor and the storage medium; the processor loads and executes instructions and data in the storage medium to implement a vector geographic element collaborative update management method.

[0010] The beneficial effects provided by the present invention are: it can be applied to fields such as land surveys and smart cities, and solve problems such as version confusion and frequent conflicts in traditional GIS data updates. BRIEF DESCRIPTION OF THE DRAWINGS

[0011] Figure 1 It is the system functional architecture diagram; Figure 2 This is a schematic diagram of the three-dimensional version tree ID structure; Figure 3 It is a version update management logic diagram; Figure 4 It is a functional diagram of version interaction operations; Figure 5 It is a schematic flow chart of the method of the present invention; Figure 6 It is a real-time conflict warning processing flow chart; Figure 7 It is the functional flow chart of spatial topology analyzer; Figure 8 It is the functional flow chart of the attribute conflict rule base; Figure 9 It is a diagram of attribute rule decision tree; Figure 10 It is a flow chart of space-attribute conflict linkage processing; Figure 11 This is the version chain storage model diagram; Figure 12 It is a version merging flowchart; Figure 13 It is a schematic diagram of the working of the hardware device of an embodiment of the present invention. DETAILED DESCRIPTION

[0012] To make the objectives, technical solutions and advantages of the present invention more clear, the embodiments of the present invention will be further described below with reference to the accompanying drawings.

[0013] Before formally explaining the present invention, the scheme of the present invention is first generally explained for easy understanding.

[0014] First, the relevant technical terms involved in the present invention are uniformly explained as follows: 1. The three-dimensional version tree is constructed by combining the spatial, user, and time dimensions, such as Figure 2 As shown, it is used to support interactive version navigation and conflict management, as well as historical version viewing and rollback functions; 2. Version branch types in the three-dimensional version tree include: user-branch, which isolates editing content by user; grid-branch, which locks the editing range according to a spatial grid (e.g., 1km×1km); and master version line (master), which stores verified stable versions. 3. Version update management and management logic of the three-dimensional version tree, such as Figure 3 As shown. This includes processes such as version submission, branch / offline version editing, version merging, and network synchronization; 4. Version interaction operations in the three-dimensional version tree include version filters and version operation functions, supporting version filtering by spatial grid, by user, by time, etc., supporting version rollback, version difference comparison, and version conflict resolution. Specific designs include Figure 4 The present invention mainly focuses on its version conflict resolution function.

[0015] 5. GeoJSON Delta data is an incremental storage format optimized for geospatial vector data. It significantly reduces storage and transmission overhead by recording only the changes (additions, deletions, and modifications) of features.

[0016] The following describes its mechanism in detail from three aspects: data structure, compression strategy, and storage process, and provides a schematic diagram to assist understanding.

[0017] Data structure: A GeoJSON Delta file consists of a header and a list of incremental operations (Deltas). The defined operation types include add, update, delete, split, merge, etc.

[0018] Compression strategies include geometric data compression strategies and attribute data compression strategies.

[0019] Geometric data compression: Delta Encoding records the relative offsets between consecutive vertices rather than absolute coordinates, reducing the number of digits. Douglas-Peucker algorithm simplification can be selected based on the positioning accuracy requirements of vector feature editing. This algorithm can achieve a compression rate of over 50% while retaining key shape features. Attribute data compression: Uses the JSONPatch format to record only field-level modification operations (such as replacing / status field values), rather than storing all attributes.

[0020] GeoJSON Delta enables efficient storage and collaborative management of geospatial data through differential encoding, geometric simplification, and optimized operational semantics. Its core advantages include reduced storage costs, recording only the changes and avoiding full data redundancy; accelerated network transmission, and small Delta files suitable for mobile devices and weak network environments; and precise version control, supporting feature-level historical tracing and conflict location.

[0021] The method of the present invention is implemented based on the collaborative update management system. The system architecture can be found in Figure 1 .

[0022] On the client side, a change application is submitted, and the system version management controller performs different operations according to the application content, such as conflict detection, updating the version database, or calling the version visualization interface.

[0023] The method of the present invention focuses on conflict detection and updating the version database content.

[0024] Please refer to Figure 5 , Figure 5 It is a schematic flow chart of the method of the present invention; The present invention provides a method for collaborative updating and managing vector geographic elements, comprising the following steps: S1. The user edits the vector and generates GeoJSON Delta data. It should be noted that the user editing in step S1 includes online editing and offline editing.

[0025] In offline editing, users create personal branches and edit vector features to generate GeoJSON Delta data.

[0026] In online editing, users can lock the spatial grid in real time to generate GeoJSON Delta data.

[0027] S2. Automatically / manually resolve conflicts between GeoJSON Delta data and the baseline version using attribute rules or spatial topology analysis. It should be noted that the present invention performs conflict warning processing in real time. Figure 6 shown.

[0028] Figure 6 There are two editing users A and B. User A submits an update to the version server. The version server synchronizes the updated content to user B and pushes a conflict warning. User B confirms the conflict handling method and submits the update.

[0029] It should be noted that the present invention uses a spatial topology analyzer to process spatial topology detection and conflict repair. Its workflow is as follows Figure 7 shown.

[0030] The conflict resolution process in step S2 through spatial topology analysis is as follows: S221. Build spatial index based on R-tree; Specifically, we build a spatial index based on an R-tree, organizing the minimum bounding rectangle (MBR) of each feature into a tree structure to accelerate range queries. In design applications, we dynamically adjust the node splitting threshold based on the scale of the data features, balancing index depth and query efficiency.

[0031] S222, predefined OGC standard topology rule base; Predefined OGC standard topology rules (such as must not overlap, must be covered by) support user-defined rule extension. The following pseudo code is used to customize the rules: { "rule_id": "ROAD_NO_OVERLAP", "description": "Roads cannot overlap with other roads", "condition": "geometry.intersects(feature)&&feature.type == 'road'", "severity": "ERROR" } S223, integrated GEOS / JTS library, performs precise geometric calculations, and quickly filters out pairs of features that are clearly non-conflicting; Integrates with the GEOS / JTS library to perform precise geometric calculations (such as buffer analysis and overlay analysis), uses block parallel computing for large-scale datasets, and uses approximate algorithms to quickly filter out pairs of features that are clearly non-conflicting.

[0032] S224. For the input spatial feature to be detected, quickly search for a set of candidate geometric features related to its topology through the R-tree spatial index, then apply the topology rule library to perform topology inspection and interpretation, and output a conflict list.

[0033] The present invention uses a spatial R-tree index to quickly find a set of topologically relevant candidate geometric elements for an input spatial element to be detected, then applies a topological rule base to perform topological inspection and interpretation, and outputs a conflict list.

[0034] An example of spatial conflict resolution is as follows: If the analyzer detects an overlapping conflict between two polygons, the system automatically calculates the minimum bounding rectangle intersection and prompts the user to select an action. If the user sets a default spatial conflict handling strategy, such as "most recent modification first, intersection of overlapping polygons, union of overlapping polygons, larger area, smaller area, line-surface edge alignment within tolerance, dangling line removal, dangling point removal," the system can automatically handle the current conflict.

[0035] For example: Conflict area: [Longitude 113.5~113.6, Latitude 22.2~22.3] User selectable solution options: 1) Use user A's boundary; 2) Use user B's boundary; 3) Keep polygons A and B and do not process them; 4) Automatically calculate the buffer zone dividing line and generate a new graphic to save.

[0036] It should be noted that the conflict resolution process using attribute rules in step S2 is as follows: S211. Load attribute rules from JSON / YAML files; The rule loader of this invention supports loading rules from JSON / YAML files and dynamically updating without restarting the system. The pseudo code example of the rule is as follows: rule_id: STATUS_CONFLICT description: "The facility status cannot be both 'operating' and 'abandoned' at the same time." condition: | (old_value == "operational" &&new_value == "abandoned") || (old_value == "abandoned" &&new_value == "operational") action: "REQUIRE_MANUAL_REVIEW"; S212. Organize the attribute rules into a decision tree structure and group them by fields; Rules are organized into a decision tree structure and grouped by fields to speed up matching. The rule decision tree diagram is as follows: Figure 9 shown.

[0037] S213, define field priority; Define the field modification priority for automatic conflict resolution (for example, Ownership Unit takes precedence over Remarks). An example is shown in the following table.

[0038] Table 1 Field priority

[0039] S214. High-priority fields automatically overwrite low-priority fields. When the priorities are the same, vote or use the latest modified data. If the conflict cannot be resolved automatically, manual processing is used.

[0040] Specifically, the conflict resolution strategy of the present invention is as follows: Automatic resolution: Higher priority fields override lower priority fields.

[0041] Semi-automatic resolution: For cases with the same priority, the latest modification or majority vote is used.

[0042] Manual intervention: Conflicts that cannot be resolved automatically are pushed to the collaboration interface.

[0043] It should be noted that in step S2, when the spatial conflict and the attribute conflict are linked, a joint solution is generated and the user selects a processing solution.

[0044] Specifically, when the position of spatial elements changes, it may cause conflicts with topology-related attributes. The processing flow is designed as follows Figure 10 This includes determining whether spatial conflicts affect attributes, triggering rule checks, generating joint solutions, or performing spatial repair processing, and user-determined solutions.

[0045] For example, if a user modifies road coordinates (spatial changes), resulting in a conflict with the "Area" attribute of surrounding plots, the process is as follows: The Spatial Topology Analyzer detected that roads and parcels overlap → marked as spatial conflicts.

[0046] The attribute rule base checks the "belonging area" field of the overlapping area parcels: If the road area ≠ the land area → trigger attribute conflict.

[0047] The system combines two types of conflicts to generate a joint solution: Solution 1: Adjust the road coordinates to avoid the land parcel.

[0048] Solution 2: Modify the "Area" attribute of the plot to be consistent with the road.

[0049] Ultimately, it is up to the user to choose which solution to adopt.

[0050] S3. After conflict resolution is completed, the three-dimensional version tree is updated and stored synchronously in real time.

[0051] The storage process is as follows: Baseline version: stores the entire initial dataset (standard GeoJSON format).

[0052] Incremental version (Delta): Each subsequent edit generates a Delta file to record the change operation. The version chain storage model is as follows Figure 11 shown.

[0053] The version merging process is as follows: Forward Apply: Apply GeoJSON Delta files one by one in chronological order to rebuild the latest version, such as Figure 12 shown.

[0054] Rollback: Reverse the GeoJSON Delta operation and restore to the historical version.

[0055] See Figure 13 , Figure 13 4 is a schematic diagram of the working of the hardware device of an embodiment of the present invention, wherein the hardware device specifically includes: a vector geographic element collaborative update management device 401, a processor 402 and a storage medium 403.

[0056] A vector geographic element collaborative update management device 401: The vector geographic element collaborative update management device 401 implements the vector geographic element collaborative update management method.

[0057] Processor 402: The processor 402 loads and executes the instructions and data in the storage medium 403 to implement the vector geographic element collaborative update management method.

[0058] Storage medium 403: The storage medium 403 stores instructions and data; the storage medium 403 is used to implement the vector geographic element collaborative update management method.

[0059] The beneficial effects of the present invention are: it can be applied to fields such as land surveys and smart cities, and solve problems such as version confusion and frequent conflicts in traditional GIS data updates.

[0060] The above description is only a preferred embodiment of the present invention and is not intended to limit the present invention. Any modifications, equivalent substitutions, improvements, etc. made within the spirit and principles of the present invention should be included in the scope of protection of the present invention.

Claims

1. A method for collaborative update management of vector geographic elements, characterized by: The following steps are involved: S1. The user edits the vector and generates GeoJSON Delta data. S2. Automatically / manually resolve conflicts between GeoJSON Delta data and the baseline version using attribute rules or spatial topology analysis. S3. After conflict resolution is completed, the three-dimensional version tree is updated and stored synchronously in real time.

2. The method for collaborative updating and management of vector geographic elements according to claim 1, characterized in that: User editing in step S1 includes online editing and offline editing.

3. The method for collaborative updating and management of vector geographic elements according to claim 1, characterized in that: The conflict resolution process using attribute rules in step S2 is as follows: S211. Load attribute rules from JSON / YAML files; S212. Organize the attribute rules into a decision tree structure and group them by fields; S213, define field priority; S214. High-priority fields automatically overwrite low-priority fields. When the priorities are the same, vote or use the latest modified data. If the conflict cannot be resolved automatically, manual processing is used.

4. A method for collaborative updating and management of vector geographic elements according to claim 3, characterized in that: The conflict resolution process in step S2 through spatial topology analysis is as follows: S221. Build spatial index based on R-tree; S222, predefined OGC standard topology rule base; S223, integrated GEOS / JTS library, performs precise geometric calculations, and quickly filters out pairs of features that are clearly non-conflicting; S224. For the input spatial feature to be detected, quickly search for a set of candidate geometric features related to its topology through the R-tree spatial index, then apply the topology rule library to perform topology inspection and interpretation, and output a conflict list.

5. The method for collaborative updating and management of vector geographic elements according to claim 1, wherein: In step S2, when spatial conflicts and attribute conflicts are linked, a joint solution is generated and the user selects a solution.

6. A method for collaborative updating and management of vector geographic elements according to claim 5, characterized in that: Step S3 is as follows: S31. Update the three-dimensional version tree; S32, storing the updated three-dimensional version tree in the Delta database; S33. Synchronously store incremental versions and baseline versions and collaboratively update other clients.

7. A storage medium, characterized in that: The storage medium stores instructions and data for implementing a vector geographic element collaborative update management method as described in any one of claims 1 to 6.

8. A vector geographic element collaborative update management device, characterized by: include: Processor and storage medium; the processor loads and executes instructions and data in the storage medium to implement a vector geographic element collaborative update management method as described in any one of claims 1 to 6.

Images