Dynamic updating method, system and equipment for drainage facility data based on temporal data

Abstract

The invention relates to the technical field of urban drainage facility big data, and provides a drainage facility data dynamic updating method, system and equipment based on tense data, and the method comprises the steps: determining entities, attributes and relationships contained in a to-be-constructed knowledge graph through constructing data models of various drainage facility data; therefore, a pipe point pipeline with a specified structure is provided, a defect detection data form template is provided for a user to carry out data entry so as to generate unified standard drainage facility data to be entered, and the drainage facility data to be entered is imported into a knowledge graph database so as to store the drainage facility data and construct a knowledge graph; the drainage facility data in the knowledge graph is the tense data with the tense attribute, so that the drainage facility tense data is dynamically updated through the association relationship of the knowledge graph and the historical data version of the drainage facility is managed; real and effective drainage facility data in different periods can be subjected to data fusion and multi-platform data sharing, so that drainage facility operation management is more scientific and efficient.

Description

Technical Field

[0001] The present invention relates to the field of urban drainage facility big data technology, and in particular to a method, system and device for dynamically updating drainage facility data based on temporal data. Background Art

[0002] Urban drainage facilities are an important part of urban infrastructure. In recent years, with the acceleration of the pace of urban infrastructure construction, a large number of drainage facilities are being newly built and renovated. In the process of comprehensive investigation and inspection of new and old drainage facilities, a large amount of investigation and inspection data is generated. These data types are diverse, the formats are diverse, and the data is complex, including CAD drawing data, point and line result table data, SHP vector data, and video, image and other image data. This kind of data has uneven quality, scattered storage, and cannot achieve system integration and visual management of massive drainage facility data. Moreover, for newly built and renovated drainage facilities, the existing technology cannot realize the dynamic update of drainage facility data in a timely and accurate manner, which brings great obstacles to the effective operation and management of drainage facilities.

[0003] At present, there is no system that can completely solve the problems of urban drainage facility survey, inspection data entry, data verification, database generation, dynamic update, and historical version data reproduction, and it is impossible to achieve full-cycle unified digital management of the big data of modern urban drainage facilities. Summary of the invention

[0004] In view of the above problems, the present invention is proposed to provide a method, system and device for dynamically updating drainage facility data based on temporal data, which overcome the above problems or at least partially solve the above problems.

[0005] One aspect of the present invention provides a method for dynamically updating drainage facility data based on temporal data, the method comprising: Data analysis is performed on the preset drainage facility inventory data to extract the common information fields and unique information fields of the element classes corresponding to the pipe points, pipelines, detection well defects and detection line defects in the drainage facility inventory data, and the storage object logic model corresponding to each element class is constructed according to the common information fields and unique information fields of the element classes corresponding to the pipe points, pipelines, detection well defects and detection line defects, and the pipe point data form template, pipeline data form template, detection well defect form template and detection line defect form template are generated; Acquire the drainage facility data to be entered generated based on the pipe point data form template, the pipeline data form template, the detection well defect form template and / or the detection line defect form template, and perform pipe network attribute verification, pipe network topology verification, data integrity and validity verification on the drainage facility data to be entered; The verified drainage facility data to be entered are identified as entity table data and entered, so that the back-end can use the query language to import the newly entered entity table data of various types into the knowledge graph database according to the storage object logic model corresponding to each element class to store the drainage facility data and construct a knowledge graph. The drainage facility data in the knowledge graph is temporal data with temporal attributes; Generate batch data update requests based on multiple newly entered entity table data for unified management and submission, set approval data version and facility update information, and store and record the facility update information, where the facility update information includes one or more of the project, data source, update type, application reason, and change description; The entity table data corresponding to the batch data update request is rendered on the map for the user to approve. When the approval instruction triggered by the user is received, the data in the knowledge graph database is updated to complete the dynamic update of the facility data.

[0006] Another aspect of the present invention further provides a drainage facility data dynamic update system based on temporal data, comprising a functional module for implementing the drainage facility data dynamic update method based on temporal data as described above.

[0007] Another aspect of the present invention also provides a drainage facility data dynamic update device based on temporal data, comprising a memory, a processor, and a computer program / instructions stored in the memory and executable on the processor, wherein the processor executes the computer program / instructions to implement the steps of the drainage facility data dynamic update method based on temporal data as described above.

[0008] The method, system and equipment for dynamically updating drainage facility data based on temporal data provided in the embodiments of the present invention construct data models for various types of drainage facility data, determine the entities, attributes and relationships contained in the knowledge graph to be constructed, and provide a specified structure of pipe point and pipeline, and detection defect data form template for users to enter data to generate unified standard drainage facility data to be entered, and import the data into the knowledge graph database to store the drainage facility data and construct the knowledge graph. The drainage facility data in the knowledge graph is temporal data with temporal attributes, which realizes the dynamic update of drainage facility temporal data and the management of historical data versions of drainage facilities through the association relationship of the knowledge graph, and realizes unified digital management of urban drainage facility big data throughout the entire cycle, so that real and effective drainage facility data from different periods can be integrated and shared on multiple platforms, laying a good data foundation for the in-depth application of smart water services in different industries, and making the operation and management of drainage facilities more scientific and efficient.

[0009] The above description is only an overview of the technical solution of the present invention. In order to more clearly understand the technical means of the present invention, it can be implemented according to the contents of the specification. In order to make the above and other purposes, features and advantages of the present invention more obvious and easy to understand, the specific implementation methods of the present invention are listed below. BRIEF DESCRIPTION OF THE DRAWINGS

[0010] Various other advantages and benefits will become apparent to those of ordinary skill in the art by reading the detailed description of the preferred embodiments below. The accompanying drawings are only for the purpose of illustrating the preferred embodiments and are not to be considered as limiting the present invention. Moreover, the same reference symbols are used throughout the accompanying drawings to represent the same components. In the accompanying drawings: Figure 1 A flow chart of a method for dynamically updating drainage facility data based on temporal data provided by an embodiment of the present invention; Figure 2 A structural block diagram of a drainage facility data dynamic update system based on temporal data provided by an embodiment of the present invention. DETAILED DESCRIPTION

[0011] The exemplary embodiments of the present disclosure will be described in more detail below with reference to the accompanying drawings. Although the exemplary embodiments of the present disclosure are shown in the accompanying drawings, it should be understood that the present disclosure can be implemented in various forms and should not be limited by the embodiments set forth herein. On the contrary, these embodiments are provided to enable a more thorough understanding of the present disclosure and to fully convey the scope of the present disclosure to those skilled in the art.

[0012] Those skilled in the art will appreciate that, unless otherwise stated, the singular forms "a", "an", "said" and "the" used herein may also include plural forms. It should be further understood that the term "comprising" used in the specification of the present invention refers to the presence of the features, integers, steps, operations, elements and / or components, but does not exclude the presence or addition of one or more other features, integers, steps, operations, elements, components and / or groups thereof.

[0013] Those skilled in the art will understand that, unless otherwise defined, all terms (including technical and scientific terms) used herein have the same meaning as generally understood by those skilled in the art in the art to which the present invention belongs. It should also be understood that terms such as those defined in general dictionaries should be understood to have meanings consistent with the meanings in the context of the prior art, and will not be interpreted with idealized or overly formal meanings unless specifically defined.

[0014] Figure 1 The flowchart of the method for dynamically updating drainage facility data based on temporal data according to one embodiment of the present invention is schematically shown. Figure 1The method for dynamically updating drainage facility data based on temporal data in an embodiment of the present invention specifically comprises the following steps: S11. Perform data analysis on the preset drainage facility inventory data to extract the common information fields and unique information fields of the feature classes corresponding to the pipe points, pipelines, detection well defects and detection line defects in the drainage facility inventory data, and construct the storage object logical model corresponding to each feature class according to the common information fields and unique information fields of the feature classes corresponding to the pipe points, pipelines, detection well defects and detection line defects, and generate the pipe point data form template, pipeline data form template, detection well defect form template and detection line defect form template.

[0015] The following is a brief description of the common information fields and unique information fields using the pipe point as an example. The common information fields of the pipe point feature class include but are not limited to drainage system type, geophysical point number, characteristics, attachment type, point level, road name, project name, survey area, operation and maintenance area, administrative area, and the shape, material, size, location, and update type of the pipe point equipment. If the attachment of the pipe point is a manhole, the unique information fields include but are not limited to: manhole geophysical point number, manhole type, water depth during surveying, mud depth during surveying, whether it is anti-settling, whether it is anti-falling, whether it is anti-theft, whether it is anti-odor, remarks, update type, etc.

[0016] In this embodiment, a data model of various types of drainage facility data is constructed based on the inventory data of drainage facilities, and the entities, attributes and relationships contained in the knowledge graph to be constructed are determined, so as to generate a specified structure of pipe point pipeline and detection defect data template for operators to enter data during the survey. Specifically, based on the inventory data of pipe point pipeline and detection defect in drainage facilities, the common fields and unique information of each element class are analyzed, and they are respectively decomposed into the storage object logical model of various types of pipe point pipeline and detection defect data, and their entities, attributes and relationships are established, and organized into point and line form templates for operators to download and use. In order to ensure the uniformity and standardization of data, content restrictions are set for some data items in various data subtables, and specific filling content is set. In order to ensure the integrity of data, required data items are set in various data subtables, and users must fill them in as required. The results serve as the pre-data basis for system data entry in the data import submodule.

[0017] Specifically, taking the control point as an example, by analyzing the stock data, the fields contained in all types of control point elements (inspection wells, rainwater inlets, storage tanks, overflow weirs, gates, valves, discharge outlets, etc.) are obtained. Such fields are regarded as the common information fields of all control point elements, and fields that are only available in the type of control point such as inspection wells are regarded as the unique information fields of a certain type of control point. The overall structure of the common information fields of such control points and the unique information fields of each type of control point is the storage object logic model corresponding to the control point element class. Further, when generating a form template for control point data, such as Excel, according to the storage object logic model of such control point, the Excel file is divided into several tables, including the control point basic data table, inspection well data table, rainwater inlet data table, storage tank data table, overflow weir data table, gate data table, valve data table, discharge outlet data table, etc., wherein the control point basic data table contains all the common information fields of the control point, and the inspection well, rainwater inlet and other data tables are filled with the unique information fields of the corresponding type of control point.

[0018] The data in the basic data table of pipe points and these pipe point type data tables can be indexed by the geophysical point number field that needs to be filled in these pipe point tables to ensure that a complete record can be formed (the starting point geophysical point number and the end point geophysical point number for pipelines). When entering data, the system first obtains the common information field of each pipe point in the basic data table of pipe points, and determines which table to find the unique information field information of this pipe point through the geophysical point number through the attachment type in the common information field, so as to form a complete pipe point record containing all information. It can be understood that the entire implementation process of pipelines, inspection wells, and inspection lines is basically the same as that of pipe points, and will not be described here.

[0019] S12. Obtain the drainage facility data to be entered that is generated based on the pipe point data form template, the pipeline data form template, the detection well defect form template and / or the detection line defect form template, and perform pipe network attribute verification, pipe network topology verification, and data integrity and validity verification on the drainage facility data to be entered.

[0020] In this embodiment, the attributes and topological problem verification parameters of the pipe network data can be configured according to the general drainage facility data verification standards and formulas, and the validity and integrity verification parameters of the detection data can be configured; based on the configured verification parameters, the drainage facility data to be entered are verified for pipe network attributes, pipe network topology, and integrity and validity of the detection data. After the verification is completed, statistical result tables for the verification of pipe network and detection abnormal data are generated respectively. After the abnormal data is processed, the data is re-entered to ensure the accuracy and validity of the entered data. S13. The drainage facility data to be entered that has passed the verification is identified as entity table data and the data is entered, so that the back end can use the query language to import the newly entered entity table data of various types into the knowledge graph database according to the storage object logical model corresponding to each element class to store the drainage facility data and construct a knowledge graph. The drainage facility data in the knowledge graph is temporal data with temporal attributes.

[0021] In this embodiment, various types of data are imported into the graph database using a query language according to a predefined knowledge graph data model, drainage facility data is stored, and a knowledge graph is constructed. Specifically, the file data of the drainage facility census or inspection project to be entered is obtained according to the file format, file, and project name, and a file filled with data based on a data template is received. According to the logical structure of the previously designed data template, the file is parsed to obtain all attributes and spatial information of this batch of drainage facility data, and an entity table is generated and entered into the drainage facility knowledge graph database.

[0022] Furthermore, constructing drainage facility data into a knowledge graph is a process of converting structured data into a semantic network. The backend imports various types of data into a graph database through a query language from the entity table after data verification, thereby constructing and storing the knowledge graph. The query language may be Cypher, SPARQL, etc., and the graph database may be Neo4j, GraphDB, etc., which are not specifically limited in the present invention. The embodiment of the present invention is explained by using an example of using Neo4j to build a knowledge graph: install Neo4j and start the database, use the Cypher query language to import data into Neo4j, create entity nodes for pipe points and pipelines, and connect pipe points and pipeline entities through the geophysical point number of the pipe point and the starting and ending geophysical point numbers of the pipe network, MATCH (p:PipePoint), (l:PipeLine) WHEREp.surveyPointNumber=l.startSurveyPointNumberORp.surveyPointNumber=l.endSurveyPointNumber, CREATE (p)-:CONNECTS_TO]->(l), query and apply After the knowledge graph is built, it can be queried and analyzed through the query language used above. Through the above steps, the drainage facility data can be converted into a knowledge graph, and then more complex data analysis and application can be carried out.

[0023] S14. Generate batch data update requests based on the newly entered multiple entity table data for unified management and submission, set the approval data version and facility update information, and store and record the facility update information. The facility update information includes one or more of the project, data source, update type, application reason, and change description.

[0024] In this embodiment, the data results obtained based on the pipe point data form template, pipeline data form template, detection well defect form template and / or detection line defect form template, that is, the drainage facility data to be entered, are configured with data entry verification parameters according to the general drainage facility data verification standard, so as to conduct pipe network attribute verification, pipe network topology verification, data integrity and validity verification on the drainage facility data to be entered, and a batch data update request is formed for submission if there is no objection to the verification result. Specifically, an application is submitted for a batch data update request with no objection to the verification result, and the application approval data version is selected, and the facility update details are filled in, including the project to which it belongs, the source of the data, the update type, the reason for the application, the description of the change, and the approver is designated, and the details of the update operation are recorded; it supports the modification and resubmission of the data update that has been rejected for approval.

[0025] S15. Render the entity table data corresponding to the batch data update request on the map for the user to approve. When the approval instruction triggered by the user is received, the data in the knowledge graph database is updated to complete the dynamic update of the facility data.

[0026] It is understandable that although step S13 has entered the entity table into the knowledge graph database, these data will have an attribute status pending approval at this time; only after approval through step S15, the status of the batch of data previously imported into the knowledge graph will become official data, completing the dynamic update of facility data.

[0027] In this embodiment, the user end can call up batch data update requests, view data update request details and render them on the map, and review the verification results; download the update details as needed, and approve the data update request. When the approval is passed, the data in the map database is updated to complete the dynamic update of facility data; when the approval is not passed, it is rejected and the rejection opinion is supported to be filled in and the rejection opinion is returned to the user end module as the source of the request for modification; after the approval is completed, an update approval log is formed for future review of the approval details.

[0028] The method for dynamically updating drainage facility data based on temporal data provided in an embodiment of the present invention constructs a data model of various types of drainage facility data, determines the entities, attributes and relationships contained in the knowledge graph to be constructed, and provides a specified structure of pipe point and pipeline, and detection defect data form template for users to enter data to generate unified standard drainage facility data to be entered, and imports this into a knowledge graph database to store drainage facility data and construct a knowledge graph. The drainage facility data in the knowledge graph is temporal data with temporal attributes, which realizes dynamic updating of drainage facility temporal data and management of drainage facility historical data versions through the association relationship of the knowledge graph, and realizes unified digital management of urban drainage facility big data throughout the entire cycle, so that real and effective drainage facility data from different periods can be integrated and shared on multiple platforms, laying a good data foundation for the in-depth application of smart water services in different industries, and making the operation and management of drainage facilities more scientific and efficient.

[0029] In an embodiment of the present invention, the drainage facility inventory data includes drainage facility pipe point and pipeline inventory data and drainage facility detection defect inventory data. Furthermore, according to the common information fields and unique information fields of the element classes corresponding to the pipe points, pipelines, detection well defects and detection line defects, a storage object logical model corresponding to each element class is constructed, including: based on the drainage facility pipe point and pipeline inventory data, each pipe point or pipeline is regarded as an entity node, the unique identification and connection relationship of the pipe point is determined by the geophysical point number field, the position information is determined by the plane coordinate X and plane coordinate Y fields of the pipe point, the pipe point type is determined by the attachment field of the pipe point, and the pipe point type can be a rainwater inlet, pipeline point, inspection well, discharge port, etc., and the update operation command to be performed is identified by the update type field of the pipe point, that is, the "update type" is used as the program to determine the update operation command to be performed; the unique identification and connection relationship of the pipeline is determined by the starting point geophysical point number field and the end point geophysical point number field, the position information of the starting point and the end point is determined by the corresponding geophysical point number, and the update operation command to be performed is identified by the update type field; the pipe point The remaining field information (i.e., attribute information) of points and pipelines is stored as the basis for auxiliary applications and query statistics; based on the inventory data of drainage facility detection defects, each detection well defect or detection line defect is taken as an entity node, and the geophysical point number field is used as the unique identifier of the detection well defect and the pipe well to which it belongs is determined, the problem type field is used to determine the category of the detected problem, and the update type field is used to identify the update operation command to be performed, that is, the "update type" is used as the program to determine the update operation command to be performed; the starting point geophysical point number field and the end point geophysical point number field are used to determine the unique identifier of the detection line defect and the pipeline to which it belongs, the problem type field is used to determine the category of the detected problem, and the distance from the starting point and the length involved in the defect are determined through the defect point distance field and the defect length field and rendered on the map; the remaining field information (i.e., attribute information) of the detection well defect and the detection line defect is stored as the basis for auxiliary applications and query statistics.

[0030] In the embodiment of the present invention, the drainage facility data to be entered is subjected to a pipe network attribute check, a pipe network topology check, and a data integrity and validity check, specifically including: according to the general drainage facility inspection standard, the drainage pipe network data is subjected to an attribute check, the user sets whether each attribute of the pipe point or pipe well is required, the data type and the attribute value range, and specifies what kind of problems are caused by violations of these rules. The system checks each record one by one according to these configured inspection parameters before the program is entered, and summarizes the problems found in the inspection into a table for display. If the user end triggers a satisfactory operation on the inspection result, the following data entry is performed. Otherwise, the data needs to be corrected and re-inspected. According to the connection relationship and spatial position of the pipe network, calculations are performed to check the topological problems of the pipe network. For example, when the drainage system types of the upstream and downstream pipe points are inconsistent, it is determined to be a mixed connection point. When the cross-sectional difference ratio of the cross-sectional area of ​​the maximum pipe diameter of the upstream pipe and the cross-sectional area of ​​the maximum pipe diameter of the downstream pipe is greater than the limit, it is determined to be a large pipe connecting a small pipe. Many rules required by users are established, and the problems found are summarized into a table for display. If the user end triggers a satisfactory operation on the verification result, the following data entry is performed. Otherwise, the data needs to be corrected and re-verified and entered. Set verification parameters to verify the test data. For example, if the pipe point in the test record cannot be found in a pipe network map, it is determined that the corresponding pipe point cannot be found. If the pipe in the test record cannot be found in a pipe network map, it is determined that the corresponding pipe cannot be found. If the defect photo corresponding to the test record is missing, it is determined to be a defect photo missing. Through these verification configurations, the validity and integrity of the defect data detected are guaranteed. The problems found are summarized into a table for display. If the user end triggers a satisfactory operation on the verification result, the following data entry is performed. Otherwise, the data needs to be corrected and re-verified and entered. Among them, a pipeline network map refers to a map that visually renders the existing drainage facility pipeline network data.

[0031] In another embodiment of the present invention, drainage facilities can also be updated through map interaction, including: requesting the latest data of various drainage facilities at the current time in the knowledge graph database, rendering on the map by adding vectors, and interactively performing data update operations such as adding pipe points, adding pipelines, modifying points and lines, deleting points and lines, and batch selection and editing on the map by clicking operations, which are summarized as data update requests for unified management and submission; and supporting the modification and resubmission of data update requests rejected by the update approval module. The specific implementation method is as follows, steps not shown in the attached figure: S21. Obtain the latest data of various drainage facilities in the knowledge graph database at the current time, create a map canvas for the latest data of the drainage facilities, and render it on the map by adding vectors to form visual map data; S22. The user terminal triggers interactive operations on the map to add new control points, add new pipelines, modify control points, modify pipelines, delete control points, delete pipelines and / or batch select and edit. Multiple data update operations triggered by the user terminal on the map generate map interactive update requests for unified management and submission, and set the approval data version and facility update information. Specifically, the new control point is implemented as follows: click the new control point function button, open the map instance mouse left click listening event, click to pick up the longitude and latitude geographic coordinates of the click position in the current coordinate system as the spatial location information of the new control point, pop up the new control point update record attribute filling panel, enter the required attributes and click Save to submit this new control point update record to the editing operation management submodule for submission, and complete the operation. The implementation of adding a new pipeline is as follows: click the new pipeline function button, open the map instance left-click mouse listening event, click two existing pipeline points on the map continuously, pick up the query request data temporal management module's real-time data query unit through the positions of the two points, obtain the returned results of the two pipeline point coordinate information and geophysical point number, pop up the new pipeline update record attribute filling panel, the pipeline's starting point geophysical point number and end point geophysical point number are automatically filled in using the obtained two points geophysical point numbers, the coordinate information of the two points is used as the starting and ending positions of the pipeline, enter the required attributes and click Save to submit this new pipeline update record to the editing operation management submodule for submission, and complete the operation. Modifying points and lines is implemented as follows: click the Modify Points and Lines function button, open the map instance mouse left-click listening event, click to pick up the longitude and latitude geographic coordinates of the clicked position in the current coordinate system, pick up as spatial location information, query the real-time data query unit of the data temporal management module, obtain the pipe point or pipeline element located at the clicked position, read the attributes, pop up the Modify Pipe Point or Modify Pipeline panel to automatically fill in the attributes for modification, click Save after the modification is completed to submit the modification update record to the Edit Operation Management submodule for submission, and complete the operation. Deleting points and lines is implemented as follows: click the Delete Points and Lines function button, open the map instance mouse left-click listening event, click to pick up the longitude and latitude geographic coordinates of the clicked position in the current coordinate system, pick up as spatial location information, query the real-time data query unit of the data temporal management module, obtain the pipe point or pipeline element located at the clicked position, read the attributes, pop up a confirmation box for whether to remove the object, if you click OK, submit the deletion operation update record to the Edit Operation Management submodule for submission, and complete the operation.Batch selection is implemented as follows: click the batch selection function button to start the map instance geometry drawing function. After the drawing is completed, the spatial information of the graphic element is obtained and used as a condition to pick up the query request data temporal management module's real-time data query unit to obtain all pipe points and pipeline features within the range. A batch update panel pops up to display these pipe points and pipelines for batch modification or batch deletion. There is a delete button after each record to remove the records that are selected but not desired to be operated from this panel. After the modification is completed, click Save to submit these updated records to the editing operation management submodule for submission to complete the operation.

[0032] S23. Render the drainage facility update data corresponding to the map interactive update request on the map for the user to review and approve. When the approval instruction triggered by the user is received, update the data in the knowledge graph database to complete the dynamic update of the facility data. Specifically, summarize each operation request for adding, modifying, and deleting the point table and line table into a table for unified management and attribute modification, and classify according to the standards of adding, modifying, deleting, or points and lines; submit and cancel the operation requests in a unified manner; select the application approval data version, fill in the facility update details, including the project, data source, update type, application reason, and change description, support the designation of approvers before submission, and store the details of this update operation in the knowledge graph database after submission; when the system is exited without submission or cancellation, the business database will store the above operations; for the data information rejected for approval, the rejected data information can be modified and resubmitted.

[0033] In the embodiment of the present invention, the entity table data corresponding to the batch data update request is rendered on the map for the user to review, or the drainage facility update data corresponding to the map interactive update request is rendered on the map for the user to review. The implementation process is similar. By calling the batch data update request and the map interactive update request, the data update request details are checked and matched with the map data, and then rendered to form a visual map update data, the verification results can be checked and the update details can be downloaded. After each approval is completed, the approval details are stored as an update approval log for future review of the approval details; it can be searched according to the updater, update time, and approval status.

[0034] Specifically, it includes steps such as visual display of update content, visual display of data verification results, visual display of update content map, downloading of update details, and approval operations.

[0035] Among them, the updated content is displayed visually: the unapproved batch data update requests are retrieved, and the basic information including application date, update content, applicant, project name, and update description are displayed on the client for the approver to view.

[0036] Visual display of data verification results: Obtain and display the verification result report for data verification of batch data update requests, including the total number of attribute data anomalies, the total number of topology data anomalies, and each abnormal road, upstream point number, downstream point number, verification type, problem type, problem description and other details. You can quickly filter and view based on these field values; when the trigger operation of the Export Excel button is received, this verification result report will be exported to an Excel local file.

[0037] Visual display of updated content on the map: retrieve the update request details corresponding to the unapproved batch data update request, render it on the map for viewing as a map service, and display different update types with different symbolizations to intuitively display the overall distribution of drainage facilities involved in this update approval.

[0038] Download update details: Display each specific update record of this update approval in a table format, and provide a download button to export it into an Excel local file.

[0039] Approval operation: Agree or reject the update request. If approved, the latest version of the facility data will be dynamically updated and the data will be updated in the data temporal management module. If not approved, the request will be rejected and the rejection opinion will be sent to the applicant.

[0040] Furthermore, the method also includes adding the entity table data corresponding to the batch data update request and / or the drainage facility update data corresponding to the map interactive update request to the knowledge graph to create relevant nodes, and adding a unique identifier for this submission to each node, and increasing the approval status field value to "pending approval" by default, so that the user terminal can match the unique identifier of each node in the knowledge graph database according to the unique identifier in the approval submission record stored in the business library, so as to obtain all pending approval records corresponding to each data update request; when the approval approval instruction triggered by the user terminal is received, the approval status field value of each node corresponding to this batch data update request in the knowledge graph is modified to "approved", and when the approval rejection instruction triggered by the user terminal is received, the approval status field value of each node corresponding to this batch data update request in the knowledge graph is modified to "rejected".

[0041] In an embodiment of the present invention, the method also includes the step of temporally managing drainage facility data. Temporally managing drainage facility data involves recording and processing changes in drainage facility data over time. This is very important for maintaining, planning and analyzing the evolution of local drainage facilities. In order to temporally manage data, it is necessary to extend the data model when importing data during knowledge graph construction, and automatically record the time for each entity's temporal attributes, namely "valid start time (validFrom)" and "valid end time (validTo)"; after the new data addition is approved for a certain piece of data, the "valid start time" of the node takes the current time, and the "valid end time" defaults to positive infinity, which means that this piece of data is born at the current time and will continue to exist unless it is operated on afterwards. Temporal management of drainage facility data specifically includes: before importing various entity table data into the knowledge graph database to construct the knowledge graph, extending the temporal attributes of the drainage facility data to record time information, the time information including the effective start time and the effective end time, and realizing the data temporal management of the drainage facility data by setting and / or updating the temporal attributes of the drainage facility data stored in the graph database; taking the nodes whose "effective end time" of the drainage facility data in the knowledge graph is after the current time as the latest drainage facility data corresponding to the current time; taking the nodes containing the specified historical time within the range from "effective start time" to "effective end time" of the drainage facility data in the knowledge graph as the historical data of the drainage facility at the specified time.

[0042] Furthermore, the temporal management of drainage facility data by setting and / or updating the temporal attributes of the drainage facility data stored in the graph database includes the following cases: When any drainage facility data is approved for data addition, the "Effective Start Time" of the node is set to the current time and the "Effective End Time" is set to positive infinity; When the data deletion of any drainage facility data is approved, all nodes of the corresponding entity in the knowledge graph are found according to the unique identifier of the current drainage facility data. It should be noted that there may be multiple nodes here because this drainage facility has been modified before and has multiple nodes with different effective times. The latest node with an "effective end time" after the current time is filtered out. This node represents the drainage facility to be deleted at the current time, keeps the "effective start time" of the current node unchanged, and updates the "effective end time" of the current node to the current time, indicating that this entity has disappeared at the current time.

[0043] When the data modification of any drainage facility data is approved, all nodes of the corresponding entity in the knowledge graph are found according to the unique identifier of the current drainage facility data. It should be noted that there may be multiple nodes here because this drainage facility has been modified before and has multiple nodes with different effective times. The latest node with an "effective end time" after the current time is filtered out. This node represents the drainage facility to be modified at the current time. The "effective end time" of the current node is updated to the current time, and a new node that meets the conditions is created in the knowledge graph according to the data modification request. The "effective start time" of the new node is set to the current time and the "effective end time" is set to positive infinity, indicating that this entity has been modified at present, and the new node becomes the latest data of this drainage facility.

[0044] In different application scenarios, based on the temporal mechanism defined above, the present invention can provide interface support for various data queries, such as unapproved data query, approval log data query, real-time data query and historical data query.

[0045] Unapproved data query: When the user submits a user update request in the batch data update module and the map interactive update module, this batch of update record requests is received by the background interface and added to the knowledge graph to create relevant nodes, and a unique identifier for this submission is added to each node, and the approval status attribute value is increased by default to "pending approval". The user completes the application operation; the approver logs in to the update approval module, and the update approval module matches the submission unique identifier of each node in the knowledge graph database according to the submission record unique identifier stored in the business library, so as to obtain all records corresponding to each submission, so that the specific update content of each submission can be called out when the update approval module is approved, and rendered on the map, and verification results and update details can be provided according to the update content; when the user approves, if passed, the approval status field value of each node in this batch of data in the knowledge graph is modified to "approved", and if rejected, it is modified to "rejected". This can support the update log submodule in the update approval module to filter out the drainage facility data involved in each approval, render it on the map, provide verification results and download update details according to the update content.

[0046] Approval log data query: Obtain all nodes in the knowledge graph whose approval status attribute value is not "pending approval", and classify them according to the unique identifier of the submission record, so as to support the update log submodule of the update approval module to obtain all update records involved in all or a single approval.

[0047] Real-time data query: Get all nodes whose "effective end time" for each type of data in the knowledge graph is after the current time, which is the current real-time data of the drainage facility to be obtained.

[0048] Historical data query: specify a specific time and obtain all nodes in the knowledge graph that include the input time within the range of "valid start time" to "valid end time" for each type of data, that is, the data of the drainage facility at the specified time to be obtained.

[0049] In an embodiment of the present invention, after the data in the knowledge graph database is updated to complete the dynamic update of the facility data, the method also includes: updating the thematic map operation: requesting the latest data of various types of drainage facilities in the knowledge graph database at the current time, and rendering them on the map by adding vectors; and / or, data time switching display operation: based on the data support of the data temporal management module, developing a timeline function to switch the data time of the map; and / or, historical evolution video synthesis display operation: specifying the time range and time interval, rendering the drainage facility data within each time node to generate image frames that are automatically fused to generate dynamic videos, and intuitively displaying the historical evolution process of the drainage facility data within the current viewing angle to the user.

[0050] Among them, the specific implementation method of updating the thematic map operation is: use the current time as the time condition to request the latest drainage facility data corresponding to the current time within the current viewing angle, create a map canvas for the latest drainage facility data, and render it by adding vectors; when symbolizing, use line segments with arrow directions to display pipeline data line elements, and give three different colors according to the different values ​​of the drainage system type field. For example, according to the drainage system type field value "rainwater", "sewage" and "combined" are given green, purple and orange colors respectively, and different arrow direction materials are given according to the starting point geophysical exploration point number, the end point geophysical exploration point number and the flow direction. If the flow direction is "downstream", the arrow is from the starting point geophysical exploration point to the end point geophysical exploration point. The exploration point number points to the end point geophysical exploration point number. If the flow direction is "countercurrent", the arrow points from the end point geophysical exploration point number to the starting point geophysical exploration point number. For the pipe point data point elements, point icons are used for display. According to the different values ​​of the drainage system type field, three different colors are given. For example, according to the drainage system type field values ​​"rainwater", "sewage" and "combined" are given green, purple and orange colors respectively. Different icons are set according to the different values ​​of the accessory type field. For example, according to the accessory type field values ​​"rainwater inlet; pipeline point; inspection well; discharge outlet; gate; septic tank; flap gate; valve; overflow weir; storage tank; pump station; sewage treatment plant; other", different representative icons are used and different icon sizes are specified.

[0051] Among them, the specific implementation method of the data time switching display operation is: based on the data time switching operation triggered by the user on the preset timeline component, the switched time node is used as the time condition to request the historical drainage facility data of the current time node within the current viewing angle, and all drainage facility layer services on the map are re-rendered according to the historical drainage facility data to display the overall situation of the drainage facility data at the selected time.

[0052] Among them, the historical evolution video synthesis display operation involves several key steps: time specification, temporal data acquisition, data visualization, and video generation. The specific implementation method is: obtain the start time, end time and time interval set by the user, calculate the target time node corresponding to the image data contained in the video to be displayed according to the start time, end time and time interval, and use the target time node as the time condition to request the historical drainage facility data corresponding to each target time node within the current viewing angle; create a map canvas for each historical drainage facility data obtained and render it for visualization by adding vectors. After rendering, the component is output to generate an image file for each target time point and named with the corresponding target time node, such as pipe_YYYYMMDD.png; after all the image files of each target time node are generated, they are stored in the pipes folder, using the preset FFmpeg command ffmpeg -piperate 1 -ipipes / pipe_%Y%m%d.png -c:v libx264 -r 30 -pix_fmt yuv420p pipe_network_history.mp4 synthesizes the image files of each target time node into a video in chronological order. This command synthesizes the image frames at a rate of 1 frame per second into a video of 30 frames per second, and returns the generated video to the user end for the user to play or download, intuitively showing the user the historical evolution process of the drainage facility data within the current viewing angle.

[0053] In an embodiment of the present invention, after the data in the knowledge graph database is updated to complete the dynamic update of the facility data, the method also includes: generating pipeline network data update data statistical information under administrative districts, projects, roads and other conditions based on the facility update records and screening conditions; and / or, generating horizontal comparison information of pipeline network data update status according to a specified period.

[0054] Specifically, field conditions are combined according to time, project, administrative area, and road, and the historical update records of drainage facility data under different field condition combinations are retrieved to count the updated data of pipe network data in different areas, roads, and road details. The updated data of pipe network data includes the number of updates N, the current total length of the pipe network Lz, the newly added length La, the deleted length Ld, and the modified length Lu. The present invention uses time, project, administrative area, road, etc. as screening conditions, and the display of statistical results is classified based on the content of area, road, road details, etc.

[0055] Specifically, field conditions are combined according to time, project, administrative area, and road to generate horizontal comparison information of pipeline network data update data at intervals of year, half year, quarter, and month, and return it to the user end in a graphical form for display by the user.

[0056] Among them, the number of updates N is the number of records in the drainage facility data update log module whose approval status is agreed under the screening conditions.

[0057] Among them, the calculation model of the current total length of the pipeline network Lz is: Where i is the number of pipelines that meet the screening conditions at the end time, The geometric length of each pipeline that meets the screening conditions at the end time; The calculation model of the additional length La is: in, is the number of pipelines that meet the screening conditions at the end time, is the geometric length of each pipeline that meets the screening conditions at the end time, is the number of pipelines that meet the screening conditions at the start time, The geometric length of each pipeline that meets the screening conditions at the start time; The calculation model of the deletion length Ld is: Among them, i is the number of pipeline records with update type of "delete" in the drainage facility data history version library that meet the screening conditions within the range from the start time to the end time. are the geometric lengths of the pipelines deleted above; The calculation model of the modified length Lu is: Among them, i is the number of pipeline records with update type of "modification" in the drainage facility data history version library that meets the screening conditions within the range from the start time to the end time. is the geometric length of each modified pipeline; s is the number of categories of pipeline unique identifiers in the pipeline records with update type "modified" within the range from the start time to the end time in the historical version library of drainage facility data that meet the screening conditions, is the geometric length of the pipeline with a repeated unique identifier under the above condition; and is the number of times this unique identifier appears under this condition. It is understandable that because the same pipeline may be modified multiple times, each pipeline should only be counted once when counting the length of the modified pipeline, so we should subtract the length of the same pipeline that is calculated multiple times when calculating. So here s means how many pipelines have been modified among so many modifications. This is confirmed based on the number of unique identifiers of the modified pipelines in the modification record. For example, I modified it 10 times, but when counting the pipelines modified in these 10 times, there are only 6 unique identifiers of the pipelines, which means that the 10 modifications only involve 6 pipelines, and some pipelines have been modified multiple times. Among them, "pipelines with repeated unique identifiers under this condition" refers to pipelines that have been modified multiple times in this case, because only when this happens multiple times will the unique identifier of this pipeline appear multiple times in the modification record.

[0058] The method for dynamically updating drainage facility data based on temporal data provided by the embodiment of the present invention can effectively solve the problems of urban drainage network survey, detection data entry, data verification, database and knowledge graph generation, dynamic update, and historical version data reproduction, and can realize the unified digital management of modern urban drainage facility big data throughout the whole cycle. It enables real and effective drainage facility data of different periods to be shared on multiple platforms, laying a good data foundation for the in-depth application of smart water services in different industries, making the operation and management of drainage facilities more scientific and efficient.

[0059] In addition, another embodiment of the present invention further provides a drainage facility data dynamic update system based on temporal data, including a functional module for implementing the drainage facility data dynamic update method based on temporal data as described above.

[0060] In one embodiment of the present invention, the drainage facility data dynamic update system based on temporal data specifically includes a batch data update module and an update approval module, wherein: The batch data update module is used to construct a data model for various types of drainage facility data, determine the entities, attributes and relationships contained in the knowledge graph to be constructed, and provide a specified structure of pipe points and pipelines, and detection defect data templates for operators to enter data during surveys; the obtained data results are configured with data entry verification parameters in accordance with the general drainage facility data verification standards, and the data results form is uploaded for data verification; if there is no objection to the verification results, a batch data update request is formed and submitted for application, and the back end uses the query language to import various types of data into the graph database according to the previously defined knowledge graph data model, stores the drainage facility data and constructs the knowledge graph; and supports the modification and resubmission of data update requests rejected by the update approval module.

[0061] The update approval module is used to view the details of data update requests and render them on the map, approve data update requests, update the data in the map database to complete the dynamic update of facility data when the approval is passed, and reject the request and support filling in the rejection opinion when it is not passed. The rejection opinion will be returned to the module as the source of the request for modification; after the approval is completed, an update approval log will be generated for future review of the approval details.

[0062] Furthermore, the batch data update module is specifically used to perform data analysis on the preset drainage facility inventory data to extract the common information fields and unique information fields of the element classes corresponding to the pipe points, pipelines, detection well defects and detection line defects in the drainage facility inventory data, respectively construct the storage object logic model corresponding to each element class according to the common information fields and unique information fields of the element classes corresponding to the pipe points, pipelines, detection well defects and detection line defects, and generate a pipe point data form template, a pipeline data form template, a detection well defect form template and a detection line defect form template; obtain the drainage facility data to be entered generated based on the pipe point data form template, the pipeline data form template, the detection well defect form template and / or the detection line defect form template, and perform the entry of the drainage facility data into the storage object logic model. Perform pipe network attribute verification, pipe network topology verification, data integrity and validity verification; identify the verified drainage facility data to be entered as entity table data and enter the data, so that the back-end can use the query language to import the newly entered entity table data of various types into the knowledge graph database according to the logical model of the storage object corresponding to each element class to store the drainage facility data and build a knowledge graph. The drainage facility data in the knowledge graph is temporal data with temporal attributes; generate batch data update requests based on the newly entered multiple entity table data for unified management and submission, set the approval data version and facility update information, and store and record the facility update information. The facility update information includes one or more of the project to which it belongs, the source of the data, the update type, the reason for the application, and the description of the change; The update approval module is specifically used to render the entity table data corresponding to the batch data update request on the map for the user to approve. When the approval instruction triggered by the user is received, the data in the knowledge graph database is updated to complete the dynamic update of the facility data.

[0063] Figure 2 The structural block diagram of the drainage facility data dynamic update system based on temporal data according to another embodiment of the present invention is schematically shown. Figure 2 In this embodiment, in addition to the batch data update module and the update approval module, the system also includes a map interactive update module, a data temporal management module, a map module and a statistical report module, wherein: The batch data update module is used to construct a data model for various types of drainage facility data, determine the entities, attributes and relationships contained in the knowledge graph to be constructed, and provide a specified structure of pipe points and pipelines, and detection defect data templates for operators to enter data during surveys; the obtained data results are configured with data entry verification parameters in accordance with the general drainage facility data verification standards, and the data results form is uploaded for data verification; if there is no objection to the verification results, a batch data update request is formed and submitted for application, and the back end uses the query language to import various types of data into the graph database according to the previously defined knowledge graph data model, stores the drainage facility data and constructs the knowledge graph; and supports the modification and resubmission of data update requests rejected by the update approval module.

[0064] The map interactive update module is used to request the latest data of various drainage facilities in the knowledge graph database at the current time, render it on the map by adding vectors, and interactively perform data update operations such as adding pipe points, adding pipelines, modifying points and lines, deleting points and lines, batch selection and editing on the map through click operations. It is summarized as data update requests for unified management and submission; and supports the modification and resubmission of data update requests rejected by the update approval module.

[0065] The update approval module is used to obtain the update data request submitted by the batch data update module and the map interactive update module, check the data update request details and render them on the map, and review the verification results; download the update details according to the needs, approve the data update request, and when the approval is passed, the data in the map database is updated to complete the dynamic update of the facility data; when it is not passed, it is rejected and supports filling in the rejection opinion and returning the rejection opinion to the batch data update module and the map interactive update module as the source of the request for modification; after the approval is completed, an update approval log is formed for future review of the approval details.

[0066] The data temporal management module is used to establish a mechanism for data temporal management of the data stored in the graph database so as to call the drainage facility data of any historical period in different scenarios.

[0067] A graph module is used to request the latest data of various drainage facilities in the knowledge graph database at the current time, and render it on the map by adding vectors; based on the data support of the data temporal management module, a timeline function is developed to switch the data time of the map; the time range and time interval are specified, and the program renders the drainage facility data within each time node to generate image frames that automatically merge and generate dynamic videos, intuitively showing users the historical evolution of the drainage facility data within the current viewing angle.

[0068] The statistical report module is used to generate administrative district, project, and road statistical information based on facility update records and screening conditions, and to generate horizontal comparison information on update status according to the specified period.

[0069] In this embodiment, the batch data update module includes a data model definition submodule, a data verification submodule, a data import submodule, a data update submission module, and a knowledge graph construction submodule, wherein: The data model definition submodule is based on the inventory data of pipe points, pipelines and detection defects in drainage facilities, analyzes the common fields and unique information of each element class, and decomposes them into logical models of storage objects for various types of pipe points, pipelines and detection defect data, establishes their entities, attributes and relationships, and organizes them into point and line form templates for operators to download and use, and to ensure the uniformity and standardization of data, sets content restrictions on some data items in various data subtables, sets specific filling content, and sets required data items in various data subtables to ensure the integrity of the data. Users must fill in the items in full as required, and the results serve as the prerequisite data basis for the data import submodule to enter system data.

[0070] The data verification submodule: in accordance with the general drainage facility data verification standards and formulas, configure the parameters for the pipe network data attribute and topology problem verification, and configure the parameters for the validity and integrity verification of the detection data; based on the configured verification parameters, the drainage facility data to be entered is verified for pipe network attributes, pipe network topology, and completeness and validity of the detection data. After the verification is completed, the statistical result tables for the pipe network and detection abnormal data verification are generated respectively. After the abnormal data is processed, the data is re-entered to ensure the accuracy and validity of the entered data.

[0071] The data import submodule obtains the file data of the drainage facility survey or inspection project to be entered according to the file format, file, and project name, receives the file filled with data based on the data template, parses the file according to the logical structure of the previously designed data template, obtains all attributes and spatial information of this batch of drainage facility data, generates an entity table and enters it into the drainage facility knowledge graph database.

[0072] The data update submission module: submits applications for batch data update requests with no objections to the verification results, selects the application approval data version, fills in the facility update details, including the project to which it belongs, data source, update type, reason for application, description of the change, designates the approver, and stores the details of the update operation in the data new temporal management submodule of the data temporal management module; supports modification and resubmission of data updates rejected by the update approval module.

[0073] The knowledge graph construction submodule: Converting drainage facility data into a knowledge graph is a process of converting structured data into a semantic network. The backend will import various types of data into the graph database through the query language of the entity table after data verification, so as to construct and store the knowledge graph.

[0074] Furthermore, the data model definition submodule includes a pipe network data model unit and a detection defect data model unit: The pipe network data model unit is used to determine the unique identification and connection relationship of the pipe point based on the stock data of the drainage facility pipe point and pipeline, and each pipe point or pipeline is regarded as an entity node. The unique identification and connection relationship of the pipe point are determined by the geophysical point number field, the position information is determined by the plane coordinate X and plane coordinate Y fields of the pipe point, the pipe point type is determined by the attachment field of the pipe point, and the update operation command to be performed is identified by the update type field of the pipe point; the unique identification and connection relationship of the pipeline are determined by the starting point geophysical point number field and the end point geophysical point number field, the position information of the starting point and the end point is determined by the corresponding geophysical point number, and the update operation command to be performed is identified by the update type field; the remaining field information of the pipe point and the pipeline is stored as the basis for auxiliary application and query statistics; The detection defect data model unit is used to take the inventory data of drainage facility detection defects as the basis, and each detection well defect or detection line defect as an entity node. The geophysical point number field is used as the unique identifier of the detection well defect and the belonging pipe well is determined, the problem type field is used to determine the category of the detected problem, and the update type field is used to identify the update operation command to be performed; the starting point geophysical point number field and the end point geophysical point number field are used to determine the unique identifier of the detection line defect and the belonging pipeline, the detected problem category is determined through the problem type field, and the distance from the starting point and the length involved in the defect are determined through the defect point distance field and the defect length field and rendered on the map accordingly; the remaining field information of the detection well defect and the detection line defect is stored as the basis for auxiliary application and query statistics.

[0075] Furthermore, the data verification submodule includes a pipe network attribute verification unit, a pipe network topology problem verification unit and a detection data verification unit.

[0076] In this embodiment, the map interactive update module includes a map editing submodule and an editing operation management submodule, wherein: The map editing submodule: obtains the latest data of various drainage facilities at the current time in the knowledge graph database, creates a map canvas for the latest data of the drainage facilities after matching with the map image data, and renders it on the map by adding vectors to form visual map data, and performs data update operations on the map through mouse interaction. The map editing submodule includes a new pipe point unit, a new pipeline unit, a point and line modification unit, a point and line deletion unit, and a batch selection unit, which is specifically used to trigger operation interactions on the map through the user end to add pipe points, add pipelines, modify pipe points, modify pipelines, delete pipe points, delete pipelines, and / or batch selection editing.

[0077] The editing operation management submodule: summarizes each operation request for adding, modifying, and deleting the point table and line table in the map editing submodule into a table, conducts unified management and attribute modification, and classifies them according to the standards of adding, modifying, deleting, or points and lines; generates map interactive update requests for multiple data update operations triggered by the user end on the map, and manages and submits them in a unified manner, selects the application approval data version, fills in the facility update details, including the project to which it belongs, the source of the data, the update type, the reason for the application, and the description of the change; supports the designation of approvers before submission, and stores the details of the update operation in the knowledge graph database after submission; when the system is exited without submission or cancellation, the business database stores the above operations; and modifies the data information rejected by the update approval module and resubmits it.

[0078] In this embodiment, the update approval module includes an update approval submodule and an update log submodule, wherein: The update approval submodule is used to retrieve the update request submitted by the batch data update module and the map interactive update module, check the data update request details and render them to form visual map update data after matching them with the map data. The verification results can be viewed and the update details can be downloaded. When the approval is determined to be passed, the data in the map database is updated to complete the dynamic update of the facility data. When the approval is determined to be not passed, it is rejected and supports filling in the rejection opinion and returning the rejection opinion to the batch data update module and the map interactive update module as the request source for modification.

[0079] The update log submodule is used to store the approval details as an update approval log after each approval is completed so that the approval details can be viewed later; the approval details can be searched according to the updater, update time, and approval status.

[0080] Furthermore, the update approval sub-module includes an update content basic information unit, a data verification result viewing unit, an update content map viewing unit, an update detail download unit and an approval operation unit, which are respectively used to realize update content visualization display, data verification result visualization display, update content map visualization display, download update details and approval operations.

[0081] In this embodiment, the data temporal management module includes a data addition temporal management submodule, a data deletion temporal management submodule, a data modification temporal management submodule and a data query temporal management submodule, wherein: The data newly added temporal management submodule is used to expand the temporal attributes of the drainage facility data to record time information before importing various entity table data into the knowledge graph database to build the knowledge graph. The time information includes the effective start time and the effective end time. The temporal management of the drainage facility data is realized by setting and / or updating the temporal attributes of the drainage facility data stored in the graph database. Specifically, the temporal management of the drainage facility data involves recording and processing the changes of the drainage facility data over time. This is very important for maintaining, planning and analyzing the evolution of local drainage facilities. If you want to manage the data temporally, you need to expand the data model when importing data during the knowledge graph construction, and record the time for each entity's automatic temporal attribute, that is, "effective start time (validFrom)" and "effective end time (validTo)"; after the data addition approval is passed for a certain data, the "effective start time" of the node takes the current time, and the "effective end time" defaults to positive infinity, which means that this data is born at the current time and will always exist if it is not operated afterwards.

[0082] The data deletion temporal management submodule is used to perform data deletion approval for a certain data. The backend finds all nodes of this entity in the knowledge graph according to the unique identifier (there can be multiple nodes because this drainage facility has been modified before and has multiple nodes with different effective times), and filters out the latest node with an "effective end time" after the current time. This node represents the drainage facility to be deleted at the current time. The "effective start time" of this node remains unchanged, and the "effective end time" is changed to the current time, indicating that this entity has disappeared at the current time.

[0083] The data modification temporal management submodule is used to perform data modification approval for a certain data. The backend finds all nodes of this entity in the knowledge graph according to the unique identifier (there can be multiple nodes because this drainage facility has been modified before and has multiple nodes with different effective times), and filters out the latest node with an "effective end time" after the current time. This node represents the drainage facility to be modified at the current time, and changes the "effective end time" of this node to the current time. A new node that meets the conditions is created in the knowledge graph according to the data modification request, and the "effective start time" of the new node is the current time. The "effective end time" defaults to positive infinity, indicating that this entity has been modified at the current time, and the new node becomes the latest data of this drainage facility.

[0084] The data query temporal management submodule is used to provide interface support for various data queries based on the temporal mechanism defined above in different application scenarios.

[0085] Furthermore, the data query temporal management submodule includes an unapproved data query unit, an approved log data query unit, a real-time data query unit and a historical data query unit, wherein: The unapproved data query unit is used for, when a user submits a user update request in the batch data update module and the map interactive update module, this batch of update record requests is received by the background interface and added to the knowledge graph to create relevant nodes, and a unique identifier of this submission is added to each node, and the approval status attribute value is increased by default to "pending approval", and the user completes the application operation; the approver logs in to the update approval module, and the update approval module matches the submission unique identifier of each node in the knowledge graph database according to the submission record unique identifier stored in the business library, so as to obtain all records corresponding to each submission, so that when the update approval module approves, the specific update content submitted each time can be called out and rendered on the map, and the verification results and update details can be provided according to the update content; when the user approves, if it is passed, the approval status field value of each node in this batch of data in the knowledge graph is modified to "approved", and if it is rejected, it is modified to "rejected", so that the update log submodule in the update approval module can be supported to filter out the drainage facility data involved in each approval, render it on the map, provide verification results and download update details according to the update content.

[0086] The approval log data query unit is used to obtain all nodes in the knowledge graph whose approval status attribute value is not "pending approval", and classify them according to the unique identifier of the submission record, so as to support the update log submodule of the update approval module to obtain all update records involved in all or a single approval.

[0087] The real-time data query unit is used to obtain all nodes of each type of data in the knowledge graph whose "effective end time" is after the current time, that is, the current real-time data of the drainage facility to be obtained.

[0088] The historical data query unit is used to specify a specific time and obtain all nodes containing the input time within the range of "valid start time" to "valid end time" for each type of data in the knowledge graph, that is, the data of the drainage facility at the specified time to be obtained.

[0089] In this embodiment, the one-picture module includes: Update the submodule of the thematic map, which is used to request the latest drainage facility data corresponding to the current time within the current viewing angle using the current time as the time condition, create a map canvas for the latest drainage facility data and render it by adding vectors; when symbolizing, use line segments with arrow directions to display pipeline data line elements, give three different colors according to the different values ​​of the drainage system type field, give different arrow direction materials according to the starting point geophysical exploration point number, the end point geophysical exploration point number and the flow direction, if the flow direction is "downstream", the arrow points from the starting point geophysical exploration point number to the end point geophysical exploration point number, if the flow direction is "upstream", the arrow points from the end point geophysical exploration point number to the starting point geophysical exploration point number; use point icons to display pipe point data point elements, give three different colors according to the different values ​​of the drainage system type field, and set different icons according to the different values ​​of the attachment type field; The data time switching submodule is used to request the historical drainage facility data of the current time node within the current viewing angle based on the data time switching operation triggered by the user on the preset timeline component, and to re-render all drainage facility layer services on the map based on the historical drainage facility data to display the overall situation of the drainage facility data at the selected time; The historical evolution video synthesis submodule is used to obtain the start time, end time and time interval set by the user, calculate the target time node corresponding to the image data contained in the video to be displayed according to the start time, end time and time interval, and use the target time node as the time condition to request the historical drainage facility data corresponding to each target time node within the current viewing angle in turn; create a map canvas for each historical drainage facility data obtained and render it for visualization by adding vectors, and after rendering, output the image of the component to generate an image file for each target time point and name it with the corresponding target time node; after all the image files of each target time node are generated, they are stored in the pipes folder, and the preset FFmpeg command is used to synthesize the image files of each target time node into a video in chronological order, and the generated video is returned to the user end for the user to play, display or download.

[0090] In this embodiment, the statistical report module includes: The pipe network statistics submodule is used to combine field conditions according to time, project, administrative area, and road, retrieve the pipe point and pipeline update records of the historical version library of drainage facility data under different field condition combinations, and count the pipe network data update data in different areas, roads, and road details. The pipe network data update data includes the number of updates N, the current total length of the pipe network Lz, the newly added length La, the deleted length Ld, and the modified length Lu; The calculation model of the current total length of the pipeline network Lz is: Where i is the number of pipelines that meet the screening conditions at the end time, The geometric length of each pipeline that meets the screening conditions at the end time; The calculation model of the additional length La is: in, is the number of pipelines that meet the screening conditions at the end time, is the geometric length of each pipeline that meets the screening conditions at the end time, is the number of pipelines that meet the screening conditions at the start time, The geometric length of each pipeline that meets the screening conditions at the start time; The calculation model of the deletion length Ld is: Among them, i is the number of pipeline records with update type of "delete" in the drainage facility data history version library that meet the screening conditions within the range from the start time to the end time. are the geometric lengths of the pipelines deleted above; The calculation model of the modified length Lu is: Where i is the number of pipeline records with update type "modified" in the drainage facility data history version library that meet the screening conditions within the time range from the start time to the end time. is the geometric length of each modified pipeline; s is the number of categories of pipeline unique identifiers in the pipeline records with update type "modified" within the range from the start time to the end time in the historical version library of drainage facility data that meet the screening conditions, is the geometric length of the pipeline with a repeated unique identifier under the above condition; and is the number of times this unique identifier appears under this condition; The statistical comparison submodule is used to combine field conditions according to time, project, administrative area, and road, generate horizontal comparison information of pipeline network data update data at intervals of years, half years, quarters, and months, and return it to the user end in a graphical form for display by the user.

[0091] As for the system embodiment, since it is basically similar to the method embodiment, the description is relatively simple, and the relevant parts can be referred to the partial description of the method embodiment.

[0092] The system embodiment described above is merely illustrative, wherein the units described as separate components may or may not be physically separated, and the components shown as units may or may not be physical units, that is, they may be located in one place, or they may be distributed on multiple network units. Some or all of the modules may be selected according to actual needs to achieve the purpose of the solution of this embodiment. Those of ordinary skill in the art may understand and implement it without creative work.

[0093] In addition, another embodiment of the present invention also provides a drainage facility data dynamic update device based on temporal data, including a memory, a processor, and a computer program / instructions stored in the memory and executable on the processor, and the processor executes the computer program / instructions to implement the steps of the drainage facility data dynamic update method based on temporal data as described above.

[0094] The method, system and equipment for dynamically updating drainage facility data based on temporal data provided in the embodiments of the present invention construct data models for various types of drainage facility data, determine the entities, attributes and relationships contained in the knowledge graph to be constructed, and provide a specified structure of pipe point and pipeline, and detection defect data form template for users to enter data to generate unified standard drainage facility data to be entered, and import the data into the knowledge graph database to store the drainage facility data and construct the knowledge graph. The drainage facility data in the knowledge graph is temporal data with temporal attributes, which realizes the dynamic update of drainage facility temporal data and the management of historical data versions of drainage facilities through the association relationship of the knowledge graph, and realizes unified digital management of urban drainage facility big data throughout the entire cycle, so that real and effective drainage facility data from different periods can be integrated and shared on multiple platforms, laying a good data foundation for the in-depth application of smart water services in different industries, and making the operation and management of drainage facilities more scientific and efficient.

[0095] In addition, those skilled in the art will appreciate that, although some embodiments herein include certain features included in other embodiments but not other features, the combination of features of different embodiments is meant to be within the scope of the present invention and form different embodiments. For example, any one of the claimed embodiments may be used in any combination.

[0096] Finally, it should be noted that the above embodiments are only used to illustrate the technical solutions of the present invention, rather than to limit it. Although the present invention has been described in detail with reference to the aforementioned embodiments, those skilled in the art should understand that they can still modify the technical solutions described in the aforementioned embodiments, or make equivalent replacements for some of the technical features therein. However, these modifications or replacements do not deviate the essence of the corresponding technical solutions from the spirit and scope of the technical solutions of the embodiments of the present invention.

Claims

1. A method for dynamically updating drainage facility data based on temporal data, characterized in that: The method comprises: Data analysis is performed on the preset drainage facility inventory data to extract the common information fields and unique information fields of the element classes corresponding to the pipe points, pipelines, detection well defects and detection line defects in the drainage facility inventory data, and the storage object logic model corresponding to each element class is constructed according to the common information fields and unique information fields of the element classes corresponding to the pipe points, pipelines, detection well defects and detection line defects, and the pipe point data form template, pipeline data form template, detection well defect form template and detection line defect form template are generated; Acquire the drainage facility data to be entered generated based on the pipe point data form template, the pipeline data form template, the detection well defect form template and / or the detection line defect form template, and perform pipe network attribute verification, pipe network topology verification, data integrity and validity verification on the drainage facility data to be entered; The verified drainage facility data to be entered are identified as entity table data and entered, so that the back-end can use the query language to import the newly entered entity table data of various types into the knowledge graph database according to the storage object logic model corresponding to each element class to store the drainage facility data and construct a knowledge graph. The drainage facility data in the knowledge graph is temporal data with temporal attributes; Generate batch data update requests based on multiple newly entered entity table data for unified management and submission, set approval data version and facility update information, and store and record the facility update information, where the facility update information includes one or more of the project, data source, update type, application reason, and change description; The entity table data corresponding to the batch data update request is rendered on the map for the user to approve. When the approval instruction triggered by the user is received, the data in the knowledge graph database is updated to complete the dynamic update of the facility data.

2. The method according to claim 1, characterized in that The drainage facility inventory data includes drainage facility pipe point and pipeline inventory data and drainage facility detection defect inventory data; The method of constructing a storage object logic model corresponding to each element class according to the common information fields and the unique information fields of the element classes corresponding to the pipe points, pipelines, detection well defects and detection line defects respectively includes: Based on the inventory data of drainage facility pipe points and pipelines, each pipe point or pipeline is regarded as an entity node. The unique identification and connection relationship of the pipe point are determined through the geophysical point number field, the position information is determined through the plane coordinate X and plane coordinate Y fields of the pipe point, the pipe point type is determined through the attachment field of the pipe point, and the update operation command to be performed is identified through the update type field of the pipe point; the unique identification and connection relationship of the pipeline is determined through the starting point geophysical point number field and the end point geophysical point number field, the position information of the starting point and the end point is determined through the corresponding geophysical point number, and the update operation command to be performed is identified through the update type field; the remaining field information of the pipe point and the pipeline is stored as the basis for auxiliary application and query statistics; Based on the inventory data of drainage facility detection defects, each detection well defect or detection line defect is taken as an entity node. The geophysical point number field is used as the unique identifier of the detection well defect and the pipe well to which it belongs is determined. The problem type field is used to determine the category of the detected problem. The update type field is used to identify the update operation command to be performed. The starting point geophysical point number field and the end point geophysical point number field are used to determine the unique identifier of the detection line defect and the pipeline to which it belongs. The problem type field is used to determine the category of the detected problem. The defect point distance field and the defect length field are used to determine the distance from the starting point and the length involved in the defect and render them on the map accordingly. The remaining field information of the detection well defect and the detection line defect is stored as the basis for auxiliary application and query statistics.

3. The method according to claim 1, characterized in that The method further comprises: Obtain the latest data of various drainage facilities in the knowledge graph database at the current time, create a map canvas for the latest data of drainage facilities and render it on the map by adding vectors to form visual map data; The user terminal triggers interactive operations on the map to add new pipe points, add new pipelines, modify pipe points, modify pipelines, delete pipe points, delete pipelines and / or batch select and edit. Multiple data update operations triggered by the user terminal on the map generate map interactive update requests for unified management and submission, and set the approval data version and facility update information; The drainage facility update data corresponding to the map interactive update request is rendered on the map for the user to approve. When the approval instruction triggered by the user is received, the data in the knowledge graph database is updated to complete the dynamic update of the facility data.

4. The method according to claim 3, characterized in that The method further comprises: Add the entity table data corresponding to the batch data update request and / or the drainage facility update data corresponding to the map interactive update request to the knowledge graph to create relevant nodes, add a unique identifier for this submission to each node, and increase the approval status field value to "pending approval" by default, so that the user end can match the unique identifier of each node in the knowledge graph database according to the unique identifier in the approval submission record stored in the business library, so as to obtain all pending approval records corresponding to each data update request; When an approval instruction triggered by the user is received, the approval status field value of each node corresponding to this batch data update request in the knowledge graph is modified to "Approved". When an approval rejection instruction triggered by the user is received, the approval status field value of each node corresponding to this batch data update request in the knowledge graph is modified to "Rejected".

5. The method according to claim 1, characterized in that The method further comprises: Before importing various entity table data into the knowledge graph database to construct the knowledge graph, the temporal attributes are extended for the drainage facility data to record time information, wherein the time information includes a valid start time and a valid end time, and the temporal management of the drainage facility data is realized by setting and / or updating the temporal attributes of the drainage facility data stored in the graph database; The nodes whose "effective end time" of drainage facility data in the knowledge graph is after the current time are regarded as the latest drainage facility data corresponding to the current time; The nodes containing the specified historical time within the range of "effective start time" to "effective end time" of the drainage facility data in the knowledge graph are taken as the historical data of the drainage facility at the specified time.

6. The method according to claim 5, characterized in that The temporal management of drainage facility data by setting and / or updating the temporal attributes of the drainage facility data stored in the graph database includes: When any drainage facility data is approved for data addition, the node's "Effective Start Time" is set to the current time and the "Effective End Time" is set to positive infinity; When the data deletion of any drainage facility data is approved, all nodes of the corresponding entity in the knowledge graph are found according to the unique identifier of the current drainage facility data, and the nodes whose "effective end time" is after the current time are filtered out, the "effective start time" of the current node is kept unchanged, and the "effective end time" of the current node is updated to the current time; When the data modification of any drainage facility data is approved, all nodes of the corresponding entity in the knowledge graph are found according to the unique identifier of the current drainage facility data, and the nodes whose "effective end time" is after the current time are filtered out. The "effective end time" of the current node is updated to the current time, and a new node that meets the conditions is created in the knowledge graph according to the data modification request, and the "effective start time" of the new node is set to the current time and the "effective end time" is set to positive infinity.

7. The method according to claim 1, characterized in that After the data in the knowledge graph database is updated to complete the dynamic update of the facility data, the method further includes: Use the current time as the time condition to request the latest drainage facility data corresponding to the current time within the current viewing angle, create a map canvas for the latest drainage facility data and render it by adding vectors; when symbolizing, use line segments with arrow directions to display pipeline data line features, give three different colors according to the different values ​​of the drainage system type field, give different arrow direction materials according to the starting point geophysical exploration point number, the end point geophysical exploration point number and the flow direction, if the flow direction is "downstream", the arrow points from the starting point geophysical exploration point number to the end point geophysical exploration point number, if the flow direction is "upstream", the arrow points from the end point geophysical exploration point number to the starting point geophysical exploration point number; use point icons to display pipe point data point features, give three different colors according to the different values ​​of the drainage system type field, and set different icons according to the different values ​​of the attachment type field; and / or Based on the data time switching operation triggered by the user on the preset timeline component, the switched time node is used as the time condition to request the historical drainage facility data of the current time node within the current viewing range, and all drainage facility layer services on the map are re-rendered according to the historical drainage facility data to display the overall situation of the drainage facility data at the selected time; and / or Get the start time, end time and time interval set by the user, calculate the target time node corresponding to the image data contained in the video to be displayed according to the start time, end time and time interval, and use the target time node as the time condition to request the historical drainage facility data corresponding to each target time node within the current viewing angle in turn; create a map canvas for each historical drainage facility data obtained and render it for visualization by adding vectors, after rendering, output the image of the component to generate an image file for each target time point and name it with the corresponding target time node; after all the image files of each target time node are generated, store them in the pipes folder, use the preset FFmpeg command to synthesize the image files of each target time node into a video in chronological order, and return the generated video to the user end for the user to play, display or download.

8. The method according to claim 1, characterized in that After the data in the knowledge graph database is updated to complete the dynamic update of the facility data, the method further includes: Combine field conditions according to time, project, administrative area, and road, retrieve the historical update records of drainage facility data under different field condition combinations, and count the updated data of pipe network data in different areas, roads, and road details. The updated data of pipe network data includes the number of updates N, the current total length of the pipe network Lz, the newly added length La, the deleted length Ld, and the modified length Lu; and / or By combining field conditions according to time, project, administrative area, and road, horizontal comparison information of pipeline network data update data at intervals of year, half year, quarter, and month is generated and returned to the user end in a graphical form for display by the user.

9. A drainage facility data dynamic update system based on temporal data, characterized in that: The method comprises a functional module for implementing the method according to any one of claims 1 to 8.

10. A drainage facility data dynamic update device based on temporal data, comprising a memory, a processor, and a computer program / instruction stored in the memory and executable on the processor, characterized in that: The processor executes the computer program / instructions to implement the steps of the method according to any one of claims 1-8.

Images