Land use dynamic monitoring data intelligent processing method and system

Abstract

The present application relates to the technical field of land use monitoring data processing, in particular to a kind of land use dynamic monitoring data intelligent processing method and system;The method comprises: obtaining land use dynamic monitoring multi-source data, constructs land use benchmark result page;Based on edge side change map spot data reading target map spot update data, difference encapsulation is carried out with target map spot benchmark data, and change map spot patch package is generated;According to the target map spot object identification and boundary difference field in patch package, determine adjacent boundary data, query cloud boundary lock table and execute write access control;Admitted patch package is written into cloud result patch library, generates result playback index and writes back patch application record.The present application realizes the patch type update of land use dynamic monitoring result, boundary write control and historical state recovery.

Description

Technical Field

[0001] This invention relates to the field of land use monitoring data processing technology, specifically to an intelligent processing method and system for dynamic land use monitoring data. Background Technology

[0002] Land use dynamic monitoring data processing is a crucial data processing step in natural resource information management. It typically requires the unified organization and continuous updating of land use results data, change patch data, boundary fragment data, land use code data, and verification evidence data generated from different monitoring batches. With the continuous increase in data sources such as remote sensing monitoring, edge verification, and cloud-based results database management, land use dynamic monitoring results are no longer just static data generated in a single instance. Instead, they are data objects that need to be stored, updated, traced, and restored under conditions of multiple batches, multiple sources, and multiple patch associations. Existing data processing methods usually treat change patches as the update objects of the results database, writing or overwriting updates to patch boundaries, land use attributes, and related evidence according to monitoring batches to maintain the timeliness of land use results data. During the continuous updating of land use dynamic monitoring results, there are still problems such as chaotic data coverage and inconsistent adjacent boundaries when changing map features are written into the results database. Specifically, the issues are as follows: First, the same map feature may generate change data multiple times under different monitoring batches, different edge sides, or different evidence sources. If each change data is directly rewritten to the cloud results database, it is easy for the previous batch of results to be overwritten by the subsequent batch of data. It is difficult to trace back the boundary, land type, and evidence status of the map feature before the update, and it is difficult to restore the state before the writing when an error is found in a certain batch of data. Second, there are usually shared boundary relationships between land use map features. The boundary change of the target map feature will affect the boundary closure relationship of adjacent map features. If the data uploaded by multiple changing map features or multiple edge sides involve the same shared boundary at the same time, it is easy to have the shared boundary written repeatedly, the boundary between the target map feature and the adjacent map feature not synchronized, and the boundary relationship of map features in the results database not consistent. Summary of the Invention

[0003] The purpose of this invention is to provide an intelligent processing method and system for dynamic land use monitoring data, so as to solve the problems mentioned in the background art, which are easy to cause data coverage confusion and inconsistent adjacent boundaries when writing change patches into the results database.

[0004] To achieve the above objectives, the technical solution of the present invention is: an intelligent processing method for dynamic land use monitoring data, comprising: S1. Obtain multi-source data of dynamic land use monitoring, construct a land use benchmark result page based on the cloud benchmark result data in the multi-source data of dynamic land use monitoring, and establish the correspondence between the map object identifier, spatial index code, benchmark land type code, boundary segment identifier, benchmark boundary segment data and result version identifier in the land use benchmark result page; Among them, the multi-source data for dynamic land use monitoring includes cloud-based benchmark results data and edge-side change patch data; the land use benchmark results page includes benchmark page identifier, patch object identifier, spatial index code, benchmark land category code, boundary segment identifier, benchmark boundary segment data, and results version identifier; S2. Based on the edge-side change patch data, read the target patch update data, query the land use benchmark results page according to the target patch object identifier, read the target patch benchmark data, perform differential encapsulation processing on the target patch update data and the target patch benchmark data, generate a change patch patch package, and set the patch application status field of the change patch patch package to an unapplied status. The target patch update data includes edge side markers, target patch object markers, monitoring batch markers, patch change data, and evidence attachment data. Patch change data includes changed boundary data and changed land use code. The target patch baseline data includes baseline boundary segment data, baseline land use code, and result version marker. S3. Based on the target parcel object identifier and boundary difference field in the changed parcel patch package, query the land use benchmark results page to determine the adjacent boundary data corresponding to the target parcel object identifier; based on the adjacent boundary data, query the cloud boundary lock table to generate boundary lock query results; based on the boundary lock query results, perform write access control on the changed parcel patch package to generate patch access results; The adjacent boundary data includes adjacent patch object identifiers and shared boundary segment identifiers; the boundary lock query results include generated boundary lock occupancy records and non-generated boundary lock occupancy records. S4. Write the access patch package into the cloud results patch library, update the patch application status field of the access patch package, generate a results replay index based on the land use benchmark results page and the access patch package, set the release status field of the adjacent boundary transaction lock corresponding to the access patch package to the released status, write the suspended patch package into the cloud patch suspension queue, and write the patch application record back to the corresponding edge side based on the edge side identifier. The result replay index includes a base page identifier, patch package identifier, monitoring batch identifier, rollback anchor point field, patch application order field, and replay status field; patch application records are generated based on the result replay index.

[0005] Preferably, in step S1, the cloud-based benchmark data is aggregated according to spatial index codes to generate benchmark data groups corresponding to the spatial index codes; the land use benchmark results page is generated based on the benchmark data groups and configured with a benchmark page identifier corresponding to the spatial index codes; the land use benchmark results page records the benchmark page identifier, spatial index code, administrative division code, and results page status field; the land use benchmark results page records the benchmark land type code, boundary segment identifier, benchmark boundary segment data, and results version identifier according to the map object identifier; intra-page correspondences are established between the map object identifier and the boundary segment identifier, between the boundary segment identifier and the benchmark boundary segment data, between the map object identifier and the benchmark land type code, and between the map object identifier and the results version identifier.

[0006] Preferably, in step S2, the changed boundary data in the target patch update data is compared with the baseline boundary segment data in the target patch baseline data to generate a boundary difference field; the boundary difference field includes a boundary segment addition field, a boundary segment deletion field, a boundary segment replacement field, and a boundary segment retention field; the changed land use code in the target patch update data is compared with the baseline land use code in the target patch baseline data to generate a land use difference field; the land use difference field includes a baseline land use code field, a changed land use code field, and a land use difference status field; the evidence attachment data in the target patch update data is written into the evidence attachment field according to the edge side identifier, the target patch object identifier, and the monitoring batch identifier; the boundary difference field, the land use difference field, and the evidence attachment field are written under the same patch package identifier to form the differential encapsulation content of the changed patch patch package.

[0007] Preferably, in step S2, the changed patch package uses the patch package identifier as the primary key of the package index, the target patch object identifier as the result update object, the monitoring batch identifier as the patch application batch, and the edge side identifier as the patch write-back object; the patch package identifier is generated based on the edge side identifier, the target patch object identifier, and the monitoring batch identifier; the rollback anchor point field consists of the base page identifier, the target patch object identifier, and the result version identifier; the patch application status field includes unapplied status, suspended status, and applied status; when the changed patch package is generated, the patch application status field is set to unapplied status; when it is marked as a suspended patch package, the patch application status field is set to suspended status; and when it is written to the cloud result patch library, the patch application status field is set to applied status.

[0008] Preferably, in step S3, the target boundary segment identifier is read from the land use benchmark results page based on the target parcel object identifier in the changed parcel patch package. The boundary segment identifier to be written is determined based on the boundary difference field. The target boundary segment identifier and the boundary segment identifier to be written are matched to determine the shared boundary segment identifier. The adjacent parcel object identifier is determined based on the shared boundary segment identifier to form adjacent boundary data. The cloud boundary lock table records the shared boundary segment identifier, patch package identifier, target parcel object identifier, adjacent parcel object identifier, lock status field, and release status field. Based on the shared boundary segment identifier in the adjacent boundary data, the cloud boundary lock table is queried. If there is a record in the cloud boundary lock table that corresponds to the shared boundary segment identifier, has a locked status field, and a non-released status field, a boundary lock occupancy record is generated. If there is no record in the cloud boundary lock table that corresponds to the shared boundary segment identifier, has a locked status field, and a non-released status field, the boundary lock query result is marked as no boundary lock occupancy record is generated.

[0009] Preferably, in step S3, the adjacent boundary transaction lock includes a transaction lock identifier, a patch package identifier, a target polygon object identifier, an adjacent polygon object identifier, a shared boundary fragment identifier, a lock status field, and a release status field. When the boundary lock query result indicates that no boundary lock occupancy record has been generated, an adjacent boundary transaction lock is generated based on the patch package identifier of the changed polygon patch package, the target polygon object identifier, and the adjacent polygon object identifier and shared boundary fragment identifier in the adjacent boundary data. The lock status field of the adjacent boundary transaction lock is set to locked, the release status field is set to unreleased, the changed polygon patch package is marked as an admission patch package, and the transaction lock identifier is written into the boundary lock association field in the patch admission result. When the boundary lock query result indicates that a boundary lock occupancy record has been generated, no adjacent boundary transaction lock is generated, and the changed polygon patch package is marked as a suspended patch package. The patch admission result includes a patch package identifier, an admission mark field, a suspended mark field, and a boundary lock association field.

[0010] Preferably, in step S4, the cloud-based result patch library records the patch package identifier, base page identifier, target patch object identifier, monitoring batch identifier, rollback anchor point field, and patch application status field. After the admission patch package is written to the cloud-based result patch library, the patch application status field of the admission patch package is set to the applied state, and the corresponding adjacent boundary transaction lock is queried based on the patch package identifier, and the release status field of the adjacent boundary transaction lock is set to the released state. The result replay index uses the base page identifier of the land use benchmark result page as the replay starting point, the patch package identifier of the admission patch package as the replay object, the monitoring batch identifier as the patch application batch, and the rollback anchor point field as the rollback association position, and generates a patch application order field according to the order in which the admission patch packages are written to the cloud-based result patch library. The patch application record is generated based on the result replay index, and the patch application record includes the edge side identifier, patch package identifier, monitoring batch identifier, patch application status field, and replay status field. When the suspended patch package is written to the cloud-based patch suspension queue, the patch application status field of the suspended patch package remains in the suspended state.

[0011] On the other hand, the present invention provides an intelligent processing system for dynamic land use monitoring data, including a memory, a processor, and a computer program stored in the memory and executable on the processor. The processor executes the computer program to implement the aforementioned intelligent processing method for dynamic land use monitoring data.

[0012] Compared with the prior art, the above-mentioned technical solution of the present invention has the following beneficial technical effects: 1. In this invention, the edge-side change patch data is differentially encapsulated and patch-written based on the change patch package. This allows boundary changes, land use changes, evidence attachments, and rollback positions to be recorded as independent patch data, preventing change data from directly overwriting the original patch results in the cloud results library. When the same patch is repeatedly updated in multiple monitoring batches, the change records corresponding to each batch can be retained, providing data basis for results tracing, error rollback, and historical state restoration. 2. In this invention, the write access control of the change patch package is performed by the adjacent boundary transaction lock, and the patch application order is recorded based on the result replay index to realize the orderly writing of the related patches of the shared boundary; when multiple change patches involve the same shared boundary segment, the patch package can be distinguished into the access patch package and the suspended patch package according to the cloud boundary lock table, so as to avoid the same shared boundary being rewritten at the same time, and support the restoration of the land use result status according to the monitoring batch. Attached Figure Description

[0013] Figure 1 This is a flowchart of one embodiment of the present invention. Detailed Implementation

[0014] Example 1, as Figure 1 As shown, the specific implementation steps of the intelligent processing method for dynamic land use monitoring data proposed in this invention are as follows: S1. Obtain multi-source data of dynamic land use monitoring, construct a land use benchmark result page based on the cloud benchmark result data in the multi-source data of dynamic land use monitoring, and establish the correspondence between the map object identifier, spatial index code, benchmark land type code, boundary segment identifier, benchmark boundary segment data and result version identifier in the land use benchmark result page; Among them, the multi-source data for dynamic land use monitoring includes cloud-based benchmark results data and edge-side change patch data; the land use benchmark results page includes benchmark page identifier, patch object identifier, spatial index code, benchmark land category code, boundary segment identifier, benchmark boundary segment data, and results version identifier; S2. Based on the edge-side change patch data, read the target patch update data, query the land use benchmark results page according to the target patch object identifier, read the target patch benchmark data, perform differential encapsulation processing on the target patch update data and the target patch benchmark data, generate a change patch patch package, and set the patch application status field of the change patch patch package to an unapplied status. The target patch update data includes edge side identifiers, target patch object identifiers, monitoring batch identifiers, patch change data, and evidence attachment data. Patch change data includes changed boundary data and changed land use codes. The target patch baseline data includes baseline boundary segment data, baseline land use codes, and result version identifiers. The changed patch patch package includes patch package identifiers, edge side identifiers, target patch object identifiers, monitoring batch identifiers, differential fields, evidence attachment fields, rollback anchor point fields, and patch application status fields. The differential fields include boundary differential fields and land use differential fields. The rollback anchor point field is generated based on the result version identifier. S3. Based on the target parcel object identifier and boundary difference field in the changed parcel patch package, query the land use benchmark results page to determine the adjacent boundary data corresponding to the target parcel object identifier; based on the adjacent boundary data, query the cloud boundary lock table to generate boundary lock query results; based on the boundary lock query results, perform write access control on the changed parcel patch package to generate patch access results; The adjacent boundary data includes adjacent polygon object identifiers and shared boundary segment identifiers; the boundary lock query results include generated boundary lock occupancy records and non-generated boundary lock occupancy records; the boundary lock occupancy records are generated based on the shared boundary segment identifier, the lock status field, and the release status field; when no boundary lock occupancy record is generated, an adjacent boundary transaction lock is generated based on the changed polygon patch package and the adjacent boundary data, the lock status field of the adjacent boundary transaction lock is set to locked, the release status field is set to not released, and the changed polygon patch package is marked as an admission patch package; when a boundary lock occupancy record is generated, the changed polygon patch package is marked as a suspended patch package; S4. Write the access patch package into the cloud results patch library, update the patch application status field of the access patch package, generate a results replay index based on the land use benchmark results page and the access patch package, set the release status field of the adjacent boundary transaction lock corresponding to the access patch package to the released status, write the suspended patch package into the cloud patch suspension queue, and write the patch application record back to the corresponding edge side based on the edge side identifier. The result replay index includes a base page identifier, patch package identifier, monitoring batch identifier, rollback anchor point field, patch application order field, and replay status field; patch application records are generated based on the result replay index.

[0015] In this embodiment S1, cloud-based benchmark data is collected according to spatial index codes to generate benchmark data groups corresponding to spatial index codes; land use benchmark results pages are generated based on benchmark data groups and configured with benchmark page identifiers corresponding to spatial index codes; land use benchmark results pages record benchmark page identifiers, spatial index codes, administrative division codes, and result page status fields; land use benchmark results pages record benchmark land type codes, boundary segment identifiers, benchmark boundary segment data, and result version identifiers according to map object identifiers; intra-page correspondences are established between map object identifiers and boundary segment identifiers, between boundary segment identifiers and benchmark boundary segment data, between map object identifiers and benchmark land type codes, and between map object identifiers and result version identifiers.

[0016] In this embodiment S1, the multi-source data for dynamic land use monitoring refers to the data set used to form the basis for updating the dynamic land use monitoring results. It includes cloud-based baseline data and edge-side change plot data. Cloud-based baseline data refers to land use results data in the cloud-based results database that has already formed a baseline state. Edge-side change plot data refers to data uploaded by edge-side monitoring nodes that indicates boundary changes, land use category changes, or evidence attachment changes of target plots. The cloud-based baseline data includes at least the plot object identifier, spatial index code, administrative division code, baseline land use category code, boundary segment identifier, baseline boundary segment data, results version identifier, and results page status field. The plot object identifier uniquely points to the land use plot object in the cloud-based results database, and the spatial index code points to the plot... The spatial index unit to which the patch belongs, the administrative division code is used to record the administrative management scope to which the patch belongs, the benchmark land type code is used to record the land use category of the patch in the current benchmark result state, the boundary segment identifier is used to mark the boundary segments that constitute the patch boundary, the benchmark boundary segment data is used to record the spatial boundary content corresponding to the boundary segments, the result version identifier is used to record the result version of the patch in the cloud result library, and the result page status field is used to record the current status of the land use benchmark result page as queryable, attachable, frozen, or updating. The system collects the cloud benchmark result data according to the spatial index code, generates a benchmark result data group corresponding to the spatial index code, and configures the benchmark page identifier for the benchmark result data group; then, the land use benchmark result page is generated based on the benchmark result data group.

[0017] In this embodiment S1, the land use benchmark result page is a logical data page in the cloud-based result library used to carry the benchmark result status. It is not limited to the display page in the user interface. The land use benchmark result page includes a header field and in-page map patch records. The header field records the benchmark page identifier, spatial index code, administrative division code, and result page status field. The in-page map patch records the benchmark land type code, boundary segment identifier, benchmark boundary segment data, and result version identifier according to the map patch object identifier. The system establishes in-page correspondences between map patch object identifiers and boundary segment identifiers, between boundary segment identifiers and benchmark boundary segment data, between map patch object identifiers and benchmark land type codes, and between map patch object identifiers and result version identifiers in the land use benchmark result page. Among them, the correspondence between map patch object identifiers and benchmark land type codes is used for subsequent reading of target map patches in the benchmark result page. In the land use benchmark results page, the correspondence between the land parcel object identifier and the boundary segment identifier is used for subsequent reading of the boundary segments that constitute the boundary of the target land parcel. The correspondence between the boundary segment identifier and the baseline boundary segment data is used for subsequent differential encapsulation processing of the changed boundary data and the corresponding baseline boundary segment data. The correspondence between the land parcel object identifier and the result version identifier is used for subsequent generation of the rollback anchor point field. The boundary segment identifier is used to indicate the numbering relationship of the boundary segments, and the baseline boundary segment data is used to carry the actual spatial boundary content of the boundary segments. Both are recorded separately to avoid directly using the boundary segment identifier as boundary data in subsequent differential processing. Through the above organization method, the land use benchmark results page provides a unified data reference foundation for reading the benchmark data of the target land parcel, generating the patch package of changed land parcels, determining the adjacent boundary data, and constructing the result replay index.

[0018] In this embodiment S2, the changed boundary data in the target patch update data is compared with the baseline boundary segment data in the target patch baseline data to generate a boundary difference field. The boundary difference field includes a boundary segment addition field, a boundary segment deletion field, a boundary segment replacement field, and a boundary segment retention field. The changed land use code in the target patch update data is compared with the baseline land use code in the target patch baseline data to generate a land use difference field. The land use difference field includes a baseline land use code field, a changed land use code field, and a land use difference status field. The evidence attachment data in the target patch update data is written into the evidence attachment field according to the edge side identifier, the target patch object identifier, and the monitoring batch identifier. The boundary difference field, the land use difference field, and the evidence attachment field are written under the same patch package identifier to form the differential encapsulation content of the changed patch patch package.

[0019] In this embodiment S2, the target patch update data is the set of updated data corresponding to the same target patch object identifier in the edge-side change patch data. It includes the edge-side identifier, target patch object identifier, monitoring batch identifier, changed boundary data, changed land use code, and evidence attachment data. After the system reads the target patch update data, it uses the target patch object identifier as the query entry point to read the target patch benchmark data in the land use benchmark results page. The target patch benchmark data includes benchmark boundary fragment data, benchmark land use code, and results version identifier. Among them, the benchmark boundary fragment data is used as a differential reference for the changed boundary data, and the benchmark land use code is used as a differential reference for the changed land use code. The result version identifier is used for the rollback anchor point field in the subsequent generated change patch package. The differential encapsulation process does not directly rewrite the cloud result library, but first extracts the differences between the target patch update data and the target patch baseline data, and writes the differences into the change patch patch package. Specifically, the change boundary data in the target patch update data is compared with the baseline boundary segment data in the target patch baseline data to generate a boundary difference field; the change land use code is compared with the baseline land use code to generate a land use difference field; and the evidence attachment data is written into the evidence attachment field according to the edge side identifier, the target patch object identifier, and the monitoring batch identifier.

[0020] In this embodiment S2, the boundary difference field is used to record the changes in boundary segments of the changed boundary data relative to the baseline boundary segment data. The boundary difference field includes a boundary segment addition field, a boundary segment deletion field, a boundary segment replacement field, and a boundary segment retention field. The boundary segment addition field is used to record boundary segments that exist in the changed boundary data but do not exist in the baseline boundary segment data. The boundary segment deletion field is used to record boundary segments that exist in the baseline boundary segment data but are no longer retained in the changed boundary data. The boundary segment replacement field is used to record the data content in the changed boundary data used to replace the corresponding boundary segments in the baseline boundary segment data. The boundary segment retention field is used to record the data content retained in the changed boundary data and the baseline boundary segment data. The boundary segment of the corresponding relationship, the land category difference field is used to record the land category code change content relative to the benchmark land category code. The land category difference field includes the benchmark land category code field, the changed land category code field, and the land category difference status field. The evidence attachment field is used to record the evidence attachment data corresponding to the target patch update data. The evidence attachment data can include the evidence source identifier, the evidence batch identifier, the evidence file identifier, and the evidence attachment status field. The boundary difference field, the land category difference field, and the evidence attachment field are written under the same patch package identifier, so that the same target patch forms a complete change patch patch differential encapsulation content in the same monitoring batch, avoiding the reference break caused by the separate storage of boundary changes, land category changes, and evidence attachments.

[0021] In this embodiment S2, the changed patch package uses the patch package identifier as the primary key of the package index, the target patch object identifier as the result update object, the monitoring batch identifier as the patch application batch, and the edge side identifier as the patch write-back object; the patch package identifier is generated based on the edge side identifier, the target patch object identifier, and the monitoring batch identifier; the rollback anchor point field consists of the base page identifier, the target patch object identifier, and the result version identifier; the patch application status field includes unapplied status, suspended status, and applied status; when the changed patch package is generated, the patch application status field is set to unapplied status; when it is marked as a suspended patch package, the patch application status field is set to suspended status; and when it is written to the cloud result patch library, the patch application status field is set to applied status.

[0022] In this embodiment S2, the changed patch package is a patch data object generated by differential encapsulation processing. It carries the differential content of the target patch update data relative to the target patch baseline data. The changed patch package uses the patch package identifier as the primary key of the package index, the target patch object identifier as the result update object, the monitoring batch identifier as the patch application batch, and the edge side identifier as the patch write-back object. The patch package identifier is generated based on the edge side identifier, the target patch object identifier, and the monitoring batch identifier, so that the patch data formed for the same target patch on the same edge side in the same monitoring batch can be uniquely called. This includes patch package identifier, edge side identifier, target patch object identifier, monitoring batch identifier, boundary difference field, land type difference field, evidence attachment field, rollback anchor point field, and patch application status field. The boundary difference field is used to record the difference content of the target patch boundary data. The land type difference field is used to record the difference content of the land type code of the target patch. The evidence attachment field is used to record the attachment relationship of evidence data corresponding to the updated data of the target patch. The rollback anchor point field is used to record the result version association position before the change patch package is written. The patch application status field is used to record whether the change patch package is currently in an unapplied, suspended, or applied state.

[0023] In this embodiment S2, the rollback anchor point field consists of a base page identifier, a target patch object identifier, and a result version identifier. The base page identifier determines the land use benchmark result page corresponding to the changed patch package; the target patch object identifier determines the patch object corresponding to the changed patch package; and the result version identifier determines the result version position before the changed patch package is generated. When the system generates the changed patch package, the rollback anchor point field is written into the changed patch package, enabling the system to locate the benchmark result state corresponding to the patch package during subsequent patch application, result replay, or error rollback. The application status field includes unapplied, suspended, and applied statuses. When a change patch package is generated, the patch application status field is set to unapplied. When a change patch package is marked as a suspended patch package in S3, the patch application status field is set to suspended. When a change patch package is written to the cloud results patch library in S4, the patch application status field is set to applied. These status fields are not manually commented fields, but rather serve as the basis for subsequent access control, cloud patch suspension queue management, results replay index generation, and patch application record write-back.

[0024] In this embodiment S3, the target boundary segment identifier is read from the land use benchmark results page based on the target parcel object identifier in the changed parcel patch package. The boundary segment identifier to be written is determined based on the boundary difference field. The target boundary segment identifier and the boundary segment identifier to be written are matched to determine the shared boundary segment identifier. The adjacent parcel object identifier is determined based on the shared boundary segment identifier to form adjacent boundary data. The cloud boundary lock table records the shared boundary segment identifier, patch package identifier, target parcel object identifier, adjacent parcel object identifier, lock status field, and release status field. Based on the shared boundary segment identifier in the adjacent boundary data, the cloud boundary lock table is queried. When there is a record in the cloud boundary lock table that corresponds to the shared boundary segment identifier, has a lock status field that is locked, and a release status field that is not released, a boundary lock occupancy record is generated.

[0025] In this embodiment S3, the system determines adjacent boundary data based on the target parcel object identifier and boundary difference field in the changed parcel patch package. Specifically, the system first uses the target parcel object identifier as the query field to read the target boundary segment identifier corresponding to the target parcel object identifier in the land use benchmark results page; then, it reads the boundary segment identifier to be written from the boundary difference field of the changed parcel patch package. The boundary segment identifier to be written refers to the boundary segment identifier that this patch package is prepared to be written into the results library and may affect the original boundary relationship. The system performs segment matching between the target boundary segment identifier and the boundary segment identifier to be written to determine the shared boundary segment identifier involved in this writing. The shared boundary segment identifier refers to the boundary segment identifier jointly referenced by the target parcel and adjacent parcels. Based on the shared boundary segment identifier, the system queries other parcel object identifiers that have an in-page correspondence with the shared boundary segment identifier in the land use benchmark results page, and determines the other parcel object identifiers as adjacent parcel object identifiers.

[0026] In this embodiment S3, the cloud boundary lock table is used to record the occupancy status of shared boundary segments during the patch writing process. The cloud boundary lock table records at least the shared boundary segment identifier, patch package identifier, target polygon object identifier, adjacent polygon object identifier, lock status field, and release status field. The system queries the cloud boundary lock table based on the shared boundary segment identifier in the adjacent boundary data to generate a boundary lock query result. If there is a record in the cloud boundary lock table that corresponds to the shared boundary segment identifier and has a locked status field and an unreleased status field, it indicates that the shared boundary segment is being occupied by other changed polygon patch packages, and the system generates a boundary lock occupancy record. If there is no record in the cloud boundary lock table that corresponds to the shared boundary segment identifier and has a locked status field and an unreleased status field, the system marks the boundary lock query result as no boundary lock occupancy record generated.

[0027] In this embodiment S3, the adjacent boundary transaction lock includes a transaction lock identifier, a patch package identifier, a target polygon object identifier, an adjacent polygon object identifier, a shared boundary fragment identifier, a lock status field, and a release status field. When the boundary lock query result indicates that no boundary lock occupancy record has been generated, an adjacent boundary transaction lock is generated based on the patch package identifier of the changed polygon patch package, the target polygon object identifier, and the adjacent polygon object identifier and shared boundary fragment identifier in the adjacent boundary data. The lock status field of the adjacent boundary transaction lock is set to locked, the release status field is set to unreleased, the changed polygon patch package is marked as an admission patch package, and the transaction lock identifier is written into the boundary lock association field in the patch admission result. When the boundary lock query result indicates that a boundary lock occupancy record has been generated, no adjacent boundary transaction lock is generated, and the changed polygon patch package is marked as a suspended patch package. The patch admission result includes a patch package identifier, an admission mark field, a suspended mark field, and a boundary lock association field.

[0028] In this embodiment S3, the adjacent boundary transaction lock is a data lock object generated by the system based on the changed patch package and adjacent boundary data when no boundary lock occupancy record is generated. The adjacent boundary transaction lock includes a transaction lock identifier, a patch package identifier, a target patch object identifier, an adjacent patch object identifier, a shared boundary fragment identifier, a lock status field, and a release status field. The transaction lock identifier is used to mark the current boundary lock record, the patch package identifier is used to associate the changed patch package to be written, the target patch object identifier is used to record the target patch corresponding to the current patch package, the adjacent patch object identifier is used to record adjacent patches that have a shared boundary relationship with the target patch, the shared boundary fragment identifier is used to record the boundary fragment that is locked this time, the lock status field is used to record whether the shared boundary fragment is occupied by the current patch package, and the release status field is used to record whether the lock is released after the shared boundary fragment is written.

[0029] In this embodiment S3, write admission control refers to the process by which the system determines whether a changed patch package can enter the cloud-based results patch library writing process based on the boundary lock query result. When the boundary lock query result indicates that no boundary lock occupancy record has been generated, the system generates an adjacent boundary transaction lock, marks the changed patch package as an admission patch package, and writes the transaction lock identifier into the boundary lock association field in the patch admission result. When the boundary lock query result indicates that a boundary lock occupancy record has been generated, the system does not generate a new adjacent boundary transaction lock, marks the changed patch package as a suspended patch package, and the patch admission result includes a patch package identifier, an admission mark field, a suspended mark field, and a boundary lock association field. The admission mark field is used to record whether the changed patch package is marked as an admission patch package, the suspended mark field is used to record whether the changed patch package is marked as a suspended patch package, and the boundary lock association field is used to record the transaction lock identifier corresponding to the admission patch package.

[0030] In this embodiment S4, the cloud-based result patch library records the patch package identifier, base page identifier, target patch object identifier, monitoring batch identifier, rollback anchor point field, and patch application status field. After the admission patch package is written to the cloud-based result patch library, the patch application status field of the admission patch package is set to the applied state, and the corresponding adjacent boundary transaction lock is queried based on the patch package identifier, and the release status field of the adjacent boundary transaction lock is set to the released state. The result replay index uses the base page identifier of the land use benchmark result page as the replay starting point, the patch package identifier of the admission patch package as the replay object, the monitoring batch identifier as the patch application batch, and the rollback anchor point field as the rollback association position, and generates the patch application order field according to the order in which the admission patch packages are written to the cloud-based result patch library. The patch application record is generated based on the result replay index, and the patch application record includes the edge side identifier, patch package identifier, monitoring batch identifier, patch application status field, and replay status field. When the suspended patch package is written to the cloud-based patch suspension queue, the patch application status field of the suspended patch package remains in the suspended state.

[0031] In this embodiment S4, the cloud-based result patch library is used to store access patch packages written to the access control system, rather than directly replacing the parcel data in the land use benchmark result page. The cloud-based result patch library records the patch package identifier, benchmark page identifier, target parcel object identifier, monitoring batch identifier, rollback anchor point field, and patch application status field. After the system writes the access patch package to the cloud-based result patch library, it updates the patch application status field of the access patch package from unapplied to applied, and queries the corresponding adjacent boundary transaction lock based on the patch package identifier of the access patch package, setting the release status field of the adjacent boundary transaction lock to released. Through this process, the access control system... After a patch package is written, its corresponding shared boundary segment is no longer locked. Subsequent suspended patch packages involving the same shared boundary segment can re-enter the boundary lock query and write admission control process. For suspended patch packages that fail to pass the write admission control, the system writes them to the cloud patch suspension queue and keeps the patch application status field of the suspended patch package in a suspended state, so that the patch package will not be mistakenly used as an applied patch in the result replay index construction. The cloud patch suspension queue can collect suspended patch packages according to the monitoring batch identifier, shared boundary segment identifier, and patch package identifier, so that patch writing can continue after the corresponding adjacent boundary transaction lock is released.

[0032] In this embodiment S4, the result replay index is generated based on the land use benchmark result page and the access patch package. It is used to record the recovery path of the land use dynamic monitoring results from the benchmark result state to the patch application state. The system uses the benchmark page identifier of the land use benchmark result page as the replay starting point of the result replay index, the patch package identifier of the access patch package as the replay object, the monitoring batch identifier as the patch application batch, and the rollback anchor point field as the rollback association position. The system generates a patch application order field according to the order in which the access patch packages are written to the cloud result patch library. The replay status field is generated according to the patch application status field of the access patch package. When the access patch package is written to the cloud result patch library... When the patch application status field of the result replay index is in the applied state, the patch package is recorded as being in a replayable state. When the patch package of a changed feature is in a suspended state, the patch package of the changed feature does not enter the patch package identifier sequence of the corresponding result replay index. The patch application record is generated based on the result replay index. The patch application record includes the edge side identifier, patch package identifier, monitoring batch identifier, patch application status field, and replay status field. The system writes the patch application record back to the corresponding edge side based on the edge side identifier, so that the edge side can obtain the application status of its uploaded changed feature patch package in the cloud result patch library and maintain consistency with the patch application record in the cloud result patch library.

[0033] Example 2: The present invention proposes an intelligent processing system for dynamic land use monitoring data, which is applied to the intelligent processing method for dynamic land use monitoring data proposed in Example 1. It includes a memory, a processor, and a computer program stored in the memory and executable on the processor. The processor executes the computer program to implement the intelligent processing method for dynamic land use monitoring data in Example 1.

[0034] The embodiments of the present invention have been described in detail above with reference to the accompanying drawings. However, the present invention is not limited thereto. Various changes can be made within the scope of knowledge possessed by those skilled in the art without departing from the spirit of the present invention.

Claims

1. A method for intelligent processing of dynamic land use monitoring data, characterized in that, Includes the following steps: S1. Obtain multi-source data of dynamic land use monitoring, construct a land use benchmark result page based on the cloud benchmark result data in the multi-source data of dynamic land use monitoring, and establish the correspondence between the map object identifier, spatial index code, benchmark land type code, boundary segment identifier, benchmark boundary segment data and result version identifier in the land use benchmark result page; Among them, the multi-source data for dynamic land use monitoring includes cloud-based benchmark results data and edge-side change patch data; the land use benchmark results page includes benchmark page identifier, patch object identifier, spatial index code, benchmark land category code, boundary segment identifier, benchmark boundary segment data, and results version identifier; S2. Based on the edge-side change patch data, read the target patch update data, query the land use benchmark results page according to the target patch object identifier, read the target patch benchmark data, perform differential encapsulation processing on the target patch update data and the target patch benchmark data, generate a change patch patch package, and set the patch application status field of the change patch patch package to an unapplied status. The target patch update data includes edge side markers, target patch object markers, monitoring batch markers, patch change data, and evidence attachment data. Patch change data includes changed boundary data and changed land use code. The target patch baseline data includes baseline boundary segment data, baseline land use code, and result version marker. S3. Based on the target parcel object identifier and boundary difference field in the changed parcel patch package, query the land use benchmark results page to determine the adjacent boundary data corresponding to the target parcel object identifier; based on the adjacent boundary data, query the cloud boundary lock table to generate boundary lock query results; based on the boundary lock query results, perform write access control on the changed parcel patch package to generate patch access results; The adjacent boundary data includes adjacent patch object identifiers and shared boundary segment identifiers; the boundary lock query results include generated boundary lock occupancy records and non-generated boundary lock occupancy records. S4. Write the access patch package into the cloud results patch library, update the patch application status field of the access patch package, generate a results replay index based on the land use benchmark results page and the access patch package, set the release status field of the adjacent boundary transaction lock corresponding to the access patch package to the released status, write the suspended patch package into the cloud patch suspension queue, and write the patch application record back to the corresponding edge side based on the edge side identifier. The result replay index includes a base page identifier, patch package identifier, monitoring batch identifier, rollback anchor point field, patch application order field, and replay status field; patch application records are generated based on the result replay index.

2. The intelligent processing method for dynamic land use monitoring data according to claim 1, characterized in that: In S1, the cloud-based benchmark results data are collected according to spatial index codes to generate benchmark results data groups corresponding to spatial index codes. The land use benchmark results page is generated based on the benchmark results data set and configured with a benchmark page identifier corresponding to the spatial index code; The land use benchmark results page records the benchmark page identifier, spatial index code, administrative division code, and results page status field; the land use benchmark results page records the benchmark land type code, boundary segment identifier, benchmark boundary segment data, and results version identifier according to the map object identifier; and establishes intra-page correspondences between map object identifiers and boundary segment identifiers, between boundary segment identifiers and benchmark boundary segment data, between map object identifiers and benchmark land type codes, and between map object identifiers and results version identifiers.

3. The intelligent processing method for dynamic land use monitoring data according to claim 2, characterized in that: In step S2, the changed boundary data in the target patch update data is compared with the baseline boundary segment data in the target patch baseline data to generate a boundary difference field. The boundary difference field includes a boundary segment addition field, a boundary segment deletion field, a boundary segment replacement field, and a boundary segment retention field. The changed land use code in the target patch update data is compared with the baseline land use code in the target patch baseline data to generate a land use difference field. The land use difference field includes a baseline land use code field, a changed land use code field, and a land use difference status field. The evidence attachment data in the target patch update data is written into the evidence attachment field according to the edge side identifier, the target patch object identifier, and the monitoring batch identifier. The boundary difference field, the land use difference field, and the evidence attachment field are written under the same patch package identifier to form the differential encapsulation content of the changed patch patch package.

4. The intelligent processing method for dynamic land use monitoring data according to claim 3, characterized in that: In S2, the changed patch package uses the patch package identifier as the primary key of the package index, the target patch object identifier as the result update object, the monitoring batch identifier as the patch application batch, and the edge side identifier as the patch write-back object; the patch package identifier is generated based on the edge side identifier, the target patch object identifier, and the monitoring batch identifier; the rollback anchor point field consists of the base page identifier, the target patch object identifier, and the result version identifier; the patch application status field includes unapplied status, suspended status, and applied status; when the changed patch package is generated, the patch application status field is set to unapplied status; when it is marked as a suspended patch package, the patch application status field is set to suspended status; and when it is written to the cloud result patch library, the patch application status field is set to applied status.

5. The intelligent processing method for dynamic land use monitoring data according to claim 4, characterized in that: In step S3, the target boundary segment identifier is read from the land use benchmark results page based on the target parcel object identifier in the changed parcel patch package. The boundary segment identifier to be written is determined based on the boundary difference field. The target boundary segment identifier and the boundary segment identifier to be written are matched to determine the shared boundary segment identifier. The adjacent parcel object identifier is determined based on the shared boundary segment identifier to form adjacent boundary data. The cloud boundary lock table records the shared boundary segment identifier, patch package identifier, target parcel object identifier, adjacent parcel object identifier, lock status field, and release status field. Based on the shared boundary segment identifier in the adjacent boundary data, the cloud boundary lock table is queried. If there is a record in the cloud boundary lock table that corresponds to the shared boundary segment identifier, has a locked status field, and an unreleased status field, a boundary lock occupancy record is generated. If there is no record in the cloud boundary lock table that corresponds to the shared boundary segment identifier, has a locked status field, and an unreleased status field, the boundary lock query result is marked as no boundary lock occupancy record is generated.

6. The intelligent processing method for dynamic land use monitoring data according to claim 5, characterized in that: In step S3, the adjacent boundary transaction lock includes a transaction lock identifier, a patch package identifier, a target polygon object identifier, an adjacent polygon object identifier, a shared boundary fragment identifier, a lock status field, and a release status field. When the boundary lock query result indicates that no boundary lock occupancy record has been generated, an adjacent boundary transaction lock is generated based on the patch package identifier of the changed polygon patch package, the target polygon object identifier, and the adjacent polygon object identifier and shared boundary fragment identifier in the adjacent boundary data. The lock status field of the adjacent boundary transaction lock is set to locked, the release status field is set to not released, the changed polygon patch package is marked as an admission patch package, and the transaction lock identifier is written into the boundary lock association field in the patch admission result. When the boundary lock query result indicates that a boundary lock occupancy record has been generated, no adjacent boundary transaction lock is generated, and the changed polygon patch package is marked as a suspended patch package. The patch admission result includes a patch package identifier, an admission mark field, a suspended mark field, and a boundary lock association field.

7. The intelligent processing method for dynamic land use monitoring data according to claim 6, characterized in that: In S4, the cloud-based results patch library records the patch package identifier, the base page identifier, the target patch object identifier, the monitoring batch identifier, the rollback anchor point field, and the patch application status field. After the admission patch package is written into the cloud-based results patch library, the patch application status field of the admission patch package is set to the applied status, and the corresponding adjacent boundary transaction lock is queried based on the patch package identifier, and the release status field of the adjacent boundary transaction lock is set to the released status. The result replay index uses the base page identifier of the land use benchmark result page as the replay starting point, the patch package identifier of the access patch package as the replay object, the monitoring batch identifier as the patch application batch, and the rollback anchor point field as the rollback association position. The patch application order field is generated according to the order in which the access patch packages are written to the cloud result patch library. The patch application record is generated based on the result replay index. The patch application record includes the edge side identifier, patch package identifier, monitoring batch identifier, patch application status field, and replay status field. When a suspended patch package is written to the cloud patch suspension queue, the patch application status field of the suspended patch package remains in the suspended state.

8. A computer program that is in the processor and can run on the processor, characterized in that: The processor executes a computer program to implement the intelligent processing method for dynamic monitoring data of land use as described in any one of claims 1-7.

Images