Forest grass comprehensive monitoring evaluation polygon monitoring update method, system and cloud platform
The system and cloud platform address inefficiencies in forest and grass monitoring by synchronizing quality inspection rules, ensuring secure and efficient centralized inspections, and accurate progress quantification, improving user experience and inspection quality.
Patent Information
- Application Number
- JP2024508637
- Authority / Receiving Office
- JP · JP
- Patent Type
- Patents
- Current Assignee / Owner
- Priority Date
- 2021-08-25
- Filing Date
- 2022-07-26
- Publication Date
- 2024-11-22
- Estimated Expiration
- 2042-07-26
AI Technical Summary
The current method for forest and grass comprehensive monitoring evaluation polygon monitoring update is inefficient, with poor quality inspection timeliness, duplicate inspections, and difficulty in updating quality inspection rules, leading to low user experience and potential data tampering, along with inaccurate progress quantification.
A system and cloud platform that enables provincial and prefectural level users to synchronize quality inspection logic rules, perform centralized inspections, and utilize encryption for secure data transmission, allowing real-time updates and accurate progress quantification.
Enhances inspection efficiency, security, and user experience by enabling real-time updates of quality inspection rules, reducing repetitive tasks, and providing accurate progress quantification through centralized inspections and encryption.
Smart Images

Figure 0007588758000001 
Figure 0007588758000002 
Figure 0007588758000003
Abstract
Description
[Technical field]
[0001] The present invention belongs to the technical field of geospatial data calculation, identification and processing, and particularly relates to a method, system and cloud platform for comprehensive forestry monitoring and evaluation polygon monitoring and updating. [Background technology]
[0002] The forest and grass comprehensive monitoring evaluation polygon monitoring and updating is based on the previous forest resource management "one map", uses remote sensing to interpret the database, and uses file checking or on-site checking methods to investigate the changes in land type, forest stand and their management attributes due to forest land used by construction projects during the year, forest land reclaimed, and forest management activities such as afforestation, logging, etc., to timely grasp the current status of forest resource protection and utilization and its fluctuations, and comprehensively grasp the situation of illegal destruction of forest resources. Forest supervision work is an important part of the forest and grass comprehensive monitoring evaluation polygon monitoring and updating.
[0003] The results of the forestry grass comprehensive monitoring evaluation polygon monitoring update are all geospatial databases, and because the amount of calculation and storage of geospatial data is large, the county level uses custom GIS desktop software with independent deployment of C / S architecture to complete spatial editing, attribute quality inspection, topological analysis and geospatial processing for county-level data. The same custom GIS desktop software is also used for provincial-level inspection, and the results submitted by the county level are imported again to repeat the inspection steps, and the failed results are repeatedly inspected until they pass, and finally the province-wide forest resources "one map" result is formed. The current working method mainly has the following disadvantages:
[0004] Difficult to update quality inspection rules. When creating quality inspection logic rules for forest resources "One Map" result data inspection, the package is compiled in advance and configured in the desktop GIS management package. If the quality inspection logic rules need to be modified, provincial users need to recompile and package the desktop GIS management software, and county users need to reinstall the desktop GIS management software. In the early stages of work, due to limited test data, users need to frequently adjust and modify the quality inspection logic rules. Therefore, not only do provincial users need to frequently compile packages, but county users also need to download and reinstall the software, making it difficult to modify the quality inspection logic rules and reducing the efficiency of updates.
[0005] Poor timeliness of quality inspection and user experience. Provincial-level users must wait until the county-level unit completes all work and submits the results before inspecting the data. If an error is found, the county-level unit must be instructed to correct it and then re-inspect. In addition, because the results are composed of multiple product databases and inspection modules, early errors require the entire work to be restarted. Because all data must be submitted face-to-face and the inspection process takes a long time, users must wait a long time for the inspection results, which results in a poor user experience.
[0006] Quality inspection is duplicated, inefficient, and poor quality. Provincial users need to carry out the inspection work of database creation for the data submitted by each county individually. When there are more counties or the amount of data is large, the work stress of the provincial level is large. In addition, when the county level thinks that all the inspections have been completed and passed, the provincial level does not trust the results submitted by the county level from the perspective of inspection, and still needs to repeat the entire inspection process, which results in duplication of work and inefficiency. In addition, due to the concentration of inspection time and large workload, the provincial level inspection mainly focuses on the basic data normative inspection part such as data space topology inspection and attribute logic inspection, and follows the logic rules, but the inspection for mutations and abnormal changes that do not meet the actual requirements of the work is weak. In addition, only after the data of each district and county is inspected, the data of the whole province can be aggregated, and the changes in the resource data of the whole province can be statistically analyzed, so the overall change at the provincial level is easy to occur and the inspection quality is poor.
[0007] The protection measures for data transmission are weak and prone to tampering attacks. If county-level units export data that has already passed inspection in their custom GIS desktop software to report to the provincial level, they may use other external GIS software, such as ArcGIS or QGIS, to maliciously modify the previous fields, land type and other fields of the forest resource change database to conceal the fact of changes, which is difficult to detect during the provincial-level inspection process and may result in the concealment of illegal incidents of destroying forest resources.
[0008] In addition, it is difficult to quantify the progress. The current work stages are divided into seven stages according to the administrative management method: whether training has been completed, file data collection and processing, forest supervision and inspection confirmation, "one map" confirmation, comprehensive database creation, "one map" update, and report preparation. Each work stage contains multiple actual tasks, and the progress entry criteria are arbitrary, making it difficult to quantify the work boundaries and progress. Secondly, the progress is not true, and the progress entry is filled in by the districts and counties themselves, and it is difficult to determine whether it is consistent with the actual work. Therefore, it is often the case that the progress statistics should be promoted by the whole province, but the actual submitted results are slow to produce results, and the actual progress is seriously inconsistent with the reported results. Thirdly, a dedicated person should be responsible for filling out the report, and personnel including progress urging, county-level entry, and provincial-level statistics should maintain the work of progress management.
[0009] In conclusion, it is urgent to provide a forestry and grass comprehensive monitoring evaluation polygon monitoring update method, system and cloud platform that can ensure timely and efficient quality inspection work in the forestry and grass comprehensive monitoring evaluation polygon monitoring update work, good user experience, safe and fast update quality inspection rules, accurate quantification of progress boundaries in progress update, truthful progress and one-touch reporting, and a transparent and smooth update process of provincial and county two-level forestry and grass comprehensive monitoring evaluation polygon monitoring. Summary of the Invention [Problem to be solved by the invention]
[0010] The present invention aims to provide a forestry grass comprehensive monitoring evaluation polygon monitoring update method, system and cloud platform which ensure that the quality inspection work in the forestry grass comprehensive monitoring evaluation polygon monitoring update work is timely and efficient, the user experience is good, the quality inspection rules are updated safely and quickly, the progress boundary is accurately quantified in the progress update, the progress is true and one-touch reporting is realized, and the update process of the provincial and county two-level forestry grass comprehensive monitoring evaluation polygon monitoring is transparent and smooth.
[0011] The above objectives are achieved by the following technical solutions:
[0012] Forest grass comprehensive monitoring evaluation, Sujimura monitoring update method, The following steps are specifically: (1) creating a provincial-level aggregated database, a provincial-level progress log database, and a provincial-level quality inspection logic rule database, the provincial-level aggregated database including at least an administrative division database, a forestry supervision database, a forestry resource status database, a forestry resource change database, and a forestry resource file database; (2) accessing the provincial-level quality inspection logic rules database, completing the addition, deletion and update, and saving the system time and user name of the operation; (3) a county-level user creates an application and imports data, and locally creates a county-level result database, a county-level progress log database, and a county-level quality inspection logic rule database, where the county-level result database at least includes an administrative division database, a forestry supervision database, a forest resources change database, a forest resources status database, and a forest resources file database; (4) the county-level user records the application creation and data import execution results in the county-level progress log database, and then aggregates the results into the provincial-level progress log database; and (5) The county-level user accesses the provincial-level quality inspection logic rule database, reads the modification time of the provincial-level quality inspection logic rule database, and compares it with the modification time of the locally stored quality inspection logic rule database. If there is no match, download the provincial-level quality inspection logic rule database to update the locally stored quality inspection logic rule database; if there is a match, proceed to step (6); (6) the county-level user executes the quality inspection rules of the county-level quality inspection logic rule database in the inspection of the administrative division database, the forest supervision database, the forest resource change database and the forest resource file database, and returns and displays the inspection result; (7) the county-level system records the administrative division database, the forest supervision database, the forest resource change database and the forest resource file database, and submits the data to the provincial-level progress log database; and (8) the county-level users submit the county-level performance database to be consolidated into the provincial-level aggregated database; and (9) the provincial-level user performs inspection and statistics on the provincial-level aggregated database to determine whether the county-level results are acceptable; if not, return to step (6); if yes, proceed to step (10); (10) The county-level user exports the result database and packages it into a compressed file, and sets the decompression password as a unified password built into the system; and the provincial-level user decompresses the result file using the unified password built into the system to receive the result submitted by the county-level user.
[0013] Further technical measures include: the provincial-level aggregated database is consistent with the database logical structure of the prefecture-level performance database; Among them, the logical structure of the administrative division database includes OBJECTID, shape, province, county, township, village, bureau, site, work area, and forest section. The logical structure of the forest supervision database includes the following: OBJECET ID, shape, interpreted change polygon number, supplementary polygon number, province, county, township, village, forestry bureau, forest farm, forest section, abscissa, ordinate, interpreted polygon area, interpreted change cause, confirmation subsection number, forest resource change base polygon, forest land management unit, change cause, change period, project name, project use, inspection document number, inspection year, inspection area, actual change in forest land use area, nature reserve area in actual change in forest land use area, nature reserve name, nature reserve level and type, previous forest resource management "one map" land type, pre-certification land type, third Includes forest area under the 2016 National Land Survey, forest category from the previous forest resource management "One Map", real estate grade from the previous forest resource management "One Map", national public interest forest grade from the previous forest resource management "One Map", nature of forest land in use, origin from the previous forest resource management "One Map", status of issuance of forest tree felling licenses, forest tree felling license number, actual felling area, actual felling stock, actual number of felled plants, felling area exceeding license, felling stock exceeding license, number of felled plants exceeding license, felling area exceeding license, felling stock without license, number of felled plants without license, remarks, survey level, survey unit, surveyor, current land type, The logical structure of the forest resources status database is: OBJECETID, shape, prefecture, township, village, bureau, field, work area, forest section, sub-section, sub-sub-section, small land name, forest land ownership, forest land use right, forest tree ownership, forest tree use right, right holder name, forest rights certificate number, land type, land use status land type, land management type, vegetation cover type, forest tree type, area, origin, forest category, real rights grade, natural forest protection area public interest forest or not, national public interest forest grade, project category, ecological area, area to which it belongs, area name, area description, natural degree, community structure, regeneration grade, health grade, harmful organisms, disaster type, damage level. , degradation type, degradation degree, wetland type, location type, location grade, afforestation type, management type, management opinion, terrain, terrain location, aspect, gradient location, gradient, altitude, accessibility, soil, soil layer thickness, humus thickness, texture, matrix, gravel content, soil structure, soil moisture, PH, compactness, drainage condition, erosion condition, dominant tree species, tree species composition, closure degree, age, age group, average breast diameter, average tree height, hectare accumulation, number of plants per hectare, tree species structure, forest land quality grade, whether it is supplementary forest land, forest land protection grade, forest land function partition, main function area, The logical structure of the forest resource change database is OBJECETID, shape, QQ _ OBJECTID, XZ _ OBJECTID, DC _ OBJECTID, province, prefecture, township, village, bureau, field, work area, forest section, Q _ sub-section, Q _ land type, Q _ forest land ownership, Q _ forest land use right, Q _ origin, Q _ forest species, Q _ dominant tree species, Q _ age group, Q _ density, Q _ number of plants per hectare, Q _ hectare accumulation, Q _ forest category, Q _ public forest right, Q _ public forest grade, Q _ forest land protection grade, Q _ land management type, XZ _ sub-section, XZ _ land type, XZ _ forest land ownership, XZ _ forest land use right, XZ _ origin, XZ _ forest species, XZ _ dominant tree species, XZ _ age group, XZ _ density, XZ _ number of plants per hectare, XZ _ hectare accumulation, XZ _ forest category, XZ _ public forest rights, XZ _ public forest grade, XZ _ forest land protection grade, XZ _ land management type, DC _ interpretation polygon number, DC _ supplementary polygon number, DC _ interpretation change cause, DC _ current land type, DC _ change cause, DC _ previous land type, DC _ certified previous land type, DC _ previous origin, DC _ previous forest category, DC _ previous rights grade, DC _ previous public forest grade, DC _ forest land used characteristics, DC _ license issuance status, change area, change cause, change time, change basis, change notes, where OBJECTID represents a unique identifier of the object and shape represents a shape.
[0014] Further technical measures include: the provincial-level progress log database structure created in step (1) includes ID, county code, log project name, quality inspection result, inspection number, error number, log time, and report time; Among these, ID is a self-incrementing item created each time a quality inspection log is submitted. The prefecture code is a six-digit code that is implemented as a national uniform administrative code. The log project name refers to the progress name of the forest and grass comprehensive monitoring evaluation polygon monitoring update. The log project name here is divided into seven progresses: application creation and data import, administrative district database inspection, forestry supervision database inspection, forest resource status database inspection, forest resource change database inspection, result summary report and result export report. The quality inspection result is either pass or fail. The number of inspections is the statistically calculated number of inspection polygons. The number of errors is the statistically calculated number of error polygons. The log time is the execution time of the log project.
[0015] Further technical means is, the provincial-level quality inspection logic rule database logic structure created in step (1) includes: quality inspection number, quality inspection type, logic type, logic rule name, logic rule condition, logic rule presentation, modification time, and modification user; Among them, the quality inspection number is the only mark in the provincial-level quality inspection logic rule database; The quality inspection type is the name of the quality inspection project, and the quality inspection project updates the work content through the forest and grass comprehensive monitoring evaluation polygon monitoring, including but not limited to administrative district database quality inspection type, forest supervision and inspection database quality inspection type, forest resource status database quality inspection type, and forest resource change database quality inspection type; The logic type is the match of the quality inspection logic rules of the quality inspection project. It is divided into graphic quality inspection logic type and attribute quality inspection logic type. A logic rule is the smallest unit in the provincial-level quality inspection logic rule database, and is a specific quality inspection entry to be executed. It is composed of a logic rule name, a logic rule condition, and a logic rule suggestion. The logic rule name is a description of the logic rule execution content, the logic rule condition is the content of the logic rule execution, and the logic rule suggestion is the suggestion content displayed when the logic execution is an error. The modification time is the time when the provincial-level quality inspection logic rule database was last modified and stored; The modifying user is the user who last modified and saved the provincial-level quality inspection logic rule database.
[0016] Further technical measures include, in step (3), after the county-level user forms the administrative division database, the forest supervision database, the forest resource change database and the forest resource file database, performing self-checking on the databases to ensure that there are no spatial topology errors or attribute logic errors locally. In order to achieve the above object, the present invention provides a method for implementing any one of the above forest grass comprehensive monitoring evaluation polygon monitoring update methods, comprising a county-level user-side application system and a provincial-level server-side application system, The application system on the county-level user side is: An application creation and data import module is used for county-level users to import local data according to their requirements and create county-level forest resources annual update project files, including but not limited to forest resources pre-term database, administrative division database, forest resources status database, forestry supervision database, and forest resources file database; a quality inspection logic rule database comparison module, which is used for a county-level user to locally create a quality inspection logic rule database, access the provincial-level quality inspection logic rule database to make a comparison against the modification time, and determine the consistency between the locally stored quality inspection logic rule database and the provincial-level quality inspection logic rule database; a quality inspection logic rule database updating module, which is used to update the content of the provincial-level quality inspection database into the locally stored quality inspection logic rule database so as to make them consistent when a county-level user finds that the locally stored quality inspection logic rule database and the provincial-level quality inspection logic rule database are not consistent; an administrative division database inspection module, which is used to perform a spatial topology inspection and an attribute logic inspection on the administrative division database edited and imported by a user; in which the spatial topology inspection includes overlapping and gaps, and the attribute logic inspection includes dictionary inspection, required item and non-required item inspection, and factor logic relationship inspection; a forestry supervision database inspection module, which is used to perform a spatial topology inspection and an attribute logic inspection on the forestry supervision database edited and imported by a user; in which the spatial topology inspection includes duplication and multiple components, and the attribute logic inspection includes dictionary inspection, required item and non-required item inspection, and factor logic relationship inspection; A forest resource current status database inspection module is used by users to perform spatial topology inspection and attribute logic inspection on the forest resource current status database completed this term, in which the spatial topology inspection includes overlap, gap, open area, multiple parts, fragmentation, super boundary, and forest compartment boundary crossing inspection, and the attribute logic inspection includes dictionary domain inspection, partition factor inspection, basic factor inspection, management factor inspection, forest ecology inspection, topography and soil factor inspection, and forest stand factor inspection; a forest resource change database generating module, which is used by a user to generate a forest resource change database according to the forest supervision database, the forest resource pre-period data, and the forest resource current status data; A forest resource change database inspection module is used by users to perform attribute logic inspection on the forest resource change database, including forest supervision factor inspection, change cause inspection, and abnormal change inspection; A result reporting module is used by users to report and consolidate the administrative division database, forest supervision database, forest resource change database and forest resource file database in the local county-level forest resource annual update application through the Internet to enter the administrative division database, forest supervision database, forest resource change database and forest resource file database in the provincial-level aggregated database; A result export module is used for allowing users to export the administrative division database, forest supervision database, forest resource status database, forest resource change database and forest resource file database in the local county-level forest resource annual update application, and then package them into a compressed file and set a compressed file password; A progress log background generation and reporting module is used to record the execution status and execution results of the current module in the local progress log database, access the provincial progress log database, and update the aggregated records of the local progress log database to the provincial progress log database after executing the application creation and data import module, the file database logic inspection module, the administrative division database inspection module, the forestry supervision database inspection module, the forest resources status database inspection module, the forest resources change database inspection module, or the result export module; Provincial-level server-side application system includes: A provincial-level quality inspection logic rule database creation module is used for a provincial-level user to provide a provincial-level quality inspection logic rule database creation function, and to set provincial-level and county-level access groups or users of the provincial-level quality inspection logic rule database and grant use rights to each access group and user; A provincial-level quality inspection logic rule database maintenance module is used to allow provincial-level users to complete operations such as adding, deleting, updating and so on the provincial-level quality inspection logic rule database and save the modified contents, and at the same time, this module uses encryption technology to provide encryption protection for the provincial-level quality inspection logic rule database to prevent malicious tampering; a provincial-level aggregated database creation module used for a provincial-level user to provide a provincial-level aggregated database creation function, set provincial-level and prefecture-level access groups or users of the provincial-level aggregated database, and grant usage rights to each access group and user; a provincial-level aggregate database aggregation module, which is used to make judgments on the data reporting applications submitted by the county level, check whether the performance data of the application unit already exists in the provincial-level aggregate database, and if so, delete and then insert the aggregate, while if not, directly insert the aggregate; A provincial-level aggregated database inspection module is used to provide provincial-level users with administrative division database, forest supervision database, forest resource change database, and forest resource file database inspection functions; A provincial-level aggregated database comparative analysis module provides provincial-level users with the function of comparative statistical analysis of forest resource change databases, and is used by county-level units to collect statistics on the change areas of factors including land type, right ownership, origin, forest category, real right grade, public interest forest grade, and forest land grade before and after the change; a provincial-level progress log database creation module, which is used by a provincial-level user to create a provincial-level progress log database and store all log information in the county-level forest and grass comprehensive monitoring evaluation polygon monitoring update; a provincial-level progress aggregation module used by a provincial-level user to receive data aggregation requests from county-level users and automatically perform appropriate updates and aggregations; A provincial-level progress query statistics module is used for displaying the progress of each county level unit by provincial-level users, displaying the quality inspection log results by project according to the name of the logged project, intuitively displaying the quality inspection and progress status of each county level unit, providing an aggregate display for the unit progress of the whole province and city / state, respectively stating whether each county's logged projects are all passed or not, and if all of them are passed, it is determined that the county-level result is complete, and if only one is passed, it is determined that the result is not complete, thereby stating the work progress status within the whole province; a provincial-level progress export module used for provincial-level users to export progress status according to need; and a forest resource "one map" result receiving module, which is used by a provincial-level user to verify the identity of a county-level user, and obtain a compressed file decompression password based on the county code of the result submitted by the user and the unified password built into the system, so as to decompress the result submitted by the county-level user.
[0017] In order to achieve the above object, the present invention provides the above forest grass comprehensive monitoring evaluation polygon monitoring update system, which is as follows: A forest grass comprehensive monitoring evaluation polygon monitoring update device is installed in the county-level user side application system; A forest grass comprehensive monitoring evaluation polygon monitoring update application system is deployed in the provincial-level server-side application system; and a base cloud platform used by the county-level user-side application system and the provincial-level server-side application system to provide computing, storage, network communication and system operation capacity support. Effect of the Invention
[0018] Compared with the prior art, the present invention has the following advantages:
[0019] 1. Quality inspection rules can be updated quickly and results can be reported safely. When provincial-level users update the provincial-level quality inspection logic rule database, users can find changes in the quality inspection logic rules through synchronous comparison, and provincial-level users can use the real-time update method to replace the previous centralized collective update method, thereby improving the timeliness of the overall update. Through dynamic updates, provincial-level users do not need to repeatedly recompile package software, and county-level users do not need to repeatedly install software, reducing the repetition of work. Provincial-level users do not need to worry about the work stress of updating the entire provincial and county-level 2-level software due to the frequent updates of the provincial-level quality inspection logic rule database, and can focus more on sorting and revising the quality inspection logic rules. County-level users also do not need to be concerned about software version updates, and do not need to worry about the results being rejected due to the wrong software version. Through encryption technology, the provincial- and county-level 2-level quality inspection logic rule database is protected, preventing the quality inspection logic rule from being maliciously attacked, and enhancing the security of quality inspection work. The forest resource "One Map" result folder reported at the provincial level is compressed, and the folder name is encrypted using a unified password built into the system to obtain the decompression password, which can only be known to provincial-level users. This can prevent county-level users from using other GIS software to maliciously tamper with the data after exporting the forest resource "One Map" result data, and effectively enhance the safety protection capability of reporting the forest resource "One Map" result data.
[0020] 2. The quality inspection work is efficient, smooth, and has a good user experience. The quality inspection work is changed from result inspection to process inspection, and the timeliness is greatly improved. The present invention changes the way that the original county level completes all submissions and then the provincial level unit starts the centralized inspection, and submits and inspects according to the data processing process, and the county level submits at any time, and the provincial level inspects at any time collectively, and the inspection work is carried out step by step according to the workflow process, and the work of the previous step is ensured to be correct before the next step is carried out, and errors are corrected in the nascent state, so that the repeated operation of the county level and the provincial level inspection are avoided, and the timeliness is greatly improved. The individual distributed inspection is changed to a centralized unified inspection, and the inspection efficiency is greatly improved. The present invention changes the original provincial level process of reusing the desktop GIS software to import the results of each county level and then inspecting them one by one, and consolidates the results of the county level into a provincial level aggregated database, and the provincial level centrally inspects the results of the whole province on a "single map", so that the inspection of the whole province can be completed with just one inspection, and the inspection efficiency is greatly improved. The change from newspaper submission to Internet reporting has greatly improved the user experience. The present invention has changed the way that the original county-level units had to submit data face-to-face, and can enter the provincial-level aggregated database simply by reporting through the local network. In addition to improving the inspection efficiency, it can also be reported and inspected immediately, greatly improving the user experience. The change from local inspection to global inspection has greatly improved the inspection quality. The present invention only focuses on the basic data normative inspection part such as data space topology inspection and attribute logic inspection in the original inspection work, and based on the real-time provincial-level aggregated database, analyzes the change situation and change rules of the forest resources of the whole province from an overall and global perspective, and takes the forest resource change database as a clue, and focuses on inspection of mutations and abnormal changes that are in line with the data inspection rules on the surface but do not meet the actual work requirements, greatly improving the height and depth of the inspection work and further improving the inspection quality. The change from full submission to key part submission has greatly reduced the stress on system storage and network.In the present invention, the quantity of elements in the county-level forest resource status database and forest resource change database is generally 100,000-400,000, and the data storage amount is 1GB-3GB, so when the forest resource status database and forest resource change database are simultaneously submitted for provincial-level aggregation, the requirements for data storage and network load at the county and provincial levels are very high, and submitting all the forest resource status databases will cause data security problems.By changing all the submissions, the present invention requires users to submit the changed part of the forest resource change database (the change cause is not 0) and not submit the unchanged part of the forest resource status database and forest resource change database (the change cause is 0), so that only the change part is inspected to control the change situation of the whole county, and greatly reduces the data storage and network transmission stress during system inspection.
[0021] 3. The progress boundary is accurate and quantified, and the progress can be reported truthfully and unattended. First, the work progress can be accurately quantified, and the work progress can be determined based on the execution status of the device module, the boundaries of each work are clear, the progress entry criteria are unified, and the work progress can be accurately quantified. Second, the progress is true, and the progress entry is determined by the log record of the module execution, and is entered by non-county users, without subjectivity, and truly reflects the actual work situation, and the reported progress and the actual progress are consistent. Third, the automatic real-time transmission, the transmission work can be automatically recorded and transmitted in real time at the same time as the user develops the work, and each level does not need personnel to maintain and manage the progress, greatly improving efficiency. [Brief description of the drawings]
[0022] The accompanying drawings, which form a part of the present invention, are used to provide a further understanding of the present invention, and the exemplary embodiments of the present invention and the description thereof are used to explain the present invention without construing an undue limitation thereon. [Figure 1]2 is a flowchart illustrating an implementation of a polygon monitoring and updating method for evaluating forest grass comprehensive monitoring according to an embodiment of the present invention; [Diagram 2] FIG. 2 is a functional configuration diagram of a prefecture-level user-side application system according to an embodiment of the present invention. [Diagram 3] 2 is a functional configuration diagram of a provincial-level server-side application system according to one embodiment of the present invention; [Figure 4] 1 is an execution flowchart of each module of a forest grass comprehensive monitoring evaluation polygon monitoring update system according to one embodiment of the present invention; [Diagram 5] FIG. 2 is a structural block diagram of a forest grass comprehensive monitoring evaluation polygon monitoring update cloud platform according to one embodiment of the present invention; DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS
[0023] The present invention will be described in detail below with reference to the accompanying drawings, but the description in this part is merely illustrative and interpretive and does not limit the scope of protection of the present invention. Furthermore, a person skilled in the art can combine the features in the embodiments and different embodiments of the present specification based on the description in the specification.
[0024] In an embodiment of the present invention, referring to FIG. 1, the forest grass comprehensive monitoring evaluation polygon monitoring update method, as shown in FIG. 1, includes the following steps:
[0025] 1. Create a provincial-level aggregate database, a provincial-level progress log database, and a provincial-level quality inspection logic rule database, set access users and permissions, and create the provincial-level quality inspection logic rule database by the provincial-level administrator, set provincial-level and county-level access groups or users for the provincial-level quality inspection logic rule database, and grant the use permissions of each access group and user; The provincial-level aggregated database includes, but is not limited to, administrative division database, forestry supervision database, forest resources status database, and forest resources change database, and its database logical structure is completely consistent with the name and database logical structure of the county-level outcome database; Among them, the logical structure of the administrative division database is (OBJECTID, shape, province, county, township, village, bureau, site, work area, forest division (Compartment)). The logical structure of the forest supervision database is (OBJECETID, shape, interpreted change polygon number, supplementary polygon number, province, county, township, village, forestry bureau, forest farm, forest section, abscissa, ordinate, interpreted polygon area, interpreted change cause, confirmed subplot number, forest resource change base polygon, forest land management unit, change cause, change period, project name, project use, inspection document number, inspection year, inspection area, actual change in forest land use area, nature reserve area in actual change in forest land use area, nature reserve name, nature reserve level and type, previous forest resource management "one map" land type, previous certification area type, forest area during the third national land survey, forest category from the previous forest resource management "One Map", real estate grade from the previous forest resource management "One Map", national public interest forest grade from the previous forest resource management "One Map", nature of forest land in use, origin from the previous forest resource management "One Map", status of issuance of forest tree felling license, forest tree felling license number, actual felling area, actual felling stock, actual number of felled plants, felling area exceeding license, felling stock exceeding license, number of felled plants exceeding license, felling area exceeding license, felling stock without license, number of felled plants without license, remarks, survey level, survey unit, surveyor, current area type), The logical structure of the forest resources status database is (OBJECETID, shape, prefecture, township, village, bureau, field, work area, forest section, subcompartment, subdivision, small land name, forest land ownership, forest land use right, forest tree ownership, forest tree use right, right holder name, forest right certificate number, land type, land use status land type, land management type, vegetation cover type, forest tree type, area, origin, forest category, real right grade, natural forest protection area public forest or not, national public forest grade, project category, ecological area, area to which it belongs, area name, area description, naturalness, community structure, regeneration grade, health grade, harmful organisms, disaster Damage type, damage level, degradation type, degradation level, wetland type, location type, location grade, afforestation type, management type, management opinion, terrain, terrain location, aspect, gradient location, gradient, altitude, accessibility, soil, soil layer thickness, humus thickness, texture, matrix, gravel content, soil structure, soil moisture, pH, compactness, drainage condition, erosion condition, dominant tree species, tree species composition, degree of closure, age, age group, average breast diameter, average tree height, hectare accumulation, number of plants per hectare, tree species structure, forest land quality grade, whether it is supplementary forest land, forest land protection grade, forest land function partition, main function area). The logical structure of the forest resource change database is (OBJECETID, shape, QQ _ OBJECTID, XZ _ OBJECTID, DC _ OBJECTID, province, prefecture, township, village, bureau, field, work area, forest section, Q _ sub-section, Q _ land type, Q _ forest land ownership, Q _ forest land use right, Q _ origin, Q _ forest species, Q _ dominant tree species, Q _ age group, Q _ density, Q _ number of plants per hectare, Q _ hectare accumulation, Q _ forest category, Q _ public interest forest right, Q _ public interest forest grade, Q _ forest land protection grade, Q _ land management type, XZ _ sub-section, XZ _ land type, XZ _ forest land ownership, XZ _ forest land use right, XZ _ origin, XZ _ forest species, XZ _ dominant tree species, XZ _ age group, XZ _density, XZ _number of plants per hectare, XZ _hectare accumulation, XZ _forest category, XZ _public forest right, XZ _public forest grade, XZ _forestland protection grade, XZ _land management type, DC _interpretation polygon number, DC _supplementary polygon number, DC _interpretation change cause, DC _current land type, DC _change cause, DC _previous land type, DC _certified previous land type, DC _previous origin, DC _previous forest category, DC _previous right grade, DC _previous public forest grade, DC _nature of forest land used, DC _license issuance status, change area, change cause, change time, change basis, change notes), In this, OBJECTID represents a unique identifier for an object, shape represents a shape, The provincial-level progress log database structure is (ID, prefecture code, log project name, quality inspection result, number of inspections, number of errors, log time, transmission time), In this, ID is a self-incrementing item generated for each submission of a quality inspection log, The prefecture code is a six-digit code and is implemented as a national uniform administrative code. The log project name refers to the progress name of the forest and grass comprehensive monitoring evaluation polygon monitoring update. The log project name here is divided into seven progresses: application creation and data import, administrative district database inspection, forestry supervision database inspection, forest resource status database inspection, forest resource change database inspection, result summary report and result export report. The quality inspection result is either pass or fail. The number of inspections is the statistically calculated number of inspection polygons. The number of errors is the statistically calculated number of error polygons. Log time is the execution time of this log project, The logical structure of the provincial-level quality inspection logical rule database is (quality inspection number, quality inspection type, logical type, logical rule name, logical rule condition, logical rule suggestion, time correction, user correction). Among them, the quality inspection number is the only symbol in the provincial-level quality inspection logic rule database; Quality inspection type is the name of the quality inspection project. The quality inspection project updates the work content of the forest and grass comprehensive monitoring evaluation polygon monitoring, including but not limited to administrative district database quality inspection type, forest supervision and inspection database quality inspection type, forest resource status database quality inspection type, and forest resource change database quality inspection type. A quality inspection project includes one or more logical types; The logic type is the matching of the quality inspection logic rules of the quality inspection project. The logic type is generally divided into graphic quality inspection logic type and attribute quality inspection logic type. For quality inspection projects with many logic rules, the logic rules can be matched based on the field object dependency that the quality inspection logic rules execute or the dependency of the quality inspection logic rules themselves to form a new logic type. For example, the quality inspection type of the forest resource current situation database can be further divided into dictionary domain inspection logic type, plot factor inspection logic type, basic factor inspection logic type, management factor inspection logic type, forest ecology inspection logic type, topography soil factor inspection logic type, forest stand factor inspection logic type, etc., and one logic type contains one or more logic rules. A logic rule is the smallest unit of the provincial-level quality inspection logic rule database and is a specific quality inspection entry to be executed. It is composed of three parts: logic rule name, logic rule condition and logic rule suggestion. The logic rule name is the explanation of the logic rule execution content, the logic rule condition is the content of the logic rule execution, and the logic rule hint is the suggestion content displayed when a logic execution error occurs. For example, ("Forest land must enter the forest land protection grade", "GLLX=10 AND LD_JD=0", "If the management type is forest land, the forest land protection grade must be entered!") are respectively the logic rule name, logic rule condition and logic rule suggestion of one logic rule. The modification time is the time when the provincial-level quality inspection logic rule database was last modified and stored; The modifying user is the user who last modified and saved the provincial-level quality inspection logic rule database.
[0026] 2. Access the provincial-level quality inspection logic rules database, complete operations such as add, delete, update, etc., and save the system time and user name of the operation.
[0027] 3. County-level users create applications and import data, and locally create county-level result databases, county-level progress log databases and county-level quality inspection logic rule databases. The county-level result databases at least include administrative district databases, forestry supervision databases, forest resources status databases, forest resources change databases and forest resource file databases, and the database structures are consistent with those at the provincial level. After the administrative district databases, forestry supervision databases, forest resources change databases and forest resource file databases are formed, self-inspection is performed on the above-mentioned databases to ensure that there are no spatial topology errors or attribute logic errors locally.
[0028] 4. County-level users shall record the execution results of application creation and data import in the county-level progress log database, and then consolidate them into the provincial-level progress log database. In it, when the progress is application creation and data import, and result export, the quality inspection result is "pass", the number of errors is 0, and the quality inspection results and the number of errors of other functions shall be filled in according to the actual situation. For example, the data of Luhuo County, Sichuan Province executes the forest supervision database inspection function, and the log record of Article 12 is created. The county code of Luhuo County is 513327, the execution result is fail, the inspection quantity is 245, the number of errors is 13, and the function execution time is 2021-05-21 16:42:32. Then, the log project will be recorded in the local progress log database as (12, 513327, forest supervision space and attribute inspection function, fail, 245, 13, 2021-05-21 16:42:32).
[0029] 5. A county-level user accesses the provincial-level quality inspection logic rule database, reads the modification time of the provincial-level quality inspection logic rule database, and compares it with the modification time of the locally stored quality inspection logic rule database; if there is no match, downloads the provincial-level quality inspection logic rule database and updates the locally stored quality inspection logic rule database.
[0030] 6. County-level users can execute the quality inspection rules in the locally stored quality inspection logic rule database during the inspection of administrative district databases, etc., and return and display the inspection results.
[0031] 7. The county-level system will record the inspection progress logs in administrative district databases and other databases, and submit the data to the provincial-level progress log database.
[0032] 8. County-level users can submit their local county-level results databases to be consolidated into the provincial-level aggregated database.
[0033] 9. The provincial-level user checks and statistics the progress data against the provincial-level aggregated database, and determines whether the county-level achievements are acceptable; if not, carry out step 6.
[0034] 10. After the county-level user exports the results database, it packages it into a compressed file and sets the decompression password as the unified password built into the system. The provincial-level user uses the unified password built into the system to decompress the result file and receive the results submitted by the county-level user.
[0035] The present invention also provides a forestry comprehensive monitoring evaluation polygon monitoring update system for implementing any of the above-mentioned forestry comprehensive monitoring evaluation polygon monitoring update methods, an embodiment of which is as follows, as shown in Figures 2 and 3, including a county-level user-side application system and a provincial-level server-side application system, and the county-level user-side application system includes:
[0036] The application creation and data import module is used by county-level users to import local data according to their requirements and create county-level forest resources annual update application files, including but not limited to forest resources pre-term database, administrative division database, forest resources status database, forestry supervision database, and forest resources file database.
[0037] The quality inspection logic rule database comparison module is used by a county-level user to create a quality inspection logic rule database locally, access the provincial-level quality inspection logic rule database to perform a modification time comparison, and judge the consistency between the locally stored quality inspection logic rule database and the provincial-level quality inspection logic rule database.
[0038] The quality inspection logic rule database update module is used to update the contents of the provincial-level quality inspection database to the locally stored quality inspection logic rule database so as to make the two consistent when a county-level user finds that the locally stored quality inspection logic rule database and the provincial-level quality inspection logic rule database are not consistent.
[0039] The administrative division database checking module is used to perform spatial topology checking and attribute logic checking on the administrative division database edited and imported by the user, in which the spatial topology checking includes overlapping, gaps, etc., and the attribute logic checking includes dictionary checking, required items and non-required items checking, factor logic relationship, etc.
[0040] The forestry supervision database inspection module is used to perform spatial topology inspection and attribute logic inspection on the forestry supervision database edited and imported by the user, in which the spatial topology inspection includes duplication, multiple components, etc., and the attribute logic inspection includes dictionary inspection, inspection of items that need to be filled in and items that do not need to be filled in, factor logical relationships, etc.
[0041] The forest resource current status database inspection module is used by users to perform spatial topology inspection and attribute logic inspection on the forest resource current status database completed in this period, among which spatial topology inspection includes overlap, gap, open area, multiple parts, fragmentation, super-boundary, and crossing of compartment boundaries, etc., and attribute logic inspection includes dictionary domain inspection, partition factor inspection, basic factor inspection, management factor inspection, forest ecology inspection, topography and soil factor inspection, and stand factor inspection, etc.
[0042] The forest resource change database generating module is used for users to generate a forest resource change database based on the forest supervision database, the forest resource previous data and the forest resource current data.
[0043] The forest resource change database checking module is used for users to perform attribute logic checking on the forest resource change database, including forest supervision factor checking, change cause checking, and abnormal change checking.
[0044] The result reporting module is used by users to integrate the administrative district database, forest supervision database, forest resource change database (only including the part where the cause of change is not 0) and forest resource file database in the local county-level forest resource annual update application based on the "forestry and grass comprehensive monitoring evaluation polygon monitoring update method" through the network into the administrative district database, forest supervision database, forest resource change database and forest resource file database of the provincial-level aggregated database.
[0045] The result export module is used by users to export the administrative division database, forest supervision database, forest resources status database, forest resources change database and forest resources file database in the local county-level forest resources annual update application based on the "forestry and grass comprehensive monitoring evaluation polygon monitoring update method", and then package them into a compressed file and set the compressed file password.
[0046] The progress log background generation and reporting module is used to record the current module execution status and execution results in the local progress log database after executing the application creation and data import module, the file database logic inspection module, the administrative division database inspection module, the forestry supervision database inspection module, the forest resources status database inspection module, the forest resources change database inspection module or the result export module, and to access the provincial-level progress log database and update the aggregated records in the local progress log database to the provincial-level progress log database.
[0047] Provincial-level server-side application systems include:
[0048] The provincial-level quality inspection logic rule database creation module is used to provide provincial-level users with the provincial-level quality inspection logic rule database creation function, set provincial-level and county-level access groups or users for the provincial-level quality inspection logic rule database, and grant usage rights to each access group and user.
[0049] The provincial-level quality inspection logic rule database maintenance module provides provincial-level users with the ability to complete operations such as addition, deletion, and update on the provincial-level quality inspection logic rule database and save the modifications. At the same time, this module is used to provide encryption protection for the provincial-level quality inspection logic rule database through encryption technology to prevent malicious tampering.
[0050] The provincial-level aggregated database creation module is used by a provincial-level user to provide the provincial-level aggregated database creation function, set up provincial-level and county-level access groups or users for the provincial-level aggregated database, and grant usage permissions for each access group and user.
[0051] The provincial-level aggregated database aggregation module is used to make judgments on the data reporting applications submitted by the user at the county level, and the provincial-level aggregated database checks whether the performance data of the applied unit already exists. If so, it deletes it and then inserts the aggregate data; otherwise, it directly inserts the aggregate data.
[0052] The provincial-level aggregated database inspection module is used to provide provincial-level users with the functions of inspecting administrative division database, forest supervision database, forest resource change database, and forest resource file database.
[0053] The provincial-level aggregated database comparative analysis module provides provincial-level users with the function of comparative statistical analysis of forest resource change databases, which is used to collect statistics on the change areas of factors such as land type, right ownership, origin, forest category, real rights grade, public interest forest grade, and forest land grade before and after changes in county-level units.
[0054] The provincial-level progress log database creation module is used by a provincial-level user to create a provincial-level progress log database to store all the log information in the county-level forestry and grass comprehensive monitoring evaluation polygon monitoring update.
[0055] The provincial-level progress aggregation module is used by the provincial-level user to receive the data aggregation requests of the county-level users and automatically update and aggregate accordingly.
[0056] The provincial-level progress query statistics module allows provincial-level users to display the quality inspection log results by project according to the log project name for the progress display at the county level, intuitively display the quality inspection and progress status at the county level, and provide a consolidated display for the progress status at the provincial and city / state levels. It statistics whether each county-level log project is passed, and if all are passed, it determines that the county-level result is complete; if there is even one failure, it determines that the county-level result is not complete, which is used to statistics the work progress of the entire province and each city (state).
[0057] The provincial progress export module is used by provincial users to export the provincial progress status document results such as .xls, .doc, etc. according to their needs.
[0058] The forest resources "One Map" result receiving module is used by the provincial-level user to verify the identity of the county-level user, and obtain the compressed file decompression password based on the county code of the result submitted by the user and the unified password built into the system, which is used to decompress the submitted result by the county-level user.
[0059] The execution flow of the above forest grass comprehensive monitoring evaluation polygon monitoring update system, as shown in Figure 4, includes the following steps:
[0060] 1. Execute a provincial-level quality inspection logic rule database creation module, a provincial-level aggregated database creation module, and a provincial-level progress log database creation module. In the provincial-level class cloud server-side application system, a provincial-level quality inspection logic rule database, a provincial-level aggregated database, and a provincial-level progress log database are created through the provincial-level administrator, provincial-level and county-level access groups or users of the provincial-level quality inspection logic rule database are set, and usage rights are granted to each access group and user.
[0061] 2. Implement the provincial-level quality inspection logic rule database maintenance module. The logic rule project of deploying the provincial-level quality inspection logic rule database includes but is not limited to administrative district database inspection quality inspection type, forestry supervision inspection database quality inspection type, forest resources status database quality inspection type, and forest resources change database quality inspection type.
[0062] 3. Run the application creation and data import module, trigger and run the progress log background generation and reporting module. Import local data according to the requirements of county-level users, including but not limited to forest resources pre-stage database, administrative division database, forest resources status database, forest supervision database, and forest resources file database. Record the current module execution status and execution results in the local progress log database, access the provincial-level progress log database, and update the aggregated records in the local progress log database to the provincial-level progress log database.
[0063] 4. Execute the quality inspection logic rule database comparison module and the county-level quality inspection logic rule database update module. The county-level user reads and decodes the data of the provincial-level quality inspection logic rule database, compares the modification time of the provincial-level quality inspection logic rule database with the modification time of the locally stored quality inspection logic rule database, and downloads the provincial-level quality inspection logic rule database instead of updating the locally stored quality inspection logic rule database.
[0064] 5. Run the administrative division database inspection module, trigger the progress log background generation and reporting module to run, and run the result reporting module. A county-level user forms an administrative division database on the county-level user's device, performs self-inspection, ensures that the local administrative division database has no spatial topology errors or attribute logic errors, records the current module execution status and execution results in the local progress log database, accesses the provincial-level progress log database, and updates the aggregated records of the local progress log database to the provincial-level progress log database. The county-level user submits the local all-forest resources "one map" result on the county-level user's device, which only includes the results of the administrative division database.
[0065] 6. Execute the provincial-level aggregated database aggregation module, the provincial-level aggregated database inspection module, the provincial-level progress aggregation module, the provincial-level progress query statistics module, and the provincial-level progress export module. The application system on the provincial cloud server side judges the data report application submitted by the county level, checks whether the result data of the application unit already exists in the provincial-level aggregated database, and if so, deletes it and then inserts the aggregate; otherwise, directly inserts the aggregate. The application system on the provincial cloud server side checks the aggregated database data of the whole province formed by the county level collectively submitted, and only checks the administrative district database of the whole province, and this inspection project and method are consistent with the content of step 3. The provincial-level application system receives the data aggregation request from the county-level user, and automatically performs appropriate updates and aggregations, and the provincial-level user performs progress statistical analysis by city, prefecture, region, and type as necessary, and exports the provincial-level log and progress table according to the selected type.
[0066] 7. Run the forest supervision database inspection module, trigger the progress log background generation and reporting module to run, and run the result reporting module. A county-level user forms a forest supervision database on the county-level user's device, performs self-inspection, ensures that there is no spatial topology error or attribute logic error in the local forest supervision database, records the current module execution status and execution result in the local progress log database, and accesses the provincial-level progress log database, updates the aggregated records of the local progress log database to the provincial-level progress log database, and the county-level user submits the local all-forest resources "one map" result on the county-level user's device, including the administrative division database result and the forest supervision database result.
[0067] 8. Execute the provincial-level aggregated database aggregation module, the provincial-level aggregated database inspection module, the provincial-level progress aggregation module, the provincial-level progress query statistics module, and the provincial-level progress export module. The application system on the provincial cloud server side judges the data report application submitted by the county level, checks whether the result data of the application unit already exists in the provincial-level aggregated database, and if so, deletes it and then inserts the aggregate; otherwise, directly inserts the aggregate. The application system on the provincial cloud server side checks the aggregated database data of the whole province formed by the county level collectively submitted, and only checks the administrative district database of the whole province, and this inspection project and method are consistent with the content of step 3. The provincial-level application system receives the data aggregation request from the county-level user, and automatically performs appropriate updates and aggregations, and the provincial-level user performs progress statistical analysis by city, prefecture, region, and type as necessary, and exports the provincial-level log and progress table according to the selected type.
[0068] 9. Run the forest resources current status database inspection module, trigger the progress log background generation and reporting module to run, and run the result reporting module. A county-level user forms a forest supervision database on the county-level user's device and performs self-inspection, ensures that there is no spatial topology error or attribute logic error in the local forest supervision database, records the current module execution status and execution result in the local progress log database, and accesses the provincial-level progress log database, updates the aggregated records of the local progress log database to the provincial-level progress log database, and the county-level user submits the local whole forest resources "one map" result on the county-level user's device, including administrative division database result, forest supervision database result, and forest resources current status database result.
[0069] 10. Execute the provincial-level aggregated database aggregation module, the provincial-level aggregated database inspection module, the provincial-level progress aggregation module, the provincial-level progress query statistics module, and the provincial-level progress export module. The application system on the provincial cloud server side judges the data report application submitted by the county level, checks whether the result data of the application unit already exists in the provincial-level aggregated database, and if so, deletes it and then inserts the aggregate; otherwise, directly inserts the aggregate. The application system on the provincial cloud server side checks the aggregated database data of the whole province formed by the county level collectively submitted, and only checks the administrative district database of the whole province, and this inspection project and method are consistent with the content of step 3. The provincial-level application system receives the data aggregation request from the county level user, and automatically performs appropriate updates and aggregations, and the provincial-level user performs progress statistical analysis by city, prefecture, region, and type as necessary, and exports the provincial-level log and progress table according to the selected type.
[0070] 11. Run the forest resource change database generation module and the forest resource change database inspection module, trigger the progress log background generation and reporting module to run, and run the result reporting module. A county-level user forms a forest supervision database on the county-level user's device and performs self-inspection, ensures that there is no spatial topology error or attribute logic error in the local forest supervision database, records the current module execution status and execution result in the local progress log database, and accesses the provincial-level progress log database, updates the aggregated record of the local progress log database to the provincial-level progress log database, and the county-level user submits the local whole forest resources "one map" result on the county-level user's device, including the administrative division database, the forest supervision database, the forest resource status database and the forest resource change database.
[0071] 12. The application system on the provincial cloud server side executes the provincial-level aggregated database aggregation module, the provincial-level aggregated database inspection module, the provincial-level aggregated database comparison and analysis module, the provincial-level progress aggregation module, the provincial-level progress query statistics module, and the provincial-level progress export module to determine the data report application submitted by the county level, and check whether the result data of the application unit already exists in the provincial-level aggregated database, and if so, delete it and then insert the aggregate, otherwise directly insert the aggregate. The application system on the provincial cloud server side inspects the aggregated database data of the whole province formed by the county level collectively submitted, and only inspects the administrative district database of the whole province, and this inspection project and method are consistent with the content of step 3. The application system on the provincial level receives the data aggregation request from the county level user, and automatically performs appropriate updates and aggregations, and the provincial level user performs progress statistical analysis by city, prefecture, region, and type as necessary, and exports the provincial-level log and progress table according to the selected type.
[0072] 13. Run the result export module and trigger the progress log background generation and reporting module to export the administrative division database, forest supervision database, forest resources status database, forest resources change database, and forest resources file database of the local county-level forest resources annual update application by a county-level user, package them into a compressed file, set the compressed file encryption, and send them to the provincial-level inspection unit by hard disk copy.
[0073] 14. Run the forest resources "One Map" result receiving module. The provincial-level user verifies the identity of the county-level user, and obtains the compressed file decompression password according to the county code of the result submitted by the user and the unified password built into the system, and decompresses it to obtain the result submitted by the county-level user.
[0074] The present invention also provides a forestry grass comprehensive monitoring evaluation polygon monitoring update cloud platform, and configures the forestry grass comprehensive monitoring evaluation polygon monitoring update system, an embodiment of which is as follows, as shown in Figure 5, including a forestry grass comprehensive monitoring evaluation polygon monitoring update device, a forestry grass comprehensive monitoring evaluation polygon monitoring update application system and a base cloud platform.
[0075] Among them, the forest grass comprehensive monitoring evaluation polygon monitoring update device is equipped with various PC machines, notebook computers, mobile workstations, tablet PCs and other devices at the county level user side, and is composed of 11 modules, including an application creation and data import module, a quality inspection logic rule database comparison module, a quality inspection logic rule database update module, an administrative district database inspection module, a forestry supervision database inspection module, a forest resource status database inspection module, a forest resource change database generation module, a forest resource change database inspection module, a result report module, a result export module and a progress log background generation and reporting module. The forestry comprehensive monitoring evaluation polygon monitoring update application system includes equipment such as servers, workstations or virtual machines which provide computing, storage and network capabilities for the operation of the provincial-level server-side application system, and provides users with a provincial-level quality inspection logic rule database creation module, a provincial-level quality inspection logic rule database maintenance module, a provincial-level aggregated database creation module, a provincial-level aggregated database aggregation module, a provincial-level aggregated database inspection module, a provincial-level aggregated database comparison and analysis module, a provincial-level progress log database creation module, a provincial-level progress aggregation module, a provincial-level progress query statistics module, a provincial-level progress export module and a forestry resource "one map" result receiving module, wherein the equipment such as servers and workstations are configured with application platforms such as operating systems, database platforms, GIS platforms and network middleware required to support the operation of the provincial-level server-side application system, and the platform capabilities of the virtual machines are provided by the base cloud platform; The base cloud platform includes, but is not limited to, X86 computing servers that build a network resource pool, storage servers that build a storage resource pool, network servers and gateways that build a network resource pool, virtualization platform software that performs resource virtualization management, and application platforms such as operating systems, database platforms, GIS platforms, and network middleware that are deployed on the virtualization platform.
[0076] It should be noted that the above is merely a preferred embodiment of the present invention, and that those skilled in the art may make various improvements and modifications without departing from the spirit of the present invention, and these improvements and modifications are also considered to be within the scope of protection of the present invention.
Claims
1. A comprehensive forest monitoring system in which a computer executes the following steps: In the evaluation polygon monitoring update method, Step (1): creating a provincial-level aggregated database, a provincial-level progress log database, and a provincial-level quality inspection logic rule database, the provincial-level aggregated database including at least an administrative division database, a forestry supervision database, a forestry resource status database, a forestry resource change database, and a forestry resource file database; Step (2) access the provincial-level quality inspection logic rules database, complete the addition, deletion and update, and save the system time and user name of the operation; Step (3); creating an application and importing data to create a county-level achievement database, a county-level progress log database and a county-level quality inspection logic rule database, the county-level achievement database including at least an administrative division database, a forestry supervision database, a forestry resource change database, a forestry resource status database and a forestry resource file database; Step (4): recording the execution result of application creation and data import in a prefecture-level progress log database, and inputting the execution result into a provincial-level progress log database; Access the provincial-level quality inspection logic rule database, read the modification time of the provincial-level quality inspection logic rule database, and compare it with the modification time of the stored quality inspection logic rule database; if there is no match, download the provincial-level quality inspection logic rule database and update the stored quality inspection logic rule database; if there is a match, proceed to step (6); step (5); Step (6): in the inspection of the administrative division database, the forest supervision database, the forest resource change database and the forest resource file database, execute the quality inspection rules of the county-level quality inspection logic rule database, and return and display the inspection result; Step (7); recording the administrative division database, the forest supervision database, the forest resource change database and the forest resource file database, and sending the data to the provincial-level progress log database; (8) aggregating the prefecture-level performance database and inputting the aggregated results into a provincial-level aggregated database; Conduct inspection and statistics on the provincial-level aggregated database to determine whether the county-level results are acceptable; if not, go back to step (6); if acceptable, go to step (10); step (9); (10) exporting the result database and packaging it into a compressed file, setting a decompression password as a system-built-in unified password, and using the system-built-in unified password to decompress the result file and receive the result; A method for updating polygon monitoring for comprehensive forest monitoring and evaluation.
2. The provincial-level progress log database structure created in step (1) includes ID, county code, log project name, quality inspection result, inspection quantity, error quantity, log time, and report time; The ID is a self-incrementing item that is created each time a quality inspection log is submitted. The prefecture code is a six-digit code that is implemented as a national uniform administrative code. The log project names refer to the progress names of the forest comprehensive monitoring evaluation polygon monitoring update. The log project names are divided into seven progresses: application creation and data import, administrative district database inspection, forest supervision database inspection, forest resource status database inspection, forest resource change database inspection, result summary report and result export report. The quality inspection result is either pass or fail. The number of inspections is the statistically calculated number of inspection polygons. The number of errors is the statistically calculated number of error polygons. Log time is the execution time of the log project 2. The method for updating polygon monitoring for forest comprehensive monitoring and evaluation according to claim 1.
3. The provincial-level quality inspection logic rule database logic structure created in step (1) includes: quality inspection number, quality inspection type, logic type, logic rule name, logic rule condition, logic rule suggestion, modification time, and modification user; The quality inspection number is the unique identification in the provincial-level quality inspection logic rules database; Quality inspection type is the name of the quality inspection project. The quality inspection project updates the work content of the forest comprehensive monitoring evaluation polygon monitoring. It includes administrative district database quality inspection type, forest supervision inspection database quality inspection type, forest resource status database quality inspection type, and forest resource change database quality inspection type. The logic type is the match of the quality inspection logic rules of the quality inspection project, and is divided into graphic quality inspection logic type and attribute quality inspection logic type. A logic rule is the smallest unit in the provincial-level quality inspection logic rule database and is a specific quality inspection entry to be executed. It is composed of a logic rule name, a logic rule condition, and a logic rule presentation. The logic rule name is a description of the logic rule execution content, the logic rule condition is the content of the logic rule execution, and the logic rule presentation is the presentation content displayed when the logic execution is an error. The modification time is the time when the provincial-level quality inspection logic rule database was last modified and stored; The modification user is the user who last modified and saved the provincial-level quality inspection logic rule database.
3. The method for updating polygon monitoring for forest comprehensive monitoring and evaluation according to claim 2.
4. In the step (3), after the county-level user forms the administrative division database, the forestry supervision database, the forestry resource change database and the forestry resource file database, the county-level user performs self-checking on the administrative division database, the forestry supervision database, the forestry resource change database and the forestry resource file database to ensure that there are no spatial topology errors or attribute logic errors locally.
4. The method for updating polygon monitoring for forest comprehensive monitoring and evaluation according to claim 3.
5. The forest comprehensive monitoring method according to claim 4. A system for implementing an evaluation polygon monitoring update method, comprising: a prefecture-level user-side application system and a provincial-level server-side application system; The application system on the county-level user side is: an application creation and data import module used for county-level users to import local data according to requirements and create county-level forest resources annual update project files, including forest resources pre-term database, administrative division database, forest resources status database, forestry supervision database and forest resources file database; a quality inspection logic rule database comparison module, which is used by a county-level user to create a quality inspection logic rule database, access the provincial-level quality inspection logic rule database to make a comparison against the modification time, and determine the consistency between the stored quality inspection logic rule database and the provincial-level quality inspection logic rule database; a quality inspection logic rule database updating module, which is used to update the content of the provincial-level quality inspection database to the stored quality inspection logic rule database so as to make the two consistent when a county-level user finds that the stored quality inspection logic rule database and the provincial-level quality inspection logic rule database are not consistent; an administrative division database checking module, which is used by a prefecture-level user to perform a spatial topology check and an attribute logic check on the administrative division database edited and imported, the spatial topology check including overlap and gap, and the attribute logic check including dictionary check, required item and non-required item check, and factor logic relationship check; A forestry supervision database inspection module is used for performing spatial topology inspection and attribute logic inspection on the forestry supervision database edited and imported by the prefecture-level user, where the spatial topology inspection includes duplication and multiple components, and the attribute logic inspection includes dictionary inspection, required item and non-required item inspection, and factor logic relationship inspection; A forest resource current status database inspection module is used by county-level users to perform spatial topology inspection and attribute logic inspection on the forest resource current status database completed in this period, the spatial topology inspection includes overlap, gap, open-air, multi-part, fragmentation, super-boundary, and crossing forest compartment boundary inspection, and the attribute logic inspection includes dictionary domain inspection, partition factor inspection, basic factor inspection, management factor inspection, forest ecology inspection, topography and soil factor inspection, and stand factor inspection; A forest resource change database generating module is used by a county-level user to generate a forest resource change database according to the forest supervision database, the forest resource pre-period data, and the forest resource status data; A forest resource change database checking module used by prefecture-level users to perform attribute logic checking on the forest resource change database, including forest supervision factor checking, change cause checking, and abnormal change checking; A result reporting module is used by county-level users to report and consolidate the administrative division database, forest supervision database, forest resource change database and forest resource file database in their local county-level forest resource annual update applications through the Internet and enter them into the administrative division database, forest supervision database, forest resource change database and forest resource file database in the provincial-level aggregated database; A result export module is used by a county-level user to export the administrative division database, the forest supervision database, the forest resources status database, the forest resources change database and the forest resources file database in the local county-level forest resources annual update application, and then package them into a compressed file and set a compressed file password; A progress log background generation and reporting module is used to record the execution status and execution result of the current module in the local progress log database, access the provincial progress log database, and update the aggregated record of the local progress log database to the provincial progress log database after executing the application creation and data import module, the file database logic inspection module, the administrative division database inspection module, the forestry supervision database inspection module, the forest resources status database inspection module, the forest resources change database inspection module, or the result export module; Provincial-level server-side application system includes: A provincial-level quality inspection logic rule database creation module is used for a provincial-level user to provide a provincial-level quality inspection logic rule database creation function, and to set provincial-level and county-level access groups or users of the provincial-level quality inspection logic rule database and grant use rights to each access group and user; A provincial-level quality inspection logic rule database maintenance module is used to allow provincial-level users to complete the operations of adding, deleting, and updating the provincial-level quality inspection logic rule database and store the modified contents, and at the same time, to provide encryption protection for the provincial-level quality inspection logic rule database through encryption technology to prevent malicious tampering; a provincial-level aggregated database creation module used for a provincial-level user to provide a provincial-level aggregated database creation function, set provincial-level and prefecture-level access groups or users of the provincial-level aggregated database, and grant usage rights to each access group and user; a provincial-level aggregated database aggregation module, which is used to make judgments on the data reporting applications submitted by the county-level users, check whether the outcome data of the application unit already exists in the provincial-level aggregated database, and if the outcome data exists, delete the already existing outcome data and then update it to the outcome data of the application unit; and if the outcome data does not exist, insert the outcome data of the application unit; A provincial-level aggregated database inspection module is used to provide provincial-level users with administrative division database, forest supervision database, forest resource change database, and forest resource file database inspection functions; A provincial-level aggregated database comparative analysis module provides provincial-level users with the function of comparative statistical analysis of forest resource change databases, and is used by county-level units to collect statistics on the change areas of factors including land type, right ownership, origin, forest category, real right grade, public interest forest grade, and forest land grade before and after the change; a provincial-level progress log database creation module, which is used by a provincial-level user to create a provincial-level progress log database and store all log information in the forest comprehensive monitoring evaluation polygon monitoring update; a provincial-level progress aggregation module used by a provincial-level user to receive data aggregation requests from county-level users and automatically perform appropriate updates and aggregations; A provincial-level progress query statistics module is used for displaying the progress of county-level units by provincial-level users, displaying the quality inspection log results by project according to the name of the logged project, intuitively displaying the quality inspection and progress status of county-level units, providing an aggregate display of the unit progress of the whole province and city / state, respectively stating whether all the logged projects of each province are passed or not, and if all are passed, determining that the county-level result is complete, and if there is one failure, determining that the result is not complete, thereby stating the work progress status within the whole province; a provincial-level progress export module used for provincial-level users to export progress status according to need; A forest resource "one map" result receiving module is used by a provincial-level user to verify the identity of a county-level user, and obtain a compressed file decompression password according to the county code submitted by the county-level user and the unified password built into the system, so as to decompress the results submitted by the county-level user. A comprehensive forest monitoring and evaluation polygon monitoring and update system.
6. The forest comprehensive monitoring and evaluation polygon monitoring and updating system according to claim 5 is provided, A forest comprehensive monitoring evaluation polygon monitoring update device is installed on the prefecture-level user side application system; A forest comprehensive monitoring evaluation polygon monitoring update application system is deployed in the provincial-level server-side application system; A base cloud platform used by the county-level user-side application system and the provincial-level server-side application system to provide computing, storage, network communication and system operation capacity support; A forest comprehensive monitoring and evaluation polygon monitoring and update cloud platform characterized by:
Citation Information
Patent Citations
Forestry big data construction method based on map
CN106547853A
Land space planning spatial data mutation checking method, application system and cloud platform
CN112988788A
Forestry data co-processing system
CN113159698A
