Flood data association management method and system

Abstract

The invention relates to a flood data association management method and system. The flood data association management method comprises the following steps: acquiring direct related data of a target session flood; acquiring a plurality of historical meteorological and hydrological data related to the target session flood; inputting the historical meteorological and hydrological data into a flood simulation module in different combination forms for flood simulation; the simulation result is compared with direct related data of the flood of the target session; dividing the historical meteorological and hydrological data into key factor data and increment factor data according to a comparison result; and first-level association is established between the target session flood and the key factor data, and second-level association is established between the target session flood and the increment factor data. The association level of the flood data and the meteorological and hydrological data is clearer, and management and redisk of the flood data are facilitated in some implementation processes.

Description

Technical Field

[0001] The present invention relates to the field of flood data management, and in particular to a flood data association management method and system. Background Art

[0002] Floods are a common natural disaster, and recording flood data is of great significance for flood prevention and disaster reduction. Generally speaking, before a flood occurs, it is possible to evaluate and warn of possible flood disasters by real-time monitoring of water levels, flow rates and other data, using mathematical models and computer calculations. After a disaster, the preservation and analysis of monitoring data of the flood process can accurately assess the intensity, scope and duration of the flood, thereby analyzing the impact of the flood and providing a reference for post-disaster reconstruction and future prevention and control.

[0003] However, current flood data management often records flood data itself, but the relationship with other related meteorological data is not clear enough, which is not conducive to more detailed data analysis and prediction. Summary of the invention

[0004] The purpose of this application is to propose a flood data association management method and system to solve the problem that the association between flood data management and other related meteorological data is not clear enough, which is not conducive to more sophisticated data analysis and prediction.

[0005] The flood data association management method of the present application includes: Obtain directly relevant data of the target flood; Acquire a plurality of historical meteorological and hydrological data related to the target flood; Inputting the historical meteorological and hydrological data into a flood simulation module in different combinations to perform flood simulation; Comparing the simulation results with the directly relevant data of the target flood; According to the comparison results, the historical meteorological and hydrological data are divided into key factor data and incremental factor data; A primary association is established between the target flood event and the key factor data, and a secondary association is established between the target flood event and the incremental factor data.

[0006] Optionally, the step of inputting the historical meteorological and hydrological data into a flood simulation module in different combinations to perform flood simulation includes: Taking a target number of the historical meteorological and hydrological data in different combinations to perform flood simulation until a simulated flood of the same scale as the target flood is formed; If the target number of historical meteorological and hydrological data cannot form a simulated flood of the same scale as the target flood, the target number will be gradually increased until a simulated flood of the same scale as the target flood is formed.

[0007] Optionally, dividing the historical meteorological and hydrological data into key factor data and incremental factor data includes: When forming a simulated flood of the same scale as the target flood, the historical meteorological and hydrological data used are divided into key factor data; The remaining unused historical meteorological and hydrological data are divided into incremental factor data.

[0008] Optionally, taking a target number of the historical meteorological and hydrological data in different combinations to perform flood simulation includes: Obtaining benchmark flood simulation parameters; A corresponding number of parameters in the benchmark flood simulation parameters are replaced with values ​​of the historical meteorological and hydrological data in different combinations to perform flood simulation.

[0009] Optionally, when comparing the simulation result with the directly related data of the target flood, if the following conditions occur, it is determined that a simulated flood of the same scale as the target flood is formed: The flood element recurrence period of the simulated flood and the target flood is at the same level; or, The difference between the recurrence period of flood elements of the simulated flood and the target flood is less than a set threshold.

[0010] Optionally, establishing a primary association between the target flood event and the key factor data includes any of the following: The key factor data is stored in a database of the target flood; The data form of the target flood event is associated with the complete data form corresponding to the key factor data.

[0011] Optionally, the flood data association management method further includes: The simulation results of the flood simulation are associated with the target flood and stored.

[0012] Optionally, establishing a secondary association between the target flood event and the incremental factor data includes: Normalizing the incremental factor data corresponding to each simulation process into water volume incremental data; The water volume increment data is associated with the corresponding simulation results.

[0013] Optionally, the acquiring of a plurality of historical meteorological and hydrological data related to the target flood includes at least one of the following: Obtaining precipitation data within a time range corresponding to the target flood; Obtain the basin flow data within the time range corresponding to the target flood.

[0014] On the other hand, the present application also provides a flood data association management system, including: A data acquisition module, used to acquire directly relevant data of a target flood and to acquire a plurality of historical meteorological and hydrological data related to the target flood; A flood simulation module, used for performing flood simulation using the historical meteorological and hydrological data in different combinations; A result comparison module, used to compare the simulation results with the directly relevant data of the target flood and divide the historical meteorological and hydrological data into key factor data and incremental factor data according to the comparison results; The association management module is used to establish a primary association between the target flood and the key factor data, and to establish a secondary association between the target flood and the incremental factor data.

[0015] The flood data association management method provided in the present application performs flood simulation by inputting historical meteorological and hydrological data into a flood simulation module in different combinations; the simulation results are compared with the directly relevant data of the target flood, and the historical meteorological and hydrological data are divided into key factor data and incremental factor data according to the comparison results. The distinction between key factor data and incremental factor data is achieved, so that the two are managed in different associations. Since there is actual flood data to provide a reference, the effect of simulation based on the actual data is usually better, and the accuracy of flood simulation is higher, so the distinction between key factor data and incremental factor data is accurate. Establishing different associations between key factor data and incremental factor data and floods makes the association level between flood data and meteorological and hydrological data clearer, which is helpful for the management and review of flood data in some implementation processes. BRIEF DESCRIPTION OF THE DRAWINGS

[0016] Figure 1 A schematic diagram of the basic flow of the flood data association management method according to the first embodiment of the present application; Figure 2 The detailed process diagram of the flood data association management method of the first embodiment of the present application is as follows: Figure 1 ; Figure 3 The detailed process diagram of the flood data association management method of the first embodiment of the present application is as follows: Figure 2 ; Figure 4The detailed process diagram of the flood data association management method of the first embodiment of the present application is as follows: Figure 3 ; Figure 5 The detailed process diagram of the flood data association management method of the first embodiment of the present application is as follows: Figure 4 ; Figure 6 This is a structural diagram of the flood data association management system of Example 1 of the present application. DETAILED DESCRIPTION

[0017] In order to enable those skilled in the art to better understand the scheme of the present invention, the technical scheme in the embodiments of the present invention will be clearly and completely described below in conjunction with the drawings in the embodiments of the present invention. Obviously, the described embodiments are only part of the embodiments of the present invention, not all of the embodiments. Based on the embodiments of the present invention, all other embodiments obtained by ordinary technicians in this field without creative work should fall within the scope of protection of the present invention.

[0018] It should be noted that the terms "first", "second", etc. in the specification and claims of the present invention and the above-mentioned drawings are used to distinguish similar objects, and are not necessarily used to describe a specific order or sequence. It should be understood that the data used in this way can be interchanged where appropriate, so that the embodiments of the present invention described herein can be implemented in an order other than those illustrated or described herein. In addition, the terms "including" and "having" and any variations thereof are intended to cover non-exclusive inclusions, for example, a process, method, system, product or device that includes a series of steps or units is not necessarily limited to those steps or units that are clearly listed, but may include other steps or units that are not clearly listed or inherent to these processes, methods, products or devices.

[0019] Embodiment 1: In order to make the relationship between flood data clearer, so as to facilitate future data analysis and disaster prediction, this embodiment provides a flood data association management method. The method of this embodiment obtains historical meteorological and hydrological data and divides them into key factor data and incremental factor data to form different levels of association, so as to make the association between flood data and related meteorological and hydrological data clearer, which is conducive to data analysis and management.

[0020] See also Figure 1 As shown, the steps of the flood data association management method provided in this embodiment include: S101, obtaining directly relevant data of the target flood; The directly relevant data of the target flood refers to the data reflecting the impact of the flood, that is, the data corresponding to the intensity, scope and duration of the flood. For example, the basic indicators that directly reflect the scale and duration of the flood are the peak water level, total flood volume and flood duration.

[0021] Of course, the directly relevant data that can be obtained in this embodiment may be data during the entire duration of the target flood.

[0022] S102, obtaining a plurality of historical meteorological and hydrological data related to the target flood; The historical meteorological and hydrological data referred to in this embodiment are the meteorological and hydrological data that may be relevant and monitored before and during the occurrence of the corresponding flood, such as the precipitation before and during the flood, the water volume of the relevant river basin before the flood, etc.

[0023] In the current flood management method, all possible relevant historical meteorological and hydrological data are usually stored indiscriminately. When analyzing floods, all precipitation and water volume data in the relevant time period and range are searched accordingly.

[0024] The flood data association management method of this embodiment will perform differentiated association on these historical meteorological and hydrological data in subsequent steps to facilitate the management of flood data.

[0025] S103, inputting historical meteorological and hydrological data into a flood simulation module in different combinations to perform flood simulation; It should be noted that, unlike traditional flood prediction and early warning simulations, the flood data association management method of this embodiment is to re-input historical meteorological and hydrological data into the flood simulation module for simulation after the flood occurs. Since there is actual flood data for reference, the simulation effect based on the actual data is usually better and more accurate.

[0026] Of course, the purpose of this embodiment is not to improve the accuracy of flood simulation, but to achieve better data management based on a more accurate simulation structure. In this embodiment, historical meteorological and hydrological data are input into the flood simulation module in different combinations. That is, this embodiment will only use a part of the historical meteorological and hydrological data to verify the impact of different historical meteorological and hydrological data on the flood of this event.

[0027] The flood data association management method of this embodiment can be applied to a GIS (Geographic Information System) system with a flood simulation module or other dedicated flood simulation software.

[0028] S104, comparing the simulation results with the directly relevant data of the target flood; Aspects to be compared include but are not limited to data such as the intensity and impact range of the simulated flood and the target flood.

[0029] S105. According to the comparison result, the historical meteorological and hydrological data are divided into key factor data and incremental factor data; Specifically, if the simulated flood is similar to the target flood, the historical meteorological and hydrological data used in the simulation process are key factor data, and the remaining historical meteorological and hydrological data are incremental factor data.

[0030] In fact, in the process of flood formation, some factors have a decisive influence, such as a large amount of precipitation. In practical applications, some small amounts of precipitation or an increase in water volume are not the decisive factors leading to the formation of floods, but they mainly lead to the expansion of the final scale of floods. Based on the flood simulation, this embodiment divides the historical meteorological and hydrological data into key factor data and incremental factor data, which can help find the main reasons for the formation of the target flood, and is conducive to the management and analysis of flood data.

[0031] S106, establishing a primary association between the target flood and the key factor data, and establishing a secondary association between the target flood and the incremental factor data; Establishing different associations between key factor data and incremental factor data and floods makes the association level between flood data and meteorological and hydrological data clearer, which is helpful for data management and review in some implementation processes.

[0032] In practical applications, different association levels can be expressed as different identifiers, and different association levels can also adopt different methods in data storage form or storage structure. For example, the first-level association associates more complete data, while the second-level association can simplify the associated data.

[0033] like Figure 2 As shown, in some embodiments, the step of inputting historical meteorological and hydrological data in different combinations into the flood simulation module for flood simulation may specifically include: S201, taking a target number of historical meteorological and hydrological data in different combinations to perform flood simulation, until a simulated flood with a scale equivalent to that of the target flood is formed; There are multiple historical meteorological and hydrological data corresponding to a flood. For example, the target number can be 1 as the initial value. Then, one historical meteorological and hydrological data is taken each time for flood simulation to determine whether a simulated flood with the same scale as the target flood can be formed. In this process, all historical meteorological and hydrological data are traversed.

[0034] Of course, in practical applications, the simulation can be started with historical meteorological and hydrological data with a greater degree of influence, which helps to reduce the number of simulations. If the historical meteorological and hydrological data cannot form a simulated flood of the same scale as the target flood, it can be considered that other historical meteorological and hydrological data cannot form a simulated flood of the same scale.

[0035] S202, if the target number of historical meteorological and hydrological data cannot form a simulated flood of the same scale as the target flood, gradually increase the target number until a simulated flood of the same scale as the target flood is formed; For example, when using one historical meteorological and hydrological data, if none of the historical meteorological and hydrological data can generate a simulated flood of the same magnitude as the target flood, then a combination of two historical meteorological and hydrological data will be used for trial. This process will be repeated until a simulated flood of the same magnitude as the target flood can be generated.

[0036] Among them, see Figure 3 As shown in the figure, when a simulated flood with the same scale as the target flood can be simulated, the historical meteorological and hydrological data are divided into key factor data and incremental factor data, including: S301, when forming a simulated flood of the same scale as the target flood, the historical meteorological and hydrological data used are divided into key factor data; S302, dividing the remaining unused historical meteorological and hydrological data into incremental factor data; As a specific example, assume that the historical meteorological and hydrological data include precipitation data 1, precipitation data 2, precipitation data 3, and precipitation data 4. If only precipitation data 1 and precipitation data 2 are output to the flood simulation module, a simulated flood with the same scale as the target flood is formed. Then, precipitation data 1 and precipitation data 2 are divided into key factor data, and precipitation data 3 and precipitation data 4 that are not used in this simulation process are divided into incremental factor data. Of course, in actual applications, historical meteorological and hydrological data, in addition to precipitation data, can also include other data such as the water volume of the basin before the flood, and the division and judgment methods of these data are the same.

[0037] In the process of flood simulation, except for the data input according to the historical meteorological and hydrological data, the rest of the data can use the benchmark simulation parameters. For example, for the water volume of the relevant basin, when the corresponding historical meteorological and hydrological data is not input, a benchmark value is used. For precipitation data, if it is not input, 0 can be used as the benchmark value. The determination of these benchmark values ​​can also be determined based on the situation when no floods occurred in the same period of history. For example, the precipitation data can use the average precipitation when no floods occurred in the same period of history as the benchmark value, and the water volume of the relevant basin uses the average water volume when no floods occurred in the same period of history.

[0038] It can be seen that Figure 4 As shown, the steps of taking a target number of historical meteorological and hydrological data in different combinations to perform flood simulation may include: S401, obtaining benchmark flood simulation parameters; The benchmark flood simulation parameters here are the benchmark values ​​mentioned above.

[0039] S402, replacing corresponding numbers of parameters in the benchmark flood simulation parameters with values ​​of historical meteorological and hydrological data in different combinations to perform flood simulation; Corresponding to the selected historical meteorological and hydrological data, the historical meteorological and hydrological data are used for simulation, and the rest are the values ​​in the benchmark flood simulation parameters. In this way, the main causes of the corresponding floods can be determined during the simulation process.

[0040] In some embodiments, the standard for forming a simulated flood of the same magnitude as the target flood can be determined by evaluating whether the intensity of the flood is comparable. The flood element recurrence period is a common way to judge the intensity of a flood, which refers to the frequency or period of flood occurrence. Floods can be divided into different levels according to different recurrence periods. Therefore, by comparing the flood element recurrence periods of the simulated flood and the target flood, it can be determined whether the magnitude of the two is comparable.

[0041] In this embodiment, when the simulation results are compared with the directly related data of the target flood, if the following conditions occur, it is determined that a simulated flood of the same scale as the target flood is formed: Case 1: The recurrence period of flood elements of the simulated flood and the target flood is at the same level.

[0042] Case 2: The difference between the recurrence period of flood elements of the simulated flood and the target flood is less than the set threshold.

[0043] Among them, the level of flood element return period is divided into: ‌Return period less than 5 years‌: This type of flood is defined as ‌Minor Flood‌. ‌Return period between 5 and 20 years‌: This belongs to the category of ‌Medium Flood‌. ‌Return period between 20 and 50 years‌: This belongs to ‌Major Flood‌. ‌Return period greater than 50 years‌: This is classified as ‌Extreme Flood‌. In the case of the same level as the target flood, for example, both are minor floods, then the two are considered to be of similar size.

[0044] Case 2 is relatively flexible and has higher accuracy in some implementation processes. For example, the threshold can be set to 3 years. When the difference in the recurrence period of flood elements is within 3 years, the two are considered to be of similar size. Of course, the set threshold can be adjusted by the user according to needs. It is understandable that since Case 2 can mainly adjust the set threshold flexibly, its recognized benchmark is more stringent in some implementation processes, which helps to make a more rigorous comparison of the flood scale and make the final result more accurate.

[0045] In some implementations, establishing a primary association between the target flood event and the key factor data includes any of the following methods: Method 1: Storing key factor data in the database of the target flood; Method 2: Associate the data form of the target flood with the complete data form corresponding to the key factor data.

[0046] In traditional flood data management, users are often required to query the corresponding meteorological data and hydrological data by themselves according to the event or location of the flood. Even if the relevant meteorological data and hydrological data of the flood are recorded, users are required to go to the corresponding database for query. The above method 1 stores the key factor data in the database of the target flood, so that users can directly retrieve the relevant meteorological data and hydrological data in the system for viewing. The above method 1 associates the data form of the target flood with the complete data form of the key factor data, helping users to directly filter out the data form most relevant to the flood, and utilizing the user's query management. The above association method is only an example of this embodiment. In actual applications, other association forms can be selected as needed.

[0047] In some implementation processes, the simulation results of flood simulation can also be stored in association with the target flood. Since the actual historical meteorological and hydrological data are used in the flood simulation process, but the simulation is performed through different data volumes and combinations, flood simulation results that are different from the actual flood are also formed. These flood simulation results are based on the actual situation but are not exactly the same, which can provide more data references and support for flood prevention and control. Storing the simulation results of flood simulation in association with the target flood can help prevention and control personnel to conduct further review and management.

[0048] like Figure 5 As shown, in this embodiment, establishing a secondary association between the target flood and the incremental factor data includes: S501, normalizing the incremental factor data corresponding to each simulation process into water volume incremental data; S502, associating the water volume increment data with the corresponding simulation results; It should be understood that the water volume increment data reflects the increase in flood water volume that will be caused by the incremental factor data. For example, based on the range and amount of a certain precipitation, the total amount of water that may be brought by the precipitation can be calculated. For example, based on the water volume measured in the basin, the difference between the actual water volume and the benchmark value used in flood simulation can be calculated, and this difference is the water volume increment data that can be formed by the incremental factor data. It can be understood that these incremental factor data are data that are not used in the flood simulation process, and the scale of the simulated flood formed will be smaller than the scale of the actual flood. On the basis of the simulated flood, if these water volume increment data are added, a result close to the actual flood can be obtained.

[0049] This embodiment normalizes these incremental factor data into water volume incremental data, and performs association management with water volume incremental data. This can simplify the complexity of data association and avoid directly associating a single flood with a large amount of meteorological data and hydrological data. At the same time, normalization into water volume incremental data also retains the effective information of the corresponding flood.

[0050] In this embodiment, obtaining multiple historical meteorological and hydrological data related to the target flood includes at least one of the following: Obtain precipitation data within the time range corresponding to the target flood; Obtain the basin flow data within the time range corresponding to the target flood.

[0051] It is understandable that the above precipitation data and basin flow data are data within the relevant range of the target flood and the relevant basin and its upstream. The precipitation data and basin flow data can basically reflect the formation of the flood. However, in actual applications, more data can be added to achieve a richer and more accurate flood data management effect.

[0052] This embodiment also provides a flood data association management system 100, see Figure 6 , the flood data association management system 100 includes: The data acquisition module 101 is used to acquire the data directly related to the target flood and to acquire a plurality of historical meteorological and hydrological data related to the target flood; The flood simulation module 102 is used to simulate floods using historical meteorological and hydrological data in different combinations; A result comparison module 103 is used to compare the simulation results with the directly related data of the target flood and divide the historical meteorological and hydrological data into key factor data and incremental factor data according to the comparison results; The association management module 104 is used to establish a primary association between the target flood event and the key factor data, and to establish a secondary association between the target flood event and the incremental factor data.

[0053] The specific steps that can be executed by the modules in the flood data association management system 100 of this embodiment can also refer to the description of the flood data association management method provided in the above embodiment, which will not be described in detail in this embodiment.

[0054] In addition, although exemplary embodiments have been described herein, the scope includes any and all embodiments based on the present disclosure that are equivalent, modified, omitted, combined (e.g., various embodiments intersecting), adapted or changed. It is not limited to the examples described in this specification or during the implementation of this application, and its examples will be interpreted as non-exclusive.

[0055] The above description is intended to be illustrative rather than restrictive. For example, the above examples (or one or more of them) can be used in combination with each other. For example, those of ordinary skill in the art may use other embodiments when reading the above description.

[0056] The above are only preferred embodiments of the present invention and are not intended to limit the present invention. For those skilled in the art, the embodiments of the present invention may have various modifications and variations. Any modification, equivalent replacement, improvement, etc. made within the spirit and principle of the present invention shall be included in the protection scope of the present invention.

Claims

1. A flood data association management method, characterized in that: include: Obtain directly relevant data of the target flood; Acquire a plurality of historical meteorological and hydrological data related to the target flood; Inputting the historical meteorological and hydrological data into a flood simulation module in different combinations to perform flood simulation; Comparing the simulation results with the directly relevant data of the target flood; According to the comparison results, the historical meteorological and hydrological data are divided into key factor data and incremental factor data; A primary association is established between the target flood event and the key factor data, and a secondary association is established between the target flood event and the incremental factor data.

2. The flood data association management method according to claim 1, characterized in that: The step of inputting the historical meteorological and hydrological data into the flood simulation module in different combinations to perform flood simulation includes: Taking a target number of the historical meteorological and hydrological data in different combinations to perform flood simulation until a simulated flood of the same scale as the target flood is formed; If the target number of historical meteorological and hydrological data cannot form a simulated flood of the same scale as the target flood, the target number will be gradually increased until a simulated flood of the same scale as the target flood is formed.

3. The flood data association management method according to claim 2, characterized in that: The dividing of the historical meteorological and hydrological data into key factor data and incremental factor data comprises: When forming a simulated flood of the same scale as the target flood, the historical meteorological and hydrological data used are divided into key factor data; The remaining unused historical meteorological and hydrological data are divided into incremental factor data.

4. The flood data association management method according to claim 2, characterized in that: The method of taking a target number of historical meteorological and hydrological data in different combinations to perform flood simulation includes: Obtaining benchmark flood simulation parameters; A corresponding number of parameters in the benchmark flood simulation parameters are replaced with values ​​of the historical meteorological and hydrological data in different combinations to perform flood simulation.

5. The flood data association management method according to claim 2, characterized in that: When comparing the simulation results with the directly related data of the target flood, if the following conditions occur, it is determined that a simulated flood of the same scale as the target flood is formed: The flood element recurrence period of the simulated flood and the target flood is at the same level; or, The difference between the recurrence period of flood elements of the simulated flood and the target flood is less than a set threshold.

6. The flood data association management method according to claim 1, characterized in that: Establishing a primary association between the target flood event and the key factor data includes any of the following: The key factor data is stored in a database of the target flood; The data form of the target flood event is associated with the complete data form corresponding to the key factor data.

7. The flood data association management method according to any one of claims 1 to 6, characterized in that: The flood data association management method further comprises: The simulation results of the flood simulation are associated with the target flood and stored.

8. The flood data association management method according to claim 7, characterized in that: The establishing of a secondary association between the target flood event and the incremental factor data includes: Normalizing the incremental factor data corresponding to each simulation process into water volume incremental data; The water volume increment data is associated with the corresponding simulation results.

9. The flood data association management method according to any one of claims 1 to 6, characterized in that: The acquiring of a plurality of historical meteorological and hydrological data related to the target flood event includes at least one of the following: Obtaining precipitation data within a time range corresponding to the target flood; Obtain the basin flow data within the time range corresponding to the target flood.

10. A flood data association management system, characterized in that: include: A data acquisition module, used to acquire directly relevant data of a target flood and to acquire a plurality of historical meteorological and hydrological data related to the target flood; A flood simulation module, used for performing flood simulation using the historical meteorological and hydrological data in different combinations; A result comparison module, used to compare the simulation results with the directly relevant data of the target flood and divide the historical meteorological and hydrological data into key factor data and incremental factor data according to the comparison results; The association management module is used to establish a primary association between the target flood and the key factor data, and to establish a secondary association between the target flood and the incremental factor data.

Images