B / s architecture geological data management method

Abstract

The present application belongs to the technical field of data management, and particularly relates to a B / S architecture geological data management method. The method comprises the following steps: analyzing a geological data package to obtain to-be-processed geological data; generating a profile control axis according to a project range and a profile configuration, and mapping the to-be-processed geological data into geological evidence points; generating candidate geological interfaces according to the geological evidence points, and elastically fitting the candidate geological interfaces according to evidence fitting rules, interface smoothing rules, stratum sequence rules and conflict deduction rules to obtain target geological objects, support relations and conflict relations; determining conflict evidence points according to fitting residuals, propagating conflict influence values and updating target geological object states; and writing back abnormal information according to a view residual of a business view. The present application can form traceable and checkable geological objects, and limit abnormal data from entering formal achievements.

Description

Technical Field

[0001] This invention relates to the field of data management technology, and specifically to a B / S architecture geological data management method. Background Technology

[0002] Geological data typically originates from boreholes, stratigraphic records, in-situ tests, laboratory experiments, geological maps, monitoring data, and output documents. It is characterized by diverse sources, complex spatial locations, clear depth relationships, and frequent version changes. As the digitization of geological data increases, the industry's demand for centralized data storage, unified retrieval, remote collaboration, and output verification continues to grow.

[0003] Existing management methods mostly use data items, layers, tables, or file directories as basic objects, which can complete data uploading, classification, querying, and display, but they are difficult to reflect the spatial continuity, profile interpretation, and evidence support relationships between geological objects. In practical use, the same stratigraphic interface may be formed by multiple boreholes, historical maps, and manual interpretations. There may also be problems such as depth deviation, coordinate errors, inconsistent stratigraphic classifications, and mixed use of different versions of results between data from different sources.

[0004] Existing technologies typically perform single-point verification during the data entry or view display stage, lacking a closed-loop mechanism to transfer evidence of local anomalies to the geological object status and the result publication status. This results in erroneous data potentially being included in the official results, and structural anomalies in the business view are difficult to be traced back to the original evidence and target object in a timely manner. Summary of the Invention

[0005] This invention provides a B / S architecture geological data management method, which at least solves the problem of how to form verifiable geological objects and reverse-constrain the status of results in the process of centralized geological data management.

[0006] This invention provides a B / S architecture geological data management method, the method comprising: Parse the geological data package to obtain the geological data to be processed; Generate profile control axes according to project scope and profile configuration, and map the geological data to be processed into geological evidence points; Candidate geological interfaces are generated based on geological evidence points. The candidate geological interfaces are elastically fitted according to evidence fitting rules, interface smoothing rules, stratigraphic sequence rules and conflict deduction rules to obtain the target geological object, the support relationship and conflict relationship between the target geological object and the geological evidence points. Conflict evidence points are determined based on the fitting residuals, and the conflict impact value is propagated according to the support and conflict relationships to update the quality status and release status of the target geological object. An operational view is generated based on the target geological object, and anomaly information is written back to the geological evidence points and the target geological object according to the view residuals of the operational view.

[0007] Compared with the prior art, the advantages and beneficial effects of the present invention are as follows: By mapping the geological data to be processed to geological evidence points, spatial location, depth range, stratigraphic attributes, source reliability, and error range are bound in the same data unit, so that the subsequent interface generation no longer depends on ordinary table records.

[0008] By generating profile control axes according to project scope and profile configuration, different borehole, test data and map data can be organized under a unified profile coordinate system, providing a basis for judging the continuity of strata across boreholes.

[0009] By generating candidate geological interfaces based on geological evidence points and performing elastic fitting according to evidence fitting rules, interface smoothing rules, stratigraphic sequence rules, and conflict deduction rules, geological interfaces are generated under the constraints of evidence support, spatial continuity, and upper and lower strata relationships, reducing interface instability caused by simple interpolation or manual connection.

[0010] By determining conflict evidence points based on the fitting residuals and propagating conflict impact values ​​according to support and conflict relationships, the linkage control of local anomaly evidence on the quality status and release status of the target geological object was realized.

[0011] By writing back anomaly information based on the view residuals of the business view, it is possible to trace back to geological evidence points and target geological objects to address issues such as stratigraphic interface intersections, insufficient evidence quantity, and inconsistent result versions in the business view. Attached Figure Description

[0012] Figure 1 This is a schematic flowchart of the method of the present invention; Figure 2 This is a schematic diagram of cross-sectional stratigraphic interface fitting in an embodiment of the present invention; Figure 3 This is a diagram showing the standardized residual and conflict identification results in an embodiment of the present invention; Figure 4 This is a schematic diagram illustrating the propagation relationship of conflict impact values ​​in an embodiment of the present invention; Figure 5 This is a graph showing the changes in abnormal values ​​in the business view in an embodiment of the present invention. Detailed Implementation

[0013] Hereinafter, embodiments of the present invention will be described with reference to the accompanying drawings. However, it should be understood that these descriptions are merely exemplary and not intended to limit the scope of the invention. In the following detailed description, numerous specific details are set forth to provide a thorough understanding of the embodiments of the present invention for ease of explanation.

[0014] B / S architecture is a software architecture that uses a browser as the user access point and a server as the data processing and business computing center. Under this architecture, users do not need to deploy complex clients locally; they can complete data uploads, parameter configurations, result viewing, and output management through a browser. The server centrally handles data parsing, rule calculation, status maintenance, access control, and result output. For data management systems requiring multi-person collaboration, cross-location access, and centralized maintenance, B / S architecture enables unified deployment of data processing logic on the server side, reducing the impact of terminal environment differences on business processes and facilitating unified control over data versions, processing procedures, and output status. Based on this, this invention proposes a geological data management method focusing on the centralized access, profile organization, geological object generation, anomaly propagation, and view write-back processes of geological data under a B / S architecture.

[0015] like Figure 1 As shown, a B / S architecture geological data management method includes: Parse the geological data package to obtain the geological data to be processed; When the system receives a geological data packet uploaded from the browser, the server performs format recognition and content parsing, reading its spatial location, depth range, stratigraphic attributes, data source, and project affiliation information to form geological data to be processed. The geological data packet may include borehole record tables, stratigraphic stratification records, test data tables, geological map data, and engineering survey attachments. During parsing, the server retains the original data packet, records the parsing status, and converts identifiable fields into standardized field names. Data lacking project identifiers, coordinate fields, or depth fields is written to a pending verification status and not proceeds to subsequent profile mapping processing. This geological data to be processed serves as the data foundation for subsequently generating profile control axis mapping results and geological evidence points.

[0016] The geological data to be processed includes data source identifier, spatial coordinates, elevation information, depth range, and stratigraphic attributes. Stratigraphic attributes include rock and soil names and engineering geological classifications.

[0017] In one embodiment, the geological data to be processed further includes a data source identifier, spatial coordinates, elevation information, depth range, and stratigraphic attributes, enabling the server to distinguish data from different sources, spatial locations, and geological meanings within the same project. The data source identifier records the source type and source file of a single data entry in the geological data package. It can be generated using the project number, file number, record line number, and data type, or it can be automatically assigned by the system during import. The data source identifier does not replace the original file storage address but is used to locate the data source in subsequent calculations of source reliability, error range, and anomaly tracing. For borehole records, the data source identifier can point to the borehole record table and its record lines; for geological maps, the data source identifier can point to the layer file, layer name, and feature number; for experimental data, the data source identifier can point to the test report number, sample number, and test batch.

[0018] Spatial coordinates are used to represent the location of geological data within the project's spatial scope. When reading spatial coordinates, the server prioritizes recognizing coordinate fields, coordinate system descriptions, and unit descriptions. When multiple coordinate fields exist in the geological data package, the valid coordinate field is determined according to the field mapping relationship in the project import template. For boreholes, sampling points, in-situ test points, and monitoring points, spatial coordinates are recorded using point coordinates; for geological boundaries or stratigraphic zones, spatial coordinates are recorded using linear or area geometry. If a coordinate field is missing but map positioning information exists, the server writes the data to a pending verification status and prompts that spatial positioning information needs to be supplemented. If a coordinate field exists but is outside the project scope, the server retains the original record and marks it as a spatial scope anomaly to prevent incorrect locations from directly participating in the generation of subsequent geological evidence points.

[0019] Elevation information is used to determine the vertical location of geological data. For borehole data, elevation information is typically the borehole opening elevation; for groundwater observation data, elevation information can be calculated from the borehole opening elevation and the water level depth; for geological map data, elevation information can be null, but the vertical reference description must be retained. The server stores elevation information along with depth intervals to avoid incomparability between different boreholes caused by using only depth to represent strata location. The depth interval includes the top and bottom boundary depths, used to represent the vertical range of strata strata, sampling sections, or test sections within the borehole. When parsing depth intervals, the server checks whether the top boundary depth is less than the bottom boundary depth and whether the depth interval exceeds the borehole's final depth; data that does not meet the check conditions is written to an anomaly log, while the original input value is retained.

[0020] Stratigraphic attributes describe the soil and rock content and engineering classification represented by the geological data. Stratigraphic attributes include soil and rock names and engineering geological classifications. Soil and rock names retain the names from the original records, such as silty clay, silty soil, strongly weathered granite, and sand. Engineering geological classifications categorize soil and rock names into the categories required for engineering analysis, such as cohesive soil, sandy soil, soft soil, gravelly soil, strongly weathered rock, and moderately weathered rock. The server merges these categories according to the soil and rock name dictionary and engineering classification rules configured for the project. When multiple engineering classifications are available for the same soil or rock name, the data is written to a pending verification status, which the user selects and confirms in the browser. Confirmed data retains the confirmation record and serves as the data basis for subsequent geological evidence point grouping, candidate geological interface generation, and fitting residual judgment.

[0021] Generate profile control axes according to project scope and profile configuration, and map the geological data to be processed into geological evidence points; The server reads the project boundaries, engineering axes, exploration point distribution, and profile configuration based on the project scope, generating profile control axes for organizing geological data. These control axes include horizontal axes, mileage directions, mapping widths, and vertical datums, used to transform the geological data to be processed into a unified profile representation space. The server projects the spatial coordinates in the geological data to obtain profile mileage and lateral offset; combines elevation information and depth intervals to obtain the top and bottom boundary elevations; then, based on the data source identifier, it determines the source reliability and error range, and writes the above data along with stratigraphic attributes into geological evidence points. These geological evidence points enter the candidate geological interface generation process for subsequent grouping according to profile location and stratigraphic attributes.

[0022] The profile configuration includes the profile axis, mileage direction, mapping width, and vertical datum, mapping the geological data to be processed into geological evidence points. This includes: determining the profile mileage and lateral offset corresponding to the geological data to be processed based on the profile axis and mileage direction; determining the top and bottom boundary elevations corresponding to the geological data to be processed based on elevation information, vertical datum, and depth range; determining the source reliability and error range based on the data source identifier, and writing the profile mileage, lateral offset, top boundary elevation, bottom boundary elevation, stratigraphic properties, source reliability, and error range into the geological evidence points.

[0023] In one embodiment, the profile configuration further includes profile axes, mileage directions, mapping widths, and vertical datums, enabling the geological data to be processed to be mapped according to the same planar and vertical references. Profile axes can be drawn by the user in a browser or generated by the server based on engineering axes, pit edges, tunnel axes, slope profile lines, or lines connecting exploration points. Mileage directions are used to determine the starting point and extension direction of the profile axes, preventing the same data point from generating opposite mileages in different directions. Mapping widths are used to limit the range of data that can participate in the current profile; their values ​​can be set according to the spacing between exploration points, the width of the engineering site, and the purpose of the profile. Data outside the mapping width is not written into the geological evidence points of the current profile, or is only retained as lateral reference data. Vertical datums are used to unify elevation calculations and can use project measurement datums, elevation control point datums, or engineering elevation datums specified in the design documents.

[0024] For point-based spatial data, the server projects the spatial coordinates onto the profile axes and calculates the profile mileage and lateral offset. When the profile axes are represented by piecewise lines, the server selects the line segment closest to the spatial coordinates and within the mapping width as the projection line segment. For linear or area-based geological map data, the server first calculates the intersection points or lines between the map geometry and the profile axes, and then maps the endpoints of these intersection points or lines to geological evidence points. The profile mileage and lateral offset can be determined according to the following relationship:

[0025]

[0026] For the first Spatial coordinates of the geological data to be processed For the first The starting coordinates of each section axis segment. For the first The coordinates of the endpoints of each section axis segment. For the first The cumulative mileage before the starting point of each profile axis segment For the profile mileage, The lateral offset is the input to the above calculation, which consists of spatial coordinates and profile axis segments. The output is the profile mileage and lateral offset, used to determine the horizontal position of the geological data on the profile control axis.

[0027] The server determines the top and bottom boundary elevations based on elevation information, vertical datum, and depth range. For borehole stratification data, the elevation information is typically the borehole opening elevation, and the depth range includes the top and bottom boundary depths. The top and bottom boundary elevations can be determined according to the following relationship:

[0028]

[0029] For the first The borehole elevation or reference elevation corresponding to the geological data to be processed. The top bound depth, The depth of the bottom boundary. This is the top boundary elevation. The above calculation takes elevation information and depth range as input and outputs the top and bottom boundary elevations, which are used to determine the vertical location of stratigraphic boundaries in the profile space. When the geological data only contains planar map information and not depth ranges, the server sets the top and bottom boundary elevations to null values ​​and marks them as planar evidence type to prevent this data from directly participating in vertical interface fitting.

[0030] Source reliability is determined based on the data type, formation time, measurement method, and verification status corresponding to the data source identifier. Field-measured borehole data, verified in-situ test data, and laboratory test data can be configured with higher source reliability; historical maps, manually entered data, or unverified attachments can be configured with lower source reliability. The error range is determined based on the measurement accuracy, map scale, coordinate transformation record, and depth record accuracy corresponding to the data source identifier. The server writes the profile mileage, lateral offset, top boundary elevation, bottom boundary elevation, stratigraphic attributes, source reliability, and error range into the geological evidence point, and records the profile control axis number used for mapping. If any key field is missing, the server retains the original parsed record and writes it to a pending verification status; data pending verification does not participate in the generation of the formal candidate geological interface and is re-executed after user supplementation or confirmation.

[0031] Candidate geological interfaces are generated based on geological evidence points. The candidate geological interfaces are elastically fitted according to evidence fitting rules, interface smoothing rules, stratigraphic sequence rules and conflict deduction rules to obtain the target geological object, the support relationship and conflict relationship between the target geological object and the geological evidence points. Candidate geological interfaces are generated based on geological evidence points. The server reads the stratigraphic attributes, profile mileage, top boundary elevation, and bottom boundary elevation of each geological evidence point. Data with the same or similar engineering geological classification and located within the influence range of the same profile control axis are grouped into the same processing unit, forming a set of stratigraphic evidence points for interface construction. The server generates candidate geological interfaces based on the set of stratigraphic evidence points and discretizes the candidate geological interfaces into interface control points. The elevations of the interface control points are adjusted according to evidence fitting rules, interface smoothing rules, stratigraphic order rules, and conflict deduction rules to form the target geological object. The server records geological evidence points that participate in the fitting and whose residuals are within the allowable range as supporting relationships, and records data with residuals exceeding the limit or conflicting with the stratigraphic order as conflict relationships, so that the target geological object can retain the basis for generation and anomaly evidence.

[0032] The process of generating candidate geological interfaces based on geological evidence points includes: grouping geological evidence points according to stratigraphic properties and profile mileage to obtain a set of stratigraphic evidence points; and generating candidate geological interfaces based on the profile mileage, top boundary elevation, and bottom boundary elevation in the set of stratigraphic evidence points.

[0033] In one embodiment, geological evidence points are grouped according to stratigraphic properties and profile mileage. These points are not simply merged based on rock and soil names, but rather a set of stratigraphic evidence points is formed by combining engineering geological classification, profile location, and vertical boundaries. The server reads the rock and soil names and engineering geological classifications from the geological evidence points and first performs standardization processing according to the rock and soil name dictionary configured for the project. For cases where the same rock and soil name exists in different written forms, the server retains the original rock and soil name and categorizes it under the same standard rock and soil name. For data with similar rock and soil names but different engineering geological classifications, the server does not directly merge them to avoid misclassifying strata with different properties as the same candidate geological interface.

[0034] The server arranges geological evidence points according to the profile control axis number and profile mileage, and determines whether a geological evidence point should participate in the current profile processing based on the mapping width. Profile mileage is used to determine the horizontal position of the geological evidence point in the profile direction, while the top and bottom boundary elevations are used to determine the vertical boundaries of the geological evidence point in the profile direction. For borehole stratification data, the server prioritizes using the top boundary elevation to generate the upper boundary candidate interface of the corresponding stratum and the bottom boundary elevation to generate the lower boundary candidate interface of the corresponding stratum. For groundwater or geological boundary data with only a single elevation, the server treats it as point or line evidence in the generation of the corresponding candidate interface, and does not forcibly expand it into a stratigraphic interval with top and bottom boundaries.

[0035] The formation of stratigraphic evidence point sets is also constrained by distance and continuity conditions. When the profile mileage difference between adjacent geological evidence points is less than the continuous judgment distance configured for the project, and they have the same engineering geological classification or belong to a classification that allows merging, the server will classify the adjacent geological evidence points into the same stratigraphic evidence point set. The continuous judgment distance can be set according to the average spacing between exploration points in the project, the site length, and the purpose of the profile; in engineering exploration projects, the continuous judgment distance usually does not exceed a certain multiple of the average spacing between adjacent exploration points to avoid directly generating continuous interfaces across areas with obvious lack of evidence. If there is a fault, fill boundary, excavation boundary, or manually confirmed zoning boundary between two geological evidence points, the server will truncate the stratigraphic evidence point set at the boundary and generate candidate geological interfaces separately.

[0036] Candidate geological interfaces are generated from the profile mileage, top boundary elevation, and bottom boundary elevation of the stratigraphic evidence point set. The server sets interface control points along the profile mileage direction. The location of the control points can be directly determined by the profile mileage of the geological evidence points, or intermediate control points can be inserted between adjacent profile mileages. The insertion interval is determined based on the exploration point spacing and profile display accuracy, and does not need to be fixed to a single value. The server uses the data adjacent to the control points in the stratigraphic evidence point set as the initial elevation basis for the candidate interfaces and records the geological evidence points associated with each control point. After the candidate geological interfaces are generated, the server establishes a source record for the candidate geological interfaces. The source record includes the geological evidence point number participating in the grouping, the corresponding stratigraphic attribute, the profile control axis number, and the initial elevation range. This source record is then used in the subsequent elastic fitting and relationship generation process.

[0037] Elastic fitting of candidate geological interfaces is performed according to evidence fitting rules, interface smoothing rules, stratigraphic sequence rules, and conflict deduction rules, including: discretizing candidate geological interfaces into multiple interface control points along the profile control axis; adjusting the elevation of the interface control points according to the evidence fitting rules; restricting elevation abrupt changes between adjacent interface control points according to the interface smoothing rules; and restricting the intersection between adjacent candidate geological interfaces according to the stratigraphic sequence rules.

[0038] In one embodiment, when elastically fitting candidate geological interfaces, the candidate geological interface is converted into multiple interface control points, and the elevation of the control points is adjusted jointly by three types of rules: evidence fitting, interface smoothing, and stratigraphic sequence. The server discretizes the candidate geological interface into multiple interface control points along the profile control axis. Each interface control point includes the profile mileage, current elevation, associated geological evidence points, and the candidate geological interface to which it belongs. The profile mileage of the interface control points can be set according to the profile mileage of the geological evidence points, or it can be set according to a fixed mileage interval. The fixed mileage interval is determined by the project accuracy requirements and the distribution of exploration points to avoid computational redundancy caused by overly dense control points, and to avoid insufficient representation of stratigraphic boundaries caused by overly sparse control points.

[0039] Evidence fitting rules are used to bring interface control points closer to the top or bottom boundary elevations given by adjacent geological evidence points. The server searches for geological evidence points within the mapping width and whose profile mileage distance is within the valid range for each interface control point, and sets the evidence weights for fitting based on source reliability and error range. The elevation of the interface control point can be obtained through weighted fitting:

[0040] in, For the first Elevation of each interface control point For the first The top or bottom boundary elevations provided by the geological evidence points involved in the fitting For the first The weight of evidence for each geological evidence point This represents the number of geological evidence points participating in the fitting of the current interface control points. The input to this calculation is the elevation and weight of the geological evidence points, and the output is the elevation of the interface control points, which is used to form preliminary fitting results for candidate geological interfaces.

[0041] Interface smoothing rules are used to limit elevation abrupt changes between adjacent interface control points that do not conform to geological continuity. The server calculates the elevation difference between adjacent control points. When the elevation difference exceeds the smoothing limit value configured for the project, the elevation is adjusted according to the reliability of the adjacent control points and their associated evidence. The smoothing limit value is set based on the empirical range of stratigraphic dip angle, the spacing between exploration points, and the project category. When there are bedrock protrusions, faults, or artificial fill boundaries in the engineering site, the smoothing limit intensity can be reduced or segmented interfaces can be set at the corresponding profile mileage to prevent genuine abrupt changes from being erroneously smoothed out. Interface smoothing rules only restrict elevation abrupt changes lacking specific boundary evidence and do not force all interfaces to be continuous.

[0042] Stratigraphic order rules are used to restrict intersections between adjacent candidate geological interfaces. The server arranges candidate geological interfaces according to engineering geological classification, stratigraphic number, or user-confirmed stratigraphic order, and checks whether the elevation of the upper interface at the same profile mileage is higher than that of the lower interface. If adjacent candidate geological interfaces intersect, the server determines the adjustment target based on the reliability and error range of the associated geological evidence points; the influence of geological evidence points with lower reliability or larger error range on the control point elevation is reduced, and data with higher reliability are retained first. After elastic fitting, the server transforms the candidate geological interfaces into target geological objects, and records geological evidence points with fitting residuals within the allowable range as supporting relationships, and records data with residuals exceeding the limit, causing interface intersections, or having their weights significantly reduced by conflict deduction rules as conflict relationships.

[0043] The conflict deduction rules include: in the case of conflict impact values ​​corresponding to geological evidence points, determining the weight deduction coefficient of the geological evidence points based on the conflict impact values; reducing the weight of the geological evidence points participating in elastic fitting based on the weight deduction coefficient; and readjusting the elevation of the interface control points based on the reduced weight.

[0044] In one embodiment, the conflict deduction rule elastic fitting process can receive existing conflict impact values ​​and use these values ​​to reduce the evidence weight of the corresponding geological evidence points. This is suitable for situations where there are historical fitting results, manual review results, or previous rounds of conflict propagation results. The server reads the conflict impact value corresponding to each geological evidence point. The conflict impact value indicates the degree to which the geological evidence point was judged as abnormal in previous processing, manual review, or view residual write-back. The conflict impact value can be set to a range of zero to one; the larger the value, the lower the direct traction effect of the geological evidence point on the current candidate geological interface. If no conflict impact value has been generated for a project, the server fits the data according to the initial evidence weight and does not perform conflict deduction.

[0045] The weight reduction factor is determined based on the impact of conflicts. The server can set the weight reduction factor linearly or according to the segmentation rules configured in the project. The weight reduction factor can be determined using the following formula:

[0046] in, For the first The original evidence weight of each geological evidence point For the first The conflict impact value corresponding to each geological evidence point For the first The evidence weights after deducting geological evidence points. The input to this calculation is the original evidence weights and conflict impact values, and the output is the evidence weights after deduction, which are used to readjust the elevations of interface control points. When the conflict impact value is zero, the evidence weights after deduction remain unchanged; when the conflict impact value is close to one, the influence of geological evidence points on the fitting results is significantly reduced, but the original data is not deleted and is still retained in the system for verification.

[0047] The server readjusts the elevation of the interface control points based on the reduced evidence weights. During readjustment, only the weights of the geological evidence points in the fitting process are changed; the original spatial location, top boundary elevation, bottom boundary elevation, and stratigraphic attributes of the geological evidence points remain unchanged. This avoids anomalous evidence directly influencing the target geological object while preserving the traceability of anomalous evidence in subsequent business views and manual reviews. If multiple geological evidence points within the same segment have high conflict impact values, the server marks the corresponding candidate geological interface segment as a segment awaiting review and does not directly generate a publishable target geological object. If only a single geological evidence point has a high conflict impact value, and adjacent evidence points have consistent stratigraphic attributes and stable elevation trends, the server refits the interface control points primarily based on the adjacent evidence points.

[0048] The conflict deduction rule is also used to maintain supportive and conflicting relationships. If the evidence weight after deduction is still higher than the participation threshold set by the project, and the residual after refitting is within the allowable range, the server records the geological evidence point and the target geological object as a supportive relationship. If the evidence weight after deduction is lower than the participation threshold, or the residual after refitting still exceeds the allowable range, the server records the geological evidence point and the target geological object as a conflicting relationship. The participation threshold is set by the project template or management personnel according to data quality requirements, and is used to distinguish between data that can continue to participate in the fitting process and data that is only retained as evidence of anomalies. Through the above processing, the target geological object not only includes the fitted geological interface, but also retains its formation basis, conflict sources, and the relationship foundation required for subsequent state updates.

[0049] Conflict evidence points are determined based on the fitting residuals, and the conflict impact value is propagated according to the support and conflict relationships to update the quality status and release status of the target geological object. After obtaining the target geological object and the supporting and conflicting relationships between the geological evidence points and the target geological object, the server performs residual checks on the geological evidence points participating in the elastic fitting. The server reads the fitted elevation of the target geological object at the corresponding profile mileage of the geological evidence point and compares it with the top or bottom boundary elevation of the geological evidence point to obtain the fitting residual. The fitting residual, combined with the error range, forms a standardized residual, which is used to determine whether a geological evidence point is a conflicting evidence point. Data identified as conflicting evidence points is not directly deleted, but rather used as the source of conflict impact values, propagating along the supporting and conflicting relationships to the associated target geological object, and updating the quality status and publication status of the target geological object accordingly.

[0050] Determining conflict evidence points based on fitting residuals includes: determining fitting residuals based on the fitted elevation of the target geological object at the profile mileage and the top or bottom boundary elevation of the geological evidence points; determining standardized residuals based on the fitting residuals and the error range; and identifying the corresponding geological evidence points as conflict evidence points when the standardized residuals are greater than the residual threshold.

[0051] In one embodiment, the fitting residual is determined based on the fitted elevation of the target geological object at the profile mileage, and the top or bottom boundary elevation of the geological evidence points. The server selects the top or bottom boundary elevation as the residual comparison object based on the boundary type corresponding to the geological evidence point when it participates in the generation of candidate geological interfaces. When a geological evidence point is used to support the upper boundary of a stratum, the server selects the top boundary elevation; when a geological evidence point is used to support the lower boundary of a stratum, the server selects the bottom boundary elevation; when a geological evidence point belongs to groundwater level, fault line, or other single elevation evidence, the server selects its corresponding elevation field as the comparison object. The server does not mix different boundary types for comparison to avoid incorrectly using upper boundary evidence for lower boundary residual judgment.

[0052] The fitting residuals can be determined as follows:

[0053] For the first The fitting residuals corresponding to each geological evidence point For the target geological object in the first The fitted elevation at the corresponding profile mileage for each geological evidence point. For the first The profile mileage corresponding to each geological evidence point For the first The calculation takes the fitted elevation of the target geological object and the boundary elevations of the geological evidence points as inputs, and outputs the fitted residuals, which measure the degree of deviation between the geological evidence points and the target geological object.

[0054] Because of the varying measurement accuracy, map scale, and reliability of manual data entry from different sources, the server does not directly use the fitted residuals as the basis for conflict determination. Instead, it determines the standardized residuals by combining the error range:

[0055] For the first Standardized residuals corresponding to each geological evidence point For the first The error range corresponding to each geological evidence point This is to avoid extremely small positive numbers with a denominator of zero. The inputs to this calculation are the fitted residuals and the error range, and the output is the standardized residuals, used to transform data from different precision sources to the same judgment scale. The error range is determined by the data source identifier, measurement method, map scale, depth recording precision, and verification status; high-precision data has a smaller error range, and low-precision data has a larger error range.

[0056] The server compares the standardized residuals with a residual threshold. The residual threshold is determined by the project's data quality requirements, exploration stage, and results publication requirements. It can be pre-configured in the project template or set by administrators during project initialization. Projects intended for formal results publication can set a lower residual threshold, while projects used for internal analysis or historical data compilation can set a higher threshold. When the standardized residuals exceed the residual threshold, the server identifies the corresponding geological evidence point as a conflict evidence point and records the conflict type, fit residuals, standardized residuals, associated target geological object, and trigger time. When the standardized residuals do not exceed the residual threshold, the server retains the corresponding geological evidence point as data supporting the target geological object.

[0057] Propagating conflict impact values ​​based on support and conflict relationships includes: determining the value corresponding to the standardized residual as the initial conflict impact value of the conflict evidence point; and propagating the initial conflict impact value to the target geological object associated with the conflict evidence point according to the propagation coefficients corresponding to the support and conflict relationships.

[0058] In one embodiment, the conflict impact value propagation is performed based on the propagation coefficients corresponding to the support and conflict relationships, respectively. The server determines the initial conflict impact value as the value corresponding to the standardized residual of the conflict evidence point and writes this initial conflict impact value into the anomaly record of the conflict evidence point. To avoid a single extreme outlier causing excessive degradation of all related objects, the server can limit the initial conflict impact value to a valid range configured in the project settings. The project configuration can set the upper limit of the initial conflict impact value to one, or it can be set to an upper limit value related to the residual threshold. Standardized residuals exceeding the upper limit participate in propagation according to the upper limit value, while the original standardized residuals are still retained in the anomaly record for review.

[0059] The propagation of conflict impact values ​​is performed based on supporting and conflicting relationships. Supporting relationships indicate that geological evidence points positively support the formation of the target geological object, while conflicting relationships indicate that there are residual exceedances, stratigraphic sequence conflicts, or anomalous deductions between geological evidence points and the target geological object. The server sets propagation coefficients for different relationship types. The propagation coefficient for conflicting relationships is higher than that for supporting relationships, representing the direct impact of conflicting data on the state of the target geological object; the propagation coefficient for supporting relationships is lower than that for conflicting relationships, representing that even when an anomaly occurs in supporting evidence, it still has some impact on the target geological object formed with the participation of that evidence. The propagation coefficient can be configured by the project template, and its value is based on factors including relationship type, evidence weight, source reliability, and the publication level of the target geological object.

[0060] The propagation of conflict impact values ​​can be performed as follows:

[0061] For the first The conflict impact value received by each target geological object. In order to be with the first A set of conflicting evidence points indicating a supporting or conflicting relationship between a target geological object. For the first The initial conflict impact value of each conflict evidence point For the first The conflicting evidence point and the first The propagation coefficients correspond to the relationships between target geological objects. The inputs to this calculation are the initial conflict impact values ​​and propagation coefficients, and the output is the conflict impact values ​​propagated to the target geological objects, which are used to determine whether the target geological objects need to be downgraded.

[0062] The server records the conflict path during propagation. The conflict path includes the conflict evidence point number, relationship type, propagation coefficient, target geological object number receiving the conflict impact value, and propagation result. If the same target geological object receives multiple conflict impact values ​​simultaneously, the server can use the maximum value as the conflict impact value for that target geological object, or it can use a weighted merging method configured for the project. Using the maximum value highlights the conflict evidence point with the greatest impact; using weighted merging is suitable for scenarios where multiple minor anomalies jointly affect the same target geological object. Regardless of the method used, the server retains a list of conflict evidence points involved in the propagation, facilitating the display of anomaly sources on the browser and manual verification.

[0063] Update the quality status and publication status of the target geological object, including: if the conflict impact value propagated to the target geological object is greater than the conflict threshold, update the quality status of the target geological object to the pending review status and update the publication status of the target geological object to the prohibited publication status.

[0064] In one embodiment, the updates to the quality status and release status are determined based on the conflict impact value propagated to the target geological object and a conflict threshold. The conflict threshold is used to distinguish whether the target geological object can continue to be used as a normal deliverable, and its setting is based on factors including project stage, deliverable purpose, geological object type, and data quality requirements. Target geological objects used for formal deliverable release can have a lower conflict threshold, while target geological objects used for internal analysis can have a higher conflict threshold. Different types of target geological objects can use different conflict thresholds; for example, stratigraphic interfaces, groundwater levels, weak interlayer boundaries, and engineering geological zones can each be configured with corresponding thresholds.

[0065] When the conflict impact value propagated to the target geological object exceeds the conflict threshold, the server updates the target geological object's quality status to "Pending Review" and its release status to "Prohibited Release." The quality status indicates whether the target geological object requires manual review or recalculation, while the release status controls whether the target geological object can be included in the formal output of the business view. The "Pending Review" status does not mean the target geological object has been deleted; it still retains its fitting interface, supporting relationships, conflict relationships, and anomaly sources. The "Prohibited Release" status only restricts the target geological object from entering the formal release process; it still allows display in the internal analysis view or anomaly review interface.

[0066] If the conflict impact value propagated to the target geological object does not exceed the conflict threshold, the server maintains the current quality status and publication status of the target geological object, or marks it as available according to the project configuration. If the target geological object was originally in a pending review state, but the conflict impact value is lower than the recovery threshold after this round of refitting and propagation, the server does not automatically restore its publication status, but instead adds it to the pending confirmation list. The recovery threshold can be lower than the conflict threshold to avoid repeated switching of status within the critical range. After the user confirms on the browser that the exception has been handled, the server records the confirmation event and updates the quality status of the target geological object to the reviewed state and the publication status to the allowed publication state based on the confirmation result.

[0067] The server synchronously generates a status change record when updating the status. The status change record includes the target geological object number, conflict evidence point number, conflict impact value, conflict threshold, original quality status, new quality status, original release status, new release status, and change time. The status change record is incorporated into the subsequent business view generation process to control whether the business view references the target geological object. If a business view needs to call a target geological object with a prohibited release status, the server excludes that target geological object from the formal deliverables view and records the reason for exclusion in the exception information. Therefore, local geological evidence point anomalies can affect the status of the target geological object through support and conflict relationships, and the status of the target geological object can in turn affect the subsequent business view generation and exception write-back.

[0068] An operational view is generated based on the target geological object, and anomaly information is written back to the geological evidence points and the target geological object according to the view residuals of the operational view.

[0069] After updating the quality status and publication status of the target geological object, the server generates corresponding business views according to the business type. Business views can include profile analysis views, stratigraphic distribution views, parameter statistics views, and result publication views. When generating business views, the server records the called target geological object, geological evidence points, object status, and result version. During the view generation process, it detects anomalies such as stratigraphic interface intersections, insufficient evidence quantity, and inconsistent result versions, forming view residuals. View residuals are used to locate data defects exposed in the business views. Based on the call records, the server writes the anomaly information to the corresponding geological evidence points and target geological objects, enabling the source of the anomalies to be traced and involved in subsequent review.

[0070] Write back anomaly information to geological evidence points and target geological objects based on the view residuals of the business view, including: detecting at least one anomaly among stratigraphic interface intersection, insufficient evidence quantity, and inconsistent result version based on the business view, and obtaining the view residuals; and writing the anomaly information to the corresponding geological evidence points and target geological objects based on the records of calling geological evidence points and target geological objects when generating the business view.

[0071] In one embodiment, the write-back of the operational view residuals synchronously saves the call record during the view generation process, and determines the object to which the abnormal information is written based on the call record. When the server generates the operational view, it not only outputs the profile lines, stratigraphic boundaries, statistical results, or result pages for display, but also saves a data source record for each display unit. The data source record includes the operational view identifier, display unit identifier, the number of the target geological object called, the number of the geological evidence point called, the quality status at the time of call, the publication status at the time of call, and the result version at the time of call. The display unit can be a stratigraphic interface, a stratigraphic partition, a parameter statistical unit, or a result publication entry in the profile. The server establishes a traceable relationship between the operational view and the target geological object and geological evidence point through the data source record, avoiding the inability to locate the specific data source when an anomaly occurs in the operational view.

[0072] The server detects at least one of the following anomalies based on the business view: stratigraphic interface intersection, insufficient evidence quantity, and inconsistent result version. Stratigraphic interface intersection is used to determine whether adjacent geological interfaces in the profile analysis view violate the stratigraphic order. The server traverses the geological interfaces in the business view according to the profile mileage, comparing the elevation relationship between adjacent interfaces; when the elevation of the upper interface is lower than that of the lower interface, or when two interfaces intersect within a mileage range where pinch-out or fault separation is not allowed, the server generates an interface intersection anomaly. Insufficient evidence quantity is used to determine whether the target geological object has sufficient supporting geological evidence points. The server configures the minimum evidence quantity for different object types according to the project template; stratigraphic interfaces can be configured based on the number of adjacent boreholes or the number of stratigraphic evidence points, and parameter statistics views can be configured based on the number of valid test samples. Inconsistent result version is used to determine whether the business view mixes data from different release batches or different review statuses; when the target geological object called by the same business view comes from different result versions, and no manual confirmation information allowing mixing is recorded, the server generates a result version anomaly.

[0073] View residuals can be summarized as follows:

[0074] For the first View residuals for each business view For the first Cross-interface anomalies in the stratum interface of each business view. For the first The number of pieces of evidence in a business view is insufficient, which is an outlier. For the first Outlier in inconsistent outcome versions in different business views , and This refers to the weighting coefficients corresponding to the anomaly types. The input for this calculation is the anomaly detection result in the business view, and the output is the view residual, used to determine whether anomaly information needs to be written into geological evidence points and target geological objects. The weighting coefficients are determined by the project template or deliverable release requirements; in formal deliverable release scenarios, higher weights can be set for inconsistent deliverable versions and overlapping stratigraphic interfaces, while in internal analysis scenarios, the weights can be reduced or only the alert status can be written.

[0075] When the view residual exceeds the view residual threshold, the server writes the anomaly information to the corresponding object based on the records of the target geological objects and geological evidence points invoked when generating the business view. The view residual threshold is set according to the business view type and the purpose of the result. Profile analysis views mainly focus on interface intersections, parameter statistics views mainly focus on insufficient evidence quantity, and result release views mainly focus on result version inconsistencies. Anomaly information includes anomaly type, anomaly location, view residual, trigger rule, business view identifier, associated target geological object number, and associated geological evidence point number. For stratigraphic interface intersection anomalies, the server writes the anomaly information to the target geological object involved in the generation of the intersection interface and simultaneously writes the geological evidence points supporting the corresponding interface control points. For insufficient evidence quantity anomalies, the server writes the anomaly information to the corresponding target geological object and records the missing evidence type and quantity. For result version inconsistency anomalies, the server writes the anomaly information to the target geological object involved in the version conflict, restricting it from entering the formal release process until user confirmation or regeneration of the business view.

[0076] In one embodiment, the specific implementation process is illustrated using a foundation pit investigation project for a city rail transit station as an example. The project establishes a business profile along its long side, with a profile length of 120m. The browser uploads the investigation data package for seven boreholes, stratigraphic records, in-situ test summaries, and existing results index files. The server performs parsing, profile mapping, interface fitting, conflict identification, status updates, and business view write-back. The spatial positions of the seven boreholes along the profile direction are 0m, 20m, 40m, 60m, 80m, 100m, and 120m, with borehole elevations of 98.60m, 98.20m, 97.90m, 97.30m, 96.90m, 96.40m, and 96.00m, respectively. In the profile configuration, the profile axis is taken as the station's central axis, the mileage direction is from west to east, the mapping width is 15m, and the vertical datum adopts the project's unified engineering elevation datum.

[0077] After parsing the geological data package, unprocessed geological data is generated. Each piece of unprocessed geological data includes a data source identifier, spatial coordinates, elevation information, depth range, and stratigraphic attributes. Taking three main types of strata as examples, the top boundary elevations of silty clay are 97.8m, 97.2m, 96.8m, 96.1m, 95.7m, 95.3m, and 95.0m, respectively; the top boundary elevations of medium sand are 92.4m, 91.8m, 91.2m, 90.6m, 90.1m, 89.6m, and 89.0m, respectively; and the top boundary elevations of strongly weathered granite are 86.3m, 85.6m, 84.9m, 84.2m, 83.5m, 82.8m, and 82.0m, respectively. The server maps the above data to geological evidence points based on the project scope and profile configuration. Each geological evidence point contains the profile mileage, lateral offset, top boundary elevation, bottom boundary elevation, stratigraphic properties, source reliability, and error range. The source reliability of borehole measured stratification data is set to 0.90, and the source reliability of historical data extracts is set to 0.60. The error range is configured from 0.40m to 0.60m based on the data source and measurement accuracy.

[0078] The server groups geological evidence points based on stratigraphic properties and profile mileage, forming three sets of stratigraphic evidence points: silty clay, medium sand, and strongly weathered granite. Based on these sets, candidate geological interfaces are generated. These candidate interfaces are discretized along the profile control axis into interface control points, and then elastic fitting is performed according to evidence fitting rules, interface smoothing rules, stratigraphic sequence rules, and conflict deduction rules to form the target geological object. Figure 2 The data was drawn based on geological evidence data from seven boreholes and three stratigraphic interfaces obtained through fitting. For example... Figure 2 As shown, the horizontal axis represents the profile mileage, and the vertical axis represents the elevation. The fitted lines for the top boundaries of silty clay, medium sand, and strongly weathered granite are represented by different colors, and the corresponding geological evidence points are marked with dots of different shapes. The three fitted interfaces in the figure generally show a slow downward trend from left to right. The geological evidence points for silty clay, medium sand, and strongly weathered granite are distributed near their respective fitted lines, and each evidence point maintains a good fit with its corresponding fitted line. This indicates that the profile control axis mapping and interface elastic fitting can stably reflect the continuous variation characteristics of the site's stratigraphic boundaries.

[0079] After fitting is complete, the server determines the fitting residuals based on the differences between the target geological object and the geological evidence points. The fitting residuals are calculated using the following formula:

[0080] For the first The fitting residuals of each geological evidence point This refers to the fitted elevation of the target geological object at the corresponding profile mileage. For the first The profile mileage corresponding to each geological evidence point. This represents the top or bottom boundary elevation of the geological evidence point. In this embodiment, the error range of each geological evidence point is greater than zero, and the standardized residuals are calculated by directly normalizing the error range.

[0081] To standardize the residuals, The error range for the geological evidence points is defined as follows. Taking the top boundary of the medium sand as an example, the fitting residuals for the seven geological evidence points are 0.22m, 0.31m, 0.45m, 1.62m, 0.38m, 0.29m, and 0.27m, respectively, corresponding to error ranges of 0.50m, 0.50m, 0.60m, 0.40m, 0.50m, 0.60m, and 0.50m. The calculated standardized residuals are 0.44, 0.62, 0.75, 4.05, 0.76, 0.48, and 0.54. The residual threshold is set to 2.50 in this project because it is a formal results release scenario, requiring strict control over the interface fitting quality. The calculation results show that only the fourth medium sand evidence point located at mileage 60m exceeds the residual threshold and is therefore identified as a conflict evidence point. Figure 3 This was plotted based on the standardized residual calculation results of the above 7 medium sand evidence points. (For example...) Figure 3 As shown, the standardized residuals of the seven geological evidence points are displayed in a bar chart, and the residual threshold is represented by a horizontal line. Only the column value corresponding to ZK4-medium sand exceeds the threshold line, while the value of the remaining evidence points is below the threshold line, indicating that the conflict identification results have clear boundaries.

[0082] The server maps the standardized residuals of conflict evidence points to initial conflict impact values. To avoid a single outlier causing uncontrolled propagation, this embodiment limits the initial conflict impact value to the range of 0 to 1. The standardized residual of ZK4-medium sand is 4.05, and the corresponding initial conflict impact value is recorded as 1.00. This conflict evidence point is associated with three target geological objects, denoted as A1, A2, and A3. Propagation coefficients are configured based on support and conflict relationships, with a coefficient of 0.45 for propagation to A1, 0.81 for propagation to A2, and 0.32 for propagation to A3. Therefore, the conflict impact values ​​received by the three target geological objects are 0.45, 0.81, and 0.32, respectively. The conflict threshold is set to 0.70 in the project. Therefore, the conflict impact value of A2 exceeds the threshold, and its quality status is updated to pending review, and its publication status is updated to prohibited publication. A1 and A3 remain available. Figure 4 It is drawn based on the relationships between conflict evidence points, target geological objects, and operational views. For example... Figure 4As shown, the left side represents conflict evidence point E4, the middle section contains three target geological objects A1, A2, and A3, and the right side contains two operational views V1 and V2. Conflict evidence point E4 is associated with A1, A2, and A3 respectively. The values ​​marked next to the connecting lines represent the propagation coefficient or the conflict impact value after propagation. Specifically, E4 propagates 0.45 to A1, 0.81 to A2, and 0.32 to A3. A1, A2, and A3 further establish calling relationships with operational views V1 and V2. As can be seen from the relationships in the figure, A2 receives the largest conflict impact value, exceeding the conflict threshold set in this embodiment. Therefore, A2 is updated to a pending review state and restricted from entering the formal release view, while A1 and A3 can still maintain normal usage.

[0083] During the business view generation phase, the server generates profile analysis views and results publication views based on the current state of the target geological object, and detects three types of anomalies: stratigraphic interface intersections, insufficient evidence, and inconsistent results versions. The business view residuals are calculated using the following formula:

[0084] For business view residuals, This is an anomaly at the stratigraphic interface. This is an outlier due to insufficient evidence. This is an outlier indicating a version inconsistency in the output. , and These are the weighting coefficients for the three types of anomalies. In this embodiment, we take... , , In the initial business view, the three types of outliers were 1.20, 0.70, and 0.80, respectively, resulting in a view residual of 0.98. After performing conflict deduction and status update, the three types of outliers became 0.35, 0.55, and 0.30, and the view residual decreased to 0.375. After manual review and correction of the source of the outliers, the three types of outliers became 0.00, 0.20, and 0.00, and the view residual further decreased to 0.04. Figure 5 This was plotted based on the outlier statistics from the three stages mentioned above. For example... Figure 5 As shown in the figure, the horizontal axis represents the processing stage, and the vertical axis represents outliers. The three sets of bars represent interface crossover outliers, insufficient evidence outliers, and inconsistent result versions outliers, respectively. The figure shows that all three types of outliers are quite noticeable in the initial view stage. After conflict deduction, interface crossover outliers and inconsistent result versions outliers decrease significantly. After manual review, interface crossover outliers and inconsistent result versions outliers drop to zero, with only a small number of insufficient evidence outliers remaining. This indicates that structural outliers in the business view have significantly converged.

[0085] Based on the above implementation process and calculation results, it can be seen that this invention does not merely achieve centralized storage of geological data, but rather establishes a traceable closed loop from geological evidence points to target geological objects and then to operational views. In this embodiment, seven borehole data points form a stable stratigraphic interface after profile mapping and elastic fitting; one conflict evidence point is accurately identified through fitting residuals and standardized residuals; one target geological object requiring review and prohibited from publication is accurately located through conflict impact value propagation; and anomaly information is written back to the target geological object and geological evidence points through operational view residuals, reducing the view residual from 0.98 to 0.04. These results demonstrate that this invention can establish a clear data link between local anomaly evidence and overall operational results, achieving coordinated processing of geological data management, quality control, and results publication under a B / S architecture.

[0086] The above are merely embodiments of the present invention and are not intended to limit the invention. Those skilled in the art can make various modifications, equivalent substitutions, and improvements within the spirit and principles of the present invention.

Claims

1. A B / S architecture geological data management method, characterized in that, The method includes: Parse the geological data package to obtain geological data to be processed. The geological data to be processed includes data source identifier, spatial coordinates, elevation information, depth range and stratigraphic attributes. The stratigraphic attributes include rock and soil names and engineering geological classifications. A profile control axis is generated according to the project scope and profile configuration, and the geological data to be processed is mapped to geological evidence points. The profile configuration includes a profile axis, mileage direction, mapping width, and vertical datum. Mapping the geological data to be processed to geological evidence points includes: determining the profile mileage and lateral offset corresponding to the geological data to be processed based on the profile axis and the mileage direction; determining the top boundary elevation and bottom boundary elevation corresponding to the geological data to be processed based on the elevation information, the vertical datum, and the depth interval; determining the source reliability and error range based on the data source identifier, and writing the profile mileage, the lateral offset, the top boundary elevation, the bottom boundary elevation, the stratigraphic attributes, the source reliability, and the error range into the geological evidence points. Based on the geological evidence points, candidate geological interfaces are generated. The candidate geological interfaces are elastically fitted according to evidence fitting rules, interface smoothing rules, stratigraphic sequence rules and conflict deduction rules to obtain the target geological object, the support relationship and conflict relationship between the target geological object and the geological evidence points. The elastic fitting of the candidate geological interface according to the evidence fitting rule, interface smoothing rule, stratigraphic sequence rule, and conflict deduction rule includes: discretizing the candidate geological interface into multiple interface control points along the profile control axis; adjusting the elevation of the interface control points according to the evidence fitting rule; limiting elevation abrupt changes between adjacent interface control points according to the interface smoothing rule; and limiting the intersection between adjacent candidate geological interfaces according to the stratigraphic sequence rule. The conflict deduction rule includes: in the case of a conflict impact value corresponding to the geological evidence point, determining the weight deduction coefficient of the geological evidence point based on the conflict impact value; reducing the weight of the geological evidence point in the elastic fitting based on the weight deduction coefficient; and readjusting the elevation of the interface control point based on the reduced weight. Conflict evidence points are determined based on the fitting residuals, and conflict impact values ​​are propagated according to the support relationship and the conflict relationship to update the quality status and release status of the target geological object. The step of determining conflict evidence points based on fitting residuals includes: determining the fitting residuals based on the fitting elevation of the target geological object at the profile mileage and the top or bottom elevation of the geological evidence points; determining standardized residuals based on the fitting residuals and the error range; and determining the corresponding geological evidence points as conflict evidence points when the standardized residuals are greater than a residual threshold. The step of propagating the conflict impact value according to the support relationship and the conflict relationship includes: determining the value corresponding to the standardized residual as the initial conflict impact value of the conflict evidence point; and propagating the initial conflict impact value to the target geological object associated with the conflict evidence point according to the propagation coefficients corresponding to the support relationship and the conflict relationship respectively. The step of updating the quality status and publication status of the target geological object includes: when the conflict impact value propagated to the target geological object is greater than the conflict threshold, updating the quality status of the target geological object to a pending review status and updating the publication status of the target geological object to a prohibited publication status; An operational view is generated based on the target geological object, and anomaly information is written back to the geological evidence points and the target geological object according to the view residuals of the operational view.

2. The method according to claim 1, characterized in that, The step of generating candidate geological interfaces based on the geological evidence points includes: The geological evidence points are grouped according to the stratigraphic properties and the profile mileage to obtain a set of stratigraphic evidence points. The candidate geological interface is generated based on the profile mileage, the top boundary elevation, and the bottom boundary elevation in the set of stratigraphic evidence points.

3. The method according to claim 1, characterized in that, The step of writing back anomaly information to the geological evidence points and the target geological object based on the view residuals of the business view includes: Based on the business view, detect at least one of the following anomalies: stratigraphic interface intersection, insufficient evidence quantity, and inconsistent result version, and obtain the view residual; Based on the records of calling the geological evidence points and the target geological object when generating the business view, the abnormal information is written to the corresponding geological evidence points and the target geological object.

Images