A system and method for processing bim municipal pipeline data
Patent Information
- Application Number
- CN202610487332.X
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Filing Date
- 2026-04-14
- Publication Date
- 2026-08-04
AI Technical Summary
然而,当前市政管线设计数据普遍存在管理混乱、代码与格式不统一、各道路管线编码体系独立等问题,极易引发数据遗漏或重叠错误,不仅给相关管理部门带来巨大的数据处理压力,也导致整体工作效率低下
本发明的创造性并非源于使用了计算机,而在于其为达成市政管线数据标准化这一具体目标所设计的特定处理规则、数据流转逻辑和程序集成方案。这些方案并非本领域技术人员的常规或显而易见选择:
Smart Images

Figure CN122508764A_ABST
Abstract
Description
Technical Field
[0001] This invention relates to the fields of building information processing and computer data processing technology, and in particular to a system and method for processing municipal pipeline data. Background Technology
[0002] The standardized BIM platform for municipal pipeline design data entry integrates various tools and technologies to help designers process municipal pipeline data more effectively and ensure its compliance with standardization requirements. Implementing municipal pipeline data standardization requires the standardized processing of multi-disciplinary pipeline data, specifically including a series of key tasks such as data submission, element layering, attribute classification, and element coding. However, current municipal pipeline design data generally suffers from problems such as chaotic management, inconsistent codes and formats, and independent coding systems for different roads and pipelines. This easily leads to data omissions or overlaps, placing enormous data processing pressure on relevant management departments and resulting in overall low work efficiency.
[0003] Traditional municipal pipeline integration involves compiling design drawings into a pipeline integration specialist's database before the construction of individual pipelines begins. This specialist then performs overall planning for each pipeline before directly entering the construction phase. However, the spatial representation of the integrated pipeline network in a two-dimensional diagram is prone to collisions and contradictions, inevitably leading to design changes and rework when pipeline conflicts arise during later construction. In contrast, integrating BIM smart pipeline network data using computer scripting programs lays a solid foundation for BIM data processing and its integration into the CIM (Construction, Planning, and Management) platform. Based on a unified park information model (CIM), this approach breaks down data barriers between planning, construction, and management, changing the traditional disconnect between these functions. It organically integrates planning, design, construction management, completion and handover, and municipal management, addressing management needs during the planning and construction phases and realizing a new paradigm of integrated park construction and management.
[0004] Therefore, how to achieve a standardized BIM platform for the rapid entry of multiple municipal pipelines into the database is a key technical problem that this invention urgently needs to solve. Summary of the Invention
[0005] This invention aims to solve the core challenge of rapidly and accurately integrating multi-disciplinary municipal pipeline data into a standardized BIM platform. It proposes a BIM municipal pipeline data processing system and method. By constructing an integrated data processing system and method, it automates the cleaning, transformation, encoding, and integration of disorganized, non-standard design data, efficiently and accurately converting it into standard data fully compliant with the "Underground Pipeline Data Specification," and directly generating a standardized database. This database can be directly accessed by 3D platforms such as ArcGIS to quickly and automatically construct BIM pipeline models with complete attribute information, thereby realizing the transformation from original design to 3D visualization modeling and analysis.
[0006] To achieve the above-mentioned objectives, the present invention proposes the following technical solution: In a first aspect, the present invention proposes a BIM municipal pipeline data processing system, comprising: The acquisition module is used to acquire and import original design data for municipal pipelines; A processing module, connected to the acquisition module, is used to perform automated standardization processing on the original design data. The processing module includes: The code specification unit is used to extract the original professional codes and serial numbers and convert them into standard professional codes according to a preset mapping relationship; Unit coding unit, used to generate standard unit codes based on probe unit information; The timing processing unit is used to read and process the probe date information from a preset data source. The unique identifier generation unit is used to integrate standard professional codes, standard unit codes, standardized date information and serial numbers to generate unique identifiers for pipelines and pipe points that conform to underground pipeline data specifications. The data standardization unit is used to unify data format, standardize element names, remove formula redundancy, and generate standard attribute data after standardization. A standard library generation module, connected to the processing module, is used to export the normalized standard attribute data and construct a standard spatial database that can be directly used for 3D modeling. The modeling module, connected to the standard library generation module, is used to automatically generate BIM municipal pipeline 3D models with complete attributes based on the standard spatial database.
[0007] In some implementations, the data straightening unit is specifically used to perform at least one of the following automated operations: Standardize the decimal precision of coordinates, elevation, and burial depth; Batch replace non-standard feature names with standard feature names; Convert the formula calculation column into a pure numeric column; Remove redundant data rows and standardize field structures.
[0008] Obtain the detection date information and increment the date according to preset rules; In some implementations, the export unit is specifically used to: the time-series processing unit is configured to: read a base date from an external date file and automatically increment the date for multiple road data according to a preset rule.
[0009] In some implementations, the standard spatial database is a structured database that conforms to the municipal underground pipeline data specifications and can be directly read by general GIS platforms.
[0010] In some implementations, the modeling module is configured to: import a standard spatial database into a 3D GIS platform and generate a BIM pipeline model that supports spatial analysis through feature recognition and graphic transformation.
[0011] In some implementations, it also includes a visualization and interaction module for performing 3D display, attribute query, spatial positioning and viewpoint transformation operations on the BIM pipeline 3D model.
[0012] In some implementations, the pipeline data includes at least: starting point number, ending point number, burial depth, elevation, material, pipe diameter, ownership information, detection unit, and detection date; the pipe point data includes at least: pipe point number, coordinates, ground elevation, features, appurtenances, and unique identifier.
[0013] Secondly, the present invention also proposes a method for processing BIM municipal pipeline data, based on any of the systems described herein, comprising the following steps: S1. Obtain and import the original design data of municipal pipelines; S2. Perform automated standardization processing on the original design data: Extract the original professional codes and serial numbers, and convert them into standard professional codes; Generate standard unit codes based on the detection unit information; read and standardize the detection date information from a preset data source; Integrate standard professional codes, standard unit codes, standard date information and serial numbers to generate unique identification codes for pipelines and pipe points that conform to the specifications; Standardize the data format, standardize the element names, and remove redundant formulas to obtain standardized attribute data after normalization. S3. Construct the standardized attribute data into a standard spatial database that can be directly used for 3D modeling; S4. Automatically generate a BIM 3D model of municipal pipelines with complete attributes based on the standard spatial database.
[0014] In some implementations, step S2 further includes: Load the raw data into the preset formula template for batch calculation; Perform data cleaning: remove redundant rows, standardize decimal precision, and standardize codes and material names; Batch replace non-standard feature names with standard feature names; Convert the formula column into a pure numeric column; Export data columns that meet the data entry requirements to the target data table with one click.
[0015] In some implementations, step S3 further includes: Export the standard attribute data as an intermediate table file, then import it into a preset database template to automatically generate a standard spatial database file. In addition, step S4 also includes: The standard spatial database is imported into the GIS platform, and through feature identification, editing, and graphic conversion, a BIM pipeline model that supports 3D visualization and spatial analysis is generated.
[0016] Compared with the prior art, the beneficial effects of the technical solution of the present invention are: The inventiveness of this invention does not stem from the use of a computer, but from the specific processing rules, data flow logic, and program integration scheme designed to achieve the concrete goal of standardizing municipal pipeline data. These schemes are not conventional or obvious choices for those skilled in the art: 1) Programmatic encapsulation of specific business rules: Using built-in Excel functions (such as VLOOKUP) is either inefficient or impossible. Therefore, this invention develops specific software programs (such as MyGet, ReplaceDcode12 / 13) to encapsulate complex business rules (such as professional code extraction and conversion, and date incrementing by road order). This integrates fragmented business rules that rely on manual judgment into a set of automatically executable and precise software program instructions.
[0017] 2) Automated linkage and synthesis of multi-source, heterogeneous data: The solution systematically integrates data and rules from different sources and with varying formats. Input A: Miscellaneous non-standard design data (such as TX-1).
[0018] Input B: Standard encoding mapping rule (e.g., TX->DX).
[0019] Enter C: External dependency file (date sequence in ddate.xls).
[0020] Enter D: Unit code rules (Municipal Academy = 12, China Consulting Academy = 13).
[0021] The core processing mechanism is to automatically generate a unique identification code (such as DX12202211010001) by calling and combining the above-mentioned specific programs, in accordance with the coding principles of the "Underground Pipeline Data Specification" (pipeline code + unit code + date + serial number).
[0022] 3) A complete automated workflow has been built: From "import-split / replace-organize-assign-synthesize-export-input-modeling", this invention defines an end-to-end automated workflow from front-end design data to back-end 3D model. The construction of this workflow, especially the specific steps of "data organization" (deleting rows, decimal processing, code conversion, date series generation, etc.), is a solution tailored to the data pain points of this industry, rather than a general workflow.
[0023] 4) This transforms a task that was originally "large in volume of data, extensive in content, involves multiple professional knowledge, is tedious and complex, and prone to errors" into a near "one-click" processing workflow. This directly overcomes the industry challenges faced by management departments, such as "high data processing pressure and low efficiency" and "omissions and overlapping errors" caused by data disorder. The final output is a standardized database that can be directly used for modeling on standardized BIM platforms and ArcGIS software, providing a reliable data foundation for BIM / CIM applications, which has significant practical application value. Attached Figure Description
[0024] Figure 1 This is a module diagram of the BIM municipal pipeline data processing system of the present invention.
[0025] Figure 2 This is an overall flowchart of the BIM municipal pipeline data processing method of the present invention.
[0026] Figure 3 This is a technical roadmap for the BIM municipal pipeline data processing system and method of the present invention.
[0027] Figure 4 This is an example diagram of the data acquisition interface for municipal pipeline survey and design according to an embodiment of the present invention.
[0028] Figure 5 This is an example diagram of the interface for selecting municipal pipeline survey and design data according to an embodiment of the present invention.
[0029] Figure 6 This is an example of the main interface of the municipal pipeline database processing system according to an embodiment of the present invention. Figure 1 (All majors).
[0030] Figure 7 This is an example of the main interface of the municipal pipeline database processing system according to an embodiment of the present invention. Figure 2 (Telecommunications major).
[0031] Figure 8 This is an example of the main interface of the municipal pipeline database processing system according to an embodiment of the present invention. Figure 3 (Function Description).
[0032] Figure 9 This is an example diagram of the interface for importing source files according to an embodiment of the present invention.
[0033] Figure 10 This is an example screenshot of the interface before opening the "nameddate" file (before data processing).
[0034] Figure 11 These are example diagrams of the complete data export interface in embodiments of the present invention.
[0035] Figure 12 This is an example diagram of the main interface of the ACCESS database template file according to an embodiment of the present invention.
[0036] Figure 13 This is an example diagram illustrating the accurate organization results of a fully professional database according to specifications, as per an embodiment of the present invention.
[0037] Figure 14 This is an example diagram of the ArcGIS interface for extracting database information according to an embodiment of the present invention.
[0038] Figure 15 This is an example diagram of the ArcGIS data information to model conversion interface according to an embodiment of the present invention. Detailed Implementation
[0039] The present invention will now be described in detail with reference to the accompanying drawings and embodiments, providing a complete and clear description of the technical solutions in the embodiments of the present invention. Obviously, the embodiments described are only a part of the embodiments of the present invention. Unless otherwise specifically stated, the relative arrangement, values, etc. of the components described in these embodiments do not limit the scope of the present invention.
[0040] Example 1: As Figure 1 As shown, this invention provides a BIM municipal pipeline data processing system, which includes an acquisition module 100, a processing module 200, a standard library generation module 300, and a modeling module 400.
[0041] The processing module 200 further includes a code standardization unit 210, a unit encoding unit 220, a timing processing unit 230, a unique identifier generation unit 240, and a data normalization unit 250.
[0042] Specifically, BIM municipal pipeline design data is obtained from municipal pipeline design drawings. This data mainly includes two categories of data items: pipes and pipe points, as detailed below: Pipeline data items must include at least: starting point number s_point, ending point number e_point, starting depth s_deep, ending depth e_deep, starting elevation s_h, ending elevation e_h, material, burial method d_type, line type line_style, pipe diameter d_s, ownership unit belong, project number projectno, casing material pd_m, element code code, road name roadname, road code roadcode, number of pipes cab-count, pressure value vol_pres, total number of holes hole_count, number of holes used hole_used, detection unit dunit, detection unit code docde, usage status usestatus, flow direction flow_d, detection date ddate, inspection description c_descrip, remark, update status updatestatus, database identifier fguid, hazard investigation status pitfall, burial date burialdate, service life, and administrative division.
[0043] The pipeline point data items should include at least the following: pipeline point number p_no, measurement point number m_no, coordinates x, coordinates y, ground elevation h, feature, attachments subsid, manhole cover type pstyle, manhole cover specification pds, manhole cover material pma, project number projectno, element code code, road name roadname, road code roadcode, map sheet number mapnumber, detection unit dunit, detection unit code docde, ownership unit belong, precision level precision, rotation angle rotang, detection date ddate, line inspection description c_descrip, remark, update status updatestatus, database identifier fguid, hazard investigation status pitfall, burial date burialdate, service life, administrative division administrative, and update type UpdateType.
[0044] Based on actual needs, the system also includes a BIM pipeline model visualization module: through the BIM pipeline model, the attributes of the BIM model are identified and searched, and the pipeline model in the 3D view interface can be zoomed in, zoomed out, dragged and rotated by the mouse.
[0045] Specifically, for the BIM pipeline model, the input is a structured database formed after system cleaning, transformation, and standardization; the output is a digital twin model carrying complete attribute information, which can be used for 3D visualization and spatial analysis. This transformation process realizes the conversion from non-standard design data to standardized BIM assets that can be used for integrated planning, construction, and management (CIM) applications.
[0046] 1. The model's input includes the following core data items: Pipeline data includes complete attribute fields such as starting point number, ending point number, starting and ending point burial depth, starting and ending point elevation, material, pipe diameter, burial method, ownership unit, element code, road name, and detection date.
[0047] Pipeline data includes complete attribute fields such as pipeline number, coordinates, ground elevation, features, attachments, manhole cover information, feature code, ownership unit, and detection date.
[0048] 2. The model output is a BIM pipeline model that can be visualized, analyzed, and manipulated in a 3D environment. Specifically, it manifests as (e.g.) Figure 13 , Figure 14 (and as described in step S12): 3D geometric model: A 3D graphic generated in platforms such as ArcGIS that reflects the spatial location and connection relationship of pipelines.
[0049] Attach complete attribute information: Each pipeline and pipe point element in the model is associated with all attribute information in the above-mentioned standardized database, supporting attribute query, identification and statistical analysis.
[0050] Interactive operation: This model supports interactive operations such as scaling, rotation, translation, viewing attributes, and spatial query.
[0051] Example 2: Figure 2 As shown, this invention provides a method for processing BIM municipal pipeline data, comprising the following steps: S1. Obtain and import the original design data of municipal pipelines; S2. Perform automated standardization processing on the original design data: Extract the original professional codes and serial numbers, and convert them into standard professional codes; Generate standard unit codes based on the detection unit information; read and standardize the detection date information from a preset data source; Integrate standard professional codes, standard unit codes, standard date information and serial numbers to generate unique identification codes for pipelines and pipe points that conform to the specifications; Standardize the data format, standardize the element names, and remove redundant formulas to obtain standardized attribute data after normalization. S3. Construct the standardized attribute data into a standard spatial database that can be directly used for 3D modeling; S4. Automatically generate a BIM 3D model of municipal pipelines with complete attributes based on the standard spatial database.
[0052] like Figure 3 The diagram shown is a technical roadmap for an embodiment of the BIM municipal pipeline data processing system and method of the present invention.
[0053] like Figure 4 As shown, the "Municipal Pipeline Database Processing System V1.0" software developed in this invention is launched.
[0054] like Figure 5 As shown, the system's main interface (all specialties) is accessed. This interface consists of four parts: import area, editing area, export area, and text navigation. The editing area contains nine pages: all specialties, telecommunications, power supply, water supply, greening water, sewage, rainwater, greywater, and function descriptions.
[0055] This is the first interface you see after starting the system, based on the raw data file exported from municipal survey and design drawings. Click "No.1 Import Source File" on the main interface (corresponding to...). Figure 7 (Interface) Start the data import process.
[0056] like Figure 7 As shown, this is the telecommunications professional page of the system's main interface. Its layout is similar to the general professional page, but the button functions are for the pipeline and pipe point data of the telecommunications professional.
[0057] Taking the processing of telecommunications data as an example, after entering the main interface for this telecommunications specialty, in the import interface ( Figure 9 Select to import only telecom pipeline data, and then perform telecom-specific data processing operations on this page.
[0058] like Figure 8 The page shown is a function description page, which details the eight specific items of data processing, as well as the location and naming rules for the exported files.
[0059] The system automatically completes the data processing steps based on the eight specific steps described on this page (deleting redundant rows, standardizing data format, replacing professional codes, assigning unit codes and dates, and standardizing material names).
[0060] like Figure 9 As shown, clicking the "Import Source File No. 1" button in the import area will bring up the "Import Source File" interface. Users can select the source Excel file through "Import by File Path" and choose "Import All" or import data from a specific discipline (such as power supply lines).
[0061] In this embodiment, the user selects a file on this interface and performs a full import (full professional version) or imports telecommunications pipeline data separately (single professional version) to complete the data input.
[0062] like Figure 10 As shown, before performing data processing, an Excel file named ddate.xls needs to be opened in advance so that the system can read the detection date information.
[0063] Before performing the "No3 Data Cleaning" step, you must ensure that the ddate.xls file has been opened beforehand as shown in this figure. The system will read the date sequence from this file for encoding.
[0064] like Figure 11 The image shows an example of the "Exported Edited File.xlsx" data generated in the root directory of drive D after all data processing is completed and "No.7 Export All" is clicked. The data in this table has been organized according to specifications and a standard unique identifier (such as DX12202211071001) has been generated.
[0065] After completing the "No. 6 One-Click Export" and "No. 7 All Export" operations, this standardized data file will be generated. The full professional version will export integrated data, while the single professional version will export data containing only that professional field (such as telecommunications).
[0066] like Figure 12 As shown, the main interface of the ACCESS database template file is opened. Through its preset forms and buttons such as "Give, Rain, Sewage, Greenery" and "Electricity, Communication", you can import the exported professional data tables.
[0067] Will Figure 11 The generated exported file can be used to import data from various disciplines for database synthesis via the corresponding buttons on this ACCESS template interface.
[0068] like Figure 13 As shown, this is the complete and standardized municipal pipeline database generated after all professional data tables were successfully imported into the ACCESS template.
[0069] pass Figure 12 After the template is imported, the system automatically generates a standard database file (.mdb format) that conforms to the "Underground Pipeline Data Specification" as direct input for BIM modeling.
[0070] like Figure 14 As shown, the generated standard database is visually verified and geometrically checked in ArcMap software to ensure the integrity and accuracy of the data.
[0071] After generating the standard database in the implementation example, the data results need to be spatially validated and logically checked in this software environment to ensure that they are error-free.
[0072] like Figure 15 As shown, in the ArcGIS 3D view, the generated BIM pipeline model can be visualized, its attributes identified, and dynamically located.
[0073] The final output is an interactive BIM pipeline model generated in this 3D environment, realizing the transformation from non-standard design data to standardized, visualized, and analyzable digital assets.
[0074] The specific implementation process of this invention is described as follows: Import the source file containing the BIM municipal pipeline design data. You can select the source file path from the "Import from File Path" option. Importing can be done by selecting pipeline or pipe point data for a single discipline, or by importing all pipeline and pipe point data from all disciplines.
[0075] In the data files of the management project, each project corresponds to a set of data parameter files. Through the user import source file function, calculation formulas are pre-made, data is cleaned, and feature names are standardized and replaced to generate all the data in the project. Export a parameter overview in XLS format, import the ACCESS database processing file to generate a standard MDB database format, and finally import it into ArcGIS software to quickly generate a BIM pipeline model.
[0076] By selecting pipeline and pipe point data, identifying features, editing features, and converting features into graphics, a new BIM pipeline model can be generated.
[0077] S1. Based on the design drawings from the municipal survey and design, use the built-in "Export Pipeline Data to Excel" function of the design drawings to obtain the basic data source file. Set up the pipeline export scheme, including the column headers and column contents for pipeline data and node data in the table settings, such as: starting node number, ending node number, starting elevation, node coordinate X, node coordinate Y, etc.
[0078] S2. Open "Municipal Pipeline Database Processing System V1.0". The main interface of "Municipal Pipeline Database Processing System" will pop up. The main interface of the software consists of four main parts: import area, editing area, export area, and text navigation.
[0079] ①The Import Area button is No. 1 for importing source files.
[0080] ② The editing area consists of multiple interfaces, including nine sections: All Disciplines, Telecommunications, Power Supply, Water Supply, Green Water, Sewage, Rainwater, Reclaimed Water, and Function Description. The All Disciplines page includes six buttons: No. 2 Copy to Formula, No. 3 Data Organization - xx Municipal 12, No. 3 Data Organization - Zhongzi 13, No. 4 Replace Element Name, No. 5 Copy Formula to Text, and No. 6 One-Click Export.
[0081] The interface formats for each specialty are basically the same; taking the telecommunications specialty as an example, the telecommunications page includes nine buttons: No. 2 Telecommunications Pipeline Copy to Formula, No. 2 Telecommunications Pipeline Copy to Formula, xx Municipal 12, China Consulting 13, No. 4 Telecommunications Replace Element Name, No. 5 Telecommunications Pipeline Copy to Text, No. 5 Electrical Wire Pipeline Copy to Text, No. 6 Telecommunications Pipeline One-Click Export, and No. 6 Telecommunications Pipeline One-Click Export.
[0082] The feature description page includes two paragraphs. The first paragraph outlines the eight specific aspects of No.3 data processing. The second paragraph specifies the export location: root directory of drive D; and the export name: exported edited file (.xlsx).
[0083] ③ The export area button is No. 7, Export All.
[0084] ④ The text navigation section is located on the left side of the interface, including the first step of importing, the second step of selecting a major, the third to sixth steps of sequential buttons, and the seventh step of exporting. Its main function is to guide the user through the operation steps.
[0085] S3. Click the "Import Source File No. 1" button in the import area of the main interface to bring up the "Import Source File" interface. Click "Import File Path" and select the Excel file to import. Click "Import All". You can also select one if you only want to import pipeline data for a specific field, such as power supply pipelines. The software initializes the imported Excel file by specifying the workbook names of the source and target worksheets. It identifies the corresponding locations of the source and target files by traversing the cells. It includes the main function of querying all workbooks containing source and target files. A simple error reporting function is also included for easy checking, along with the main code for text boxes, buttons, etc.
[0086] S4. Click the "Copy No.2 Telecom Pipeline Points to Formulas" button in the main interface editing area. The software will automatically call the program to copy the contents of the workbook "Telecom Pipelines" in the Excel template to the workbook "Telecom Pipelines (with Formulas)". After the copying is complete, a "Copying Telecom Pipelines to Formulas Complete" prompt box will appear.
[0087] Before running the "Data Cleaning" function in the software, you must open the Excel file named "ddate" to read the data from the Excel file. Then, click "No3 Data Cleaning - xx Municipal 12" or "No3 Data Cleaning - Zhongzi 13" in the main interface editing area. The software program will automatically complete the eight steps of data cleaning in the Excel template: 1. Delete redundant formula data rows; 2. Multiply the decimal point by 100; 3. Convert four-digit numbers to three-digit numbers, i.e., replace numbers with two digits before the decimal point, such as 10.1 with 901; 22.1 with 821; and so on, numbered downwards from 9, 8, 7, etc. 4. dcode: xx Municipal is 12; Zhongzi is 13; 5. ddate: Measure the first road in the area, e.g., 20230620, then add 1 day for each subsequent road, e.g., 20230621, 20230622, etc.; 6. projectno: Combination N12 + 20230620 + _1; 7. Modify code names that do not conform to the standard; 8. Material needs to be modified. A "Replacement Completed" prompt box appears after one small program completes. A "Data Processing Completed" prompt box appears after all programs have finished running.
[0088] Based on the requirements analysis, the main functions of the processing module are "character splitting and combining", "number sorting", "batch replacement", "data assignment" and "generating standard codes".
[0089] ① Character splitting & combination function description: Automatically identify the node codes in the original data table according to "node attributes" and "node numbers", assign new node codes according to the specification requirements, and revise the original node numbers in the format of "#000".
[0090] ② Example description of number sorting function: For the code of the target row, you can manually select the number of decimal places to retain. For example, the coordinates in the coordinate (x,y) column are usually three decimal places, the elevation (h) column is usually two decimal places, the index map number (mapnumber) is usually one decimal place, and the modification date (ddate) is usually an integer. To ensure the ease of operation and the efficiency of system operation, the modification operation interface is also set in the workbook.
[0091] ③ Data Assignment: Taking the assignment of "ddate(design date)" as an example, set up objects for the "source file workbook" and the "target file workbook" respectively. Then, automatically search for matching items by traversing all contents of the fixed columns and complete the replacement work.
[0092] S6. Click the "No.4 Telecom Replace Feature Name" button in the main interface editing area. The software will then automatically replace the non-compliant feature names in the workbook "Telecom Management Points (with Formulas)" in the Excel template in batches. After the replacement is complete, a "Feature Name Replacement Complete" prompt box will appear.
[0093] S7. Click the "Copy No.5 Telecom Management Points to Text" button in the main interface editing area. The software will then automatically copy the columns containing formulas from the workbook "Telecom Management Points (with Formulas)" in the Excel template to plain text columns. After the copy is complete, a "Copying formulas to text for Telecom Management Points complete" prompt box will appear.
[0094] S8. Click the "No.6 Telecom Management Points One-Click Export" button in the main interface editing area. The software will automatically export the columns required by the database from the workbook "Telecom Management Points (with formulas)" in the Excel template to the workbook "Telecom Management Points" with one click. After the copy is complete, a "Telecom Management Points One-Click Export Completed" prompt box will appear.
[0095] S9. After all the data processing for each major is complete, click the "No.7 Export All" button in the export area of the main interface. The software will then automatically export all edited workbooks to the root directory of drive D as "Export Edited Files.xlsx".
[0096] S10. Open the ACCESS database template file, click on the preset software-automatically edited form, and use the form buttons to import data tables. Clicking the buttons for "Water Supply, Rainwater, Sewage, Green Space" and "Electricity, Communication" allows you to import all professional data tables. Depending on the different road data, you can also import data for a specific professional field for easy modification. After importing all 14 professional tables, a complete municipal pipeline database file will be generated.
[0097] S11. ArcMap Database Inspection: Visual verification of the database in ArcMap is essential and has yielded excellent results. Inspection can identify and correct errors and inconsistencies in the data, ensuring data quality and reliability. Data accuracy directly impacts analysis results; inspection can reduce errors caused by data issues and improve the credibility of the analysis. Accurate and complete data provides a solid foundation for decision-making, helping to make more scientific planning and management decisions. High-quality data can enhance user trust in the system and analysis results, increasing system utilization. The steps for inspecting a database in ArcMap are as follows: ① Connect to the database: Ensure that ArcMap is connected to the required database (such as File Geodatabase or Enterprise Geodatabase).
[0098] ② Check data integrity: Use the "Repair Geometry" tool to check and repair errors in the geometric data.
[0099] ③ View the attribute table: Right-click the layer and select "Open Attribute Table" to check if the data is complete and if the fields are correct.
[0100] ④ Run the spatial analysis tool: Use the "Check Geometry" tool to verify the validity of the geometric features.
[0101] ⑤ Check metadata: Review the layer's metadata to ensure that all information and data sources are up-to-date.
[0102] ⑥ Data backup: Back up the database regularly to prevent data loss.
[0103] S12. Visual dynamic positioning, model attribute identification, browsing, modification, and model searching in the 3D view. The pipeline model in the 3D view interface can be zoomed in, zoomed out, dragged, and rotated using the mouse. Additionally, to facilitate viewing the interior of the BIM pipeline model, the processing module also includes functions such as hiding and showing local pipeline points.
[0104] Of the above steps, steps S4 to S10 are the key steps in this project.
[0105] The function of running "Copy No.2 Telecom Pipeline Point to Formula" mentioned in step S4 belongs to the processing module, which can complete the copying of data in batches with one click.
[0106] This step automates the batch copying process by writing scripts, solving the problems that manual processing is not only time-consuming and laborious, but also prone to errors due to repetitive operations.
[0107] The function described in step S5, which involves running "No3 Data Organization - xx Municipal 12" or "No3 Data Organization - Zhongzi 13" to complete the eight data organization tasks with one click, belongs to the processing module. These tasks include deleting redundant data rows, standardizing data formats, standardizing data codes, entering dates, and standardizing material writing.
[0108] This step utilizes VBA programming technology to complete complex multi-stage operations commonly involved in Excel spreadsheet data processing. It involves format standardization, cross-sheet linkage, and batch calculations. By writing software programs to complete the entire multi-step data processing workflow, its core value lies in improved efficiency, guaranteed accuracy, and scenario adaptability, perfectly solving various pain points associated with manual processing.
[0109] The step S6, which involves running "No4 Telecom Replacement Element Name" to complete the batch replacement of non-compliant element names with one click, belongs to the processing module. It realizes the standardized replacement of element names in order to meet the element name standard requirements of the "Underground Pipeline Data Specification" DB1310 / T 233-2020.
[0110] The function described in step S7, "Copy No.5 Telecom Pipeline Point as Text," belongs to the processing module and completes the copying of data in batches with one click.
[0111] This step uses script programming to automate batch copying, effectively avoiding the problems of low efficiency and error-proneness of manual operation.
[0112] The function described in step S8, "One-click Export of No.6 Telecom Pipeline Points," belongs to the processing module and allows for the batch export of "telecom pipeline points" with a single click. This process is repeated to export pipelines and points for seven different water supply systems: power supply, water supply, greening water, sewage, rainwater, and greywater.
[0113] This step uses script programming to automate the batch export task, solving the dual problems of time consumption and errors that existed when relying on manual methods.
[0114] The function of running "No7 All Export" described in step S9 belongs to the processing module. After all disciplines have completed data processing, the data is exported for all disciplines.
[0115] This step uses script programming to perform lightweight processing on all data, extracting only the data that has been finally organized according to specifications and data rules, so that complete and standardized data can be exported.
[0116] The step S10, which involves using a database template file to run the functions of the form buttons "supply, rain, sewage, greening" and "electricity, communication", belongs to the processing module. This method imports the corresponding professional data tables and generates a complete municipal pipeline database file.
[0117] Taking the design of an underground pipeline project on Road XX in a certain city (please use "xxx", "A", "B", "C", or other alternatives for specific place names in the attached diagram and text) as an example. This project is a typical municipal road project, with a total road length of 1.4km and a width of 30m. The underground pipelines include seven specialized pipelines: telecommunications, power supply, water supply, greening water, sewage, rainwater, and reclaimed water.
[0118] Implementation Process 1: Run the fast version for all professions.
[0119] like Figure 4 As shown, based on the design drawings from the municipal survey and design, the original pipeline data file for this project was collected using the "Export Pipeline Data to Excel" function in the menu tools. Custom settings were then configured according to design requirements, such as... Figure 5 The "XX Municipal Engineering Institute Pipeline Export Scheme" shown above was used to complete an underground pipeline project for municipal roads in a certain area.
[0120] By launching the software "Municipal Pipeline Database Processing System V1.0" developed in this invention, you can enter the system's main interface. For example... Figure 6As shown, this interface is the "Main Interface of Municipal Pipeline Database Processing System (All Disciplines)," supporting batch processing of data from seven disciplines. The first step is to click "Import Source File No. 1" in the import area to open... Figure 9 The interface for importing source files is shown. By selecting the source file location under "Import by File Path" and then selecting "Import All," you can achieve unified import of data from all disciplines.
[0121] Before executing the processing module, an Excel file named "ddate" must be opened so that the system can read the date information within it. This file contains two columns of data: one for the location and the other for the corresponding date.
[0122] Then, click the buttons in the editing area in sequence to perform subsequent processing: Step 2: Click "No2 Copy to Formula" to copy the source data to the data column with the preset formula function.
[0123] Step 3: If this road was designed by xx Municipal Survey and Design, click “No3 Data Organization - xx Municipal 12”. This step automatically completes eight data organization tasks: ① Delete redundant formula data rows; ② Standardize decimal places (e.g., multiply by 100 for conversion); ③ Standardize professional code numbers (e.g., replace “10.1” with “901”, “22.1” with “821”, and number them downwards in the order of 9, 8, 7…); ④ Write the survey unit code (dcode): The code for xx Municipal is 12, and the survey unit code information in the field (if the survey unit is China Consulting, the code is 13 and should be substituted accordingly); ⑤ Write the date (ddate): According to the measurement order of the area, starting from the base date of the first road (e.g., 20230620), the date of each subsequent road increases by 1 day; ⑥ Generate project number (projectno): The combination format is “N12+20230620+_1”; ⑦ Correct non-standard code names; ⑧ Batch update materials (material). After each subroutine finishes running, a "Replacement Complete" message box will pop up; after all subroutines have finished executing, a "Data Processing Complete" message box will pop up.
[0124] Step 4: Click "No. 4 Replace Feature Names" to batch replace feature names and make them conform to the standard. After the replacement is complete, a "Replace Feature Names Complete" prompt box will pop up.
[0125] Step 5: Click "No.5 Copy as Text". The system will automatically convert all data columns with formulas in all workbooks of the Excel template into plain text values.
[0126] Step 6: Click "No. 6 One-Click Export" in the editing area. The software will automatically export all data columns required by the database from the Excel template workbook to a worksheet named "Plain Text". After the process is complete, the system will pop up a "One-Click Export Complete" prompt box.
[0127] Step 7: Click the "No.7 Export All" button in the export area. The software will automatically export the entire edited workbook file to the root directory of drive D, naming the file "Exported Edited Files.xlsx", and its content will be as follows: Figure 11 As shown.
[0128] like Figure 12 As shown, open the main interface of the ACCESS database template file, click on the software's preset automatic editing form, and use the buttons on the form such as "Give, Rain, Sewage, Greenery" and "Electricity, Communication" to import all professional data tables into the template. After all imports are complete, the template will be generated as shown. Figure 13 The database shown is a complete professional database that has been accurately organized according to specifications.
[0129] like Figure 14 As shown, database information is extracted from ArcGIS software for visual verification. The specific operations are performed in ArcMap: First, use the "Repair Geometry" tool to check and repair errors in the geometric data to ensure data integrity; next, right-click the layer and select "Open Attribute Table" to view the attribute table and check if the data is complete and the fields are correct; then, use the "Check Geometry" tool to verify the validity of the geometric features. In addition, the database should be backed up regularly to prevent data loss.
[0130] like Figure 15 As shown, database information in ArcGIS is converted into a 3D model. In the 3D view, the pipeline model can be visualized, dynamically located, its attributes identified, browsed, modified, and searched. The pipeline model in the 3D view can be zoomed in, zoomed out, dragged, and rotated using the mouse.
[0131] In addition, to facilitate user operation, the software also provides, for example Figure 7 The "Main Interface of Municipal Pipeline Database Processing System (Function Description)" shown in the image details the specific content included in data processing, as well as the location and naming rules for exported data.
[0132] Implementation Process Two: Single-Specialty Dedicated Version Operation: like Figure 3As shown, this block diagram provides a clear and intuitive graphical representation of the system's structure, data flow paths, and core business processes, which helps to facilitate understanding, communication, and system analysis and optimization.
[0133] like Figure 4 As shown, we enter the project data acquisition phase. Based on the municipal survey and design drawings, we use the "Export Pipeline Data to Excel" function provided in the menu tools of the "Glodon Pipeline 2022" software to collect the original pipeline data files for this project. Users can customize settings according to specific design requirements, such as... Figure 5 The "xx Municipal Institute Pipeline Export Scheme" shown above completes the export configuration for underground pipeline projects of municipal roads in a specific area.
[0134] Launch the "Municipal Pipeline Database Processing System V1.0" software developed in this invention. The system's main interface supports single-discipline data entry. Taking telecommunications as an example, enter... Figure 6 The image shows the "Main Interface of Municipal Pipeline Database Processing System (Telecommunications Professional)". First, click the "No.1 Import Source File" button in the import area to open the file as shown. Figure 9 The interface for importing source files is shown. You can select the source file location using "Import File Path". Taking power supply lines as an example, select "Power Supply Lines" and click "Import" to import data specific to a single discipline.
[0135] Entering the data management phase. For example... Figure 10 As shown, before running the software's "Data Cleaning" function, you must first open an Excel file named "ddate" so that the system can read the date sequence data in that file.
[0136] Then, click the buttons in the editing area in sequence: click "Copy No.2 Telecom Pipeline to Formula" and "Copy No.2 Telecom Line to Formula" to copy the telecom pipeline data from the source file to the data columns with preset formula functions, respectively, to prepare for subsequent automated processing.
[0137] Step 3: If the road data being processed is provided by xx Municipal Survey and Design Institute, click the "No.3 Data Processing - xx Municipal 12" button. This operation will automatically perform the following 8 data processing steps in sequence: ① Delete redundant formula data rows; ② Standardize decimal point handling (e.g., perform multiplication by 100 conversion); ③ Standardize professional codes: When a "four-digit to three-digit" conversion rule occurs (i.e., the original code has two decimal places), for example, replace "10.1" with "901", "22.1" with "821", and number them sequentially downwards in the order of 9, 8, 7... according to this rule; ④ Write the survey unit code (dcode): In this example, the code corresponding to xx Municipal is 12; ⑤ Write Date (ddate): Following the measurement order of the area, starting from the base date of the first road (e.g., 20230620), the date for each subsequent road increases by one day sequentially (i.e., 20230621, 20230622, etc.); ⑥ Generate Project No. (projectno): Generate using the format "N12+20230620+_1"; ⑦ Correct code names that do not conform to standard specifications; ⑧ Update Material Field: Batch substitute the survey unit code "12" into the relevant records. Similarly, if the survey unit is China Consulting, then substitute the code "13". During program execution, a "Replacement Completed" prompt box will pop up after each sub-item operation is completed; after all subroutines have been executed, a "Data Processing Completed" prompt box will pop up.
[0138] Step 4: Click the "No.4 Telecommunications Replace Element Name" button. The system will perform batch search and replacement of telecommunications-related element names to ensure they conform to the standard element names defined in the specifications. After this operation is completed, a "Element Name Replacement Completed" prompt box will pop up on the interface.
[0139] Step 5: Click the "Copy Telecom Pipeline Points as Text" and "Copy Telecom Lines as Text" buttons. The software will automatically copy all data columns with formula calculations from the "Telecom Pipeline Points (with Formulas)" and "Telecom Lines (with Formulas)" workbooks in the Excel template and convert them into plain text value columns. After the operation is complete, the interface will display "Copying formulas for Telecom Pipeline Points as Text Completed" and "Copying formulas for Telecom Lines as Text Completed" prompts respectively.
[0140] Step 6: Click the "One-Click Export of No. 6 Telecom Pipelines" and "One-Click Export of No. 6 Telecom Lines" buttons. The software will automatically export all the required data columns from the database in the "Telecom Pipelines (with Formulas)" workbook to the target workbooks "Telecom Pipelines" and "Telecom Lines" with one click. After the operation is complete, the interface will display "One-Click Export of Telecom Pipelines Completed" and "One-Click Export of Telecom Lines Completed" prompt boxes respectively.
[0141] Step 7: Click the "No.7 Export All" button in the export area. The software will automatically export the entire edited workbook file to the root directory of drive D, and name it "Exported Edited Files.xlsx". Its content will be as follows: Figure 11 As shown.
[0142] like Figure 12 As shown, open the main interface of the ACCESS database template file and click on the software's preset automatic editing form. Using the "Power, Telecommunications" and other buttons on the form, you can directly import telecommunications-related data tables into the database template.
[0143] like Figure 14 As shown, database information is extracted and visualized in ArcGIS software for verification. Specifically, in ArcMap: use the "Repair Geometry" tool to check and repair geometric data errors, ensuring data integrity; right-click the layer and select "Open Attribute Table" to view the attribute table and verify data integrity and field correctness; use the "Check Geometry" tool to verify the validity of geometric features. It is recommended to back up the database regularly to prevent data loss.
[0144] like Figure 15 As shown, database information in ArcGIS is converted into a 3D model. In the 3D view, the pipeline model can be visualized, dynamically located, its attributes identified, browsed, modified, and searched. The pipeline model in the 3D view can be zoomed in, zoomed out, dragged, and rotated using the mouse.
[0145] In summary, this invention obtains BIM municipal pipeline data, where each discipline includes multiple data items, to obtain the data items of BIM municipal pipelines. Finally, the data items are processed according to system formulas. By adopting this method, useful data can be extracted quickly, the processing efficiency of data items can be improved, and the accuracy of BIM municipal pipeline data can be guaranteed.
[0146] This invention implements a BIM municipal pipeline data processing system and method, involving data processing for seven professional pipelines: telecommunications, power supply, water supply, greening water, sewage, rainwater, and reclaimed water. It enables standardized data submission, element layering, attribute classification, and element coding for pipeline data from multiple disciplines. One-click import and export allow for the direct generation of BIM pipeline models from the database.
[0147] The coding principles for matching pipeline data obtained from municipal pipeline survey and design drawings differ significantly from the data items required by the municipal pipeline database in the standardized BIM platform, necessitating data correction.
[0148] The first aspect involves seven professional pipelines: telecommunications, power supply, water supply, greening water, sewage, rainwater, and reclaimed water. In the standardized BIM platform, the professional codes for municipal pipelines are DX (telecommunications), GD (power supply), SS (water supply), LS (greening water), WS (sewage), YS (rainwater), and ZS (reclaimed water). The professional codes used to obtain pipeline data information from municipal pipeline design drawings need to be replaced with standard codes.
[0149] The field information corresponding to the starting point number (s_point) and ending point number (e_point) in the pipeline data item and the pipe point number (p_no) in the pipe point data item needs to have its professional code and valid serial number extracted respectively.
[0150] Taking telecommunications as an example, the design data code for municipal pipelines is TX-1. Extract the professional code TX from Excel and extract the valid serial number 1. According to the standardized "Underground Pipeline Data Specification," this is a unique identifier. The coding principle is: pipeline code + detection unit code + date (8-digit year-month-day) + pipeline point serial number. The serial number is represented by four digits, with "0" used to replace any missing digits. Therefore, the pipeline point number for this telecommunications specialty is "DX12202211010001".
[0151] Using the software program MyGet in the system of this invention, the extraction of English letters from professional codes and the extraction of valid serial numbers are respectively realized.
[0152] Then, the VLOOKUP function is used to replace the professional code, and the REPT function is used to fill in the four-digit valid serial number.
[0153] The "detection unit code (dcode)" is implemented using the software program ReplaceDcode12 or ReplaceDcode13 in the system of this invention. The coding principle is to automatically fill in the code according to different detection units, such as 12 for the Municipal Institute and 13 for the China Consulting Institute.
[0154] The date (8-digit year-month-day) is achieved by using the software program ReplaceDdate in the system of this invention to read the detection dates of each road in ddate.xls.
[0155] Finally, the built-in merging function is used to merge the elements into a unique identifier with all elements according to the encoding principles.
[0156] In this way, by using the municipal pipeline design data code described in the system of the present invention, the required data items for the municipal pipeline database in the standardized BIM platform can be generated quickly and accurately.
[0157] In summary, this invention solves the problem of converting municipal pipeline design data from "non-standard" to "standard" efficiently, accurately, and automatically by creating a rule-driven, process-fixed dedicated software system. It directly outputs a standardized database that can be used for 3D visualization modeling, achieving a qualitative improvement in data processing efficiency and quality, and significantly enhancing the efficiency, accuracy, and direct usability of municipal pipeline data processing in BIM / CIM platforms.
[0158] It should be understood that the above description of the preferred embodiments is merely illustrative and not intended to limit the scope of protection of the present invention. Those skilled in the art, under the guidance of the present invention, can make various substitutions, modifications, or alterations without departing from the scope of protection defined by the appended claims. These include, but are not limited to, adjusting the execution order of the actions or steps recorded in the claims, operating in a different sequence or continuity than that shown in the drawings, or, where feasible, employing a multitasking or parallel processing method. All such embodiments fall within the scope of protection of the present invention.
Claims
1. A BIM municipal pipeline data processing system, characterized in that, include: The acquisition module is used to acquire and import original design data for municipal pipelines; A processing module, connected to the acquisition module, is used to perform automated standardization processing on the original design data. The processing module includes: The code specification unit is used to extract the original professional codes and serial numbers and convert them into standard professional codes according to a preset mapping relationship; Unit coding unit, used to generate standard unit codes based on probe unit information; The timing processing unit is used to read and process the probe date information from a preset data source. The unique identifier generation unit is used to integrate standard professional codes, standard unit codes, standardized date information and serial numbers to generate unique identifiers for pipelines and pipe points that conform to underground pipeline data specifications. The data standardization unit is used to unify data format, standardize element names, remove formula redundancy, and generate standard attribute data after standardization. A standard library generation module, connected to the processing module, is used to export the normalized standard attribute data and construct a standard spatial database that can be directly used for 3D modeling. The modeling module, connected to the standard library generation module, is used to automatically generate BIM municipal pipeline 3D models with complete attributes based on the standard spatial database.
2. The BIM municipal pipeline data processing system according to claim 1, characterized in that, The data warping unit is specifically used to perform at least one of the following automated operations: Standardize the decimal precision of coordinates, elevation, and burial depth; Batch replace non-standard feature names with standard feature names; Convert the formula calculation column into a pure numeric column; Remove redundant data rows and standardize field structures. Obtain the detection date information and increment the date according to preset rules.
3. The BIM municipal pipeline data processing system according to claim 1, characterized in that, The export unit is specifically used for: the time series processing unit is configured to: read the base date from an external date file and automatically increment the date for multiple road data according to preset rules.
4. The BIM municipal pipeline data processing system according to claim 1, characterized in that, The standard spatial database is a structured database that conforms to the specifications for municipal underground pipeline data and can be directly read by general GIS platforms.
5. The BIM municipal pipeline data processing system according to claim 1, characterized in that, The modeling module is configured to import a standard spatial database into a 3D GIS platform and generate a BIM pipeline model that supports spatial analysis through feature recognition and graphic conversion.
6. The BIM municipal pipeline data processing system according to claim 1, characterized in that, Also includes: The visualization and interaction module is used to perform 3D display, attribute query, spatial positioning and viewpoint transformation operations on the BIM pipeline 3D model.
7. The BIM municipal pipeline data processing system according to claim 1, characterized in that, The pipeline data shall include at least: starting point number, ending point number, burial depth, elevation, material, pipe diameter, ownership information, detection unit, and detection date; the pipe point data shall include at least: pipe point number, coordinates, ground elevation, features, appurtenances, and unique identifier.
8. A method for processing BIM municipal pipeline data, based on the system described in any one of claims 1-7, characterized in that, Includes the following steps: S1. Obtain and import the original design data of municipal pipelines; S2. Perform automated standardization processing on the original design data: Extract the original professional codes and serial numbers, and convert them into standard professional codes; Generate standard unit codes based on the detection unit information; read and standardize the detection date information from a preset data source; Integrate standard professional codes, standard unit codes, standard date information and serial numbers to generate unique identification codes for pipelines and pipe points that conform to the specifications; Standardize the data format, standardize the element names, and remove redundant formulas to obtain standardized attribute data after normalization. S3. Construct the standardized attribute data into a standard spatial database that can be directly used for 3D modeling; S4. Automatically generate a BIM 3D model of municipal pipelines with complete attributes based on the standard spatial database.
9. The method for processing BIM municipal pipeline data according to claim 8, characterized in that, Step S2 also includes: Load the raw data into the preset formula template for batch calculation; Perform data cleaning: remove redundant rows, standardize decimal precision, and standardize codes and material names; Batch replace non-standard feature names with standard feature names; Convert the formula column into a pure numeric column; Export data columns that meet the data entry requirements to the target data table with one click.
10. The method for processing BIM municipal pipeline data according to claim 9, characterized in that, Step S3 also includes: Export the standard attribute data as an intermediate table file, then import it into a preset database template to automatically generate a standard spatial database file. In addition, step S4 also includes: The standard spatial database is imported into the GIS platform, and through feature identification, editing, and graphic conversion, a BIM pipeline model that supports 3D visualization and spatial analysis is generated.