A multi-dimensional verification-based GIM file quality inspection handover management system and method

Abstract

The application relates to the technical field of file management, and discloses a GIM file quality inspection handover management system and method based on multidimensional verification, which comprises the following steps: establishing a task index, receiving and analyzing GIM files, integrating the GIM files into structured data sets, performing verification on the data sets in three dimensions of basic attributes, topological structures and indexes, generating data packets according to the verification results and binding the data packets with the index to obtain task handover records, generating a quality inspection report and a visual data source according to the task handover records, counting engineering quantity information, automatically generating a complete set of handover file sets based on the statistical results and the handover records, and completing handover. Through the integrated process of task index establishment, analysis driving, multidimensional verification and result automatic generation, the application realizes the full-process automation and structuring of GIM file quality inspection handover, and improves the quality inspection efficiency, data accuracy and consistency of handover results.

Description

Technical Field

[0001] This invention relates to the field of document management technology, and more specifically, to a GIM document quality inspection and handover management system and method based on multi-dimensional verification. Background Technology

[0002] In the digital construction and handover of power grid projects, the GIM (Grid Information Model) file, as the carrier of core information integrating the basic model, tower structure, insulator string configuration, and line route, is of paramount importance in terms of data quality. However, the complex data structure and numerous fields of GIM files, coupled with inconsistent formats due to differences in design software and personnel habits, pose significant challenges to quality review.

[0003] Currently, the verification of GIM files heavily relies on manual visual inspection and experience-based judgment, which is not only inefficient but also makes it difficult to systematically identify deeper issues such as missing fields, formatting errors, broken topological relationships, and logical inconsistencies in indicators. In the engineering data handover process, multiple structured deliverables need to be generated, including project detail tables, route files, intersection statistics tables, and conductor / ground wire parameter files. Current practices primarily rely on manual extraction, organization, and verification of data from scattered source files. This process is highly susceptible to errors such as duplicate entry, field misalignment, and inconsistent quantity statistics, and it fails to establish a traceable link between the handover deliverables and the original design data and task indexes.

[0004] Furthermore, with the development of digitalization, the handover results also need to support 3D visualization for intuitive review of tower locations, route alignments, etc. However, the existing process lacks a technical path to automatically convert verification results and engineering data into a visual loading format, resulting in a significant amount of manual data preparation work still required for 3D scene construction. At the same time, the scattered and inconsistent statistical methods for engineering quantities also increase the difficulty for management departments in batch review and archiving. Summary of the Invention

[0005] In view of this, the present invention proposes a GIM file quality inspection and transfer management system and method based on multi-dimensional verification, which aims to solve the problem of low efficiency of manual or single-dimensional tool quality inspection in the prior art, making it difficult to ensure the high-quality transfer of digital engineering data.

[0006] In one aspect, this invention proposes a GIM file quality inspection and handover management method based on multi-dimensional verification, comprising: Obtain project number information, design stage information, project type information, and visitor identification information, and establish a task index; When receiving a GIM file, the GIM file is associated with the task index, and parsing is performed on the GIM file. The parsing results are then integrated into a GIM dataset containing basic model data, insulator string model data, tower model data, and line path data. The GIM dataset is subjected to multidimensional verification, including basic attribute verification, topology verification, and index verification, to obtain multidimensional verification results. A verification result data package is generated based on the multidimensional verification results, and the verification result data package is bound to the task index to obtain a task handover record. A quality inspection report file is generated based on the task handover record and a download path is provided. A visual loading data source is constructed based on the verification result data package. Based on the statistical data of the verification results, the project quantity information is obtained to obtain the project statistical results; Based on the engineering statistics and the task handover records, a project detail table, route path file, crossover statistics table and conductor / ground wire parameter file are generated to obtain a multi-dimensional quality inspection handover file set and complete the handover.

[0007] Furthermore, when acquiring project number information, design stage information, project type information, and visitor identification information, and establishing a task index, the following is included: Perform a uniqueness comparison on the project number information, process the stage label numbering according to the design stage information, group the project categories according to the project type information, and verify the visitor identification information for permissions. Combine the information that has passed the comparison, grouping, numbering and verification according to the preset field order to obtain the task index.

[0008] Furthermore, when associating GIM files with the task index, parsing the GIM files, and integrating the parsing results into a GIM dataset containing basic model data, insulator string model data, tower model data, and line path data, the following steps are included: The GIM file is read line by line, each line is split according to the field delimiter, and the split fields are categorized according to the field order in the task index. After classification, structural identification is performed on the fields according to their categories. Coordinate field identification rules are used to determine whether they belong to basic model data, hanging point and link field identification rules are used to determine whether they belong to insulator string model data, pole and tower model field and component level field are combined to determine whether they belong to pole and tower model data, and path sequence field and path cascade field are combined to determine whether they belong to line path data. The identified data is written into the corresponding data areas in the order of basic model data, insulator string model data, tower model data, and line path data, and then combined according to the order in which they appear in the file to obtain the GIM dataset.

[0009] Furthermore, when performing multidimensional verification on the GIM dataset, the following steps are included: When performing basic attribute verification, the number field, type field and coordinate field are extracted from the basic model data, insulator string model data, tower model data and line path data respectively. The field integrity, field format and value domain relationship are compared and verified to obtain the basic attribute verification record. When performing topology verification, a connection chain is generated based on the node number, component number, and connection field in the basic model data and tower model data. The continuity of the connection chain, the reference relationship between nodes, and the order of path cascading are compared topologically to obtain a topology comparison record. When performing index verification, relevant index fields are extracted from the tower model data and insulator string model data in the GIM dataset. Based on the numerical relationship and recording order of the index fields, the consistency, numerical range and mutual matching relationship of the index records are compared and verified to obtain index verification records. Write the basic attribute verification records, topology comparison records, and indicator verification records into the multidimensional verification results.

[0010] Furthermore, when generating the verification result data packet based on the multidimensional verification result, the process includes: The multidimensional verification results are classified and organized according to the basic attribute verification records, topology comparison records, and indicator verification records, and attribute verification record areas, topology comparison record areas, and indicator verification record areas are established respectively. Write the records of missing fields, incorrect formats, and abnormal values ​​in the attribute verification record area into the attribute verification entries in the order of their appearance. Write the records of broken connection chains, abnormal node references, and path cascading errors in the topology comparison record area into the topology verification entries according to the link number; Write the interval anomaly records, value inconsistency records, and matching error records in the indicator verification record area into the indicator verification entries in the order of their source. The attribute verification items, topology verification items, and indicator verification items are combined in a fixed field order to form a verification result data package.

[0011] Furthermore, when binding the verification result data packet with the task index to obtain the task handover record, it includes: Retrieve the project number, project type code, stage number, and permission number from the task index, and organize the execution order of attribute verification entries, topology verification entries, and indicator verification entries in the verification result data package; Determine the task visibility range based on the permission number, and write the corresponding verification entries for the visibility range into the entry temporary storage area; Establish a number association between the project number and the attribute verification item in the item temporary storage area; establish a category association between the project type code and the topology verification item; establish a stage association between the stage number and the indicator verification item. Based on the field structure of the task index, the entries after being associated by number, category, and stage are structured and organized to obtain the task handover records corresponding to the task index.

[0012] Furthermore, when generating a quality inspection report file based on the task handover record and providing a download path, and constructing a visual loading data source based on the verification result data package, the process includes: Extract the project number, project type code, stage number and permission number from the task handover record, and write the extracted information into the basic information area of ​​the quality inspection report file according to the record order. Write the attribute verification entries, topology verification entries, and indicator verification entries from the task handover record into the verification information area of ​​the quality inspection report file according to the entry type; The basic information area and verification information area of ​​the quality inspection report file are processed to generate a downloadable quality inspection report file, and the generated file path is written to the download path record area; Based on the verification result data package, extract the attribute fields, coordinate fields, and number fields from the basic model data, insulator string model data, tower model data, and line path data. Then, construct a visual loading data source based on the model type using the extracted fields. Write the constructed visualization data source to the data loading index area.

[0013] Furthermore, when obtaining the project statistics results based on the statistical project quantity information of the verification result data package, the following are included: Read the number of records for basic model data, insulator string model data, tower model data and line path data from the verification result data package, and write the number of each type of record into the engineering quantity record area respectively; Calculate the number of basic records for the project based on the number of records in the basic model data, calculate the number of tower records for the project based on the number of records in the tower model data, calculate the number of insulator string records for the project based on the number of records in the insulator string model data, and write the number of each record into the quantity details area. Organize the route data according to the route sequence, count the number of route segments, and write the number of route segments into the route number record area; The records in the project quantity record area, quantity details area, and path quantity record area are combined in statistical order to obtain the project statistical results.

[0014] Furthermore, when generating a multidimensional quality inspection handover file set based on the project statistics results and the task handover records, including a project details table, route path file, crossover statistics table, and conductor / ground wire parameter file, the file set includes: Based on the engineering statistics results, read the quantity records of the basic model data, insulator string model data, tower model data and line route data, and write the quantity records into the quantity area of ​​the engineering details table according to the data type. Write the project number, project type code, stage number and permission number from the task handover record into the information area of ​​the project details table in the order of the fields, and combine the contents of the quantity area with the contents of the information area to obtain the project details table; Based on the path sequence, path concatenation field, and node coordinates of the route path data, the path segments are written sequentially into the path record area of ​​the route path file; Based on the path record area of ​​the route path file, analyze the distance and positional relationship between each path segment and external object, and write the distance and position records into the intersection record area of ​​the intersection statistics table; Based on the number field, coordinate field, and association field in the tower model data and insulator string model data, write the number record, spatial location record, and association record into the parameter record area of ​​the conductor parameter file; Write the project details, route path file, crossover statistics table, and conductor / ground wire parameter file into the multidimensional quality inspection handover file set in a fixed combination order.

[0015] Compared with existing technologies, the advantages of this invention are as follows: By acquiring project number information, design stage information, project type information, and visitor identification information at the beginning of the task and constructing a task index, the project documents have clear identification and management entry points before entering the quality inspection process, reducing the problems of unclear project sources and difficulty in tracing tasks caused by traditional manual recording methods. After receiving the GIM file, a correspondence is established between the file and the task index, and parsing is performed. The content is organized into four types of structured data: basic model data, insulator string model data, tower model data, and line path data. This transforms the scattered original fields that have long relied on manual judgment into a dataset that can be processed uniformly, thereby reducing the manual parsing bias caused by differences in design software and inconsistent field formats. By performing basic attribute verification, topology verification, and index verification on this dataset, missing fields, format errors, abnormal connection relationships, and logical contradictions in indicators can be identified in the same process and form multi-dimensional verification results, solving the problem that manual quality inspection cannot systematically cover all error types. By binding the verification result data package with the task index and forming a task handover record, a one-to-one correspondence is established between the verification results, task information, and subsequent handover materials, reducing the situation where data cannot be matched or lacks a traceable chain in traditional manual processing. A quality inspection report file is generated based on the task handover record and a download path is provided. Simultaneously, a visual loading data source is constructed based on the verification result data package, allowing the verification content of the same task to be viewed in file form and also to be loaded into a 3D scene, with attribute selection and location display, effectively solving the problem of manual data processing required for previous 3D displays. By statistically analyzing the number of projects in the verification result data package and obtaining project statistics, and then generating project detail tables, route path files, intersection statistics tables, and conductor / ground wire parameter files based on the statistical results and task handover records, project data statistics and the generation of multiple types of handover materials are completed in a single process, reducing data inconsistencies caused by manual extraction and multiple data entries. Through the above-mentioned associated parsing, verification, statistics, and handover process, this invention improves the accuracy of GIM file quality inspection and the consistency of data handover, ensuring that digital engineering data maintains structural uniformity and traceability throughout the entire process.

[0016] On the other hand, this application also provides a GIM file quality inspection and handover management system based on multi-dimensional verification, used to implement the above-mentioned GIM file quality inspection and handover management method based on multi-dimensional verification, including: The task index creation module is configured to retrieve project number information, design stage information, project type information, and visitor identification information to create a task index. The GIM file parsing and integration module is configured to associate the GIM file with the task index when receiving a GIM file, and to perform parsing processing on the GIM file, integrating the parsing results into a GIM dataset containing basic model data, insulator string model data, tower model data and line path data. The multidimensional verification module is configured to perform multidimensional verification on the GIM dataset, including basic attribute verification, topology verification and index verification, to obtain multidimensional verification results. The report generation module is configured to generate a verification result data package based on the multidimensional verification results, bind the verification result data package with the task index to obtain a task handover record, generate a quality inspection report file based on the task handover record and provide a download path, and construct a visual loading data source based on the verification result data package; The engineering data statistics module is configured to statistically analyze the engineering quantity information based on the verification result data package and obtain engineering statistics results. The output module is configured to generate an engineering detail table, a route path file, a crossover statistics table, and a conductor / ground wire parameter file based on the engineering statistics results and the task handover record, thereby obtaining a multi-dimensional quality inspection handover file set and completing the handover.

[0017] It is understandable that the aforementioned GIM file quality inspection and transfer management system and method based on multidimensional verification have the same beneficial effects, and will not be elaborated further here. Attached Figure Description

[0018] Various other advantages and benefits will become apparent to those skilled in the art upon reading the following detailed description of preferred embodiments. The accompanying drawings are for illustrative purposes only and are not intended to limit the invention. Furthermore, the same reference numerals denote the same parts throughout the drawings. In the drawings: Figure 1 A flowchart illustrating a GIM file quality inspection and handover management method based on multi-dimensional verification, provided in this embodiment of the invention; Figure 2 This is a functional block diagram of a GIM file quality inspection and transfer management system based on multi-dimensional verification, provided in an embodiment of the present invention. Detailed Implementation

[0019] Exemplary embodiments of the present disclosure will now be described in more detail with reference to the accompanying drawings. While exemplary embodiments of the present disclosure are shown in the drawings, it should be understood that the present disclosure may be implemented in various forms and should not be limited to the embodiments set forth herein. Rather, these embodiments are provided to enable a more thorough understanding of the present disclosure and to fully convey the scope of the disclosure to those skilled in the art. It should be noted that, unless otherwise specified, embodiments and features in the embodiments of the present invention can be combined with each other. The present invention will now be described in detail with reference to the accompanying drawings and embodiments.

[0020] In some embodiments of this application, see Figure 1 As shown, a GIM file quality inspection and handover management method based on multi-dimensional verification includes: S1: Obtain project number information, design stage information, project type information, and visitor identification information, and establish a task index; S2: When receiving a GIM file, associate the GIM file with the task index and perform parsing processing on the GIM file. Integrate the parsing results into a GIM dataset containing basic model data, insulator string model data, tower model data and line path data. S3: Perform multidimensional validation on the GIM dataset, including basic attribute validation, topology validation, and index validation, to obtain multidimensional validation results; S4: Generate a verification result data package based on the multidimensional verification results, bind the verification result data package with the task index to obtain the task handover record, generate a quality inspection report file based on the task handover record and provide a download path, and build a visual loading data source based on the verification result data package; S5: Based on the verification result data package, statistical information on the number of projects is collected to obtain the project statistics results; S6: Based on the engineering statistics results and task handover records, generate engineering details, route path files, crossover statistics, and conductor / ground wire parameter files to obtain a multi-dimensional quality inspection handover file set and complete the handover.

[0021] Specifically, during S1 execution, the project number information is read in a formatted manner. The project number is input as a string and its uniqueness is checked according to the numbering structure of the project management system. Design stage information is loaded as an enumerated field, including the preliminary design stage, construction drawing stage, etc. Project type information is matched according to a predefined type table. Visitor identification information is input as an account or token and permission is verified through the access control interface. The verification fields include access level and visibility range. The above four types of information are combined in a fixed field order to construct a task index. During S2 execution, the received GIM file is read line by line. Each line is split into multiple fields according to the delimiter. The field content identifies the model type by field name, field characteristics, or field value form. For example: fields containing "Insulator" or containing a hanging point number structure are classified as insulator string model data; fields containing "TwrModel" or whose content conforms to the tower coordinate arrangement structure are classified as tower model data; coordinate fields containing continuous three-dimensional coordinate groups and prefixed with "BasePoint" are classified as basic model data; and fields containing a combination of "PathSeq" and "NextNode" fields are classified as line path data. The identified fields are written to their corresponding data areas, maintaining the same order as the original line numbers in the file. The four types of areas are merged to obtain the GIM dataset. During S3, basic attribute verification reads the number, type, and coordinate fields and compares their contents according to the field format definition table. Topology verification reads the node numbers and connection fields to generate connection chains, searches these chains, and checks for breakpoints, duplicate references, or incorrect connection directions. Path cascading relationships are verified by comparing the order of the path sequence field and the cascading field. Indicator verification extracts indicator fields, such as length, inclination angle, and number of strings, and checks their numerical relationships, interval relationships, and mutual reference relationships according to the record order, writing the verification information into the multidimensional verification results. During S4, the basic attribute verification records are organized into attribute verification entries, the topology comparison records into topology verification entries, and the indicator verification records into indicator verification entries, and these are combined according to a fixed field order to generate a verification result data package. The project number, project type code, stage number, and permission number from the task index are written as master record fields into the task handover record. Entries from the verification result data package are written into the task handover record in the corresponding field order. Simultaneously, a quality inspection report file containing basic information and verification information areas is generated. The visualization loading data source organizes the number, coordinate, and attribute fields from the verification result data package, generating the data structure required for 3D loading based on the model type.During S5 execution, the number of records for basic model data, insulator string model data, tower model data, and line path data in the verification result data package is extracted and written to the engineering quantity record area; a quantity detail area is generated based on the four types of quantity information; the path sequence is organized, and the number of path segments is calculated and written to the path quantity record area; the above records are combined in statistical order to form the engineering statistical results. During S6 execution, the quantity records are written to the quantity area of ​​the engineering detail table based on the engineering statistical results, and the project number, project type code, stage number, and authority number from the task handover record are written to the information area; the two areas are combined to obtain the engineering detail table. The line path file reads the path sequence, path cascading field, and node coordinates, and writes the path segments composed of adjacent path nodes sequentially to the path record area. The crossing (crossing) statistics table calculates the coordinate distance and positional relationship between the path segment and external objects, and writes the distance and position records to the crossing record area. The conductor and ground wire parameter file writes the corresponding information to the parameter record area based on the number field, coordinate field, and association field in the tower model data and insulator string model data. The project details table, route path file, crossover statistics table, and conductor / ground wire parameter file are combined in a fixed order to obtain a multi-dimensional quality inspection and handover file set.

[0022] In the complete processing of a project file, the process first receives project number information, design stage information, project type information, and visitor identification information. A uniqueness check is performed on the project number, confirming the absence of duplicates by comparing it with an existing list of project numbers. Based on the design stage information, stage labels are assigned according to stage identification rules; for example, common stages may include preliminary design, construction drawing design, or delivery review, and each stage is assigned a fixed stage number. The project type information is used to search the project category grouping table to group project types. Access verification is performed on the visitor identification information, determining the accessible data range and the range of visible entries by comparing the access number range. The information, after comparison, grouping, numbering, and verification, is then arranged sequentially according to the field order of the task index to generate a task index. Upon receiving the GIM file, the file content is read line by line, and each line is split into field groups based on field separators. The fields are then categorized sequentially according to the field arrangement structure in the task index. The data type of a field is identified by field name keywords, field coding structure features, or field value form. For example, a 3D coordinate field typically has three types of values ​​(X, Y, Z) and a fixed structure, which can be identified as basic model data. When both attachment point and link fields appear in a field group, it can be identified as insulator string model data. When the field code contains tower type short codes, component levels, and parent-child hierarchical relationships, it can be identified as pole / tower model data. When field values ​​are sequentially increasing and contain path sequence fields and path cascading fields, it can be identified as line path data. After identification, the fields are written to the basic model data area, insulator string model data area, pole / tower model data area, and line path data area respectively, and combined according to the original order of appearance in the file to form the GIM dataset. Subsequently, basic attribute verification, topology verification, and indicator verification were performed on the GIM dataset: Basic attribute verification involved extracting the ID, type, and coordinate fields and comparing their completeness, format, and value range item by item; Topology verification generated connection chains based on node IDs, component IDs, and connection fields, and used graph traversal (e.g., depth-first search) to check for breakpoints, cross-references, or abnormal path cascading order; Indicator verification involved reading the indicator fields from the tower model data and insulator string model data to check the numerical range, consistency, and matching relationships between indicators. These three types of verification records formed basic attribute verification records, topology comparison records, and indicator verification records, respectively, constituting the multi-dimensional verification results. After obtaining the multi-dimensional verification results, the three types of records were categorized and organized into attribute verification entries, topology verification entries, and indicator verification entries, respectively. The visibility range was determined based on the task index's permission number, and entries within the visible range were written to the entry temporary storage area.Subsequently, the project number is appended to the attribute verification item to form a number association, the project type code is appended to the topology verification item to form a category association, and the stage number is appended to the indicator verification item to form a stage association. The associated items are then structured according to the field structure of the task index to generate a task handover record. When generating the quality inspection report file, the project number, project type code, stage number, and permission number are extracted from the task handover record and written into the basic information area of ​​the quality inspection report file. The three types of verification items are written into the verification information area according to the item type. The two information areas are processed to generate a downloadable quality inspection report file, and a download path record is created. Then, based on the verification result data package, the number field, coordinate field, and attribute field of the basic model data, insulator string model data, tower model data, and line path data are extracted. The number field is used as a node index, the coordinate field as spatial positioning, and the attribute field as additional attributes. Based on the model type, a hierarchical data structure suitable for 3D display is constructed and written into the loading data index area. Then, based on the number of basic model data, tower model data, insulator string model data, and path segment data in the verification result data package, the relevant records are written into the engineering quantity record area, quantity detail area, and path quantity record area, respectively, and combined to form the engineering statistical results. Finally, based on the engineering statistical results and task handover records, an engineering detail table, a line path file, a crossover statistics table, and a conductor and ground wire parameter file are generated: the engineering detail table consists of the project number, project type code, stage number, authority number, and quantity area content; the line path file records path segments based on the path sequence, path cascade field, and node coordinates; the crossover statistics table generates crossover records based on the distance and positional relationship between path segments and external objects; the conductor and ground wire parameter file generates number, position, and association records based on the number field, coordinate field, and association field. The above files are combined in a fixed order to form a multi-dimensional quality inspection handover file set and the handover is completed.

[0023] In some embodiments of this application, the process of obtaining project number information, design stage information, project type information, and visitor identification information and establishing a task index includes: Perform a uniqueness comparison on the project number information, process the stage label numbering according to the design stage information, group the project categories according to the project type information, and verify the visitor identification information for permissions. Combine the information that has passed the comparison, grouping, numbering and verification according to the preset field order to obtain the task index.

[0024] Specifically, in the process of acquiring project number information, design phase information, project type information, and visitor identification information, and establishing a task index, the project number information is first subjected to a uniqueness comparison. During the uniqueness comparison, the input project number information is split into a complete character sequence, and the project number list in the task storage area is called. Each project number in the list is read sequentially and compared with the character sequence of the input project number character by character position. During the comparison process, an equality judgment is performed character by character starting from the first character. When two character segments are inconsistent at any position, they are recorded as not being the same number item, and the comparison continues with the next number item. When all characters of a project number are completely consistent with the input project number, this situation is recorded as a duplicate number, and a number conflict flag is triggered in the task index construction process. If no completely consistent character sequence is found after all the project number lists have been compared, the input project number information is marked as a registrable number. Subsequently, stage label numbering is performed based on the design stage information. During this process, the design stage information is used as an input field, and the mapping relationship between stage labels and corresponding stage numbers is read item by item from the stage number table. A text comparison is performed between the design stage information and the label content in the stage number table, using a character-by-character matching method to determine if the design stage information matches a particular stage label. If a match is found, the corresponding stage number is read and written to the stage number field. If no match is found after comparing all labels, the stage information is recorded as an undefined stage and a default number is written. Next, project categories are grouped based on project type information. When grouping projects by category, the project type information is used as the text to be identified. Each type keyword (e.g., line, tower, and channel) is read sequentially from the project type identification table, and a text inclusion comparison is performed. By scanning all characters of the project type information, it is determined whether it contains a certain type keyword. If an inclusion relationship is detected, the project category corresponding to that keyword is written to the project category field. If no match is found after traversing all type keywords, it is classified as an undefined category. Finally, visitor identification information is used for permission verification. During permission verification, the identity code in the visitor identification information is extracted as an independent string and compared character by character with the identity code field in the permission configuration table, with each character being compared from the first character to the last. If the comparison result is a complete match, the permission level corresponding to that identity code is read and written to the permission field. If all permission configuration items do not match, the permission field is marked as having no permission. After the uniqueness comparison, stage label number processing, project category grouping, and permission verification are all completed, the project number information, stage number, project category field, and permission field are combined and written to the task index according to the preset field order.The default field order is a fixed field arrangement order defined in advance in the task record structure. By specifying in the task record structure configuration table that the project number field is arranged first, the stage number field is arranged second, the project category field is arranged third, and the permission field is arranged fourth, all task indexes can perform read, compare and write operations according to the same field order during subsequent parsing, verification and handover processes, ensuring the structural consistency of task records.

[0025] For example, during the creation of a task index, the input project number information is DL-202412-A01, the design stage information is preliminary design, the project type information is 35kV line project, and the visitor identification information is U023. When performing a uniqueness comparison of the project number information, the system first reads the list of registered project numbers from the task storage area, such as DL-202310-B03, DL-202408-C12, etc., and then splits the input project number DL-202412-A01 into a continuous character sequence. The sequence is then compared character by character, starting from the first character, with the numbers in the list. For example, the system checks the consistency of the character "D" with the first character "D" of an existing number, then compares the next character until the third character of a number item matches (e.g., 2 matches 2, 0 matches 0). The comparison continues until the fifth character of a number item is inconsistent; if this occurs, the number item is marked as inconsistent, and the same character-by-character comparison is performed on the next item. When all number items have been compared character-by-character, and no character sequence is found that completely matches the input project number, the system marks the input project number as a registrable number. In the stage label numbering process, the preliminary design is used as input. The system reads the stage labels (e.g., feasibility study, preliminary design, construction drawings) from the stage number table and checks for consistency character by character. When a preliminary design entry is matched, all characters match, indicating a match. The system reads the corresponding stage number "02" from this entry and registers it in the task index field. In the project category grouping process, the 35kV line project is used as text input and compared sequentially with the type keywords in the project type identification table (e.g., line, tower, corridor). By determining whether the text contains consecutive character sequences for "line," and detecting the corresponding character sequence, the project category is marked as a line category. During the permission verification process, U023 is extracted as a character code and compared item by item with the identity code field in the permission configuration table. For example, U011, U023, and U101 are compared sequentially. When U023 is matched, all characters are consistent, and its corresponding permission level P2 is read and written to the permission field. After all processing steps are completed, according to the preset field order: project number field, stage number field, project category field, and permission field, DL-202412-A01, 02, line category, and P2 are written to the task index in sequence to obtain the task record.

[0026] In some embodiments of this application, when associating a GIM file with a task index, performing parsing processing on the GIM file, and integrating the parsing results into a GIM dataset containing basic model data, insulator string model data, tower model data, and line path data, the process includes: The GIM file is read line by line, each line is split according to the field delimiter, and the split fields are categorized according to the field order in the task index. After classification, structural identification is performed on the fields according to their categories. Coordinate field identification rules are used to determine whether they belong to basic model data, hanging point and link field identification rules are used to determine whether they belong to insulator string model data, pole and tower model field and component level field are combined to determine whether they belong to pole and tower model data, and path sequence field and path cascade field are combined to determine whether they belong to line path data. The identified data is written into the corresponding data areas in the order of basic model data, insulator string model data, tower model data, and line path data, and then combined according to the order in which they appear in the file to obtain the GIM dataset.

[0027] Specifically, when reading the GIM file line by line, the file content is loaded into a buffer line by line, with each line treated as a model record. Fields are then segmented using field separators such as commas or tabs. The segmented fields are then matched sequentially with the pre-arranged fields in the task index, ensuring that information such as project number, category, coordinates, and component fields are placed in fixed classification slots, guaranteeing a consistent input format for subsequent identification logic. After field classification, the data type of the record is determined using structural identification rules. When using coordinate field identification rules, the system first checks if the field contains three-dimensional coordinates, such as sequentially appearing X, Y, and Z values, and further determines if the coordinate values ​​fall within a common route spatial range. A common route spatial range typically consists of a horizontal coordinate (X) within a route corridor range of zero to several kilometers, a vertical coordinate (Y) within a lateral deviation range of several hundred meters to the left or right of the crossing point, and an elevation coordinate (Z) within a reasonable range between the local terrain elevation and the top surface of the tower foundation. When the coordinate values ​​meet these spatial distribution characteristics, the record can be identified as basic model data. When using the identification rules for attachment point and link fields, the system checks whether records contain features such as attachment point number, link pointer number, and string length. If attachment point numbers and corresponding link fields appear consecutively, the records can be classified as insulator string model data. When using a combination of tower type and component level fields, the tower type number is first identified from the records. Then, the component level field is checked for a hierarchical numbering structure, such as the hierarchical relationship between tower type DLT1 and component codes 01-03. Based on this, the records can be identified as tower model data. When using path sequence and path cascading fields to identify line path data, the path number in the path sequence field and the preceding / following relationship in the path cascading field are analyzed for continuity. If the path number shows a continuous evolution and the cascading fields of adjacent records correspond, the records can be classified as line path data. After completing the data type identification, the four types of records are written into the basic model data area, insulator string model data area, tower model data area, and line path data area, respectively, maintaining the original file order to form a GIM dataset divided according to the model structure and in a consistent order. For example, when a record contains the tower type field DLT2, the component level field 02-01, and the coordinate values ​​X123.5, Y45.2, and Z18.6, the record is written into the tower model data area according to the tower type field and level field identification rules.

[0028] In one specific embodiment, the received GIM file contains a total of 4 exemplary records, each of which is separated by commas and the fields are in the following order: project number, field category, field name, X coordinate, Y coordinate, Z coordinate, component code, attachment point number, link pointing number, path sequence number, and path cascading marker.

[0029] When performing a line-by-line read, for example, the first record is: 2024-A01, Basic Class, Ground Point, 103.52, 32.18, 486.3, Empty, Empty, Empty, Empty, Empty. After splitting, it can be seen that the field category is Basic Class, and the X, Y, and Z coordinates all fall within the spatial range of common local lines. X is located within the line corridor range, Y is located within the line lateral offset range, and Z is located within the local terrain and tower foundation range. Therefore, according to the coordinate field identification rules, this record is classified as basic model data.

[0030] The second record is: 2024-A01, Tower type, DLT1 type, 103.55, 32.20, 512.6, 01-02, empty, empty, empty, empty. After splitting, it is identified as tower model data by judging that the tower model field DLT1 matches the hierarchical structure of the component code 01-02, and the coordinate Z value is located between the tower foundation height and the lower edge of the tower body.

[0031] The third record is: 2024-A01, Insulator String Class, String III, Empty, Empty, Empty, Empty, H12, L12-13, Empty, Empty. This record contains the attachment point number H12 and the link pointing number L12-13. The field structure presents a typical attachment point-link representation of an insulator string. Therefore, according to the attachment point field rules and link field rules, it is classified as insulator string model data.

[0032] The fourth record is: 2024-A01, Path Class, Line Segment, Empty, Empty, Empty, Empty, Empty, Empty, P05, P04-P05. The field contains a continuous path sequence number P05, and a concatenated field P04-P05 corresponding to the previous path segment number, indicating that P05 is the successor to P04. Therefore, based on the path sequence field and the path concatenation field, it is written into the line path data area.

[0033] After identification, the four records are written into the basic model data area, tower model data area, insulator string model data area, and line path data area respectively, and combined while maintaining the original order to finally form a structured GIM dataset.

[0034] In some embodiments of this application, multidimensional verification of the GIM dataset includes: When performing basic attribute verification, the number field, type field and coordinate field are extracted from the basic model data, insulator string model data, tower model data and line path data respectively. The field integrity, field format and value domain relationship are compared and verified to obtain the basic attribute verification record. When performing topology verification, a connection chain is generated based on the node number, component number, and connection field in the basic model data and tower model data. The continuity of the connection chain, the reference relationship between nodes, and the order of path cascading are compared topologically to obtain a topology comparison record. When performing index verification, relevant index fields are extracted from the tower model data and insulator string model data in the GIM dataset. Based on the numerical relationship and recording order of the index fields, the consistency, numerical range and mutual matching relationship of the index records are compared and verified to obtain index verification records. Write the basic attribute verification records, topology comparison records, and indicator verification records into the multidimensional verification results.

[0035] Specifically, when performing multidimensional verification on the GIM dataset, the following steps are taken: First, the number, type, and coordinate fields are extracted from each of the basic model data, insulator string model data, tower model data, and line path data. The extracted fields are then compared against the format definitions of similar fields. For example, the number field uses a unified combination of project number and component number; the type field uses a preset set of category values; and the coordinate field uses a three-dimensional coordinate format. During verification, checks are performed to ensure fields are not missing, conform to numerical formats, and fall within the commonly used spatial range of the line. For instance, the X-coordinate must fall within the line corridor range, and the Z-coordinate must fall within the range from the ground surface to the tower height. Missing fields, format errors, and mismatched value ranges are recorded in the basic attribute verification record. When performing topology verification, node numbers, component numbers, and connection fields are read from the basic model data and tower model data, and connection chains are generated accordingly. Connection chains represent the connection sequence between adjacent components. After generating the connection chains, a topology comparison is performed to check for broken links, references to non-existent nodes, and consistency in the order of path cascading fields. For example, if node 05 in the connection chain 01 to 02 to 05 is not found in the dataset, this is recorded as a node reference anomaly; if the order of path cascading fields P03-P04 and P04-P05 is reversed, this is recorded as a path cascading error. All verification results are uniformly written into the topology comparison record. During index verification, the index fields to be compared, such as insulator string length, tower component height, or relative spacing, are extracted from the tower model data and insulator string model data, and compared and verified according to the numerical relationship between the index fields and the recording order. For example, if the difference between the insulator string length and the hanging point height of the same type of tower exceeds the specified range, this is recorded as a range anomaly; if the index of the same component is inconsistent in different records, this is recorded as a numerical inconsistency; if there is a corresponding relationship between indices but they are not matched, this is recorded as a matching error. All verification results are compiled and written into the index verification record. Finally, the basic attribute verification records, topology comparison records, and indicator verification records are written into the multidimensional verification results, which are used to generate verification result data packages, count the number of projects, and build a visual loading data source.

[0036] In some embodiments of this application, generating a verification result data packet based on the multidimensional verification result includes: The multidimensional verification results are classified and organized according to the basic attribute verification records, topology comparison records, and indicator verification records, and attribute verification record areas, topology comparison record areas, and indicator verification record areas are established respectively. Write the records of missing fields, incorrect formats, and abnormal values ​​in the attribute verification record area into the attribute verification entries in the order of their appearance. Write the records of broken connection chains, abnormal node references, and path cascading errors in the topology comparison record area into the topology verification entries according to the link number; Write the interval anomaly records, value inconsistency records, and matching error records in the indicator verification record area into the indicator verification entries in the order of their source. The attribute verification items, topology verification items, and indicator verification items are combined in a fixed field order to form a verification result data package.

[0037] Specifically, in the process of generating the verification result data package based on the multidimensional verification results, firstly, records with missing fields, mismatched formats, abnormal value ranges, broken connection chains, abnormal node references, path cascading errors, interval anomalies, inconsistent values, and matching errors are extracted from the basic attribute verification records, topology comparison records, and indicator verification records, respectively. These records are then categorized into the attribute verification record area, topology comparison record area, and indicator verification record area according to their verification type. Subsequently, for the attribute verification record area, records with missing fields, mismatched formats, and abnormal value ranges are written into attribute verification entries one by one according to their order of appearance in the original multidimensional verification results, ensuring that each record maintains its original order of appearance during the verification process. For the topology comparison record area, records belonging to the same link number are grouped together based on the link number contained in the broken connection chain records, abnormal node reference records, and path cascading error records, and then written into topology verification entries in ascending order of link number, thus centrally expressing topology anomalies of the same link. For the indicator verification record area, verification records from different sources are written into the indicator verification entries according to their original source order, based on the record source order of interval anomaly records, inconsistent value records, and matching error records. This allows for tracking of verification results by source location in subsequent processing steps. After writing the three verification entries, the attribute verification entries, topology verification entries, and indicator verification entries are combined according to a fixed field order. This fixed field order corresponds to the pre-defined entry arrangement in the quality inspection handover scenario, ensuring that the verification result data package maintains structural consistency across different processing stages. Through the above steps, the categorized and organized verification entries are combined to obtain the verification result data package, which is used for subsequent binding of task indexes, generation of task handover records, and construction of a visual loading data source.

[0038] In one specific embodiment, after performing multidimensional validation on a certain GIM dataset, the multidimensional validation results include the following: three records of missing fields: the basic model data is missing an ID field, the insulator string model data is missing a type field, and the tower model data is missing a coordinate field. Two records of format mismatch: the coordinate field of a certain line path data contains a character value, and the ID field of a certain tower model data has a non-standard format. One record of value range anomaly: the Z coordinate of a certain basic model data exceeds the commonly used spatial range of the line. Two records of broken connection chains: corresponding to link number 03 and link number 07, respectively. One record of node reference anomaly: a reference to a non-existent node appears in link number 07. One record of path cascading error: the path cascading field is out of order. One record of interval anomaly: the difference between the insulator string length and the corresponding hanging point height exceeds the allowable range. One record of inconsistent values: the height of a certain component is inconsistent in different records. One record of matching error: the relative spacing of a certain path segment does not match the corresponding tower position. Based on these verification results, the processing steps are as follows: First, an attribute verification record area is established based on records with missing fields, mismatched formats, and abnormal value ranges. These three types of records are then written into attribute verification entries according to their order in the original verification results, ensuring that the order of records in the attribute verification entries corresponds to the verification discovery order of missing, format, and range. Next, records with broken connection chains, abnormal node references, and path cascading errors are grouped into the topology comparison record area and sorted by link number. All abnormal records for link number 03 are written into the topology verification entry first, followed by all abnormal records for link number 07, thus maintaining the clustering of topology anomalies by link number. Then, records with interval anomalies, inconsistent values, and mismatches are grouped into the indicator verification record area and written into indicator verification entries according to their source order, ensuring that the indicator verification entries correspond one-to-one with the original verification positions for easy subsequent tracking. Finally, the attribute verification entries, topology verification entries, and indicator verification entries are combined according to a fixed field order to form a verification result data package for task binding, report generation, and visualization construction.

[0039] In some embodiments of this application, when binding the verification result data packet with the task index to obtain the task handover record, the following steps are included: Retrieve the project number, project type code, stage number, and permission number from the task index, and organize the execution order of attribute verification entries, topology verification entries, and indicator verification entries in the verification result data package; Determine the task visibility range based on the permission number, and write the corresponding verification entries for the visibility range into the entry temporary storage area; Establish a number association between the project number and the attribute verification item in the item temporary storage area; establish a category association between the project type code and the topology verification item; establish a stage association between the stage number and the indicator verification item. Based on the field structure of the task index, the entries after being associated by number, category, and stage are structured and organized to obtain the task handover records corresponding to the task index.

[0040] Specifically, in the process of binding the verification result data package with the task index to obtain the task handover record, the project number, project type code, stage number, and permission number are first read from the task index, and these four items are used as the basic information for item filtering and association. Then, the attribute verification items, topology verification items, and indicator verification items in the verification result data package are organized according to the order in which they appear in the data package, forming a clearly ordered sequence of items. After organization, the visible item range is determined based on the permission level corresponding to the permission number. The correspondence between permission number and permission level is set by task management rules; for example, permission level one allows writing all items, permission level two allows writing attribute verification items and topology verification items, and permission level three allows writing only attribute verification items. Based on the allowed item types at each permission level, the category of each organized item is determined, and items within the visible range are written to the item temporary storage area, while items outside the visible range are not written to the item temporary storage area. After obtaining the entry staging area, number association, category association, and stage association are established respectively in the following ways: When establishing number association, the attribute verification entry is located from the entry staging area, and the project number is inserted as a prefix field at the beginning of the attribute verification entry's field, making the first field of the attribute verification entry the project number, thus forming an attribute verification entry structure containing the project number; when establishing category association, the topology verification entry is located from the entry staging area, and the project type code is inserted as a category field into the field sequence of the topology verification entry, so that each topology verification entry contains the project type code in a fixed position; when establishing stage association, the indicator verification entry is located from the entry staging area, and the stage number is appended to the field sequence of the indicator verification entry, so that the indicator verification entry contains the stage number in a specified field position. Through the insertion operation, all three types of entries carry the key fields in the task index and form a corresponding relationship with the task index. After completing the three association operations, the entries in the entry temporary storage area are structured according to the field structure of the task index. That is, the project number, project type code, stage number and permission number are written in the order required by the task index. Then, the attribute verification entries, topology verification entries and indicator verification entries after association processing are written into the entry record area in a preset order, thereby generating a task handover record consistent with the field structure of the task index.

[0041] In one specific embodiment, the task index includes project number A001, project type code LT01, stage number P2, and permission number 2. The verification result data package includes three attribute verification entries, two topology verification entries, and two indicator verification entries. First, the seven entries in the verification result data package are arranged sequentially according to their original order in the data package, forming attribute verification entry sequences, topology verification entry sequences, and indicator verification entry sequences. During entry filtering, the visibility range is determined based on the permission level corresponding to permission number 2. Permission level 2 allows writing attribute verification entries and topology verification entries but not indicator verification entries. Therefore, the three attribute verification entries and two topology verification entries are written to the entry temporary storage area, while the two indicator verification entries are filtered out and not written to the entry temporary storage area. Subsequently, number association, category association, and stage association are established. When establishing number association, the project number A001 is inserted at the beginning of the fields of the three attribute verification entries in the entry temporary storage area, so that the first field of each attribute verification entry is A001. When establishing category association, the project type code LT01 is inserted into the field sequence of the two topology verification entries in the entry temporary storage area, so that both topology verification entries contain the LT01 field. When establishing stage association, since the entry temporary storage area does not contain indicator verification entries, the stage number P2 field is not inserted. After completing the three association logics, the entry temporary storage area is structured according to the field structure of the task index, that is, the project number, project type code, stage number and permission number are written in the order of the fields. Then, according to the sorting order of attribute verification entries and topology verification entries, the five entries after association processing are written into the entry record area, finally resulting in a task handover record with the same structure as the task index and containing entries visible only to permission number 2.

[0042] In some embodiments of this application, when generating a quality inspection report file based on the task handover record and providing a download path, and constructing a visual loading data source based on the verification result data package, the process includes: Extract the project number, project type code, stage number and permission number from the task handover record, and write the extracted information into the basic information area of ​​the quality inspection report file according to the record order. Write the attribute verification entries, topology verification entries, and indicator verification entries from the task handover record into the verification information area of ​​the quality inspection report file according to the entry type; The basic information area and verification information area of ​​the quality inspection report file are processed to generate a downloadable quality inspection report file, and the generated file path is written to the download path record area; Based on the verification result data package, extract the attribute fields, coordinate fields, and number fields from the basic model data, insulator string model data, tower model data, and line path data. Then, construct a visual loading data source based on the model type using the extracted fields. Write the constructed visualization data source to the data loading index area.

[0043] Specifically, in the process of generating a quality inspection report file based on the task handover record and providing a download path, and simultaneously constructing a visual loading data source based on the verification result data package, the task handover record is first read. The project number, project type code, stage number, and permission number are extracted item by item from the task handover record. These four extracted fields are then written into the basic information area of ​​the quality inspection report file according to the order in the task handover record, ensuring that the basic information area fully presents the basic identifier content of the task index. Subsequently, the attribute verification entries, topology verification entries, and indicator verification entries in the task handover record are categorized according to entry type. Attribute verification entries are written into the attribute verification record area of ​​the quality inspection report file, topology verification entries into the topology verification record area, and indicator verification entries into the indicator verification record area, maintaining the order of the entries in the task handover record to ensure the traceability of the entry information in the report file. After writing the basic information area and verification information area, the quality inspection report file is structured and formatted to generate a downloadable quality inspection report file according to a predetermined format. The file's storage path is recorded during file generation and written to the download path record area for later access. When constructing the visualization loading data source, fields are read from each category of the verification result data package, including basic model data, insulator string model data, tower model data, and line path data. Attribute fields, coordinate fields, and number fields are extracted from each category, maintaining their original order based on their distribution in the original data. Subsequently, according to the data category to which the extracted fields belong, the basic model data fields are combined into basic model loading data, the insulator string model data fields into insulator string loading data, the tower model data fields into tower loading data, and the line path data fields into line path loading data, resulting in visualization loading data sets for the corresponding four categories. After the construction is completed, the four types of visualization loading data are written into the loading data index area according to the model type. This enables the loading data index area to record the type, location, and field range of various model data, providing a data source for model loading, attribute click query, and location jump in the subsequent 3D scene display.

[0044] In one specific embodiment, during the execution of an engineering data verification task, all candidate entries in the entry temporary storage area are first read, and each entry is filtered based on the task handover constraint rules: For attribute verification entries, the field integrity status, entry timestamp, and responsible person number of the entry record are compared in turn. When the field integrity meets the engineering data requirements and the entry timestamp is within the current task cycle, and the responsible person number is consistent with the current task executor, the entry is determined to be allowed to be written into the task handover record; For topology verification entries, the structural integrity requirements are determined based on the number of associated nodes contained in the entry, the topology closure detection result, and the completion mark of the preceding task. When all three conditions are met, the entry is marked as allowed to be written into the task handover record; For indicator verification entries, the entry is determined to be allowed to be written based on the corresponding engineering stage label, whether the key indicators have been calculated, and the stability of the calculation results. When all conditions are met, the entry is accepted into the handover scope. After completing the above judgment, the system performs number association and category association operations on the entries that are allowed to be written: the system appends the project number corresponding to the current verification task to the entry attribute table of each attribute verification entry in the form of key-value pairs; the project type code is written into the topology verification entry as a type label field to form a category association; and the stage number is written into the indicator verification entry as a stage index field to clarify the project stage to which the entry belongs. Taking a municipal road reconstruction and expansion project as an example, the system reads three candidate entries from the entry temporary storage area: attribute verification entry A records the coordinates and width information of the road centerline, all fields have been entered, and the person in charge is the current task operator; topology verification entry B contains the topology closure detection results of the road section nodes, the closure degree is maintained at 1, and the previous section verification task has been completed; indicator verification entry C corresponds to the base compaction stage of road construction, in which the compaction degree index and the smoothness index have been calculated and the fluctuation range meets the stage stability conditions. Write the project number GZ-2025-DL01 into the attribute table of item A, write the project type code DL into the type label field of item B, and write the stage number 03 into the stage index field of item C. This completes the construction of number association, category association and stage association for the three types of items, so that the task handover record can maintain clear project context consistency and traceability.

[0045] In some embodiments of this application, when obtaining project statistics results based on the statistical project quantity information of the verification result data package, the following steps are included: Read the number of records for basic model data, insulator string model data, tower model data and line path data from the verification result data package, and write the number of each type of record into the engineering quantity record area respectively; Calculate the number of basic records for the project based on the number of records in the basic model data, calculate the number of tower records for the project based on the number of records in the tower model data, calculate the number of insulator string records for the project based on the number of records in the insulator string model data, and write the number of each record into the quantity details area. Organize the route data according to the route sequence, count the number of route segments, and write the number of route segments into the route number record area; The records in the project quantity record area, quantity details area, and path quantity record area are combined in statistical order to obtain the project statistical results.

[0046] Specifically, when calculating project quantity information based on the verification result data package, the verification result data package is first parsed by category. After parsing the basic model data, insulator string model data, tower model data, and line route data, a line-by-line traversal and counting is performed for each type of data. The total number of record entries is obtained by accumulating the number of rows for each type of record, and the accumulated number of record entries for each type is written into the project quantity record area. Subsequently, when calculating the number of basic records, the accumulated total number of entries of the basic model data is directly used as the basic record number and written into the quantity details area. When calculating the number of tower records and insulator string records, the same traversal and accumulation are performed on the records of the tower model data and insulator string model data, respectively, and the resulting number of entries is written into the quantity details area in the order of tower record number segment and insulator string record number segment. The detailed area presents all three quantities as directly readable integer values. When processing line path data, the path sequences in the records are organized by extracting the path number field and arranging them in ascending order. The sorted path sequences are then scanned one by one, and the count value for each path segment is accumulated by adding 1 to the count value, ultimately obtaining the number of path segments, which is then written to the path quantity record area. After completing the writing of records in the engineering quantity record area, the quantity details area, and the path quantity record area, the fields in the three types of record areas are read sequentially according to the preset statistical combination order. The number of basic records, the number of tower records, the number of insulator string records, and the number of path segments are combined in sequence to form an engineering statistical result containing four quantity indicators, so that the engineering statistical result can fully reflect the model range and quantity scale involved in the verification result data package.

[0047] In one specific embodiment, the verification result data package contains 128 basic model data entries, 47 tower model data entries, 94 insulator string model data entries, and 62 line path data entries. When calculating the engineering quantity information, the basic model data is counted line by line, accumulating to 128, and written to the basic model quantity field of the engineering quantity record area; the same line counting is performed on the tower model data, accumulating to 47, and written to the tower model quantity field of the engineering quantity record area; the insulator string model data is counted, accumulating to 94, and written to the insulator string model quantity field of the engineering quantity record area; subsequently, the basic record count, tower record count, and insulator string record count in the quantity details area are written as 128, 47, and 94 respectively; when processing the line path count... First, 62 path records are read, and the path sequence field is extracted from each record. The extracted path sequences are sorted in ascending order by number. After sorting, each path is scanned one by one starting from the first one. For each scanned path segment, the path count is incremented by 1. Finally, the total number of path segments is 62, and this value is written to the path count record area. Finally, the number of basic models (128), tower models (47), insulator string models (94), and path segments (62) are read from the project quantity record area, quantity details area, and path quantity record area in statistical order. The four sets of data are combined in a fixed order to obtain the project statistics results for this project. This allows the project statistics results to clearly present the project scale and data distribution involved in the current verification result data package.

[0048] In some embodiments of this application, when generating a multidimensional quality inspection handover file set based on engineering statistical results and task handover records, including generating an engineering detail table, route path file, crossover statistics table, and conductor / ground wire parameter file, the following are included: Based on the engineering statistics results, read the quantity records of the basic model data, insulator string model data, tower model data and line route data, and write the quantity records into the quantity area of ​​the engineering details table according to the data type. Write the project number, project type code, stage number and permission number from the task handover record into the information area of ​​the project details table in the order of the fields, and combine the contents of the quantity area with the contents of the information area to obtain the project details table; Based on the path sequence, path concatenation field, and node coordinates of the route path data, the path segments are written sequentially into the path record area of ​​the route path file; Based on the path record area of ​​the route path file, analyze the distance and positional relationship between each path segment and external object, and write the distance and position records into the intersection record area of ​​the intersection statistics table; Based on the number field, coordinate field, and association field in the tower model data and insulator string model data, write the number record, spatial location record, and association record into the parameter record area of ​​the conductor parameter file; Write the project details, route path file, crossover statistics table, and conductor / ground wire parameter file into the multidimensional quality inspection handover file set in a fixed combination order.

[0049] Specifically, the quantities of foundation models, insulator string models, tower models, and route segments are read item by item from the engineering statistics. Each quantity is written into the quantity area of ​​the engineering details table according to its corresponding data type. A fixed order is followed when writing to the quantity area: foundation model quantity first, insulator string model quantity second, tower model quantity third, and route segment quantity last, ensuring that the position of each piece of information in the quantity area is consistent with the statistical results. Subsequently, the project number, project type code, stage number, and authority number are extracted sequentially from the task handover record and written into the information area of ​​the engineering details table according to the field order. After the information area is written, the information area and the quantity area are concatenated with fields in the order of information area first, then quantity area, thus forming the engineering details table. When generating the route file, the route sequence field, route concatenation field, and node coordinate field are read item by item from the route data, arranged from smallest to largest according to the route sequence, and the route segments within the same sequence are arranged in ascending order according to the path concatenation field. The number, cascading field, and node coordinates of each arranged path segment are sequentially written into the path record area of ​​the line path file, forming a continuous line path structure. When generating the intersection statistics table, each path segment in the line path file is read one by one. The straight-line distance and horizontal projection distance are calculated using the node coordinates of the path segment and the coordinates of the external object. The intersection is determined based on the height difference, lateral offset, and front-back positional relationship between the path segment and the external object. If both the distance calculation and positional relationship assessment indicate an intersection or crossing relationship between the path segment and the external object, the corresponding distance and positional records are written into the intersection record area of ​​the intersection statistics table. If no intersection or crossing relationship is formed, the segment is skipped and not written into the record area. When generating the conductor and ground wire parameter file, the number, coordinate, and association fields are extracted from the tower model data and insulator string model data. For each tower record, its number and spatial coordinates are read; for each insulator string record, its number, hanging point coordinates, and associated tower number are read. The logical relationship between the two types of data is confirmed by matching tower numbers, comparing anchor point coordinates, and verifying the consistency of associated fields. Successfully matched number records, spatial location records, and associated field records are then written to the parameter record area of ​​the conductor and ground wire parameter file. If the number does not match or the anchor point coordinates do not conform to the spatial range of the corresponding tower, the record is excluded. After all files are generated, the project details table, route path file, cross-span statistics table, and conductor and ground wire parameter file are written into the multidimensional quality inspection handover file set in a fixed combination order. The combination order is: project details table first, route path file second, cross-span statistics table third, and conductor and ground wire parameter file last. This ensures that the multidimensional quality inspection handover file set contains complete project information, route information, cross-span information, and parameter information, facilitating reading and use in subsequent handover stages.

[0050] In a specific engineering example, the task index records project number GJ001, project type code LX, stage number SJ, and permission number P1. The verification result data package shows that there are 40 records for basic model data, 15 records for insulator string model data, 25 records for pole tower model data, and 32 path segments in the line route data. Based on the engineering statistics, firstly, 40 records are written to the basic model quantity column of the project details table, 15 records to the insulator string quantity column, 25 records to the pole tower quantity column, and 32 records to the path segment quantity column, forming the quantity area of ​​the project details table. Subsequently, the project number GJ001, project type code LX, stage number SJ, and permission number P1 are read from the task handover record and written to the information area in field order. After the information area is written, the fields of the two areas are concatenated by placing the information area first and the quantity area last to obtain the complete project details table. When generating the line route file, the 32 path segments in the line route data are read, and each segment contains path sequence values, path concatenation values, and node coordinates. For example, a segment with a path sequence of one and a path concatenation of one represents the first continuous segment of the line; a segment with a path sequence of one and a path concatenation of two represents the second segment of the same line, and so on. The path sequences are arranged from smallest to largest, and within the same sequence, they are arranged from smallest to largest concatenation field. The number, concatenation value, and node coordinates of each segment are sequentially written into the path record area, forming a continuously readable line path file. When generating the crossover statistics table, the path record area of ​​the line path file is analyzed line by line. For example, if the starting coordinates of path segment one are three meters horizontally away from the coordinates of a communication pipeline, with a zero elevation difference, and the horizontal distance is less than five meters, then a crossover relationship is determined, and the three-meter distance and zero elevation difference are written into the crossover record area. If path segment two is more than ten meters away from an external object and the elevation difference is not within the judgment condition, then this segment is not written into the crossover record area. Through segment-by-segment analysis, several crossover records are finally obtained. When generating the conductor / ground wire parameter file, twenty-five tower records are read from the tower model data. Each record contains the tower number and its spatial coordinates. Then, fifteen insulator string records are read from the insulator string model data. Each insulator string record contains the insulator string number, attachment point coordinates, and associated tower number. For example, if an insulator string record shows that its associated tower number is T005, and a tower with the number T005 exists in the tower model data, then the spatial location is determined to match the spatial coordinate range of that tower based on the attachment point coordinates. This confirms the association, and the insulator string number, attachment point coordinates, and associated tower number are written to the parameter record area. If an insulator string record has an associated tower number of T030, but a tower with the number T030 does not exist in the project, or the attachment point coordinates are not within the coordinate range of the corresponding tower, then this record is excluded and not written to the parameter record area.After all files are generated, the project details table, route path file, crossover statistics table, and conductor / ground wire parameter file are written into the multidimensional quality inspection handover file set in the following order: project details table first, route path file second, crossover statistics table third, and conductor / ground wire parameter file last. This will ultimately form a complete multidimensional quality inspection handover file set that can be handed over and read at once.

[0051] In another preferred embodiment based on the above embodiments, see [reference] Figure 2 As shown, this embodiment provides a GIM file quality inspection and handover management system based on multi-dimensional verification, used to implement the above-mentioned GIM file quality inspection and handover management method based on multi-dimensional verification, including: The task index creation module is configured to retrieve project number information, design stage information, project type information, and visitor identification information to create a task index. The GIM file parsing and integration module is configured to associate the GIM file with the task index when receiving a GIM file, and to perform parsing processing on the GIM file, integrating the parsing results into a GIM dataset containing basic model data, insulator string model data, tower model data and line path data. The multidimensional verification module is configured to perform multidimensional verification on the GIM dataset, including basic attribute verification, topology verification, and index verification, and obtain multidimensional verification results. The report generation module is configured to generate a verification result data package based on the multidimensional verification results, bind the verification result data package with the task index to obtain the task handover record, generate a quality inspection report file based on the task handover record and provide a download path, and construct a visual loading data source based on the verification result data package; The engineering data statistics module is configured to statistically analyze the engineering quantity information based on the verification result data package and obtain the engineering statistics results. The output module is configured to generate a project detail table, route path file, crossover statistics table and conductor / ground wire parameter file based on the project statistics results and task handover records, thereby obtaining a multi-dimensional quality inspection handover file set and completing the handover.

[0052] Understandably, the task index creation module centrally registers four categories of basic information: project number, design stage, project type, and visitor identifier. This allows subsequent file parsing, verification, and statistical processes to be driven by a unified index framework, reducing information gaps during manual handover. The GIM file parsing and integration module, supported by the task index, structurally decomposes the received GIM files, sequentially integrating basic model data, insulator string model data, tower model data, and line path data into a definable dataset, providing clear data boundaries for subsequent multidimensional verification. The multidimensional verification module performs cross-validation from three directions: basic attributes, topology, and indicator relationships. This allows for parallel verification of model field integrity, topological continuity, and logical matching relationships of indicators, significantly reducing the risk of missed and false detections. The report generation module establishes a task handover record based on the verification result data package and further generates a quality inspection report file and a visual loading data source, making the results both readable and usable for engineering applications. The engineering data statistics module statistically analyzes the quantitative relationships among basic model data, insulator string model data, tower model data, and line route data, providing a clear overview of the project scale, composition ratios, and number of critical paths. Finally, the output module generates and combines the project details table, line route file, crossover statistics table, and conductor / ground wire parameter file into a multi-dimensional quality inspection and handover document set, achieving a structured and verifiable deliverable handover. This overall structure creates a coherent link between project document reception, verification, statistics, and handover, improving the reliability of the quality inspection process, the clarity of data organization, and the accuracy of deliverable handover.

[0053] Those skilled in the art will understand that embodiments of this application can be provided as methods, systems, or computer program goods. Therefore, this application can take the form of a completely hardware embodiment, a completely software embodiment, or an embodiment combining software and hardware aspects. Furthermore, this application can take the form of a computer program goods embodied on one or more computer-usable storage media (including, but not limited to, disk storage, CD-ROM, optical storage, etc.) containing computer-usable program code.

[0054] This application is described with reference to flowchart illustrations and / or block diagrams of methods, apparatus (systems), and computer program goods according to embodiments of this application. It will be understood that each block of the flowchart illustrations and / or block diagrams, and combinations of blocks in the flowchart illustrations and / or block diagrams, can be implemented by computer program instructions. These computer program instructions can be provided to a processor of a general-purpose computer, special-purpose computer, embedded processor, or other programmable data processing apparatus to produce a machine, such that the instructions, executed by the processor of the computer or other programmable data processing apparatus, generate instructions for implementing the flowchart... Figure 1 One or more processes and / or boxes Figure 1A device that provides the functions specified in one or more boxes.

[0055] These computer program instructions may also be stored in a computer-readable storage medium that can direct a computer or other programmable data processing device to function in a particular manner, such that the instructions stored in the computer-readable storage medium produce an article of manufacture including instruction means, which are implemented in a process Figure 1 One or more processes and / or boxes Figure 1 The function specified in one or more boxes.

[0056] These computer program instructions may also be loaded onto a computer or other programmable data processing apparatus to cause a series of operational steps to be performed on the computer or other programmable apparatus to produce a computer-implemented process, thereby providing instructions that, when performed on the computer or other programmable apparatus, provide for implementing the process. Figure 1 One or more processes and / or boxes Figure 1 The steps of the function specified in one or more boxes.

[0057] Finally, it should be noted that the above embodiments are only used to illustrate the technical solutions of the present invention and not to limit it. Although the present invention has been described in detail with reference to the above embodiments, those skilled in the art should understand that modifications or equivalent substitutions can still be made to the specific implementation of the present invention. Any modifications or equivalent substitutions that do not depart from the spirit and scope of the present invention should be covered within the scope of protection of the claims of the present invention.

Claims

1. A method for quality inspection and handover management of GIM files based on multi-dimensional verification, characterized in that, include: Obtain project number information, design stage information, project type information, and visitor identification information, and establish a task index; When receiving a GIM file, the GIM file is associated with the task index, and parsing is performed on the GIM file. The parsing results are then integrated into a GIM dataset containing basic model data, insulator string model data, tower model data, and line path data. The GIM dataset is subjected to multidimensional verification, including basic attribute verification, topology verification, and index verification, to obtain multidimensional verification results. A verification result data package is generated based on the multidimensional verification results, and the verification result data package is bound to the task index to obtain a task handover record. A quality inspection report file is generated based on the task handover record and a download path is provided. A visual loading data source is constructed based on the verification result data package. Based on the statistical data of the verification results, the project quantity information is obtained to obtain the project statistical results; Based on the engineering statistics and the task handover records, a project detail table, route path file, crossover statistics table and conductor / ground wire parameter file are generated to obtain a multi-dimensional quality inspection handover file set and complete the handover.

2. The GIM file quality inspection and transfer management method based on multi-dimensional verification according to claim 1, characterized in that, When acquiring project number information, design stage information, project type information, and visitor identification information, and establishing a task index, the following is included: Perform a uniqueness comparison on the project number information, process the stage label numbering according to the design stage information, group the project categories according to the project type information, and verify the visitor identification information for permissions. Combine the information that has passed the comparison, grouping, numbering and verification according to the preset field order to obtain the task index.

3. The GIM file quality inspection and transfer management method based on multi-dimensional verification according to claim 2, characterized in that, When associating GIM files with the task index, parsing the GIM files, and integrating the parsing results into a GIM dataset containing basic model data, insulator string model data, tower model data, and line route data, the following steps are taken: The GIM file is read line by line, each line is split according to the field delimiter, and the split fields are categorized according to the field order in the task index. After classification, structural identification is performed on the fields according to their categories. Coordinate field identification rules are used to determine whether they belong to basic model data, hanging point and link field identification rules are used to determine whether they belong to insulator string model data, pole and tower model field and component level field are combined to determine whether they belong to pole and tower model data, and path sequence field and path cascade field are combined to determine whether they belong to line path data. The identified data is written into the corresponding data areas in the order of basic model data, insulator string model data, tower model data, and line path data, and then combined according to the order in which they appear in the file to obtain the GIM dataset.

4. The GIM file quality inspection and transfer management method based on multi-dimensional verification according to claim 3, characterized in that, When performing multidimensional validation on the GIM dataset, the following are included: When performing basic attribute verification, the number field, type field and coordinate field are extracted from the basic model data, insulator string model data, tower model data and line path data respectively. The field integrity, field format and value domain relationship are compared and verified to obtain the basic attribute verification record. When performing topology verification, a connection chain is generated based on the node number, component number, and connection field in the basic model data and tower model data. The continuity of the connection chain, the reference relationship between nodes, and the order of path cascading are compared topologically to obtain a topology comparison record. When performing index verification, relevant index fields are extracted from the tower model data and insulator string model data in the GIM dataset. Based on the numerical relationship and recording order of the index fields, the consistency, numerical range and mutual matching relationship of the index records are compared and verified to obtain index verification records. Write the basic attribute verification records, topology comparison records, and indicator verification records into the multidimensional verification results.

5. The GIM file quality inspection and transfer management method based on multi-dimensional verification according to claim 4, characterized in that, When generating the verification result data packet based on the multidimensional verification result, the following are included: The multidimensional verification results are classified and organized according to the basic attribute verification records, topology comparison records, and indicator verification records, and attribute verification record areas, topology comparison record areas, and indicator verification record areas are established respectively. Write the records of missing fields, incorrect formats, and abnormal values ​​in the attribute verification record area into the attribute verification entries in the order of their appearance. Write the records of broken connection chains, abnormal node references, and path cascading errors in the topology comparison record area into the topology verification entries according to the link number; Write the interval anomaly records, value inconsistency records, and matching error records in the indicator verification record area into the indicator verification entries in the order of their source. The attribute verification items, topology verification items, and indicator verification items are combined in a fixed field order to form a verification result data package.

6. The GIM file quality inspection and handover management method based on multi-dimensional verification according to claim 5, characterized in that, When binding the verification result data package with the task index to obtain the task handover record, the following is included: Retrieve the project number, project type code, stage number, and permission number from the task index, and organize the execution order of attribute verification entries, topology verification entries, and indicator verification entries in the verification result data package; Determine the task visibility range based on the permission number, and write the corresponding verification entries for the visibility range into the entry temporary storage area; Establish a number association between the project number and the attribute verification item in the item temporary storage area; establish a category association between the project type code and the topology verification item; establish a stage association between the stage number and the indicator verification item. Based on the field structure of the task index, the entries after being associated by number, category, and stage are structured and organized to obtain the task handover records corresponding to the task index.

7. The GIM file quality inspection and transfer management method based on multi-dimensional verification according to claim 6, characterized in that, When generating a quality inspection report file based on the task handover record and providing a download path, and constructing a visual loading data source based on the verification result data package, the process includes: Extract the project number, project type code, stage number and permission number from the task handover record, and write the extracted information into the basic information area of ​​the quality inspection report file according to the record order. Write the attribute verification entries, topology verification entries, and indicator verification entries from the task handover record into the verification information area of ​​the quality inspection report file according to the entry type; The basic information area and verification information area of ​​the quality inspection report file are processed to generate a downloadable quality inspection report file, and the generated file path is written to the download path record area; Based on the verification result data package, extract the attribute fields, coordinate fields, and number fields from the basic model data, insulator string model data, tower model data, and line path data. Then, construct a visual loading data source based on the model type using the extracted fields. Write the constructed visualization data source to the data loading index area.

8. The GIM file quality inspection and transfer management method based on multi-dimensional verification according to claim 7, characterized in that, When obtaining the project statistics results based on the statistical project quantity information of the verification result data package, the following are included: Read the number of records for basic model data, insulator string model data, tower model data and line path data from the verification result data package, and write the number of each type of record into the engineering quantity record area respectively; Calculate the number of basic records for the project based on the number of records in the basic model data, calculate the number of tower records for the project based on the number of records in the tower model data, calculate the number of insulator string records for the project based on the number of records in the insulator string model data, and write the number of each record into the quantity details area. Organize the route data according to the route sequence, count the number of route segments, and write the number of route segments into the route number record area; The records in the project quantity record area, quantity details area, and path quantity record area are combined in statistical order to obtain the project statistical results.

9. The GIM file quality inspection and transfer management method based on multi-dimensional verification according to claim 8, characterized in that, When generating a multidimensional quality inspection handover file set based on the project statistics and the task handover record, including the project details table, route path file, intersection statistics table, and conductor / ground wire parameter file, the file set includes: Based on the engineering statistics results, read the quantity records of the basic model data, insulator string model data, tower model data and line route data, and write the quantity records into the quantity area of ​​the engineering details table according to the data type. Write the project number, project type code, stage number and permission number from the task handover record into the information area of ​​the project details table in the order of the fields, and combine the contents of the quantity area with the contents of the information area to obtain the project details table; Based on the path sequence, path concatenation field, and node coordinates of the route path data, the path segments are written sequentially into the path record area of ​​the route path file; Based on the path record area of ​​the route path file, analyze the distance and positional relationship between each path segment and external object, and write the distance and position records into the intersection record area of ​​the intersection statistics table; Based on the number field, coordinate field, and association field in the tower model data and insulator string model data, write the number record, spatial location record, and association record into the parameter record area of ​​the conductor parameter file; Write the project details, route path file, crossover statistics table, and conductor / ground wire parameter file into the multidimensional quality inspection handover file set in a fixed combination order.

10. A GIM file quality inspection and handover management system based on multi-dimensional verification, used to implement the GIM file quality inspection and handover management method based on multi-dimensional verification as described in any one of claims 1-9, characterized in that, include: The task index creation module is configured to retrieve project number information, design stage information, project type information, and visitor identification information to create a task index. The GIM file parsing and integration module is configured to associate the GIM file with the task index when receiving a GIM file, and to perform parsing processing on the GIM file, integrating the parsing results into a GIM dataset containing basic model data, insulator string model data, tower model data and line path data. The multidimensional verification module is configured to perform multidimensional verification on the GIM dataset, including basic attribute verification, topology verification and index verification, to obtain multidimensional verification results. The report generation module is configured to generate a verification result data package based on the multidimensional verification results, bind the verification result data package with the task index to obtain a task handover record, generate a quality inspection report file based on the task handover record and provide a download path, and construct a visual loading data source based on the verification result data package; The engineering data statistics module is configured to statistically analyze the engineering quantity information based on the verification result data package and obtain engineering statistics results. The output module is configured to generate an engineering detail table, a route path file, a crossover statistics table, and a conductor / ground wire parameter file based on the engineering statistics results and the task handover record, thereby obtaining a multi-dimensional quality inspection handover file set and completing the handover.

Images