Geological data visualization display method and system

Abstract

The application provides a geological data visualization display method and system, and belongs to the technical field of geological information. The method comprises the following steps: loading layers of original geological vector data to obtain to-be-verified geological layer data, and verifying elements of the to-be-verified geological layer data based on a quality checking rule set; determining abnormal elements based on an element verification result, and classifying and updating errors of the abnormal elements in the to-be-verified geological layer data to obtain updated geological layer data; retrieving a thematic element set from the updated geological layer data based on a user-defined query condition; selecting a scalable vector graphics symbol matched with the element code of each element in the thematic element set from a standardized symbol library, and symbol rendering is performed on the element based on the scalable vector graphics symbol to obtain a visual thematic map. The application can realize geological data quality inspection, retrieval and visualization, and improve the mapping efficiency and the standardization of the results.

Description

Technical Field

[0001] This application belongs to the field of geological information technology, and more specifically, relates to a method and system for visualizing geological data. Background Technology

[0002] In the fields of geological survey and mineral resource exploration, Geographic Information System (GIS) technology is widely used. Geological data visualization can combine the spatial and attribute information of geological elements to represent geological bodies in a symbolic form, providing decision support for various geological operations. Although existing mainstream GIS platforms have basic mapping capabilities, they still have shortcomings in serving professional geological operations.

[0003] On the one hand, geological symbols lack standardized and automated management mechanisms. Symbol matching relies heavily on manual configuration one by one and cannot be automatically matched and managed based on geological element coding. This results in low processing efficiency when dealing with large amounts of data, is prone to human error, and makes it difficult to guarantee the standardization of maps. At the same time, symbols lack classification and hierarchical management methods, making it inconvenient to conduct management and retrieval by major element categories.

[0004] On the other hand, there are shortcomings in the ability to inspect the quality of geological spatial data. Data quality directly determines the reliability of subsequent analysis results. Existing methods mostly rely on manual verification or use automated tools with fixed rules. The inspection rules are difficult to customize and adjust flexibly, resulting in low overall quality inspection efficiency. Summary of the Invention

[0005] The purpose of this application is to provide a method and system for visualizing geological data, addressing the issues of insufficient automation and standardization of geological symbols and poor flexibility in customizing spatial data quality inspection rules. To solve these problems, the technical solution provided by this application is as follows: Firstly, a method for visualizing geological data is provided, including: The original geological vector data is loaded into layers to obtain geological layer data to be verified. Feature verification is performed on the geological layer data to be verified based on the quality inspection rule set. The quality inspection rule set includes pre-built spatial geometry rules and geological feature attribute verification rules. Based on the feature verification results, abnormal features are identified, and the abnormal features in the geological layer data to be verified are classified and updated to obtain the updated geological layer data. Based on user-defined query conditions, the thematic feature set matching the user-defined query conditions is retrieved from the updated geological layer data; For each element in the thematic element set, a scalable vector graphic symbol matching the element's code is selected from the standardized symbol library, and the element is rendered based on the scalable vector graphic symbol to obtain a visualized thematic map.

[0006] Secondly, a geological data visualization system is provided, including: The layer loading and verification module is used to load the original geological vector data into layers to obtain geological layer data to be verified, and to perform feature verification on the geological layer data to be verified based on the quality inspection rule set; the quality inspection rule set includes pre-built spatial geometry rules and geological feature attribute verification rules. The anomaly correction module is used to identify anomalous features based on the feature verification results, and to classify and update the anomalous features in the geological layer data to be verified, so as to obtain the updated geological layer data. The data mining module is used to retrieve a set of thematic elements that match user-defined query conditions from updated geological layer data. The visualization thematic module is used to select a scalable vector graphic symbol that matches the code of each element in the thematic element set from the standardized symbol library, and to perform symbol rendering on the element based on the scalable vector graphic symbol to obtain a visualization thematic map.

[0007] Thirdly, embodiments of this application also provide an electronic device, which includes a memory and a processor. The memory stores a computer program, and the processor executes the computer program to implement the geological data visualization method provided by any possible implementation of the first aspect.

[0008] Fourthly, embodiments of this application also provide a computer-readable storage medium storing a computer program that, when executed by a processor, implements the geological data visualization method provided by any possible implementation of the first aspect.

[0009] The beneficial effects of the technical solution provided in this application are as follows: The geological data visualization method and system provided in this application, compared with related technologies, are as follows: This application embodiment uses a quality inspection rule set to perform element verification and performs error classification and update processing on detected abnormal elements to obtain updated geological layer data. Compared with traditional manual verification or fixed rule quality inspection tools, this application embodiment uses a rule set to complete the automated verification of layer elements and classifies and handles identified abnormal elements. This allows for flexible quality control of geological vector data, improving the problems of inflexible adjustment of inspection rules and low quality inspection efficiency in traditional models, and ensuring the quality of geological layer data input into subsequent processes.

[0010] Based on the updated geological layer data obtained after quality rectification, this embodiment of the application performs data mining retrieval according to user-defined query conditions, quickly obtaining the thematic element set required for business operations, eliminating the need for manual element screening and organization. Furthermore, this embodiment of the application utilizes a standardized symbol library to automatically match corresponding scalable vector graphic symbols based on element codes to complete rendering and generate visual thematic maps. Unlike the traditional method of manually configuring symbols one by one, this embodiment of the application relies on coding to automatically match symbols, avoiding operational errors caused by manual configuration. Attached Figure Description

[0011] To more clearly illustrate the technical solutions in the embodiments of this application, the accompanying drawings used in the description of the embodiments of this application will be briefly introduced below.

[0012] Figure 1 A flowchart illustrating the geological data visualization method provided in this application embodiment; Figure 2 A structural block diagram of the geological data visualization system provided in the embodiments of this application; Figure 3 A schematic block diagram of an electronic device provided in an embodiment of this application. Detailed Implementation

[0013] The embodiments of this application are described below with reference to the accompanying drawings. It should be understood that the embodiments described below with reference to the accompanying drawings are exemplary descriptions for explaining the technical solutions of the embodiments of this application, and do not constitute a limitation on the technical solutions of the embodiments of this application.

[0014] Those skilled in the art will understand that, unless specifically stated otherwise, the singular forms “a,” “an,” “the,” and “the” used herein may also include the plural forms. It should be further understood that the terms “comprising” and “including” as used in embodiments of this application mean that the corresponding feature can be implemented as the presented feature, information, data, step, operation, element, and / or component, but do not exclude implementation as other features, information, data, step, operation, element, component, and / or combinations thereof supported by the art. It should be understood that when we say that an element is “connected” or “coupled” to another element, the one element can be directly connected or coupled to the other element, or it can mean that the one element and the other element establish a connection relationship through an intermediate element. Furthermore, “connected” or “coupled” as used herein can include wireless connection or wireless coupling. The term “and / or” as used herein indicates at least one of the items defined by the term; for example, “A and / or B” can be implemented as “A,” or as “B,” or as “A and B.” When describing multiple (two or more) items, if the relationship between the multiple items is not explicitly defined, the multiple items can refer to one, several or all of the multiple items. For example, the description of "parameter A includes A1, A2, A3" can be implemented as parameter A includes A1 or A2 or A3, or it can be implemented as parameter A includes at least two of the three items A1, A2 and A3.

[0015] It is understood that in the embodiments of this application, data related to user information is involved. When the embodiments of this application are applied to specific products or technologies, user permission or consent is required, and the collection, use and processing of related data must comply with relevant laws, regulations and standards.

[0016] To make the objectives, technical solutions, and advantages of this application clearer, the following description will be provided in conjunction with the accompanying drawings and specific embodiments.

[0017] This application provides a method for visualizing geological data, which can be executed by an electronic device, such as... Figure 1 As shown, the method may include: S101: Load the original geological vector data into a layer to obtain the geological layer data to be verified, and perform feature verification on the geological layer data to be verified based on the quality inspection rule set; the quality inspection rule set includes pre-built spatial geometry rules and geological feature attribute verification rules.

[0018] In this embodiment, a geological data visualization method further includes: Before loading layers onto the original geological vector data, obtain the user's input rules for editing geological features, and configure the initial geological data inspection rules based on the rules for editing. The rules for checking initial geological data are validated, including syntax checking and logical conflict detection. A quality inspection rule set is obtained based on the inspection rules that pass the rule validation. The quality inspection rule set includes spatial geometry rules and geological element attribute verification rules. Among them, the spatial geometry rules include invalid geometry check rules, surface element gap check rules, intra-layer element overlap check rules, cross-layer element overlap check rules, and spatial location accuracy check rules. The geological element attribute verification rules include mandatory field integrity verification, field format verification, and enumerated value verification.

[0019] In this embodiment, the quality inspection rule set includes spatial geometry rules and geological element attribute verification rules; element verification is performed on the geological layer data to be verified based on the quality inspection rule set, including: Based on the spatial geometry rules in the quality inspection rule set, spatial geometry verification is performed on each element in the geological layer data to be verified in order to identify spatial geometry anomalies of the elements. Spatial geometry anomalies include invalid geometry, voids in surface elements, overlapping elements, cross-layer overlap, and spatial position accuracy not meeting the requirements. Based on the geological element attribute verification rules in the quality inspection rule set, geological element attribute field verification is performed on each element in the geological layer data to be verified in order to identify attribute anomalies such as missing required fields, field formats not meeting specifications, and field values ​​not being within the preset enumeration range.

[0020] For example, this embodiment can be used in the actual business scenario of creating geological hazard thematic maps. It processes a vector dataset of geological hazard hazards obtained from field surveys. This dataset records the location coordinates and business attributes of landslide, collapse, and debris flow hazards. The original data is collected in the field and then processed and stored indoors. This embodiment can read the original geological hazard hazard vector dataset stored on the storage medium into the runtime memory, complete the layer loading process, and form a geological layer data to be verified that can be called by various verification logics. Subsequently, it calls a pre-built quality inspection rule set to perform geological element verification work on the entire layer.

[0021] Before performing layer loading operations, operators can customize inspection rules through an interactive interface, based on the technical requirements of the current geological survey project. The operator's interface operations are translated into corresponding rule editing instructions. These instructions can include adding inspection constraints, adjusting existing rule parameters, and deleting outdated rules. In this embodiment, upon receiving such rule editing instructions, initial geological data inspection rules that have not yet undergone validity verification are generated. For example, when conducting a county-level geological hazard risk survey project, staff need to add inspection constraints for surface feature voids and modify the tolerance parameters corresponding to spatial location accuracy to meet the accuracy control requirements of the project's results.

[0022] This embodiment performs a complete rule verification process on the generated initial geological data inspection rules. Syntax checking primarily identifies writing-level issues such as missing parameters and mismatched parameter data types, as well as semantic-level issues such as parameter values ​​exceeding limits, inconsistencies in business logic, and incorrect object relationships. Spatial location accuracy verification requires the input of numerical tolerances; if the operator enters incorrect text, the syntax check will detect such errors and prompt for correction. Logical conflict detection is used to identify mutually exclusive and contradictory situations between multiple rules. For example, if two sets of constraints—prohibiting void generation and allowing voids within a specific range—are enabled simultaneously on the same layer, the system can identify this configuration conflict and remind the operator to readjust the rule combination. Only after all verification steps are passed will the corresponding multiple inspection constraints be combined to form a quality inspection rule set that can be formally put into use.

[0023] The quality inspection rule set is divided into two main categories, used to control the spatial morphology of elements and the content of business attributes, respectively. Spatial geometry-related verification is performed sequentially on each geological element within the layer to be verified in memory, identifying various spatial morphological defects. Invalid geometry identification primarily checks for structural defects in the spatial geometric shape itself. For example, self-intersecting lines, line segment lengths approaching zero, and broken closed loops at the boundaries of area disaster assessment zones are all judged as invalid geometric anomalies. Area element gap verification is used to identify blank areas not covered by any area elements after adjacent area units are spliced ​​together. This project sets a gap detection threshold of 0.5 square meters according to geological survey technical specifications. Any blank area exceeding this threshold is marked as an anomaly. This threshold can be flexibly modified according to different project technical indicators.

[0024] Intra-layer feature overlap verification is used to detect instances where different polygons within the same disaster zoning layer overlap each other. Cross-layer feature overlap verification requires introducing an external reference layer and comparing the spatial coverage relationship between the current operational layer and the reference layer. For example, comparing geological hazard hazard polygons with an ecological protection red line reference layer, marking the portion of the hazard area that encroaches on the protection red line. Spatial location accuracy verification is used to check the degree of feature coordinate offset. Based on the local geological data specifications, a two-meter plane offset threshold is set. If the deviation between the stored coordinates and the theoretical coordinates measured in the field exceeds this value, the location accuracy is deemed substandard.

[0025] For the verification of geological hazard element attributes under the geological hazard topic, each business attribute field of each geological hazard element is checked one by one to identify various attribute data defects. Completeness verification focuses on fields that are explicitly required to be filled in according to business specifications, such as hazard name, unique hazard code, hazard scale, and hazard impact range. These contents are required to be filled in during field surveys; if the field content is empty during the formal verification phase, it is considered to have a missing data issue. Format verification imposes constraints on the field storage format; for example, the hazard code is uniformly limited to 6 digits, and the actual stored content that does not conform to this format requirement is marked as abnormal. Enumerated value verification pre-builds a set of legal values ​​based on geological hazard survey standards. The set includes all allowed content for hazard type, scale level, and hazard stability; if the element attribute value is not within the preset set range, the attribute value is judged as abnormal.

[0026] The entire verification process employs a multi-threaded parallel processing mode, dividing all elements to be inspected into multiple tasks and assigning them to different computing threads to simultaneously verify spatial morphology and attribute content. During processing, the number of elements verified, real-time processing speed, and remaining processing time are continuously monitored. For geological element data ranging from tens of thousands to hundreds of thousands, the parallel processing mode can significantly shorten the overall verification time. After all elements have been traversed, all spatial and attribute defect information is summarized, and a complete anomaly record is output, providing a basic data source for subsequent error level classification and human-machine rectification and repair.

[0027] For example, when performing feature verification, multiple inspection execution modes are supported, including real-time inspection, batch inspection, incremental inspection, and scheduled inspection. Real-time inspection is used to conduct quality verification immediately during geological feature editing; incremental inspection only verifies geological features that have changed within a layer, eliminating the need to traverse all features in the layer, thus reducing computational overhead; scheduled inspection automatically starts quality inspection tasks according to a preset plan, suitable for periodic data quality monitoring of projects. During verification execution, in addition to multi-threaded parallel processing, progress monitoring and system resource management are also enabled. Progress monitoring provides real-time statistics and feedback on the number of features that have been verified, the real-time processing speed, and the estimated remaining processing time; system resource management dynamically allocates computing resources, ensuring that the quality inspection task runs smoothly without consuming excessive system resources and affecting other business operations.

[0028] Meanwhile, after configuring various inspection rules, operators can export the entire set of rules as a rule attribute table. This table can be used for rule reuse and standardized workflow between different projects. In this embodiment, when conducting quality control on geological hazard element layers storing collapse, landslide, and debris flow risks, it includes verifying multiple key business fields of the geological hazard elements within the layer, achieving comprehensive quality verification of the geological hazard elements.

[0029] This embodiment achieves integrated verification of the spatial geometry of geological layers and the attributes of geological elements through an editable and rule-validated quality inspection rule set. It can adapt to custom thresholds and rule combinations for different geological survey projects, avoiding syntax and logical errors caused by rule configuration and reducing the probability of errors in large-scale geological data verification. Simultaneously, this embodiment distinguishes between two types of verification results: spatial geometric anomalies and geological element attribute anomalies. It accurately identifies various problems in geological vector data, improving the flexibility and processing efficiency of geological spatial data quality inspection, and providing a reliable data foundation for subsequent geological data mining and symbol rendering.

[0030] S102: Based on the feature verification results, identify abnormal features, and perform error classification and update on the abnormal features in the geological layer data to be verified, so as to obtain the updated geological layer data.

[0031] In this embodiment, abnormal features are identified based on the feature verification results, and error classification and updates are performed on the abnormal features in the geological layer data to be verified. Specifically, this includes: Based on the element verification results, abnormal elements are identified, and the abnormal type and location of each abnormal element are obtained. The error level of each abnormal element is determined based on its anomaly type and location; the error levels include Level 1, Level 2, Level 3, and Level 4 errors; the processing priority of Level 1, Level 2, Level 3, and Level 4 errors decreases sequentially. The processing order of elements is determined based on the error level of each abnormal element. Based on the processing order, abnormal elements with error levels of Level 1, Level 2, or Level 3 are modified and updated, and error messages are generated for abnormal elements with error level of Level 4.

[0032] For example, this embodiment processes all the verification results output by the aforementioned element verification step, targeting the county-level geological disaster investigation business scenario, and the processing object is the batch of abnormal elements obtained after the geological disaster hazard layer has been verified.

[0033] In this embodiment, abnormal features refer to geological features that, after feature verification, are determined not to meet the constraints of the quality inspection rule set. Examples include disaster zoning features with overlapping polygon features and disaster point features with empty required fields. Anomaly type is used to characterize which specific inspection rule a geological feature violates. These can be divided into two main categories: spatial geometric anomalies and geological feature attribute anomalies. For example, invalid geometry, overlapping features within a layer, and missing required fields are all different anomaly types. Anomaly location is used to mark the location of the anomaly on the corresponding geological feature. This can be the overall spatial range of the feature, a local coordinate segment of the feature, or a corresponding data row in the attribute table. For example, a local coordinate segment where polygon features self-intersect, or an attribute table row record with defective attribute fields. Feature identifier is the identification information used to uniquely distinguish each geological feature. It can be generated using geological feature coding, and different geological features have unique feature identifiers.

[0034] The system iterates through all element verification results, extracts the anomaly type, anomaly location, and element identifier for each abnormal element, establishes a corresponding association between element identifiers and anomaly information, and completes the collection and organization of anomaly information. The collected anomaly information can be synchronously mapped to the map view and attribute table to achieve bidirectional positioning. When an operator selects an abnormal element in the map view, they can jump to the corresponding record in the attribute table; when they select a record in the attribute table, they can also locate the corresponding element's spatial location on the map.

[0035] In this embodiment, error levels are categorized into Level 1, Level 2, Level 3, and Level 4 errors, with the processing priority decreasing sequentially from Level 1 to Level 4. The error levels are determined by referencing relevant industry technical requirements for geological data quality inspection, combined with the anomaly type and the actual impact range of the anomaly, forming a customized grading system for comprehensive judgment in this embodiment. Level 1 errors have the highest processing priority and correspond to situations where elements cannot participate in subsequent data mining and symbol rendering, such as completely missing core coding fields for geological disaster elements or completely broken loop closures of surface elements. Level 2 errors are next in priority and correspond to situations that distort thematic statistical analysis results, such as disaster stability field values ​​not falling within the preset enumeration set or overlapping surface elements within the same layer. Level 3 errors correspond to situations that do not block program operations but do not conform to the data entry specifications, such as tiny gaps in surface elements exceeding the tolerance threshold. Level 4 errors have the lowest processing priority and are considered minor flaws requiring only notification, such as inconsistent wording in attribute description text, which will not interfere with subsequent business processes.

[0036] The system prioritizes elements according to their processing order, handling Level 1 errors first, followed by Level 2, 3, and 4 errors. For Level 1, 2, or 3 errors, operators use information obtained from bidirectional positioning in the map view and attribute table to verify and modify the data, updating the spatial geometry or geological attribute fields of the elements within the layer. For Level 4 errors, no direct modification is performed; instead, an error message is generated and pushed to the user interface, prompting operators to prioritize handling these elements. After all processing is complete, the modified and updated layer data becomes the updated geological layer data, ready for subsequent data mining and retrieval.

[0037] For example, after collecting information on abnormal elements, the system can also provide intelligent repair suggestions. These suggestions, combined with the anomaly type and surrounding context information, output targeted handling reference solutions to assist operators in rectifying problems. After anomaly handling is completed, the system can perform quality statistical analysis, including the distribution of various errors, quality change trends, and corresponding improvement suggestions. Quality inspection results support export in multiple formats, including detailed reports with detailed anomaly records, summary reports for quick review, and interactive reports for interactive browsing, facilitating project archiving, reporting, and traceability.

[0038] For example, after retrieving a set of thematic elements, the system can categorize and highlight the search results on the interface. Operators can select to show or hide some elements by checking boxes, retaining only the target elements of business interest. It also supports exporting the thematic search results, which includes information such as geological element codes, element names, spatial locations, element descriptions, total number of elements, and element percentages, meeting project statistical archiving needs.

[0039] This embodiment relies on the verification results to collect various information of abnormal elements, classifies them into four error levels according to the degree of business impact and sets processing priorities, and reasonably arranges the processing order of elements; it distinguishes between different error levels and adopts differentiated handling methods to guide operators to prioritize the handling of anomalies with greater impact, reduce ineffective operations, improve the orderliness and processing efficiency of geological layer rectification work, and ensure that the updated geological layer data can reliably support subsequent thematic mining and symbol rendering work.

[0040] S103: Based on user-defined query conditions, retrieve a set of thematic elements that match the user-defined query conditions from the updated geological layer data.

[0041] In this embodiment, the user-defined query conditions are filter expressions for attribute fields generated by the user through the expression builder; based on the user-defined query conditions, a set of thematic elements matching the user-defined query conditions is retrieved from the updated geological layer data, specifically including: Perform validity checks on user-defined query conditions; If the verification passes, for each feature in the updated geological layer data, the corresponding attribute field value of the feature is read; the read attribute field value is substituted into the filtering expression for logical operation; if the logical operation result is true, the feature is included in the thematic feature set.

[0042] For example, this embodiment processes the updated geological layer data that has undergone rectification. The business scenario is the extraction of geological disaster thematic information. The updated geological layer data refers to the rectification of spatial geometry and geological element attribute anomalies in all geological elements within the layer. The expression builder is an interactive tool integrated into the Geographic Information System (GIS) plugin interface. It allows operators to select attribute fields, set comparison relationships, select field values, and generate user-defined query conditions. The user-defined query conditions are filtering expressions for attribute fields generated by the expression builder. The thematic element set is a subset of in-memory elements selected from the updated geological layer data that all meet the filtering conditions.

[0043] After the operator selects the updated geological layer data, the system reads all geological element attribute fields within the layer and displays them on the user interface. For geological hazard element attribute fields under the geological hazard topic, these can include geological element codes, hazard types, stability, and scale levels, all of which are derived from the geological hazard investigation business specifications. After the operator selects a target attribute field, the system further reads and displays all actual values ​​for that field. For example, selecting the stability field displays all business values ​​for stable, potentially unstable, and unstable. The operator then selects fields, values, and logical relationships based on business needs, and uses the expression builder to generate user-defined query conditions.

[0044] The system performs validity checks on user-defined query conditions, including checks on the existence of geological element fields, data type matching between fields and comparison values, and logical relationship syntax. If a geological element attribute field that does not exist in the referenced layer is found, or if text comparison content is configured for a numerical field, the system determines that the validation has failed, terminates the search process, and prompts the operator to make corrections.

[0045] If the verification passes, the system iterates through each geological element in the updated geological layer data, reading the corresponding attribute field value. The attribute field value is a business record stored for a single disaster element, such as the stability value corresponding to a single landslide hazard. The read attribute field value is substituted into a filtering expression for logical operation. If the logical operation result is true, the element is included in the thematic element set; if the logical operation result is false, the element is not included. After iterating through all elements, a complete thematic element set is obtained and output for subsequent symbol matching and rendering.

[0046] This embodiment performs pre-validation of user-defined query conditions to avoid retrieval anomalies caused by incorrect expression configuration; it completes logical judgment by reading the attribute field values ​​of each element one by one, and accurately extracts the elements of business interest from the updated geological layer data to form a thematic element set, providing a reliable element data source for the subsequent automatic generation of thematic maps and improving the automation level of geological thematic information mining.

[0047] S104: For each element in the thematic element set, select a scalable vector graphic symbol that matches the element's code from the standardized symbol library, and perform symbol rendering on the element based on the scalable vector graphic symbol to obtain a visualized thematic map.

[0048] In this embodiment, the geological data visualization method further includes: Before selecting a scalable vector graphic symbol that matches the code of each element in the thematic element set from the standardized symbol library, the standard specification data of the geological map legend is obtained, and the standard specification data of the geological map legend is analyzed and modeled to obtain the geological element symbol data model. Based on the geological element symbol data model conversion, scalable vector graphic symbols corresponding to each geological element are obtained, and identifiers including geological element codes and legend symbol types are generated for the scalable vector graphic symbols. The geological element symbol data model and the labeled scalable vector graphic symbols are classified and stored, and a multi-level hierarchical tree index is constructed based on the geological element categories and geological element codes to obtain a standardized symbol library.

[0049] In this embodiment, for each element in the thematic element set, a scalable vector graphic symbol matching the element's code is selected from the standardized symbol library, including: Analyze the identifiers carried by scalable vector graphics symbols in the standardized symbol library and extract the geological element codes within the identifiers; For each element in the thematic element set, read the element code field of that element, compare the element code field with the geological element code corresponding to the scalable vector graphic symbol, and if the comparison result is consistent, then it is determined that the scalable vector graphic symbol matches the element.

[0050] For example, this embodiment processes the thematic element set obtained through data mining retrieval, targeting county-level geological disaster survey operations. The thematic element set is a subset of unstable geological disaster hazard elements obtained through screening, and includes point-like geological disaster elements such as landslides, collapses, and debris flows. Before performing the step of selecting symbols from the standardized symbol library, the construction process of the standardized symbol library needs to be completed.

[0051] In this embodiment, the geological map legend and symbol standard specification data are officially released mapping standard documents from the geological industry, derived from publicly published geological mapping technical materials. These documents fully specify the mapping styles corresponding to different geological elements. The geological element symbol data model is a structured data organization formed after parsing the standard specifications. The geological element symbol data model includes fields for map type, geological element name, geological element code, symbol style, mapping element and brief description, element layer file type, and legend symbol type. Parsing modeling involves extracting and converting the textual descriptions and map information from the standard documents into structured records that the system can recognize. For example, for a landslide hazard point, its corresponding mapping style, 6-digit geological element code, and point symbol category are all entered into the geological element symbol data model.

[0052] For example, a geological element symbol data model can include fields for map type, geological element name, geological element code, symbol style, cartographic element and brief description, element layer file type, and legend symbol type. Legend symbol types are divided into four categories, corresponding to polygon fill color, polygon fill pattern, line symbol, and point symbol, respectively, each corresponding to geological elements of different spatial geometric types. After conversion to scalable vector graphic symbols, the symbols generate identifiers according to the rules of geological element code plus legend symbol type, which are used for subsequent symbol identification and matching.

[0053] Based on the geological element symbol data model, scalable vector graphic symbols corresponding to each geological element are obtained. These scalable vector graphic symbols are vector cartographic symbols, and scaling them will not produce jagged edges or distortion. For each converted scalable vector graphic symbol, an identifier is generated that includes a geological element code and a legend symbol type. This identifier follows the naming logic of the disclosure record and is composed of the geological element code and the legend symbol type.

[0054] Geological element symbol data models and labeled scalable vector graphic symbols are categorized and stored. A standardized symbol library is obtained by constructing a multi-level hierarchical tree index based on the major geological element categories and their codes. The multi-level hierarchical tree index uses the major element categories as the first level of classification, and then builds a sub-category hierarchical tree based on the 3rd and 4th digits of the geological element code. This is a clearly defined index construction rule. Each tree node is associated with the geological element name, code, and cartographic description, supporting symbol retrieval by name or code. For example, geological hazards are used as the first-level major category node, and then the 3rd and 4th digits of the code are used to distinguish subcategories such as landslides, collapses, and debris flows, thus forming a standardized symbol library.

[0055] After the symbol library is constructed, the symbol selection process is executed. The identifiers carried by the scalable vector graphics symbols within the standardized symbol library are parsed, and the geological element codes within the identifiers are extracted. This parsing process reads the symbol's associated identifiers, separating the coding information and the symbol's type; for example, it extracts the landslide element code and point symbol type corresponding to a given symbol.

[0056] For each element in the thematic element set, its element code field is read. The element code field is stored in the attribute table of the geological elements and is a 6-digit code generated after field surveys and data collection. The element code field is compared with the geological element code corresponding to the scalable vector graphic symbol. According to the disclosed matching logic, the scalable vector graphic symbol is considered a match for the element only if the comparison results are completely identical. If the element code field is empty or missing, or if there is no symbol with a completely identical code, then there is no matching scalable vector graphic symbol, and the element will not load professional cartographic symbols. The comparison also considers the legend symbol type; point-type disaster elements only match symbols of the point category and will not use area or line symbols.

[0057] After symbol matching and selection are completed, the element is rendered using scalable vector graphics. Symbol rendering binds the successfully matched scalable vector graphics to the corresponding spatial geometry object of the element, completing the drawing according to the map view's scale. After traversing and processing all elements in the thematic element set, a final visualized thematic map is output, yielding a thematic result map of the distribution of unstable geological hazard points, which can be directly used for geological hazard assessment and analysis.

[0058] This embodiment builds a standardized symbol library based on publicly available industry cartographic standards. It achieves orderly symbol management through a multi-level hierarchical tree index and automatically compares and matches element codes with scalable vector graphic symbols based on the identifiers carried by the symbols. This eliminates the traditional manual configuration of symbols one by one, enabling automatic selection and rendering of thematic element symbols. It ensures that thematic map symbol representation conforms to geological cartographic standards, effectively improving the efficiency of thematic map production and the standardization of map outputs.

[0059] Based on the same principle as the geological data visualization method provided in the embodiments of this application, the embodiments of this application also provide a geological data visualization system, such as... Figure 2 As shown, the geological data visualization system 20 may specifically include: a layer loading and verification module 21, an anomaly modification module 22, a data mining module 23, and a visualization topic module 24. The layer loading and verification module 21 is used to load the original geological vector data into layers to obtain the geological layer data to be verified, and to perform element verification on the geological layer data to be verified based on a quality inspection rule set. The quality inspection rule set includes pre-built spatial geometry rules and geological element attribute verification rules. The anomaly modification module 22 is used to determine abnormal features based on the feature verification results, and to classify and update the abnormal features in the geological layer data to be verified, so as to obtain the updated geological layer data. Data mining module 23 is used to retrieve a set of thematic elements that match the user-defined query conditions from the updated geological layer data based on user-defined query conditions. The visualization module 24 is used to select a scalable vector graphic symbol that matches the code of each element in the thematic element set from the standardized symbol library, and to perform symbol rendering on the element based on the scalable vector graphic symbol to obtain a visualization thematic map.

[0060] In one embodiment of this application, the geological data visualization system 20 further includes: a rule set configuration module, used for: Obtain user-input rule editing instructions for geological elements, and configure initial geological data inspection rules based on the rule editing instructions; The rules for checking initial geological data are validated, including syntax checking and logical conflict detection. A quality inspection rule set is obtained based on the inspection rules that pass the rule validation. The quality inspection rule set includes spatial geometry rules and geological element attribute verification rules. Among them, the spatial geometry rules include invalid geometry check rules, surface element gap check rules, intra-layer element overlap check rules, cross-layer element overlap check rules, and spatial location accuracy check rules. The geological element attribute verification rules include mandatory field integrity verification, field format verification, and enumerated value verification.

[0061] In one embodiment of this application, the quality inspection rule set includes spatial geometry rules and geological element attribute verification rules; the layer loading verification module 21 is specifically used for: Based on the spatial geometry rules in the quality inspection rule set, spatial geometry verification is performed on each element in the geological layer data to be verified in order to identify spatial geometry anomalies of the elements. Spatial geometry anomalies include invalid geometry, voids in surface elements, overlapping elements, cross-layer overlap, and spatial position accuracy not meeting the requirements. Based on the geological element attribute verification rules in the quality inspection rule set, geological element attribute field verification is performed on each element in the geological layer data to be verified in order to identify attribute anomalies such as missing required fields, field formats not meeting specifications, and field values ​​not being within the preset enumeration range.

[0062] In one embodiment of this application, the exception modification module 22 is specifically used for: Based on the element verification results, abnormal elements are identified, and the abnormal type and location of each abnormal element are obtained. The error level of each abnormal element is determined based on its anomaly type and location; the error levels include Level 1, Level 2, Level 3, and Level 4 errors; the processing priority of Level 1, Level 2, Level 3, and Level 4 errors decreases sequentially. The processing order of elements is determined based on the error level of each abnormal element. Based on the processing order, abnormal elements with error levels of Level 1, Level 2, or Level 3 are modified and updated, and error messages are generated for abnormal elements with error level of Level 4.

[0063] In one embodiment of this application, the user-defined query condition is a filtering expression for the attribute field generated by the user through the expression builder; the data mining module 23 is specifically used for: Perform validity checks on user-defined query conditions; If the verification passes, for each feature in the updated geological layer data, the corresponding attribute field value of the feature is read; the read attribute field value is substituted into the filtering expression for logical operation; if the logical operation result is true, the feature is included in the thematic feature set.

[0064] In one embodiment of this application, the geological data visualization system 20 further includes a symbol library construction module, used for: Obtain standard and specification data of geological map legends and symbols, analyze and model the standard and specification data of geological map legends and symbols, and obtain a data model of geological element symbols; Based on the geological element symbol data model conversion, scalable vector graphic symbols corresponding to each geological element are obtained, and identifiers including geological element codes and legend symbol types are generated for the scalable vector graphic symbols. The geological element symbol data model and the labeled scalable vector graphic symbols are classified and stored, and a multi-level hierarchical tree index is constructed based on the geological element categories and geological element codes to obtain a standardized symbol library.

[0065] In one embodiment of this application, the visualization topic module 24 is specifically used for: Analyze the identifiers carried by scalable vector graphics symbols in the standardized symbol library and extract the geological element codes within the identifiers; For each element in the thematic element set, read the element code field of that element, compare the element code field with the geological element code corresponding to the scalable vector graphic symbol, and if the comparison result is consistent, then it is determined that the scalable vector graphic symbol matches the element.

[0066] The system in this application embodiment executes the method provided in this application embodiment, and its implementation principle is similar. The actions performed by each module in the system of each embodiment of this application correspond to the steps in the method of each embodiment of this application. For detailed functional descriptions of each module of the system, please refer to the descriptions in the corresponding methods shown above, which will not be repeated here.

[0067] Figure 3 A schematic diagram of the structure of an electronic device to which this application embodiment applies is shown, such as... Figure 3 As shown, the electronic device can be used to implement the methods provided in any embodiment of this application.

[0068] like Figure 3 As shown, the electronic device 300 may primarily include at least one processor 301. Figure 3 The diagram shows components such as a memory 302, a communication module 303, and an input / output interface 304. Optionally, these components can be connected and communicate with each other via a bus 305. It should be noted that... Figure 3The structure of the electronic device 300 shown is merely illustrative and does not constitute a limitation on the electronic devices to which the methods provided in the embodiments of this application are applicable.

[0069] The memory 302 can be used to store operating systems and applications, etc. The applications can include computer programs that implement the methods shown in the embodiments of this application when invoked by the processor 301, and can also include programs for implementing other functions or services. The memory 302 can be ROM (Read Only Memory) or other types of static storage devices that can store static information and instructions, RAM (Random Access Memory) or other types of dynamic storage devices that can store information and computer programs, or it can be EEPROM (Electrically Erasable Programmable Read Only Memory), CD-ROM (Compact Disc Read Only Memory) or other optical disc storage, optical disc storage (including compressed optical discs, laser discs, optical discs, digital universal optical discs, Blu-ray discs, etc.), magnetic disk storage media or other magnetic storage devices, or any other medium that can be used to carry or store desired program code in the form of instructions or data structures and that can be accessed by a computer, but is not limited thereto.

[0070] Processor 301 is connected to memory 302 via bus 305 and implements corresponding functions by calling the application programs stored in memory 302. Processor 301 can be a CPU (Central Processing Unit), a general-purpose processor, a DSP (Digital Signal Processor), an ASIC (Application Specific Integrated Circuit), an FPGA (Field Programmable Gate Array), or other programmable logic devices, transistor logic devices, hardware components, or any combination thereof. It can implement or execute the various exemplary logic blocks, modules, and circuits described in conjunction with the disclosure of this application. Processor 301 can also be a combination that implements computing functions, such as a combination of one or more microprocessors, a combination of a DSP and a microprocessor, etc.

[0071] Electronic device 300 can connect to a network via communication module 303 (which may include, but is not limited to, components such as a network interface) to communicate with other devices (such as user terminals or servers) through the network and achieve data interaction, such as sending data to or receiving data from other devices. Communication module 303 may include wired network interfaces and / or wireless network interfaces, meaning the communication module may include at least one of wired or wireless communication modules.

[0072] The electronic device 300 can connect to necessary input / output devices, such as a keyboard or display device, via the input / output interface 304. The electronic device 300 itself may have a display device, and other external display devices can also be connected via the input / output interface 304. Optionally, a storage device, such as a hard drive, can also be connected via the input / output interface 304 to store data from the electronic device 300, retrieve data from the storage device, or store data from the storage device in the memory 302. It is understood that the input / output interface 304 can be a wired interface or a wireless interface. Depending on the actual application scenario, the device connected to the input / output interface 304 can be a component of the electronic device 300 or an external device connected to the electronic device 300 when needed.

[0073] The bus 305 used to connect the components may include a path for transmitting information between the components. The bus 305 may be a PCI (Peripheral Component Interconnect) bus or an EISA (Extended Industry Standard Architecture) bus, etc. Depending on its function, the bus 305 may be divided into an address bus, a data bus, a control bus, etc.

[0074] Optionally, for the solution provided in the embodiments of this application, the memory 302 can be used to store a computer program that executes the solution of this application, and the processor 301 runs the computer program. When the processor 301 runs the computer program, it implements the operation of the method or system provided in the embodiments of this application.

[0075] Based on the same principle as the method provided in the embodiments of this application, the embodiments of this application provide a computer-readable storage medium storing a computer program, which, when executed by a processor, can implement the corresponding content of the aforementioned method embodiments.

[0076] It should be noted that the terms "first," "second," "third," "fourth," "1," "2," etc. (if present) in the specification, claims, and accompanying drawings of this application are used to distinguish similar objects and are not necessarily used to describe a specific order or sequence. It should be understood that such data can be interchanged where appropriate so that the embodiments of this application described herein can be implemented in a sequence other than that shown in the figures or text.

[0077] In the embodiments of this application, the terms "module" or "unit" refer to a computer program or part of a computer program that has a predetermined function and works with other related parts to achieve a predetermined goal, and can be implemented wholly or partially using software, hardware (such as processing circuitry or memory), or a combination thereof. Similarly, a processor (or multiple processors or memory) can be used to implement one or more modules or units. Furthermore, each module or unit can be part of an overall module or unit that includes the functionality of that module or unit.

[0078] It should be understood that although arrows indicate various operation steps in the flowcharts of this application's embodiments, the order in which these steps are implemented is not limited to the order indicated by the arrows. Unless explicitly stated herein, in some implementation scenarios of this application's embodiments, the implementation steps in each flowchart can be executed in other orders as required. Furthermore, some or all steps in each flowchart, based on the actual implementation scenario, may include multiple sub-steps or multiple stages. Some or all of these sub-steps or stages can be executed at the same time, and each sub-step or stage can also be executed at different times. In scenarios where execution times differ, the execution order of these sub-steps or stages can be flexibly configured according to requirements, and this application's embodiments do not limit this.

[0079] The above description is only an optional implementation method for some implementation scenarios of this application. It should be noted that for those skilled in the art, other similar implementation methods based on the technical concept of this application without departing from the technical concept of this application also fall within the protection scope of the embodiments of this application.

Claims

1. A method for visualizing geological data, characterized in that, include: The original geological vector data is loaded into layers to obtain geological layer data to be verified, and the geological layer data to be verified is subject to feature verification based on the quality inspection rule set. The quality inspection rule set includes pre-built spatial geometry rules and geological element attribute verification rules; Based on the feature verification results, abnormal features are identified, and the abnormal features in the geological layer data to be verified are classified and updated to obtain the updated geological layer data. Based on user-defined query conditions, a set of thematic elements matching the user-defined query conditions is retrieved from the updated geological layer data; For each element in the thematic element set, a scalable vector graphic symbol matching the element's code is selected from the standardized symbol library, and the element is rendered based on the scalable vector graphic symbol to obtain a visualized thematic map.

2. The geological data visualization method as described in claim 1, characterized in that, Before loading the original geological vector data into layers, the following is also included: Obtain user-inputted rule editing instructions for geological elements, and configure initial geological data inspection rules based on the rule editing instructions; The initial geological data inspection rules are validated, including syntax checking and logical conflict detection. A quality inspection rule set is obtained based on the inspection rules that pass the rule validation. The quality inspection rule set includes spatial geometry rules and geological element attribute verification rules; wherein, the spatial geometry rules include invalid geometry check rules, surface element gap check rules, layer element overlap check rules, cross-layer element overlap check rules, and spatial location accuracy check rules, and the geological element attribute verification rules include mandatory field integrity verification, field format verification, and enumerated value verification.

3. The geological data visualization method as described in claim 2, characterized in that, The feature verification of the geological layer data to be verified based on the quality inspection rule set includes: Based on the spatial geometry rules in the quality inspection rule set, spatial geometry verification is performed on each element in the geological layer data to be verified in order to identify spatial geometry anomalies of the elements. The spatial geometry anomalies include invalid geometry, voids in surface elements, overlapping elements, cross-layer overlap, and spatial position accuracy not meeting the requirements. Based on the geological element attribute verification rules in the quality inspection rule set, geological element attribute field verification is performed on each element in the geological layer data to be verified in order to identify attribute anomalies such as missing required fields, field formats not meeting specifications, and field values ​​not being within the preset enumeration range.

4. The geological data visualization method as described in claim 1, characterized in that, The process of identifying anomalous features based on feature verification results, and classifying and updating the anomalous features in the geological layer data to be verified, includes: Based on the element verification results, abnormal elements are identified, and the abnormal type and location of each abnormal element are obtained. The error level of each abnormal element is determined based on its anomaly type and location; the error levels include Level 1 error, Level 2 error, Level 3 error, and Level 4 error; the processing priority of Level 1 error, Level 2 error, Level 3 error, and Level 4 error decreases sequentially. The processing order of elements is determined based on the error level of each abnormal element. Based on the processing order, abnormal elements with error levels of Level 1, Level 2, or Level 3 are modified and updated, and an error message is generated for abnormal elements with error level of Level 4.

5. The geological data visualization method as described in claim 1, characterized in that, The user-defined query conditions are filter expressions for attribute fields generated by the user through the expression builder; The process of retrieving a set of thematic elements matching the user-defined query conditions from the updated geological layer data, based on user-defined query conditions, includes: Perform a validity check on the user-defined query conditions; If the verification passes, for each feature in the updated geological layer data, the corresponding attribute field value is read; the read attribute field value is substituted into the filtering expression for logical operation; if the logical operation result is true, the feature is included in the thematic feature set.

6. The geological data visualization method as described in claim 1, characterized in that, Before selecting a scalable vector graphic symbol matching the element code from a standardized symbol library for each element in the thematic element set, the method further includes: Obtain standard and specification data of geological map legends and symbols, and perform analytical modeling on the standard and specification data of geological map legends and symbols to obtain a geological element symbol data model; Based on the geological element symbol data model, scalable vector graphic symbols corresponding to each geological element are obtained, and identifiers including geological element codes and legend symbol types are generated for the scalable vector graphic symbols. The geological element symbol data model and the labeled scalable vector graphic symbols are classified and stored, and a multi-level hierarchical tree index is constructed based on the geological element categories and geological element codes to obtain a standardized symbol library.

7. The geological data visualization method as described in claim 1, characterized in that, The step of selecting a scalable vector graphic symbol that matches the encoding of each element in the thematic element set from a standardized symbol library includes: The identifiers carried by scalable vector graphics symbols in the standardized symbol library are analyzed, and the geological element codes within the identifiers are extracted. For each element in the thematic element set, the element code field of the element is read, and the element code field is compared with the geological element code corresponding to the scalable vector graphic symbol. If the comparison result is consistent, it is determined that the scalable vector graphic symbol matches the element.

8. A geological data visualization system, characterized in that, include: The layer loading and verification module is used to load the original geological vector data into a layer to obtain geological layer data to be verified, and to perform feature verification on the geological layer data to be verified based on a quality inspection rule set; the quality inspection rule set includes pre-built spatial geometry rules and geological feature attribute verification rules. The anomaly modification module is used to determine abnormal elements based on the element verification results, and to perform error classification and update on the abnormal elements in the geological layer data to be verified, so as to obtain the updated geological layer data. The data mining module is used to retrieve a set of thematic elements that match the user-defined query conditions from the updated geological layer data based on user-defined query conditions. The visualization thematic module is used to select a scalable vector graphic symbol that matches the code of each element in the thematic element set from the standardized symbol library, and to perform symbol rendering on the element based on the scalable vector graphic symbol to obtain a visualization thematic map.

9. The geological data visualization system as described in claim 8, characterized in that, It also includes a rule set configuration module, used for: Obtain user-inputted rule editing instructions for geological elements, and configure initial geological data inspection rules based on the rule editing instructions; The initial geological data inspection rules are validated, including syntax checking and logical conflict detection. A quality inspection rule set is obtained based on the inspection rules that pass the rule validation. The quality inspection rule set includes spatial geometry rules and geological element attribute verification rules; wherein, the spatial geometry rules include invalid geometry check rules, surface element gap check rules, layer element overlap check rules, cross-layer element overlap check rules, and spatial location accuracy check rules, and the geological element attribute verification rules include mandatory field integrity verification, field format verification, and enumerated value verification.

10. The geological data visualization system as described in claim 8, characterized in that, It also includes a symbol library building module, used for: Obtain standard and specification data of geological map legends and symbols, and perform analytical modeling on the standard and specification data of geological map legends and symbols to obtain a geological element symbol data model; Based on the geological element symbol data model, scalable vector graphic symbols corresponding to each geological element are obtained, and identifiers including geological element codes and legend symbol types are generated for the scalable vector graphic symbols. The geological element symbol data model and the labeled scalable vector graphic symbols are classified and stored, and a multi-level hierarchical tree index is constructed based on the geological element categories and geological element codes to obtain a standardized symbol library.

Images