GIS spatial data real-time synchronization and operation and maintenance management system and method

Abstract

The invention discloses a GIS spatial data real-time synchronization and operation and maintenance management system and method in the technical field of GIS data synchronization, and the method comprises the steps: monitoring and capturing GIS spatial data change events from different data sources in real time, and packaging the GIS spatial data change events into a structured message unit, the message unit comprises a time sequence fingerprint and a space influence matrix; and receiving the message unit, performing topology consistency verification on the GIS spatial data change event based on the time sequence fingerprint and the spatial influence matrix, calculating a topology risk score, marking the message unit as a to-be-synchronized state if the verification passes, and generating a topology error event if the verification fails. According to the method, a highly consistent spatial data operation and maintenance system is constructed through real-time change capture, topology consistency instant verification, global serialization propulsion, multi-version synchronous execution and a difference self-healing closed loop.

Description

Technical Field

[0001] This invention relates to a GIS spatial data real-time synchronization and operation and maintenance management system and method, belonging to the field of GIS data synchronization technology. Background Technology

[0002] General-purpose GIS data synchronization platforms are mostly used for static data publishing, periodic update distribution, and geographic information resource sharing services. The core of these systems focuses on map data visualization, feature retrieval, data call interfaces, and cross-departmental information access mechanisms, but lacks the ability to handle topological disturbances, node synchronization delays, version conflict accumulation, and consistency offsets caused by real-time spatial data updates. With the continuous growth of real-time urban infrastructure monitoring, comprehensive natural resource inspections, remote sensing dynamic interpretation, spatiotemporal IoT data acquisition, and high-frequency vector editing, GIS data is shifting from a single static structure to a high-concurrency, multi-node, and highly real-time collaborative operation and maintenance model. This transforms spatial data synchronization from an incremental data copying task into a problem of time-series coordination across intranets, regions, and computing nodes, high-precision topology verification, and version-level consistency maintenance.

[0003] Existing GIS data synchronization systems are mainly geared towards static data publishing and periodic updates. They lack the ability to effectively handle issues such as topological damage, version conflict accumulation, cross-node data inconsistency, and uncontrolled synchronization delays caused by spatial data changes in real-time, high-concurrency, and multi-node collaborative scenarios. They cannot meet the needs of infrastructure dynamic inspection, IoT data collection, and other businesses for strong consistency, high real-time performance, and self-healing spatial data synchronization and operation and maintenance management. Summary of the Invention

[0004] The purpose of this invention is to overcome the shortcomings of the prior art and provide a GIS spatial data real-time synchronization and operation and maintenance management system and method. By real-time change capture, immediate topology consistency verification, global serialization promotion, multi-version synchronous execution and difference self-healing closed loop to build a strongly consistent spatial data operation and maintenance system, it has the ability to effectively handle problems such as topology structure destruction, version conflict accumulation, cross-node data inconsistency and synchronization delay loss caused by spatial data changes in real-time, high-concurrency and multi-node collaborative scenarios.

[0005] To achieve the above objectives, the present invention is implemented using the following technical solution:

[0006] In a first aspect, the present invention provides a method for real-time synchronization and operation and maintenance management of GIS spatial data, including:

[0007] Real-time monitoring and capture of GIS spatial data change events from different data sources, and encapsulation of the GIS spatial data change events into structured message units, the message units including time sequence fingerprints and spatial influence matrices;

[0008] Upon receiving the message unit, the system performs topological consistency verification on the GIS spatial data change event based on the temporal fingerprint and spatial influence matrix, and calculates the topological risk score. If the verification passes, the message unit is marked as pending synchronization; if the verification fails, a topological error event is generated.

[0009] Based on the temporal fingerprint, spatial influence matrix, and topological risk score, a global sequence number is assigned to the message unit in the state to be synchronized, and a global spatial data state view is maintained.

[0010] The order of the global sequence numbers is used to apply changes to the target spatial database in a transactional manner, and a data snapshot is created based on the global sequence numbers, spatial influence matrix, and topological risk score.

[0011] The system tracks the synchronization transaction status corresponding to the data snapshots and global sequence numbers in real time, calculates the global consistency deviation by comparing data snapshots on different nodes, and detects synchronization delay events.

[0012] Based on the topology error event or the global consistency deviation, a decision instruction is generated according to a preset strategy, and the instruction is sent to the global serialization and state coordination module to adjust the synchronization process until all node data reaches a strongly consistent state, thereby completing the real-time synchronization and operation and maintenance management of GIS spatial data.

[0013] Furthermore, the time-series fingerprint expression is:

[0014]

[0015] in: Indicates a unique temporal fingerprint. For data source identification, For event timestamps, For operator identification, For space operation types;

[0016] The expression for the spatial influence matrix is:

[0017]

[0018] in: This is the spatial influence matrix. Quantify the results of geometric change magnitude. The score is based on the weight of attribute changes. and These are the dynamic weight parameters learned by the system during runtime.

[0019] Furthermore, the topological risk score is:

[0020]

[0021] in: To score the topological risk, This is the spatial influence matrix. This represents the existing topological conflict count. and These are the convergence weights calculated online during system operation.

[0022] Furthermore, the formula for the topological consistency check is:

[0023]

[0024] in: To verify the result vector, For the latest geometric node set of the spatial object, For the set of referenced topology rules, Mapping of spatial historical version relationships, This is for verifying the function.

[0025] Furthermore, the global sequence number expression is:

[0026]

[0027] in: This is the global serial number. As a unique temporal fingerprint, This is the spatial influence matrix. To score the topological risk, This is a generating function.

[0028] Furthermore, the data snapshot is generated by a snapshot generation model, the model expression of which is:

[0029]

[0030] in: To create a new snapshot identifier, This is the global serial number. This is the spatial influence matrix. To score the topological risk, , Generate adjustment parameters for the snapshot.

[0031] Furthermore, the global consistency deviation is:

[0032]

[0033] in: This represents the global consistency deviation value, where J represents the total number of nodes. As the node's trust weight factor, This is a spatial difference detection function. Indicates the first Each node in the sequence number The corresponding snapshot instance, This represents the current global spatial data state view version boundary.

[0034] Secondly, this invention provides a GIS spatial data real-time synchronization and operation and maintenance management system, including:

[0035] Spatial data change capture module: used to monitor and capture GIS spatial data change events from different data sources in real time, and encapsulate the GIS spatial data change events into structured message units, the message units including time sequence fingerprints and spatial influence matrices;

[0036] Topology Consistency Real-Time Verification Module: Used to receive the message unit, perform topology consistency verification on the GIS spatial data change event based on the time fingerprint and spatial influence matrix, and calculate the topology risk score. If the verification passes, the message unit is marked as pending synchronization. If the verification fails, a topology error event is generated.

[0037] Global Serialization and State Coordination Module: Used to assign global sequence numbers to message units in the state to be synchronized based on the temporal fingerprint, spatial influence matrix and topological risk score, and maintain a global spatial data state view;

[0038] Multi-version concurrency control synchronous execution module: used to apply changes to the target spatial database in the form of transactions according to the order of the global sequence number, and to create data snapshots based on the global sequence number, spatial influence matrix and topology risk score;

[0039] Distributed transaction status monitoring module: used to track the synchronization transaction status corresponding to the data snapshot and global sequence number in real time, calculate the global consistency deviation by comparing data snapshots on different nodes, and detect synchronization delay events;

[0040] Consistency Decision and Self-Healing Module: Based on the topology error event or the global consistency deviation, it generates decision instructions according to a preset strategy and sends the instructions to the global serialization and state coordination module to adjust the synchronization process until all node data reaches a strongly consistent state, thereby completing the real-time synchronization and operation and maintenance management of GIS spatial data.

[0041] Thirdly, the present invention provides a GIS spatial data real-time synchronization and operation and maintenance management device, including a processor and a storage medium;

[0042] The storage medium is used to store instructions;

[0043] The processor is configured to operate according to the instructions to perform the steps of the method according to any of the foregoing.

[0044] Fourthly, the present invention provides a computer-readable storage medium having a computer program stored thereon, which, when executed by a processor, implements the steps of any of the methods described above.

[0045] Compared with the prior art, the beneficial effects achieved by the present invention are as follows:

[0046] I. This solution implements a strong, consistent, real-time synchronization mechanism for cross-source spatial data. Relying on the collaborative design of global sequence numbers, snapshots, and state view boundaries, it ensures that multiple nodes maintain a monotonously ordered data progression process even under high-frequency changes and complex topologies, effectively eliminating structural distortion caused by concurrent writes, delayed commits, and cross-region replica drift. Furthermore, through real-time topology consistency verification and differentiated risk scoring, geometric legitimacy, adjacency topology relationships, and mandatory boundary constraints are integrated into a unified verification system. This builds the ability to proactively intercept topology violations, preventing errors from entering the synchronous execution chain and reducing the costs of subsequent rollbacks, compensation, and large-scale repairs at the structural level.

[0047] Second, this solution employs multi-version concurrency control and dynamic snapshot isolation strategies to decouple read and write operations. During write transactions, it maintains a consistent and accessible view, enhancing the continuity and zero-blocking characteristics of online queries, spatiotemporal analysis, operational monitoring, and thematic mapping services, and preventing business availability impacts due to synchronization window locking. Simultaneously, a global deviation quantification model and consistency repair strength indicators are designed to form a self-healing closed loop. This enables the system to automatically make decisions, automatically backtrack, and automatically correct when cross-node version offsets, topology instability, or synchronization delays are detected. This achieves fully autonomous operation and maintenance from anomaly detection to recovery, improving system resilience and recovery efficiency.

[0048] Third, this solution forms a closed-loop governance link through global serialization coordination, deviation self-healing feedback and risk-driven synchronization sorting, so as to achieve the operational goals of transparent and controllable synchronization process, predictable state progress and unblocked anomaly correction. Ultimately, it ensures strong consistent version control and high reliability synchronization capability in the dynamic update scenario of full-domain and wide-coverage GIS data, and improves the real-time business carrying capacity of spatial data system in government affairs, surveying and mapping, land and resources and sensing Internet of Things scenarios. Attached Figure Description

[0049] The accompanying drawings, which form part of this specification, are used to provide a further understanding of the invention. The illustrative embodiments of the invention and their descriptions are used to explain the invention and do not constitute an undue limitation of the invention. In the drawings:

[0050] Figure 1This is a flowchart illustrating a method for real-time synchronization and operation and maintenance management of GIS spatial data provided in Embodiment 1 of the present invention. Detailed Implementation

[0051] The present invention will now be described in detail with reference to the accompanying drawings and embodiments. It should be noted that, unless otherwise specified, the embodiments and features described herein can be combined with each other.

[0052] The following detailed description is exemplary and intended to provide further detailed explanation of the invention. Unless otherwise specified, all technical terms used in this invention have the same meaning as commonly understood by one of ordinary skill in the art. The terminology used in this invention is for describing particular embodiments only and is not intended to limit the scope of exemplary embodiments according to the invention.

[0053] Example 1:

[0054] Please see Figure 1 This solution proposes a method for real-time synchronization and operation and maintenance management of GIS spatial data. The specific steps are as follows:

[0055] Step 1: The spatial data change capture module monitors and captures GIS spatial data change events from different data sources in real time. These events include the addition, deletion, and modification of vector elements, as well as changes in geometry and attributes. The captured original change events are encapsulated into message units with preliminary identifiers. It should be noted that in Step 1, the spatial data change capture module not only performs the monitoring function but also performs unified event modeling and semantic hierarchical processing on different types of GIS data sources. This ensures that the original change records possess identifiable structural features and status identifiers before entering the topology consistency verification stage. Spatial data change triggering sources include manual editing services, mobile on-site data collection services, third-party data push services, and automated script generation services. The module employs a spatial object behavior detection mechanism based on event sourcing theory, abstracting all vector element addition, deletion, and modification operations into consistent operational semantics. It also generates structured descriptions of the attribute fields, spatial geometric nodes, and historical version relationships associated with the changes, making the message units traceable. To ensure that change events do not suffer semantic loss or disorder during high-concurrency processing, the module generates a time-series fingerprint for each record. The time-series fingerprint is calculated using the data source identifier, event trigger timestamp, operator identifier, and change type, and a hash digest is generated through spatial data uniqueness constraints. This digest represents an independent spatial change entity. The time-series fingerprint uses the following formula:

[0056]

[0057] in: Indicates a unique temporal fingerprint. For data source identification, For event timestamps, For operator identification, This is a spatial operation type. This formula ensures that the same data object can still be uniquely identified when changes are triggered from different sources, while avoiding duplicate consumption and processing jitter. Internally, the module deconstructs the behavior of change dimensions at different granularities. Changes in spatial geometric points and attribute fields are mapped to a change impact matrix. By quantifying the scope and potential topological impact of changes on the target dataset, the impact matrix is ​​calculated using the following method:

[0058]

[0059] in: This is the spatial influence matrix. Quantify the results of geometric change magnitude. The score is based on the weight of attribute changes. and These are the dynamic weight parameters learned by the system during runtime. This formula provides a basis for difference sensitivity in the subsequent topology verification module, enabling the system to distinguish between critical changes and changes with minor impact, thereby improving resource scheduling efficiency during the verification phase. Finally, all change events are output in the form of structured message units. These message units possess complete semantic identification, replayability, and spatial impact levels, providing the input basis for the next step of real-time topology consistency verification, and thus entering the verification phase.

[0060] Step 2: The topology consistency real-time verification module receives message units and performs real-time verification of the spatial geometric relationships in the change event based on the predefined global topology rule base. This verification includes checking the validity of the geometry, the logical correctness of the spatial relationships, and whether it violates the topology rules that enforce system constraints. If the verification passes, the message unit is marked as pending synchronization; if the verification fails, a topology error event is immediately generated and transferred to the consistency decision and self-healing module for processing. It should be noted that in Step 2, after receiving the message unit from Step 1, the topology consistency real-time verification module does not need to re-parse the context when performing verification because the message unit already contains the temporal fingerprint and spatial influence matrix. Instead, it constructs a verification task queue based on the global topology rule base and uses a spatial structure-aware verification engine to complete continuous verification. The verification process includes geometric legality detection, adjacency topology relationship judgment, and global constraint enforcement check. Geometric legality is used to confirm that the geometric shape does not have self-intersections, void breaks, or redundant nodes. Adjacency relationships are used to ensure that the region patches are closed and the line segments share consistent boundaries. Enforced constraints are used to ensure that cross-data source editing behavior conforms to global spatial rules. To improve verification accuracy, this module employs a topology risk scoring mechanism based on spatial structure differences and dynamically adjusts the verification priority of message units from different data sources. The topology risk score is driven by an influence matrix and calculated using the following formula:

[0061]

[0062] in: To score the topological risk, This is the spatial influence matrix. This represents the existing topological conflict count. and This is the convergence weight calculated online during system runtime. The formula quantifies the probability of a change event triggering a topological anomaly, ensuring the system maintains differentiated verification strategies even under high concurrency and prioritizing the verification of high-risk events when resources are limited. The verification execution phase employs a topological consistency evaluation algorithm to standardize the topological semantic relationships between the changed object and surrounding spatial entities. The algorithm is implemented through incremental comparisons of the geometric set, adjacency set, and logical rule set. The judgment criteria are expressed as follows:

[0063]

[0064] in: To verify the result vector, For the latest geometric node set of the spatial object, For the set of referenced topology rules, Mapping of spatial historical version relationships, This is a verification function that outputs three results: valid, warning, or prohibited, representing the closed-loop verification logic process. If If the output is valid, the message unit is marked as pending synchronization and enters the next stage of the serialization process. If the output is prohibited, the system immediately generates a topology error event and sends it to the consistency decision and self-healing module, and locks the affected object in the global state space, establishing an input connection for the global serialization and state coordination in step three.

[0065] Step 3: The global serialization and state coordination module assigns a globally unique and monotonically increasing sequence number to all message units marked as pending synchronization. This sequence number serves as the global order benchmark across all nodes and services. Simultaneously, this module maintains a global spatial data state view to record the latest globally agreed-upon data version. It should be noted that in Step 3, after receiving message units marked as pending synchronization in Step 2, the global serialization and state coordination module generates a monotonically increasing global sequence number through the global timing controller. This sequence number is used not only for cross-node commit order consistency but also for defining the backtracking boundary for subsequent consistency decisions. Since each message unit already possesses a timing fingerprint in Step 1... With influence matrix The sequence allocation process is not a simple numbering; rather, it is completed based on a sequence priority mechanism dominated by influencing weights, in order to reduce the probability of large-scale spatial topological fluctuations blocking the advancement of a globally consistent state. The global sequence number expression is:

[0066]

[0067] in: This is the global serial number. As a unique temporal fingerprint, This is the spatial influence matrix. To score the topological risk, As a generator function, high-risk change items are prioritized during sequence generation to achieve earlier synchronization. This aims to shorten the system cycle for topology conflict exposure and repair, and reduce the scale of state backtracking and write amplification effects. After sequence allocation, the global state coordination submodule establishes a state-locked region for all objects entering the commit sequence interval and constructs irreversible data version boundaries. The boundary threshold is defined as follows:

[0068]

[0069] in: This is the threshold for global version advancement. K is the system dynamic adjustment coefficient, and K is the total number of messages to be synchronized. and The first and second are respectively the first in the sequence interval. The system generates an impact matrix and risk score for each message to be synchronized. Once a threshold is reached, the system updates the global state view, marking the corresponding sequence interval as a consistent version. The threshold design aims to ensure that the cumulative impact of changes is within a controllable range when state advancement actions occur, avoiding a chain reaction of multi-node consistency rollback caused by instantaneous topology shocks. This module also maintains a global spatial data state view, establishing a global version mapping table through sequence numbers and state boundary indexes. This provides a stable baseline consistent view for subsequent multi-version concurrency control and outputs the sorted synchronization instructions to the multi-version concurrency control synchronization execution module, ensuring that the transactional application in step four has a clear version anchor.

[0070] Step 4: The multi-version concurrency control synchronization execution module applies changes to the target spatial database in a transactional manner within a distributed environment, based on the global sequence number order. This process employs a multi-version concurrency control mechanism to ensure that read operations do not block write operations and creates a corresponding data snapshot for each synchronization transaction, allowing other services to still access a consistent view during synchronization. It should be noted that in Step 4, the multi-version concurrency control synchronization execution module receives the global sequence number from Step 3. Subsequently, a distributed transaction execution queue is established according to the strict sequence, and an independent snapshot version number is generated for each change. This is used to distinguish between ongoing write transactions and the externally visible stable and consistent view. The multi-version concurrency control mechanism operates on the principle of write isolation and read concurrency coexistence. During write transaction execution, it does not block query access from application services, online analysis systems, and visualization engines, ensuring that spatial data maintains readability and historical version reproducibility in synchronization scenarios. The version snapshot generation strategy is driven by sequence numbers and combines spatial influence matrices from steps one and two. Topological risk score Participating in version scheduling enables version management to have load awareness capabilities. The snapshot generation model is represented as follows:

[0071]

[0072] in: To create a new snapshot identifier, This is the global serial number. This is the spatial influence matrix. To score the topological risk, , Snapshot adjustment parameters are generated. The purpose of this formula is to enable the system to identify change events with a large impact or those exhibiting characteristics of accumulated topological risks, thereby achieving a higher snapshot isolation level and reducing potential rollback propagation and cross-node write conflicts. Before a write transaction commits, a commit consistency check is performed. The commit controller compares the current change version with the global spatial data state view. Only when the write transaction matches the current version boundary... A transaction can only be committed and update the stable view if it remains consistent and no conflict flag is triggered; otherwise, the transaction is converted to a deferred commit state and waits for the next coordination window. After successful synchronization, this module distributes the latest visible snapshot to read requests and reports the final transaction state to the distributed transaction state monitoring module, providing complete state input for step five, enabling the system to continue performing synchronization consistency monitoring and deviation identification.

[0073] Step 5: The distributed transaction status monitoring module tracks the execution status and data replica consistency of each synchronization transaction at each stage in real time. By continuously comparing data snapshots corresponding to the same sequence number on different nodes, it detects and reports any data inconsistencies or synchronization delays that deviate from the global status view. It should be noted that in Step 5, after receiving the transaction commit result from Step 4, the distributed transaction status monitoring module uses the global sequence number... As an index benchmark, the corresponding snapshot is used in a multi-node environment. The consistency comparison process is executed, monitoring aspects including transaction execution status, data replica synchronization latency, cross-node spatial geometric difference offset, and topology consistency. This is because the snapshot generation process in step four is affected by... and To mitigate the impact of changes, this module employs a difference-sensitive comparison strategy, enabling the system to achieve higher monitoring accuracy and shorter detection cycles when facing high-impact changes or potential topology conflicts. To quantify the degree of snapshot deviation between different nodes, this module introduces a global consistency deviation metric model, expressed as:

[0074]

[0075] in: This represents the global consistency deviation value, where J represents the total number of nodes. As the node's trust weight factor, This is a spatial difference detection function used to measure geometric precision offset, attribute field differences, and topological deviation. Indicates the first Each node in the sequence number The corresponding snapshot instance, This represents the current global spatial data state view version boundary. The purpose of this formula is to quantify the snapshot consistency status of all nodes using a unified scoring method, when... When within the normal range, the system determines that synchronization is normal and enters a stable operating state. When the deviation exceeds the threshold, this module generates a synchronization offset event and classifies it as either a delay risk or a consistency violation. For cases where there is time lag but no data deviation has occurred, the system calculates a synchronization delay index to identify network jitter, node performance degradation, and cross-regional transmission congestion. The delay index is defined as:

[0076]

[0077] in: The delay index, For node transaction commit timestamps This module advances the timestamp for the global view. It's used to determine if transactions are experiencing synchronization queue backlogs or cross-node execution efficiency degradation. If consistency deviations or latency anomalies are detected, this module will store the event information along with the deviation magnitude and associated sequence number. The snapshot mapping table is then pushed to the consistency decision and self-healing module, entering the decision execution process in step six.

[0078] Step Six: The consistency decision and self-healing module automatically makes decisions based on the received topology error events or data inconsistency events, according to preset strategies. These decisions include triggering a data version rollback within a specified range, requiring the retransmission of change events with specific sequence numbers, or initiating a local data repair process. The decision instructions are then sent to the global serialization and state coordination module to adjust the synchronization process until all node data reaches a strongly consistent state. It should be noted that in Step Six, the consistency decision and self-healing module receives synchronization offset events, topology conflict events, and global deviation quantification results from Step Five. Then, a repair decision stack is constructed using a globally consistent recovery rule set, and based on the sequence number... Compared to snapshot version Establish rollback and retransmission boundaries. This module does not directly execute repair actions; it is only responsible for policy generation, conflict resolution, and version rollback scope control, which are jointly implemented by the global sequence controller and the multi-version snapshot system. To determine the extent of event repair, this module measures the deviation magnitude and topology risk indicators. With cumulative conflict count The consistency recovery determination function is defined as follows:

[0079]

[0080] in: As a consistency repair strength index, This represents the global consistency deviation value. To score the topological risk, For existing topological collision counts, , and This is an adaptive recovery weighting coefficient. This indicator is used to determine the scope and method of data repair. A higher value indicates a deeper impact from the change, a more concentrated topology risk, and more severe legacy conflicts, thus triggering a higher-level recovery strategy. Recovery strategies include three types of decisions: local repair, mid-range rollback, and global sequence rollback. The recovery level is determined by the following version rollback threshold formula:

[0081]

[0082] in: This is the rollback limit value. Where Q is the rollback braking coefficient, and Q is the total number of snapshots. and These represent the impact matrix and risk score of the q-th snapshot within the rollback sequence interval. This threshold is used to limit the rollback depth, preventing the recovery process from exceeding the limits and causing secondary disturbances to the already stable view, ensuring the predictability of the repair within the control boundary. After completing the recovery level calculation, this module sends instructions to the global serialization and state coordination module in step three through the consistency adjudication engine. This module performs sequence freezing, retransmission triggering, and conflict segment isolation, and temporarily blocks the write commit path in step four to ensure that no new drift occurs during global consistency recovery. After the repair process is completed, the recovery instructions are synchronously updated to the distributed monitoring module, causing the system to re-enter the sequence advancement state and restore the normal synchronization closed loop.

[0083] This solution constructs a strongly consistent spatial data operation and maintenance system through real-time change capture, immediate topology consistency verification, global serialization, multi-version synchronous execution, and a self-healing loop for differences. Its core benefits lie in achieving sequential autonomous distribution of cross-node data changes, proactive interception of topology anomalies, and self-recovery capabilities. However, traditional spatial data synchronization often employs periodic refreshes, static mirror overlays, or unordered copy updates, lacking a version conflict detection mechanism driven by a spatial impact matrix and a snapshot-level difference diagnosis model. This leads to topology corruption, chain-like cross-node rollbacks, version lock-ups, and uncontrolled accumulation of data inconsistencies after frequent additions, deletions, and modifications, making it difficult to support the strongly consistent data collaboration requirements for dynamic infrastructure inspection and cloud-based multi-source GIS editing scenarios.

[0084] Example 2:

[0085] A GIS spatial data real-time synchronization and operation and maintenance management system, which can implement the GIS spatial data real-time synchronization and operation and maintenance management method described in Embodiment 1, includes:

[0086] Spatial data change capture module: used to monitor and capture GIS spatial data change events from different data sources in real time, and encapsulate the GIS spatial data change events into structured message units, the message units including time sequence fingerprints and spatial influence matrices;

[0087] Topology Consistency Real-Time Verification Module: Used to receive the message unit, perform topology consistency verification on the GIS spatial data change event based on the time fingerprint and spatial influence matrix, and calculate the topology risk score. If the verification passes, the message unit is marked as pending synchronization. If the verification fails, a topology error event is generated.

[0088] Global Serialization and State Coordination Module: Used to assign global sequence numbers to message units in the state to be synchronized based on the temporal fingerprint, spatial influence matrix and topological risk score, and maintain a global spatial data state view;

[0089] Multi-version concurrency control synchronous execution module: used to apply changes to the target spatial database in the form of transactions according to the order of the global sequence number, and to create data snapshots based on the global sequence number, spatial influence matrix and topology risk score;

[0090] Distributed transaction status monitoring module: used to track the synchronization transaction status corresponding to the data snapshot and global sequence number in real time, calculate the global consistency deviation by comparing data snapshots on different nodes, and detect synchronization delay events;

[0091] Consistency Decision and Self-Healing Module: Based on the topology error event or the global consistency deviation, it generates decision instructions according to a preset strategy and sends the instructions to the global serialization and state coordination module to adjust the synchronization process until all node data reaches a strongly consistent state, thereby completing the real-time synchronization and operation and maintenance management of GIS spatial data.

[0092] Example 3:

[0093] This invention also provides a GIS spatial data real-time synchronization and operation and maintenance management device, which can realize the GIS spatial data real-time synchronization and operation and maintenance management method described in Embodiment 1, including a processor and a storage medium;

[0094] The storage medium is used to store instructions;

[0095] The processor is configured to operate according to the instructions to perform the steps of the following method:

[0096] Real-time monitoring and capture of GIS spatial data change events from different data sources, and encapsulation of the GIS spatial data change events into structured message units, the message units including time sequence fingerprints and spatial influence matrices;

[0097] Upon receiving the message unit, the system performs topological consistency verification on the GIS spatial data change event based on the temporal fingerprint and spatial influence matrix, and calculates the topological risk score. If the verification passes, the message unit is marked as pending synchronization; if the verification fails, a topological error event is generated.

[0098] Based on the temporal fingerprint, spatial influence matrix, and topological risk score, a global sequence number is assigned to the message unit in the state to be synchronized, and a global spatial data state view is maintained.

[0099] The order of the global sequence numbers is used to apply changes to the target spatial database in a transactional manner, and a data snapshot is created based on the global sequence numbers, spatial influence matrix, and topological risk score.

[0100] The system tracks the synchronization transaction status corresponding to the data snapshots and global sequence numbers in real time, calculates the global consistency deviation by comparing data snapshots on different nodes, and detects synchronization delay events.

[0101] Based on the topology error event or the global consistency deviation, a decision instruction is generated according to a preset strategy, and the instruction is sent to the global serialization and state coordination module to adjust the synchronization process until all node data reaches a strongly consistent state, thereby completing the real-time synchronization and operation and maintenance management of GIS spatial data.

[0102] Example 4:

[0103] This invention also provides a computer-readable storage medium that can implement the GIS spatial data real-time synchronization and operation and maintenance management method described in Embodiment 1. The medium stores a computer program that, when executed by a processor, performs the steps of the following method:

[0104] Real-time monitoring and capture of GIS spatial data change events from different data sources, and encapsulation of the GIS spatial data change events into structured message units, the message units including time sequence fingerprints and spatial influence matrices;

[0105] Upon receiving the message unit, the system performs topological consistency verification on the GIS spatial data change event based on the temporal fingerprint and spatial influence matrix, and calculates the topological risk score. If the verification passes, the message unit is marked as pending synchronization; if the verification fails, a topological error event is generated.

[0106] Based on the temporal fingerprint, spatial influence matrix, and topological risk score, a global sequence number is assigned to the message unit in the state to be synchronized, and a global spatial data state view is maintained.

[0107] The order of the global sequence numbers is used to apply changes to the target spatial database in a transactional manner, and a data snapshot is created based on the global sequence numbers, spatial influence matrix, and topological risk score.

[0108] The system tracks the synchronization transaction status corresponding to the data snapshots and global sequence numbers in real time, calculates the global consistency deviation by comparing data snapshots on different nodes, and detects synchronization delay events.

[0109] Based on the topology error event or the global consistency deviation, a decision instruction is generated according to a preset strategy, and the instruction is sent to the global serialization and state coordination module to adjust the synchronization process until all node data reaches a strongly consistent state, thereby completing the real-time synchronization and operation and maintenance management of GIS spatial data.

[0110] As is known from common technical knowledge, this invention can be implemented through other embodiments that do not depart from its spirit or essential characteristics. Therefore, the disclosed embodiments described above are merely illustrative and not exhaustive. All modifications within the scope of this invention or its equivalents are included in this invention.

[0111] Those skilled in the art will understand that embodiments of the present invention can be provided as methods, systems, or computer program products. Therefore, the present invention can take the form of a completely hardware embodiment, a completely software embodiment, or an embodiment combining software and hardware aspects. Furthermore, the present invention can take the form of a computer program product embodied on one or more computer-usable storage media (including, but not limited to, disk storage, CD-ROM, optical storage, etc.) containing computer-usable program code.

[0112] This invention is described with reference to flowchart illustrations and / or block diagrams of methods, apparatus (systems), and computer program products according to embodiments of the invention. It will be understood that each block of the flowchart illustrations and / or block diagrams, and combinations of blocks in the flowchart illustrations and / or block diagrams, can be implemented by computer program instructions. These computer program instructions can be provided to a processor of a general-purpose computer, special-purpose computer, embedded processor, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, generate instructions for implementing the flowchart illustrations and / or block diagrams. Figure 1 One or more processes and / or boxes Figure 1 A device that provides the functions specified in one or more boxes.

[0113] These computer program instructions may also be stored in a computer-readable storage medium that can direct a computer or other programmable data processing device to function in a particular manner, such that the instructions stored in the computer-readable storage medium produce an article of manufacture including instruction means, which are implemented in a process Figure 1 One or more processes and / or boxes Figure 1 The function specified in one or more boxes.

[0114] These computer program instructions may also be loaded onto a computer or other programmable data processing equipment to cause a series of operational steps to be performed on the computer or other programmable equipment to produce a computer-implemented process, thereby providing instructions that execute on the computer or other programmable equipment for implementing the process. Figure 1 One or more processes and / or boxes Figure 1 The steps of the function specified in one or more boxes.

[0115] Finally, it should be noted that the above embodiments are only used to illustrate the technical solutions of the present invention and not to limit it. Although the present invention has been described in detail with reference to the above embodiments, those skilled in the art should understand that modifications or equivalent substitutions can still be made to the specific implementation of the present invention. Any modifications or equivalent substitutions that do not depart from the spirit and scope of the present invention should be covered within the scope of protection of the claims of the present invention.

Claims

1. A method for real-time synchronization and operation and maintenance management of GIS spatial data, characterized in that, include: Real-time monitoring and capture of GIS spatial data change events from different data sources, and encapsulation of the GIS spatial data change events into structured message units, the message units including time sequence fingerprints and spatial influence matrices; Upon receiving the message unit, the system performs topological consistency verification on the GIS spatial data change event based on the temporal fingerprint and spatial influence matrix, and calculates the topological risk score. If the verification passes, the message unit is marked as pending synchronization; if the verification fails, a topological error event is generated. Based on the temporal fingerprint, spatial influence matrix, and topological risk score, a global sequence number is assigned to the message unit in the state to be synchronized, and a global spatial data state view is maintained. The order of the global sequence numbers is used to apply changes to the target spatial database in a transactional manner, and a data snapshot is created based on the global sequence numbers, spatial influence matrix, and topological risk score. The system tracks the synchronization transaction status corresponding to the data snapshots and global sequence numbers in real time, calculates the global consistency deviation by comparing data snapshots on different nodes, and detects synchronization delay events. Based on the topology error event or the global consistency deviation, a decision instruction is generated according to a preset strategy, and the instruction is sent to the global serialization and state coordination module to adjust the synchronization process until all node data reaches a strongly consistent state, thereby completing the real-time synchronization and operation and maintenance management of GIS spatial data.

2. The method for real-time synchronization and operation and maintenance management of GIS spatial data according to claim 1, characterized in that, The time-series fingerprint expression is: in: Indicates a unique temporal fingerprint. For data source identification, For event timestamps, For operator identification, For space operation types; The expression for the spatial influence matrix is: in: This is the spatial influence matrix. Quantify the results of geometric change magnitude. The score is based on the weight of attribute changes. and These are the dynamic weight parameters learned by the system during runtime.

3. The method for real-time synchronization and operation and maintenance management of GIS spatial data according to claim 1, characterized in that, The topological risk score is: in: To score the topological risk, This is the spatial influence matrix. This represents the existing topological conflict count. and These are the convergence weights calculated online during system operation.

4. The method for real-time synchronization and operation and maintenance management of GIS spatial data according to claim 1, characterized in that, The formula for the topology consistency check is: in: To verify the result vector, For the latest geometric node set of the spatial object, For the set of referenced topology rules, Mapping of spatial historical version relationships, This is for verifying the function.

5. The method for real-time synchronization and operation and maintenance management of GIS spatial data according to claim 1, characterized in that, The global sequence number expression is: in: This is the global serial number. As a unique temporal fingerprint, This is the spatial influence matrix. To score the topological risk, This is a generating function.

6. The method for real-time synchronization and operation and maintenance management of GIS spatial data according to claim 1, characterized in that, The data snapshot is generated by a snapshot generation model, the model expression of which is: in: To create a new snapshot identifier, This is the global serial number. This is the spatial influence matrix. To score the topological risk, , Generate adjustment parameters for the snapshot.

7. The method for real-time synchronization and operation and maintenance management of GIS spatial data according to claim 1, characterized in that, The global consistency deviation is: in: This represents the global consistency deviation value, where J represents the total number of nodes. As the node's trust weight factor, This is a spatial difference detection function. Indicates the first Each node in the sequence number The corresponding snapshot instance, This represents the current global spatial data state view version boundary.

8. A GIS spatial data real-time synchronization and operation and maintenance management system, characterized in that, include: Spatial data change capture module: used to monitor and capture GIS spatial data change events from different data sources in real time, and encapsulate the GIS spatial data change events into structured message units, the message units including time sequence fingerprints and spatial influence matrices; Topology Consistency Real-Time Verification Module: Used to receive the message unit, perform topology consistency verification on the GIS spatial data change event based on the time fingerprint and spatial influence matrix, and calculate the topology risk score. If the verification passes, the message unit is marked as pending synchronization. If the verification fails, a topology error event is generated. Global Serialization and State Coordination Module: Used to assign global sequence numbers to message units in the state to be synchronized based on the temporal fingerprint, spatial influence matrix and topological risk score, and maintain a global spatial data state view; Multi-version concurrency control synchronous execution module: used to apply changes to the target spatial database in the form of transactions according to the order of the global sequence number, and to create data snapshots based on the global sequence number, spatial influence matrix and topology risk score; Distributed transaction status monitoring module: used to track the synchronization transaction status corresponding to the data snapshot and global sequence number in real time, calculate the global consistency deviation by comparing data snapshots on different nodes, and detect synchronization delay events; Consistency Decision and Self-Healing Module: Based on the topology error event or the global consistency deviation, it generates decision instructions according to a preset strategy and sends the instructions to the global serialization and state coordination module to adjust the synchronization process until all node data reaches a strongly consistent state, thereby completing the real-time synchronization and operation and maintenance management of GIS spatial data.

9. A GIS spatial data real-time synchronization and operation and maintenance management device, characterized in that, Including processor and storage media; The storage medium is used to store instructions; The processor is configured to operate according to the instructions to perform the steps of the method according to any one of claims 1 to 7.

10. A computer-readable storage medium having a computer program stored thereon, characterized in that, When executed by a processor, the program implements the steps of the method according to any one of claims 1 to 7.

Images