Organizational method of digital twin river channel data bottom plate
By using object-oriented programming principles, the river channel was delineated and an object model with continuous inheritance relationships was established, which solved the problem of low efficiency in organizing traditional river topographic data, achieved efficient data management and calculation, and improved the user experience.
Patent Information
- Application Number
- CN202311061079.4
- Authority / Receiving Office
- CN · China
- Patent Type
- Patents(China)
- Current Assignee / Owner
- Filing Date
- 2023-08-23
- Publication Date
- 2026-02-24
- Estimated Expiration
- 2043-08-23
AI Technical Summary
Traditional river topographic data organization methods are inefficient in computation and storage in digital twin river applications, failing to meet real-time computing needs, resulting in a reduced user experience and hindering the rapid switching between different 3D twin objects of different rivers.
Using object-oriented programming principles, the river channel is divided into three scales. The river topographic data is reorganized and semi-finished data is produced. A river object model with continuous inheritance relationship is established. Using object-oriented programming principles, the river topography and related data are divided into three levels of objects: L1, L2, and L3, and set as parent and child objects to achieve unified organization and management of data.
It significantly improves data management and access efficiency, increases computational efficiency by several orders of magnitude, unifies the methods for updating, accessing, and calculating river topographic data at different scales, and simplifies the implementation of the data engine.
Smart Images
Figure CN117197373B_ABST
Abstract
Description
Technical Field
[0001] This application relates to the field of geographic information system technology, specifically to a method for organizing a digital twin river channel data base. Background Technology
[0002] The digital twin river channel data base is one component of the digital twin watershed data base. It comprises a river channel topographic data source and a data engine. The river channel topographic data source typically contains only electronic vector maps of the river channel topography and data from fixed cross-sections along the river, including data from multiple surveys over the years. The data engine includes basic calculation methods for data applications, data update methods, data access methods, and data thinning methods.
[0003] River topography analysis and research are typically conducted within the scope of interest, such as watersheds, river sections, and cross-sections. Traditional river topography data organization involves converting vector data into a Digital Elevation Model (DEM). Based on information such as the survey projects and number of measurements, the DEM is then segmented and organized in a "pattern-block-row-column" manner. Other data are linked to the river topography data through spatial relationships, resulting in a relatively loose data organization. This topographic segmentation is merely for reducing the volume of individual data points to facilitate calculation; it lacks actual physical meaning and makes the data difficult to understand. Furthermore, data can only be accessed and stored after filtering based on coordinate location information, and the complex algorithms result in low computational and retrieval efficiency.
[0004] In digital twin river applications, it is necessary to frequently use a series of semi-finished data obtained from the river topography DEM itself, such as river channel storage, river slope, and river scour and deposition distribution, for more in-depth calculation and analysis. However, river topography DEM is a type of data with a large volume, and traditional river topography organization cannot meet the real-time calculation efficiency, resulting in a serious reduction in user experience.
[0005] Traditional river topographic data organization methods are clearly not conducive to the display, analysis, and calculation of river objects in a two-way and real-time digital twin environment, or to the rapid switching between different three-dimensional river twin objects. Summary of the Invention
[0006] The purpose of this application is to provide a method for organizing digital twin river channel data baseboards. By utilizing the concept of object-oriented programming, a river channel object model is established with different ranges and different regions of river channels. The river channel topography and related data are organized with the data engine. The river channel topography and related data are the member variables of the object, and the data engine algorithm is the member method of the object, so as to realize the organization of digital twin river channel data baseboards.
[0007] To achieve the above objectives, this application provides the following technical solution:
[0008] This application provides a method for organizing a digital twin river channel data base, including the following specific steps:
[0009] River channel delineation divides the river channels within a certain watershed into three levels of scale: Level L1, macro scale at the whole watershed level; Level L2, meso scale at the river section or key area level; and Level L3, micro scale at the river channel block unit level.
[0010] Reorganize the river topographic data, convert all topographic maps of each measurement under all river topographic survey projects in a certain watershed into DEMs, and use fixed cross sections distributed in a certain watershed to divide all river topographic DEMs within its range into DEM block units with the range between two adjacent fixed cross sections and continuous distribution. Each DEM block unit is the range of L3 level river.
[0011] Semi-digitized river topographic data was created and added to the data source of the digital twin river data base. The semi-digitized river topographic data includes river slope maps, river scour and deposition distribution maps, and river channel volume-elevation relationships.
[0012] The physical organization of data includes the organization of fixed cross-section results, the organization of segmented DEMs, and the organization of semi-finished data.
[0013] A river object model is established. Following the principles of object-oriented programming, the river topographic data base is divided into three levels of objects: L1, L2, and L3, and set as parent-child objects with a continuous inheritance relationship.
[0014] The river object model is instantiated by assigning an index to each river object instance and instantiating the object model according to the physical organization of the data and the logical structure of the river object model.
[0015] The method for dividing the river channel range is as follows: the range is divided using fixed cross-sections that are continuously distributed on the river channel within the basin. The L3 level river channel block unit is composed of the river channel range between two adjacent fixed cross-sections. The L2 level river segment range is composed of the river channel range between two fixed cross-sections that represent the start and end points of the river segment. The L1 level river channel range is the entire basin range. Among the three levels of river channel range, the L2 level river channel range is composed of several L3 level river channel ranges, and the L1 level river channel range is composed of several L2 level river channel ranges.
[0016] The semi-finished river topography data is generated by processing the river topography DEM block units as the data source. The range of each semi-finished data is completely consistent with the range of L3 level river topography. The semi-finished river topography data is added to the data source of the digital twin river data base.
[0017] The organization of the fixed cross-section results includes storing the fixed cross-section results in a relational database. The data table includes fields such as cross-section code, measurement number, zero-point coordinate, cross-section azimuth, and cross-section result data content. The organization of the segmented DEM includes storing the segmented DEM in a relational database. The data table includes fields such as segmented index, measurement number, upper cross-section code, lower cross-section code, grid side length, number of rows, number of columns, starting coordinate, and DEM data content. The segmented index uses the upper cross-section code. The organization method of the semi-finished data is basically the same as the organization method of the segmented DEM that generates the semi-finished data. The segmented index uses the upper cross-section code.
[0018] The establishment of the river object model specifically involves dividing the river topography data base into three levels of objects (L1, L2, and L3) according to the principles of object-oriented programming. These objects are then set as parent-child objects with a continuous inheritance relationship. The river topography and related data are used as member variables of the river object model, and various methods of the data engine are used as member methods of the river object.
[0019] The member variables of an L3-level object include: the index of the L3-level instance, the DEM data of the river channel between two adjacent fixed sections, the result data of the upper and lower fixed sections, and the semi-finished result data of the corresponding measurement. Member methods include: calculation methods for topographic slope, scour and sedimentation distribution, channel volume-to-elevation relationship, and river channel scour and sedimentation-to-elevation relationship within the specified area; data update methods for updating river topographic data and section result data; and other methods including various member variable data access methods and data thinning methods.
[0020] The member variables of an L2-level object include the index of the L2 instance and all the next-level (L3-level) objects within its scope.
[0021] Members of an L1-level object may include the index of the L1 instance and all next-level (L2-level) objects within its scope.
[0022] The instantiation of the river object model specifically involves assigning an index to each river object instance. The index for L3 level instances is set as the upper fixed section code; the index for L2 level instances is set as the upper fixed section code and the lower fixed section code combined and merged; the index for L1 level instances is custom-defined. The object model is instantiated according to the physical organization of the data and the logical structure of the river object model. Each member variable after instantiation is the index of the data in the physical organization. The section data is the section code, and the remaining data is the upper section code within the L3 level instance range.
[0023] Compared with the prior art, the beneficial effects of the present invention are:
[0024] (1) The method of dividing the river topography makes the physical division of the river topography data completely consistent with the logical division of the river that has practical significance, which greatly improves the efficiency of data management, access and operation of related programs.
[0025] (2) The river data base model constructed using object-oriented thinking enables a unified organization of river topography at different scales, and the data access, calculation and operation methods of river objects at all levels are completely unified.
[0026] (3) Semi-quantified data saves a lot of time in real-time calculation of river topography, thus improving the calculation efficiency by several orders of magnitude.
[0027] (4) It unifies the methods for updating, storing and calculating river topographic data of different scales and ranges, making the data engine easier to implement. Attached Figure Description
[0028] To more clearly illustrate the technical solutions of the embodiments of this application, the accompanying drawings used in the embodiments of this application will be briefly introduced below. It should be understood that the following drawings only show some embodiments of this application and should not be regarded as a limitation of the scope. For those skilled in the art, other related drawings can be obtained based on these drawings without creative effort.
[0029] Figure 1 This is a schematic diagram of a river object model according to an embodiment of the present invention;
[0030] Figure 2 This is a flowchart of a method according to an embodiment of the present invention. Detailed Implementation
[0031] The technical solutions of the embodiments of this application will now be described with reference to the accompanying drawings. It should be noted that similar reference numerals and letters in the following drawings indicate similar items; therefore, once an item is defined in one drawing, it does not need to be further defined and explained in subsequent drawings.
[0032] The terms “comprising,” “including,” or any other variations thereof are intended to cover a non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements includes not only those elements but also other elements not expressly listed, or elements inherent to such a process, method, article, or apparatus. Without further limitation, an element defined by the phrase “comprising one…” does not exclude the presence of other identical elements in the process, method, article, or apparatus that includes said element.
[0033] The terms “first,” “second,” etc., are used only to distinguish one entity or operation from another, and should not be construed as indicating or implying relative importance, nor as requiring or implying any such actual relationship or order between these entities or operations.
[0034] Please see Figure 1 and Figure 2 This invention provides a method for organizing a digital twin river channel data base, comprising the following specific steps:
[0035] Step 1: River Channel Delineation. The river channel from the Three Gorges Dam to Zhutuo is defined as the watershed. Hundreds of fixed cross-sections are continuously laid out from the dam to Zhutuo, with cross-section codes ranging from S30—
[0036] —S400. The river channels within the Three Gorges Reservoir area are considered as a macro-scale region at the L1 level, encompassing the entire basin. The eight river sections within the reservoir basin are considered as eight meso-scale regions at the L2 level, namely:
[0037] Zhutuo to Jiangjin (starting and ending section codes are S400-S370)
[0038] Jiangjin to Dadukou (starting and ending section codes are S370-S343)
[0039] From Dadukou to Tongluoxia (starting and ending section codes are S3343-S323)
[0040] From Tongluoxia to Liduzhen (starting and ending section codes are S323-S273)
[0041] From Lidu Town to Fuling (starting and ending section codes are S273-S267)
[0042] From Fuling to Fengjie (starting and ending section codes are S267-S118),
[0043] From Fengjie to Miaohe (starting and ending section codes are S118-S40),
[0044] Miaohe to the dam (starting and ending section codes are S40-S30).
[0045] The river channel segmentation unit formed by every two adjacent cross sections within the reservoir area is considered as a micro-scale region at the L3 level, starting from the dam front, i.e., from S30-S31 and S31-S32 in front of the dam to S398-S399 and S399-S400 at the reservoir tail.
[0046] Step 2: Reconstruct river topographic data. Convert all topographic maps from all river topographic survey projects in the Three Gorges Reservoir basin into DEMs. Using all L3-level river block units as dividing areas, divide all river topographic DEMs in a certain basin into DEM block units that are continuously distributed within the range between two adjacent fixed cross sections.
[0047] Step 3: Create semi-finished river topographic data. This semi-finished data includes river slope maps, riverbed scour and deposition distribution maps, and riverbed volume-elevation relationships. The semi-finished data is generated from the river topographic DEM blocks generated in Step 2, and the range of each semi-finished data point is completely consistent with the L3 level river topographic range. Add the semi-finished river topographic data to the data source of the digital twin river data base.
[0048] Step 4: Physical organization of data
[0049] ① Organization of fixed section results: Fixed section results are stored in a relational database. The data table includes fields such as section code, measurement number, distance from zero point marker to starting point, zero point marker coordinates, section azimuth, and the content of the section result data.
[0050] ② Organization of River Channel Topographic Block DEM: The block DEM is stored in a relational database. The data table includes fields such as block index, measurement order, upper section code, lower section code, grid side length, number of rows, number of columns, starting coordinates, and DEM data content. The block index uses the upper section code.
[0051] ③ Organization of semi-finished data: The organization method of semi-finished data is exactly the same as that of L3-level block DEM. The block index uses the upper section encoding.
[0052] Step 5: Establish the river channel object model. Following the principles of object-oriented programming, the three levels of river topographic data objects L1, L2, and L3 are set as parent-child objects with a continuous inheritance relationship. The river topography and related data are set as member variables of the river channel object model (see Table 1), and the various basic calculation methods and data manipulation methods contained in the data engine are set as member methods of the river channel object model (see Table 2).
[0053] The member variables of the L3-level river channel block unit object include: the DEM data of the river channel topography block within its range, the upper and lower fixed cross-section results information, and the semi-finished data of the corresponding range. Member methods include: basic calculation methods for topographic slope calculation, scour and sedimentation distribution calculation, channel storage-to-elevation relationship calculation, and river channel scour and sedimentation-to-elevation relationship calculation within this range; methods for updating river channel topographic data and cross-section results data; methods for storing and retrieving various member variable data; and methods for thinning river channel topography.
[0054] The member variables of an L2-level river segment object include all its subordinate (L3-level) objects.
[0055] The members of the L1 level Three Gorges Reservoir Basin object include all its subordinate (L2 level) objects.
[0056] To express the hierarchical relationship between the three levels of objects, each level of object also has two member variables: the index of the instance of the object at this level and the indexes of all the instances of the subordinate objects contained within the scope of the object at this level.
[0057] Each level of instance only needs to obtain the index of the lower-level instance once or level by level until the lowest level object (L3 level) has no lower-level instance index. Finally, the member methods of the L3 level object are used to obtain relevant terrain data or perform data calculation, update, thinning and other operations.
[0058] Table 1 Member variables of the river object model
[0059]
[0060] Table 2 Member methods and parameters of the river object model
[0061]
[0062] Step 6: Instantiation of the river channel object model. Based on the river channel object model established in Step 5, each river channel object has one instance, and instantiation only applies to member variables. All river channel topography-related data appear as data indexes in the instantiated object, i.e., indexes of each data item in the database.
[0063] In the Three Gorges Reservoir basin, for L3 level instances, such as the river channel between sections S30 and S31, the instance index is set to the upper section code S30. There are no lower-level instances. According to the methods in steps 3 and 4, the river channel topography and semi-finished data within the range can all be set to S30. The fixed section data are therefore the upper and lower section codes S30 and S31 within this range. For L2 level instances, such as the section from Miaohe to the dam, the instance index is set to the upper fixed section code and the lower fixed section code combined and merged, which is S30_S40. The lower-level instance index includes S30, S31 to S39, and S40. For L1 level instances, i.e., the Three Gorges Reservoir basin, the instance index is custom and set to A. The lower-level instance index includes the indexes of all river sections in the entire basin, i.e., S30_S40, S40_S118, ..., S343_S370, S370_S400 (see Table 3).
[0064] Table 3 Examples of member variables for river object instances
[0065]
[0066] The above description is merely an embodiment of this application and is not intended to limit the scope of protection of this application. Various modifications and variations can be made to this application by those skilled in the art. Any modifications, equivalent substitutions, improvements, etc., made within the spirit and principles of this application should be included within the scope of protection of this application.
Claims
1. A method for organizing a digital twin river channel data base, characterized in that, The specific steps include the following: River channel delineation divides the river channels within a certain watershed into three levels of scale: Level L1 (macro-scale, full watershed level), Level L2 (meso-scale, river segment level), and Level L3 (micro-scale, river segment unit level). Reorganize the river topographic data, convert all topographic maps of all river topographic survey projects in a certain watershed into DEMs, and divide all river topographic DEMs in a certain watershed into DEM block units that are continuously distributed between two adjacent fixed cross sections, using the range of all L3-level rivers as the dividing area. Semi-finished river topographic data was created and used as a new data source for the digital twin data base. The semi-finished river topographic data includes river slope map, river scour and deposition distribution map, and river channel storage and elevation relationship. The physical organization of data includes the organization of fixed cross-section results, the organization of segmented DEMs, and the organization of semi-finished data. A river object model is established. Following the principles of object-oriented programming, the river topographic data base is divided into three levels of objects: L3, L2, and L1, and set as parent-child objects with a continuous inheritance relationship. The river object model is instantiated, and each river object instance is assigned an index. The object model is instantiated according to the physical organization of the data and the logical structure of the river object model. The method for dividing the river channel range is as follows: the river channel within the basin is divided by continuously distributed fixed cross-sections on the river channel. The L3 level river channel block unit is composed of the river channel range between two adjacent fixed cross-sections. The L2 level river segment range is composed of the river channel range between two fixed cross-sections representing the start and end points of the river segment. The L1 level river channel range is the entire basin range. Among the three levels of river channel range, the L2 level river channel range is composed of several L3 level river channel ranges, and the L1 level river channel range is composed of several L2 level river channel ranges.
2. The method for organizing a digital twin river channel data base plate according to claim 1, characterized in that, The semi-finished river topography data is generated by performing calculations on the generated river topography DEM block units as the data source, and is added to the digital twin river data base as a new data source. The range of each semi-finished data is completely consistent with the range of L3 level river topography.
3. The method for organizing a digital twin river channel data base plate according to claim 1, characterized in that, The organization of the fixed section results includes storing the fixed section results in a relational database. The data table includes fields such as section code, measurement number, zero point mark distance, zero point mark coordinates, section azimuth, and section result data content. The organization of the segmented DEM includes storing the segmented DEM in a relational database. The data table includes fields such as segment code, measurement order, upper section code, lower section code, grid side length, number of rows, number of columns, starting coordinates, and DEM data content. The segment index uses upper section code. The organization method of the semi-finished data is the same as the organization method of the segmented DEM that generated the semi-finished data, wherein the segment code uses upper section code.
4. The method for organizing a digital twin river channel data base plate according to claim 1, characterized in that, The establishment of the river object model specifically involves dividing the river topographic data base into three levels of objects (L1, L2, and L3) according to the principles of object-oriented programming. These objects are then set as parent-child objects with a continuous inheritance relationship. The river topography and related data are used as member variables of the river object model, including the river DEM data within the object scope, the corresponding semi-finished data, and the fixed cross-section result data. Various methods of the data engine are used as member methods of the river object model, including calculation and operation methods for various member data.
5. A method for organizing a digital twin river channel data base plate according to claim 1, characterized in that, The member variables of an L3-level object include: the index of the L3-level instance, the index of the river channel DEM data between two adjacent fixed cross-sections, the index of the upper and lower fixed cross-section result data, and the corresponding semi-finished result data index. Member methods include: calculation methods for topographic slope, scour and sedimentation distribution, channel volume-to-elevation relationship, and river channel scour and sedimentation-to-elevation relationship within this range; data update methods for updating river channel topographic data and cross-section result data; and methods for storing and retrieving various member variable data and data thinning methods. Member variables of an L2-level object include: the L2-level instance index, and all L3-level instance indices within its scope. The member variables of an L1-level object include: the L1-level instance index and the indices of all L2-level objects within its scope.
6. The method for organizing a digital twin river channel data base plate according to claim 1, characterized in that, The instantiation of the river object model specifically involves assigning an index to each river object instance. The index for L3 level instances is set to the upper fixed section code; the index for L2 level instances is set to the upper fixed section code and the lower fixed section code concatenated and merged. The L1 level instance index is customizable. The object model is instantiated based on the physical organization of the data and the logical structure of the river object model. Each river topographic data member variable after instantiation is a unique code for the data in the physical organization within the instance. That is, the cross-section data is the code for that cross-section, and the remaining data is the code for the upper cross-section within the L3 level instance range.