Disclosure of Invention
Aiming at the defects of the prior art, the application provides a river bank ecological slope protection impact-resistant flow velocity rechecking method, which is based on MIKE21 program expansion package MIKE SDK provided by Danish water conservancy research and combines with space geographic analysis software QGIS, so that the quick extraction and analysis of the two-dimensional flow field bank slope flow velocity calculated by MIKE21 are realized, and the design efficiency of ecological bank protection is greatly improved.
The application relates to a river bank ecological slope protection impact-resistant flow velocity rechecking method, which comprises the following steps:
generating a grid file according to a topography by using a surface water simulation system, indicating boundary conditions of a research area in the surface water simulation system, introducing the grid file into MIKE21, determining upstream and downstream boundaries, and calculating in the MIKE21 to obtain a dfsu file containing flow velocity and water depth information;
reading grid coordinates from the calculation result dfsu file, obtaining boundary grid coordinates from the calculation result dfsu file by utilizing boundary type coding, and generating a CSV file;
importing the generated coordinate CSV file into a QGIS, adding left and right bank attributes into an attribute table, and exporting the generated attribute table into an xlsx file after sorting according to the left and right bank attributes;
reading the topographic grid coordinates, matching the topographic grid coordinates with the left and right bank coordinates to obtain index information of boundary grid coordinates, reading calculation result speed information, and obtaining boundary flow rate information by utilizing the index information of the boundary grid coordinates;
sequencing the boundary grid coordinates, calculating the accumulated length of the sequenced coordinate points along the axis direction of the river bank, corresponding to pile number sections needing to be paved with ecological slope protection, comparing the maximum flow velocity of the corresponding pile number section and the anti-impact flow velocity of the ecological slope protection, and evaluating whether the ecological slope protection is applicable to the pile number sections.
Preferably, the boundary conditions of the investigation region include a slip-free boundary, a flow boundary and a water level boundary.
Preferably, the step of importing the data into the MIKE21 to determine the upstream and downstream boundaries, and performing calculation in the MIKE21 to obtain a dfsu file containing flow rate and water depth information includes:
newly establishing a MIKE21FM item in MIKE ZERO software, importing a grid file, and determining an upstream boundary and a downstream boundary;
given a water level and flow boundary condition in MIKE21, calculating flow field flow velocity and water level results under different working conditions;
and selecting dfsu for output, and selecting flow rate and water level information in the output content.
Preferably, the boundary conditions of the water level flow rate given in the MIKE21 comprise river bank and river inlet and outlet water level flow rate conditions.
Preferably, the reading the grid coordinates from the calculation result dfsu file includes reading the grid coordinates from the calculation result dfsu file by using a MATLAB mzReadMesh function provided by the MIKE SDK.
Preferably, adding the left and right bank attributes in the attribute table includes:
selecting scattered points belonging to the left bank in the QGIS, marking the left bank in the attribute table, and selecting scattered points belonging to the right bank, marking the right bank in the attribute table.
Preferably, the step of reading the topographic grid coordinate, matching the topographic grid coordinate with the left and right bank coordinates to obtain index information of the boundary grid coordinate, reading the calculation result speed information, and obtaining the boundary flow rate information by using the index information of the boundary grid coordinate includes:
reading a boundary coordinate attribute table to obtain coordinate information of the left bank and the right bank;
reading coordinates in the grid file, and matching the coordinates with left and right bank coordinates to obtain index information of grid points positioned at the boundary in the calculation result dfsu file;
and obtaining boundary flow velocity information from the calculation result dfsu file by using the index information.
Preferably, the ordering of the boundary grid coordinates includes:
if the river flow direction is from west to east, sequencing coordinate points and corresponding boundary flow rates according to the sequence from small to large of X coordinates of the left bank boundary and the right bank boundary;
if the river flow direction is from east to west, the coordinate points and the corresponding boundary flow rates are ordered according to the order from the big to the small of the X coordinates of the left and right bank boundaries.
Preferably, if the maximum flow rate of the corresponding pile section is not greater than the anti-impact flow rate of the ecological slope protection, the ecological slope protection is applicable to the pile section, and if the maximum flow rate of the corresponding pile section is greater than the anti-impact flow rate of the ecological slope protection, the ecological slope protection is not applicable to the pile section.
Preferably, grid node coordinates are filled in the CSV file in a form of a table.
The beneficial effects of the application are as follows:
1. according to the application, the MIKE21 program provided by Danish water conservancy research expands the MIKE SDK and combines with the space geographic analysis software QGIS, so that the quick extraction and analysis of the two-dimensional flow field bank slope flow velocity calculated by MIKE21 are realized, and the design efficiency of ecological bank protection is greatly improved.
2. The application omits a complicated post-processing method in the traditional calculation of the bank flow velocity, directly extracts the bank flow velocity by utilizing the MATLAB API provided by the MIKE SDK, directly corresponds to the pile number in engineering design practice, and greatly facilitates the rechecking of the ecological slope protection impact flow velocity.
3. The boundary nodes are distinguished from nodes in the river channel by special coding for the boundary nodes when the grid is constructed, so that the post-processing is convenient.
4. The boundary grid coordinates are led into the QGIS for post-processing, so that the left and right bank parts in the boundary grid coordinates are effectively distinguished, and the left and right bank flow velocity is conveniently calculated respectively.
5. And the post-processing is carried out on the boundary grid coordinates through the QGIS, so that the continuous coding of the boundary grid nodes along the river levee shaft is ensured, and the boundary flow velocity pile number is conveniently calculated.
Detailed Description
In order to make the technical problems, technical schemes and beneficial effects to be solved more clear, the application is further described in detail below with reference to the accompanying drawings and embodiments. It should be understood that the specific embodiments described herein are for purposes of illustration only and are not intended to limit the scope of the application.
In the following description, for purposes of explanation and not limitation, specific details are set forth such as the particular system architecture, techniques, etc., in order to provide a thorough understanding of the embodiments of the present application. It will be apparent, however, to one skilled in the art that the present application may be practiced in other embodiments that depart from these specific details. In other instances, detailed descriptions of well-known systems, devices, circuits, and methods are omitted so as not to obscure the description of the present application with unnecessary detail.
It should be understood that the terms "comprises" and/or "comprising," when used in this specification and the appended claims, specify the presence of stated features, integers, steps, operations, elements, and/or components, but do not preclude the presence or addition of one or more other features, integers, steps, operations, elements, components, and/or groups thereof.
It should also be understood that the term "and/or" as used in the present specification and the appended claims refers to any and all possible combinations of one or more of the associated listed items, and includes such combinations.
As used in the present description and the appended claims, the term "if" may be interpreted as "when..once" or "in response to a determination" or "in response to detection" depending on the context. Similarly, the phrase "if a determination" or "if a [ described condition or event ] is detected" may be interpreted in the context of meaning "upon determination" or "in response to determination" or "upon detection of a [ described condition or event ]" or "in response to detection of a [ described condition or event ]".
Furthermore, the terms "first," "second," "third," and the like in the description of the present specification and in the appended claims, are used for distinguishing between descriptions and not necessarily for indicating or implying a relative importance.
Reference in the specification to "one embodiment" or "some embodiments" or the like means that a particular feature, structure, or characteristic described in connection with the embodiment is included in one or more embodiments of the application. Thus, appearances of the phrases "in one embodiment," "in some embodiments," "in other embodiments," and the like in the specification are not necessarily all referring to the same embodiment, but mean "one or more but not all embodiments" unless expressly specified otherwise. The terms "comprising," "including," "having," and variations thereof mean "including but not limited to," unless expressly specified otherwise. "plurality" means "two or more".
Example 1
Fig. 1 shows a schematic structural diagram of a method for checking the impact flow rate of an ecological slope protection on a river bank according to a preferred embodiment of the present application (fig. 1 shows a first embodiment of the present application), and for convenience of explanation, only the parts related to the present embodiment are shown, and the details are as follows:
the application relates to a river bank ecological slope protection impact-resistant flow velocity rechecking method, which comprises the following steps:
step 1: generating a grid file according to a topographic map by using a surface water simulation system (SMS, surface WaterModeling System), indicating boundary conditions of a research area in the surface water simulation system, including a slip-free boundary, a flow boundary and a water level boundary, newly building a MIKE21FM project in MIKE ZERO software, importing the grid file, determining an upstream boundary and a downstream boundary, setting the water level and flow boundary conditions in the MIKE21, and calculating to obtain a dfsu file containing flow velocity and water depth information. Calculating flow field flow velocity and water level results under different working conditions, selecting dfsu for output, and selecting information such as flow velocity, water level and the like in output contents;
step 2: reading grid coordinates from the calculation result dfsu file by using a MATLAB mzReadMesh function provided by the MIKE SDK, obtaining boundary grid coordinates (the code of the river boundary in the grid file of the MIKE21 is 1) from the calculation result dfsu file by using boundary type codes, and generating a CSV file; the format of the CSV file is shown in Table 1 (in which grid node coordinates are filled in, see Table 3 for specific examples).
Table 1: boundary coordinate format table
Step 3: and importing the generated coordinate CSV file into a QGIS, and adding left and right bank attributes into an attribute table, wherein the format of the attribute table is shown in table 2. Selecting a scattered point belonging to the left bank in the QGIS, marking the left bank (0) in the attribute table, and then selecting a scattered point belonging to the right bank, marking the right bank (1) in the attribute table. And sorting the generated attribute table according to the left and right bank attributes, and respectively and integrally exporting scattered points positioned on the left and right banks into xlsx files (formats).
Table 2: boundary coordinate attribute table
X
|
Y
|
Left and right banks
|
…
|
…
|
0/1 |
*0 represents the left bank, 1 represents the right bank
Step 4: reading the topographic grid coordinates, matching the topographic grid coordinates with the left and right bank coordinates to obtain index information of boundary grid coordinates, reading calculation result speed information, and obtaining boundary flow rate information by utilizing the index information of the boundary grid coordinates; the method specifically comprises the following steps:
step 401: the DFSU MATLAB API provided by the MIKE SDK is utilized to read a result file calculated by the MIKE21, firstly, a storage position of speed information (Current speed) in the DFSU file is checked, and then speed information in a calculation result is read.
Step 402: and reading the boundary coordinate attribute table by MATLAB to obtain the coordinate information of the left bank and the right bank. And (3) reading coordinates in the grid file by using a MATLAB mzReadMesh function provided by the MIKE SDK, and matching the coordinates with the left and right bank coordinates to obtain index information of grid points positioned at the boundary in the calculation result dfsu file. And obtaining boundary flow rate information from the calculation result dfsu file by using the index information.
Step 5: sequencing the boundary grid coordinates, calculating the accumulated length of the sequenced coordinate points along the axis direction of the river bank, corresponding to pile number sections needing to be paved with ecological slope protection, comparing the maximum flow velocity of the corresponding pile number section and the anti-impact flow velocity of the ecological slope protection, and evaluating whether the ecological slope protection is applicable to the pile number sections. If the maximum flow rate of the corresponding pile section bank is not greater than the anti-impact flow rate of the ecological slope protection, the ecological slope protection is applicable to the pile section, and if the maximum flow rate of the corresponding pile section bank is greater than the anti-impact flow rate of the ecological slope protection, the ecological slope protection is not applicable to the pile section.
The method for ordering the boundary grid coordinates comprises the following steps:
if the river flow direction is from west to east, sequencing coordinate points and corresponding boundary flow rates according to the sequence from small to large of X coordinates of the left bank boundary and the right bank boundary; if the river flow direction is from east to west, the coordinate points and the corresponding boundary flow rates are ordered according to the order from the big to the small of the X coordinates of the left and right bank boundaries.
Example two
The application uses the anti-impact rechecking calculation of the ecological slope protection in the new covered flood diversion tunnel embankment reinforcement and treatment engineering of the Ann new area as an embodiment for the detailed description, and has guiding significance on the anti-impact rechecking calculation of other ecological slope protection.
Step 1: generating a grid file from terrain scattered points by using SMS (short message service), referring to FIG. 2, newly establishing MIKE21FM project in MIKE ZERO software, importing the grid file, determining boundary conditions (river bank, river channel inlet and outlet water level flow conditions), calculating flow field flow velocity and water level results under different working conditions, selecting dfsu for output, and selecting information such as flow velocity, water level and the like in output contents.
Step 2: and reading the boundary coordinates of the coordinate grid by using a MATLAB mzReadMesh function provided by the MIKE SDK, and generating a CSV file. The grid boundary coordinates CSV file is shown in Table 3.
Table 3: boundary grid coordinate table
X
|
Y
|
526958.8
|
4322764
|
526873.1
|
4322715
|
526798.3
|
4322649
|
…
|
…
|
…
|
…
|
…
|
…
|
504392.9
|
4328130
|
504307.8
|
4328182
|
504218.2
|
4328226 |
Step 3: and importing the generated coordinate CSV file into a QGIS, and adding left and right bank attributes into an attribute table. Selecting a scattered point belonging to the left bank in the QGIS, marking the left bank (0) in the attribute table, and then selecting a scattered point belonging to the right bank, marking the right bank (1) in the attribute table. And ordering the generated attribute table according to the left and right bank attributes, and then exporting the attribute table into an xlsx file. The coordinate attribute file is shown in table 4.
Table 4: boundary left-right bank attribute table
X
|
Y
|
Left and right banks
|
526958.8
|
4322764
|
0
|
526873.1
|
4322715
|
0
|
526798.3
|
4322649
|
0
|
…
|
…
|
…
|
…
|
…
|
…
|
…
|
…
|
…
|
503556.2
|
4326815
|
1
|
503502.5
|
4326899
|
1
|
503442.7
|
4326979
|
1 |
*0 represents the left bank, 1 represents the right bank
Step 401: and reading a result file calculated by MIKE21 by using a DFSU MATLAB API, outputting the 5 th data set in the DFSU file by using speed information (Current speed) in the simulation of the model, and reading all the speed information.
Step 402: and reading the attribute table xlsx file by using MATLAB to obtain the coordinate files of the left bank and the right bank. And (3) using a MATLAB mzReadMesh function provided by the MIKE SDK to read grid coordinates of the calculation result dfsu file, and using a coordinate position to match the grid coordinates with left and right bank coordinates to obtain index information of boundary coordinate points in the grid of the calculation result dfsu file. And obtaining boundary flow rate information by using the index information.
Step 5: the new covered house flood diversion tunnel in the Anshen area flows from west to east, so that the boundary coordinate points and the corresponding boundary flow rates are ordered according to the sequence from small to large of the X coordinates of the left and right bank boundaries. And calculating the accumulated length of the ordered river bank coordinate points along the direction of the river bank axis. The new cover house flood diversion channel embankment reinforcement and management engineering of the new male security area needs to apply ecological slope protection in the whole section, so 500 meters is the maximum flow velocity in an interval statistics interval, and the ecological slope protection impact flow velocity is compared to evaluate whether the ecological slope protection is applicable in the pile number section. The cumulative length of the river bank coordinate points is the corresponding pile number of the grid point, the maximum flow velocity in the pile number is counted every 500 meters from the river dike head as an interval, and the table of the maximum flow velocity in the pile number is shown in tables 5 and 6.
Table 5: left bank boundary flow velocity pile number meter
Initial pile number
|
Termination pile number
|
Maximum flow rate in a segment
|
0+000
|
0+500
|
0.18
|
0+500
|
1+000
|
0.17
|
1+000
|
1+500
|
0.15
|
…
|
…
|
…
|
30+000
|
30+500
|
0.71
|
30+500
|
31+000
|
0.67
|
31+000
|
31+500
|
0.68 |
Table 6: right bank boundary flow velocity pile number meter
Initial pile number
|
Termination pile number
|
The most in the segmentHigh flow rate
|
0+000
|
0+500
|
0.64
|
0+500
|
1+000
|
0.56
|
1+000
|
1+500
|
0.68
|
…
|
…
|
…
|
30+000
|
30+500
|
0.26
|
30+500
|
31+000
|
0.27
|
31+000
|
31+500
|
0.29 |
It should be understood that the specific order or hierarchy of steps in the processes disclosed are examples of exemplary approaches. Based on design preferences, it is understood that the specific order or hierarchy of steps in the processes may be rearranged without departing from the scope of the present disclosure. The accompanying method claims present elements of the various steps in a sample order, and are not meant to be limited to the specific order or hierarchy presented.
In the foregoing detailed description, various features are grouped together in a single embodiment for the purpose of streamlining the disclosure. This method of disclosure is not to be interpreted as reflecting an intention that the claimed embodiments of the subject matter require more features than are expressly recited in each claim. Rather, as the following claims reflect, application lies in less than all features of a single disclosed embodiment. Thus the following claims are hereby expressly incorporated into this detailed description, with each claim standing on its own as a separate preferred embodiment of this application.
The previous description of the disclosed embodiments is provided to enable any person skilled in the art to make or use the present application. As will be apparent to those skilled in the art; various modifications to these embodiments will be readily apparent, and the generic principles defined herein may be applied to other embodiments without departing from the spirit or scope of the disclosure. Thus, the present disclosure is not intended to be limited to the embodiments shown herein but is to be accorded the widest scope consistent with the principles and novel features disclosed herein.
The foregoing description includes examples of one or more embodiments. It is, of course, not possible to describe every conceivable combination of components or methodologies for purposes of describing the aforementioned embodiments, but one of ordinary skill in the art may recognize that many further combinations and permutations of various embodiments are possible. Accordingly, the embodiments described herein are intended to embrace all such alterations, modifications and variations that fall within the scope of the appended claims. Furthermore, as used in the specification or claims, the term "comprising" is intended to be inclusive in a manner similar to the term "comprising," as interpreted when employed as a transitional word in a claim. Furthermore, any use of the term "or" in the specification of the claims is intended to mean "non-exclusive or".
Those of skill in the art will further appreciate that the various illustrative logical blocks (illustrative logical block), units, and steps described in connection with the embodiments of the application may be implemented by electronic hardware, computer software, or combinations of both. To clearly illustrate this interchangeability of hardware and software, various illustrative components (illustrative components), elements, and steps have been described above generally in terms of their functionality. Whether such functionality is implemented as hardware or software depends upon the particular application and design requirements of the overall system. Those skilled in the art may implement the described functionality in varying ways for each particular application, but such implementation is not to be understood as beyond the scope of the embodiments of the present application.
The various illustrative logical blocks or units described in the embodiments of the application may be implemented or performed with a general purpose processor, a digital signal processor, an Application Specific Integrated Circuit (ASIC), a field programmable gate array or other programmable logic device, discrete gate or transistor logic, discrete hardware components, or any combination thereof designed to perform the functions described. A general purpose processor may be a microprocessor, but in the alternative, the general purpose processor may be any conventional processor, controller, microcontroller, or state machine. A processor may also be implemented as a combination of computing devices, e.g., a digital signal processor and a microprocessor, a plurality of microprocessors, one or more microprocessors in conjunction with a digital signal processor core, or any other similar configuration.
The steps of a method or algorithm described in connection with the embodiments disclosed herein may be embodied directly in hardware, in a software module executed by a processor, or in a combination of the two. A software module may be stored in RAM memory, flash memory, ROM memory, EPROM memory, EEPROM memory, registers, hard disk, a removable disk, a CD-ROM, or any other form of storage medium known in the art. In an example, a storage medium may be coupled to the processor such that the processor can read information from, and write information to, the storage medium. In the alternative, the storage medium may be integral to the processor. The processor and the storage medium may reside in an ASIC, which may reside in a user terminal. In the alternative, the processor and the storage medium may reside as distinct components in a user terminal.
In one or more exemplary designs, the above-described functions of embodiments of the present application may be implemented in hardware, software, firmware, or any combination of the three. If implemented in software, the functions may be stored on a computer-readable medium or transmitted as one or more instructions or code on the computer-readable medium. Computer readable media includes both computer storage media and communication media that facilitate transfer of computer programs from one place to another. A storage media may be any available media that can be accessed by a general purpose or special purpose computer. For example, such computer-readable media may include, but is not limited to, RAM, ROM, EEPROM, CD-ROM or other optical disk storage, magnetic disk storage or other magnetic storage devices, or any other medium that may be used to carry or store program code in the form of instructions or data structures and other data structures that may be read by a general or special purpose computer, or a general or special purpose processor. Further, any connection is properly termed a computer-readable medium, e.g., if the software is transmitted from a website, server, or other remote source via a coaxial cable, fiber optic cable, twisted pair, digital Subscriber Line (DSL), or wireless such as infrared, radio, and microwave, and is also included in the definition of computer-readable medium. The disks (disks) and disks (disks) include compact disks, laser disks, optical disks, DVDs, floppy disks, and blu-ray discs where disks usually reproduce data magnetically, while disks usually reproduce data optically with lasers. Combinations of the above may also be included within the computer-readable media.
The above embodiments are only for illustrating the technical solution of the present application, and not for limiting the same; although the application has been described in detail with reference to the foregoing embodiments, it will be understood by those of ordinary skill in the art that: the technical scheme described in the foregoing embodiments can be modified or some technical features thereof can be replaced by equivalents; such modifications and substitutions do not depart from the spirit and scope of the technical solutions of the embodiments of the present application, and are intended to be included in the scope of the present application.