Cross-document migration method, device and equipment for wall node and storage medium

Abstract

The application discloses a cross-document migration method and device for a wall node, equipment and a storage medium, the method comprises the following steps: in response to the export instruction of the source wall node in the source BIM document, obtaining the source contour information of the source wall node and the source steel bar scheme information adopted by the source wall node, and associating and packaging the source contour information and the source steel bar scheme information to generate a node data packet; in response to the import instruction of importing the node data packet into the target wall node of the target BIM document, obtaining and analyzing the node data packet; obtaining the target contour information of the target wall node, and comparing the target contour information with the source contour information parsed from the node data packet; when the target contour information is consistent with the source contour information, generating a corresponding steel bar model on the target wall node according to the source steel bar scheme information parsed from the node data packet.

Description

Technical Field

[0001] This application relates to the field of computer-aided design technology, and in particular to a method, apparatus, device and storage medium for cross-document migration of wall nodes. Background Technology

[0002] In the application of Building Information Modeling (BIM) technology, wall joints, as key components of structural design, typically have complex geometric contours and dense rebar arrangements, making their refined design a persistent challenge in the industry. Compared to traditional 2D CAD design, while 3D BIM design offers advantages in information integrity, existing technologies still have significant shortcomings in the cross-project reuse of wall joints.

[0003] Currently, mainstream BIM structural design software generally adopts the following approach for handling wall details: when designers face the same wall outline in each new project, they need to redraw the geometry and manually place each rebar. This results in a large amount of repetitive work, and it is difficult to ensure the consistency of reinforcement design between different projects. This method, which relies entirely on manual repetitive operations, is not only inefficient, but also prone to design errors due to differences in human operation.

[0004] Therefore, how to achieve the overall migration and reuse of the geometric contours of wall nodes and the information on the configuration of reinforcing bars, so that nodes with the same structure can be directly called between different projects, has become a technical problem that urgently needs to be solved by those skilled in the art. Summary of the Invention

[0005] The purpose of this application is to provide a method, apparatus, device and storage medium for cross-document migration of wall nodes. This application realizes the overall safe migration of wall node outline and reinforcement, avoiding the labor consumption and misuse risks of repeated modeling and reinforcement.

[0006] According to one aspect of this application, a cross-document migration method for wall nodes is provided, the method comprising:

[0007] In response to the export command for the source wall node in the source BIM document, the source outline information of the source wall node and the source reinforcement scheme information adopted by the source wall node are obtained, and the source outline information and the source reinforcement scheme information are associated and encapsulated to generate a node data package;

[0008] In response to an import command to import the node data packet into the target wall node of the target BIM document, the node data packet is obtained and parsed;

[0009] Obtain the target contour information of the target wall node, and compare the target contour information with the source contour information parsed from the node data packet;

[0010] When the target contour information is consistent with the source contour information, a corresponding rebar model is generated on the target wall node according to the source rebar scheme information parsed from the node data packet.

[0011] Optionally, the step of obtaining the source contour information of the source wall node and the source reinforcement scheme information adopted by the source wall node, and associating and encapsulating the source contour information and the source reinforcement scheme information to generate a node data packet includes:

[0012] Obtain the family identifier of the source profile family used by the source wall node and the source profile parameter information instantiated based on the source profile family, and associate the family identifier of the source profile family and the source profile parameter information to form source profile information;

[0013] Obtain detailed information on the reinforcement details of each reinforcement element arranged in the source wall node to form source reinforcement scheme information;

[0014] Obtain the auxiliary information associated with the source wall node, wherein the auxiliary information includes at least one of the following: the view information to which the source wall node belongs, the annotation information associated with the source wall node, the offset of the reinforcing bar relative to the outline, and the display status of the auxiliary line;

[0015] The source contour information, the source reinforcement scheme information, the auxiliary information, and the relationships between each piece of information are serialized according to a preset data structure to generate a structured node data packet.

[0016] Optionally, obtaining the reinforcement details of each reinforcement element arranged in the source wall node to form source reinforcement scheme information further includes:

[0017] A global correlation search is performed on each rebar element in the source rebar scheme information to determine the style resource information referenced by each rebar element in the source BIM document; wherein the global correlation search includes at least one of the following: obtaining the source line style information used by the rebar element from the line style manager of the source BIM document, obtaining the source text style information used by the rebar element from the text style manager of the source BIM document, obtaining the source line type information used by the rebar element from the line type manager of the source BIM document, and obtaining the source material information used by the rebar element from the material manager of the source BIM document;

[0018] Analyze the reference relationship types between each rebar element and its corresponding style resource information, and set a corresponding copy strategy for each style resource information according to the reference relationship type. Specifically, when the reference relationship type is a strong dependency, a forced copy strategy is set for the corresponding style resource information, which requires that the style resource information be written into the target BIM document during import. When the reference relationship type is a weak dependency, a simplified copy strategy is set for the corresponding style resource information, which requires that the style resource information with the same name in the target BIM document be used first during import.

[0019] The style resource information and corresponding copy strategy of each rebar element are associated and stored in the source rebar scheme information.

[0020] Optionally, obtaining the target contour information of the target wall node and comparing the target contour information with the source contour information parsed from the node data packet includes:

[0021] Based on the family identifier and source profile parameter information of the source profile family parsed from the source profile information, the source profile geometry of the source wall node is determined.

[0022] Obtain the target outline geometry of the target wall node from the target BIM document;

[0023] The geometric dimensions of the target contour are compared with those of the source contour.

[0024] When the geometric dimensions of the target contour are inconsistent with the geometric dimensions of the source contour, it is determined that the target contour information is inconsistent with the source contour information, and the import process is terminated.

[0025] When the geometric dimensions of the target contour are consistent with those of the source contour, it is determined that the target contour information is consistent with the source contour information, and it is checked whether there is a target contour family in the family manager of the target BIM document that is consistent with the family identifier of the source contour family; if so, when the definition of the target contour family is inconsistent with the definition of the source contour family, a new identifier is generated for the source contour family, and the definition of the source contour family is written into the family manager of the target BIM document with the new identifier; if not, the definition of the source contour family is written into the family manager of the target BIM document with the family identifier of the source contour family.

[0026] Optionally, when the target contour information matches the source contour information, generating a corresponding rebar model on the target wall node according to the source rebar scheme information parsed from the node data packet includes:

[0027] The source reinforcement scheme information and the auxiliary information are parsed from the node data packet, and a corresponding reinforcement instance is created on the target wall node based on the auxiliary information and the reinforcement details of each reinforcement element in the source reinforcement scheme information;

[0028] Iterate through each rebar instance sequentially, and based on the target style resource information and target copy strategy corresponding to the currently iterated target rebar instance, perform the following conflict resolution operations:

[0029] If the target copy strategy is a forced copy strategy, then it checks whether there is a style resource with the same name as the target style resource information in the corresponding manager of the target BIM document; when there is a style resource with the same name and the same definition, the style resource with the same name in the target BIM document is directly used to assign to the target rebar instance; when there is a style resource with the same name but the definition is different, a new name is generated for the target style resource information, and the definition of the target style resource information is written into the corresponding manager of the target BIM document with the new name, and then the style resource written with the new name is assigned to the target rebar instance; when there is no style resource with the same name, the definition of the target style resource information is written into the corresponding manager of the target BIM document with the original name of the target style resource information, and the style resource written with the original name is assigned to the target rebar instance.

[0030] If the target copy strategy is a simplified copy strategy, then it is detected whether there is a style resource with the same name as the target style resource information in the corresponding manager of the target BIM document; when there is a style resource with the same name, the style resource with the same name in the target BIM document is directly used to assign to the target rebar instance; when there is no style resource with the same name, the definition of the target style resource information is written into the corresponding manager of the target BIM document with the original name of the target style resource information, and the style resource written with the original name is assigned to the target rebar instance.

[0031] Optionally, the step of detecting whether a target contour family exists in the family manager of the target BIM document that matches the family identifier of the source contour family; if so, then when the definition of the target contour family is inconsistent with the definition of the source contour family, a new identifier is generated for the source contour family, and the definition of the source contour family is written into the family manager of the target BIM document with the new identifier; if not, then the definition of the source contour family is written into the family manager of the target BIM document with the family identifier of the source contour family, including:

[0032] Instantiate a conflict detector and input the family identifier of the source profile family and the identifier information of the target BIM document into the conflict detector;

[0033] The conflict detector traverses the family manager of the target BIM document to detect whether there is a target profile family in the family manager that matches the family identifier of the source profile family.

[0034] When there is a target contour family with the same family identifier, the definition of the target contour family is obtained, and the definition of the source contour family is compared with the definition of the target contour family.

[0035] If the comparison result indicates that the two definitions are consistent, the conflict detector generates a conflict-free identifier and sends the conflict-free identifier to an import option configurator; in response to receiving the conflict-free identifier, the import option configurator generates an abandon import policy and instructs an element importer not to perform a write operation.

[0036] If the comparison result indicates that the two definitions are inconsistent, the conflict detector generates a conflict identification information and sends the conflict identification information to the import option configurator; in response to receiving the conflict identification information, the import option configurator generates a new identifier for the source contour family according to the preset conflict handling rules and sends the new identifier to the element importer; the element importer writes the definition of the source contour family with the new identifier into the family manager of the target BIM document;

[0037] When no target contour family with the same family identifier does not exist, the conflict detector returns a conflict-free identifier to the import option configurator; in response to receiving the conflict-free identifier, the import option configurator generates a direct import strategy and sends the family identifier of the source contour family to the element importer; the element importer writes the definition of the source contour family into the family manager of the target BIM document using the family identifier of the source contour family.

[0038] The element importer returns the writing result information after the writing operation is completed.

[0039] To achieve the above objectives, this application also provides a cross-document migration device for wall nodes, the device comprising:

[0040] The export module is used to respond to the export command for the source wall node in the source BIM document, obtain the source outline information of the source wall node and the source reinforcement scheme information adopted by the source wall node, and associate and encapsulate the source outline information and the source reinforcement scheme information to generate a node data package.

[0041] The parsing module is used to obtain and parse the node data packet in response to an import instruction that imports the node data packet into the target wall node of the target BIM document;

[0042] The comparison module is used to obtain the target contour information of the target wall node and compare the target contour information with the source contour information parsed from the node data packet;

[0043] The import module is used to generate a corresponding rebar model on the target wall node according to the source rebar scheme information parsed from the node data packet when the target contour information is consistent with the source contour information.

[0044] Optionally, the export module is used for:

[0045] Obtain the family identifier of the source profile family used by the source wall node and the source profile parameter information instantiated based on the source profile family, and associate the family identifier of the source profile family and the source profile parameter information to form source profile information;

[0046] Obtain detailed information on the reinforcement details of each reinforcement element arranged in the source wall node to form source reinforcement scheme information;

[0047] Obtain the auxiliary information associated with the source wall node, wherein the auxiliary information includes at least one of the following: the view information to which the source wall node belongs, the annotation information associated with the source wall node, the offset of the reinforcing bar relative to the outline, and the display status of the auxiliary line;

[0048] The source contour information, the source reinforcement scheme information, the auxiliary information, and the relationships between each piece of information are serialized according to a preset data structure to generate a structured node data packet.

[0049] To achieve the above objectives, this application also provides a computer device, which specifically includes: a memory, a processor, and a computer program stored in the memory and executable on the processor, wherein the processor executes the computer program to implement the steps of the cross-document migration method for wall nodes described above.

[0050] To achieve the above objectives, this application also provides a computer-readable storage medium having a computer program stored thereon, which, when executed by a processor, implements the steps of the cross-document migration method for wall nodes described above.

[0051] This application provides a method, apparatus, device, and storage medium for cross-document migration of wall nodes. By associating and encapsulating the contour information of the source wall node with the reinforcement scheme information to form a node data package, it achieves the overall packaging and cross-document migration of the geometric shape and internal reinforcement design of the wall node. When importing into the target document, a mandatory geometric comparison is first performed between the contour of the target wall node and the source contour. Only when they are completely consistent is the source reinforcement scheme applied to the target node to generate the reinforcement model. This mechanism fundamentally solves the inefficiency problem of repeatedly modeling and reinforcing wall nodes in different projects in existing technologies, significantly reducing the repetitive work of designers. Simultaneously, through mandatory contour consistency verification, it effectively avoids design errors caused by applying reinforcement schemes due to contour mismatch, ensuring the consistency and accuracy of the reinforcement design of the same wall node in different BIM documents. Attached Figure Description

[0052] 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 scope of this application. Furthermore, the same reference numerals denote the same parts throughout the drawings. In the drawings:

[0053] Figure 1 This is a schematic diagram of an optional process for cross-document migration of wall nodes provided in Embodiment 1;

[0054] Figure 2 This is a schematic diagram of an optional component structure of the cross-document migration device for wall nodes provided in Embodiment 2;

[0055] Figure 3 This is a schematic diagram of an optional hardware structure for the computer device provided in Embodiment 3. Detailed Implementation

[0056] To make the objectives, technical solutions, and advantages of this application clearer, the following detailed description is provided in conjunction with the accompanying drawings and embodiments. It should be understood that the specific embodiments described herein are merely illustrative and not intended to limit the scope of this application. All other embodiments obtained by those skilled in the art based on the embodiments in this application without inventive effort are within the scope of protection of this application.

[0057] Example 1

[0058] This application provides a cross-document migration method for wall nodes, such as... Figure 1 As shown, the method specifically includes the following steps:

[0059] Step S101: In response to the export command for the source wall node in the source BIM document, obtain the source outline information of the source wall node and the source reinforcement scheme information adopted by the source wall node, and associate and encapsulate the source outline information and the source reinforcement scheme information to generate a node data package.

[0060] The source contour information includes at least the geometric dimensions and contour style information of the source wall node (e.g., appearance attributes such as line type, color, and line width of the contour line). It may also include the contour family information used to generate the source wall node, and lofting-related parameters used to construct the wall node contour (e.g., dimensional parameters such as wall thickness, cantilever length, and corner angle). The source contour information can completely characterize the geometric contour features of the source wall node. Furthermore, the source reinforcement scheme information includes information on all the reinforcement bars arranged in the source wall node, including but not limited to the arrangement position, geometric dimensions, specifications, and material properties of each reinforcement bar. The source reinforcement scheme information can completely reflect the reinforcement configuration of the source wall node.

[0061] In this embodiment, after obtaining the source contour information and the source reinforcement scheme information, these two types of information are associated and encapsulated, and a binding relationship is formed between them. A node data packet is then generated based on this binding relationship. Specifically, the node data packet is a structured data packet, and its storage format can be pre-specified by the user, for example, using the ".gqmd" format. This format can completely store the associated source contour information and the source reinforcement scheme information, achieving integrated storage and migration of the two types of information.

[0062] Step S102: In response to the import instruction to import the node data packet into the target wall node of the target BIM document, obtain the node data packet and parse it.

[0063] In this embodiment, when a user selects a completed wall node (i.e., the target wall node) in the target BIM document and initiates an import command for that node, in response to the import command, the node data package, which has been pre-exported from the source BIM document, is first retrieved. Subsequently, the node data package is parsed, restoring the structured data stored within it into a memory object that can be recognized and manipulated by a computer. This extracts the source outline information, source reinforcement scheme information, and the relationship between them, providing a data foundation for subsequent comparison and application steps.

[0064] Step S103: Obtain the target contour information of the target wall node, and compare the target contour information with the source contour information parsed from the node data packet.

[0065] In this embodiment, the geometric description data of the target wall node selected by the user is obtained from the current target BIM document, serving as the target contour information. The target contour information fully describes the geometric shape of the target wall node. Subsequently, the source contour information parsed from the node data packet in step S102 is compared and analyzed with the obtained target contour information to determine whether their geometric features match. This comparison step is a preliminary verification to ensure the safety of subsequent rebar reuse.

[0066] Step S104: When the target contour information is consistent with the source contour information, generate the corresponding rebar model on the target wall node according to the source rebar scheme information parsed from the node data packet.

[0067] In this embodiment, if the comparison result of step S103 indicates that the geometric features of the target contour information are completely consistent with those of the source contour information, then it is determined that the current target wall node has the conditions to safely receive the source reinforcement scheme. Under this premise, based on the source reinforcement scheme information parsed from the node data packet in step S102, which contains the complete design data of all reinforcements in the source wall node, a corresponding reinforcement instance is automatically created on the target wall node, thereby generating a complete reinforcement model and completing the cross-document migration of wall node data from the source document to the target document.

[0068] In this embodiment, by associating and encapsulating the contour information of the source wall node with the reinforcement scheme information to form a node data package, the overall packaging and cross-document migration of the wall node geometry and internal reinforcement design are realized. When importing into the target document, a mandatory geometric comparison is first performed between the target wall node's contour and the source contour. Only when they are completely identical is the source reinforcement scheme applied to the target node to generate the reinforcement model. This mechanism fundamentally solves the inefficiency problem of repeatedly modeling and reinforcing wall nodes in different projects in existing technologies, significantly reducing the repetitive work of designers. Simultaneously, through mandatory contour consistency verification, design errors caused by applying reinforcement schemes due to contour mismatch are effectively avoided, ensuring the consistency and accuracy of the reinforcement design for the same wall node in different BIM documents.

[0069] Specifically, step S101, which involves obtaining the source contour information of the source wall node and the source reinforcement scheme information used by the source wall node, and associating and encapsulating the source contour information and the source reinforcement scheme information to generate a node data packet, includes the following steps:

[0070] Step A1: Obtain the family identifier of the source profile family used by the source wall node and the source profile parameter information instantiated based on the source profile family, and associate the family identifier of the source profile family and the source profile parameter information to form source profile information.

[0071] In this context, a profile family refers to a reusable parametric template used to define the cross-sectional shape of a wall node. Essentially, it's a type of geometric definition unit stored in a family library, such as an L-shaped corner profile family or a T-shaped node profile family. These templates contain several adjustable parameters to adapt to different design scenarios. Profile parameter information refers to the specific parameter values ​​assigned to the profile family when it's instantiated at a particular wall node. Examples include the wall thickness, the extension length of the cantilever slab, and the angle of the corner. These parameter values ​​determine the final precise geometric shape of the node. In this step, by obtaining the unique identifier of the source profile family and the specific profile parameter information used when instantiating it at the source wall node, and storing these two together, source profile information that completely describes the geometric characteristics of the source wall node is formed, providing an accurate geometric data foundation for subsequent encapsulation and reuse.

[0072] Step A2: Obtain the reinforcement details of each reinforcement element arranged in the source wall node to form the source reinforcement scheme information.

[0073] Among these, the rebar details are the fundamental unit constituting the source rebar scheme information, used to fully describe the design attributes of each rebar. Specifically, for each rebar arranged in the source wall node, its rebar details include at least the rebar's geometric parameters (such as diameter, length, bending angle, spatial positioning coordinates or relative positional relationship with the outline) and material properties (such as rebar grade and type). This information collectively defines the specific shape and material of each rebar in the wall node, providing accurate data for subsequently reconstructing the same rebar configuration on the target wall node.

[0074] It should also be noted that wall joints typically involve the intersection of adjacent walls, floor slabs, beams, and other components. The internal reinforcing bars are not isolated but form complex spatial topological relationships with surrounding components. For example, horizontal reinforcing bars at corners need to be bent and extended into adjacent walls for anchorage, additional reinforcing bars in the core area of ​​the joint need to form specific lap relationships with the main reinforcing bars, and vertical reinforcing bars may penetrate floor slabs and anchor into the walls below. Therefore, in the process of obtaining detailed information on reinforcing bars, in addition to recording the geometric parameters (diameter, length, bending angle) and material properties (grade, model) of each reinforcing bar, it is also necessary to capture the host association information of each reinforcing bar in the source wall joint through spatial semantic analysis algorithms. This host association information includes at least: the structural component type identifier to which the reinforcing bar is attached (such as belonging to a certain wall, floor slab, or core area of ​​the joint), the spatial interference relationship between the reinforcing bar and adjacent components (such as the specific location coordinates of the interface between components), and the anchorage direction and spatial range of the lap area of ​​the reinforcing bar within the joint. This process ensures that the exported source reinforcement scheme information not only includes the static properties of the reinforcement, but also solidifies its dynamic spatial constraints in complex wall joints, providing a complete data foundation for the subsequent adaptive arrangement of reinforcement in the target document.

[0075] Step A3: Obtain the auxiliary information associated with the source wall node, wherein the auxiliary information includes at least one of the following: the view information to which the source wall node belongs, the annotation information associated with the source wall node, the offset of the reinforcing bar relative to the outline, and the display status of the auxiliary lines.

[0076] The ancillary information consists of a set of environmental attributes of the source wall node in the source BIM document, used to reconstruct the complete design context of the node in the target BIM document. Specifically, view information refers to the view type or view identifier of the source wall node in the source BIM document; for example, the node originates from a specific structural detail or 3D view. This information is used to automatically locate the view environment to which the node belongs in the target document. The offset of the rebar relative to the contour refers to the distance parameter of the rebar, either as a whole or locally, relative to the contour reference boundary; for example, the thickness of the rebar protective layer or the distance between the rebar centerline and the contour edge. This parameter directly affects the positioning accuracy of the rebar and the structural safety. The auxiliary line display status is a Boolean flag used to indicate whether auxiliary lines (such as positioning lines or reference lines) are displayed in the source wall node. This status information is used to maintain the consistency of auxiliary line display in the target document, facilitating subsequent editing and verification.

[0077] Step A4: Serialize the source contour information, the source reinforcement scheme information, the auxiliary information, and the relationships between each piece of information according to a preset data structure to generate a structured node data packet.

[0078] In this embodiment, a three-level association mapping structure is first constructed. The first level is the root node of the source contour information, using the family identifier of the source contour family as the unique index key. The second level is the reinforcement scheme branch node, which establishes a spatial position mapping relationship between the reinforcement details of each reinforcement element and the source contour parameter information, anchoring the reinforcement information to the specific geometric position of the contour. The third level is the auxiliary information child node, which establishes exclusive associations between auxiliary information such as view information and annotation information and the root node and branch node, respectively, so that the offset is bound to the corresponding reinforcement element and the view information is bound to the contour root node. Subsequently, according to this three-level association mapping structure, a matching tree data structure is preset, and the source contour information, source reinforcement scheme information, and auxiliary information are entered hierarchically. At the same time, the association relationship between each level is converted into structured mapping labels and embedded in the fields of the corresponding information. Finally, the tree-like data structure is serialized, and the numerical and character data of various types of information are encoded and fused with the associated mapping labels. This ensures that the data package not only stores the original data of various types of information, but also solidifies the inherent association logic between information. Ultimately, a structured node data package that can be directly parsed and can completely restore the information relationship is generated, ensuring that after the data package is parsed, various types of information can still maintain the same association state as in the source BIM document.

[0079] Through steps A1 to A4 above, the technical problem of how to fully capture and encapsulate the geometric shape, internal reinforcement, and design environment information of wall node data during export is solved. This is achieved by obtaining the family identifier and instantiation parameters of the contour family to form source contour information, obtaining the geometric and material properties of each rebar to form source rebar scheme information, and adding auxiliary information such as views, annotations, offsets, and auxiliary line status. Then, the above information and its relationships are serialized in a structured manner to generate a node data package containing complete design elements. This achieves the technical effect of establishing a strong binding relationship between geometric contours and rebar configuration during the export stage, fully preserving the node design context. This provides a complete, clearly structured, and accurately parsable data foundation for subsequent cross-document migration, ensuring that the full design intent of the source wall nodes can be efficiently restored during migration.

[0080] Furthermore, step A2, which involves obtaining the reinforcement details of each reinforcement element arranged in the source wall node to form source reinforcement scheme information, also includes:

[0081] Step A21: Perform a global association search on each rebar element in the source rebar scheme information to determine the style resource information referenced by each rebar element in the source BIM document; wherein, the global association search includes at least one of the following: obtaining the source line style information used by the rebar element from the line style manager of the source BIM document, obtaining the source text style information used by the rebar element from the text style manager of the source BIM document, obtaining the source line type information used by the rebar element from the line type manager of the source BIM document, and obtaining the source material information used by the rebar element from the material manager of the source BIM document.

[0082] In this embodiment, starting with each rebar element, a global correlation search is performed in the source BIM document, traversing all external resources that the rebar element depends on, thereby identifying and extracting style resource information related to the visual appearance and physical definition of the rebar. This style resource information includes, but is not limited to: line style information (such as line color and line width), text style information (such as font and font height), line type information (such as solid lines and dashed lines), and material information (such as steel appearance and fill pattern). This ensures that the display and physical properties of the rebar can be completely captured, providing data support for subsequently restoring the original appearance of the rebar in the target document.

[0083] Step A22: Analyze the reference relationship type between each rebar element and its corresponding style resource information, and set a corresponding copy strategy for each style resource information according to the reference relationship type; wherein, when the reference relationship type is a strong dependency, a forced copy strategy is set for the corresponding style resource information, which requires that the style resource information be written into the target BIM document during import; when the reference relationship type is a weak dependency, a simplified copy strategy is set for the corresponding style resource information, which requires that the style resource information with the same name in the target BIM document be used first during import.

[0084] In this embodiment, the reference relationship type between each rebar element and the style resource information it references is first analyzed. This reference relationship type is used to characterize whether the absence of style resources will lead to damage to the structural function or core definition of the rebar element. When the reference relationship type is determined to be a strong dependency, it means that the style resource is an indispensable component of the rebar element. For example, the material definition or specific line type of the rebar may be bound to its structural identity. In this case, a forced copy strategy is set for the style resource information to ensure that the complete definition of the style resource can be written into the target BIM document during import, avoiding distortion of rebar information due to missing styles. When the reference relationship type is determined to be a weak dependency, it means that the style resource mainly affects the visual appearance of the rebar rather than its core definition. For example, the text style used for rebar annotation. In this case, a simplified copy strategy is set for the style resource to prioritize matching existing style resources with the same name in the target BIM document during import. In addition, the specific execution logic of the forced copy strategy and the simplified copy strategy will be described in detail in the relevant steps of the import stage later.

[0085] Step A23: Store the style resource information and corresponding copy strategy of each rebar element in the source rebar scheme information.

[0086] Steps A21 to A23 above resolve the technical issue that the style definitions (such as line type, text style, and material) of rebar elements cannot be migrated along with the rebar details when exporting wall nodes. Existing technologies only record the geometric and material properties of the rebar, ignoring the style resources the rebar relies on in the source BIM document, leading to abnormal rebar display or discrepancies with the original design after import. By performing a global association search on each rebar element during the export phase, actively capturing its referenced style resource information, and pre-setting differentiated copy strategies for each style resource based on the strength of the reference relationship, the following beneficial effects are achieved: Firstly, it ensures that style resources crucial to the rebar display effect can be completely captured and migrated along with the node data package; secondly, by distinguishing between strong and weak dependencies, it provides an intelligent processing basis for the subsequent import phase. This solution completes the identification of style resources and strategy pre-setting during the export phase, laying a data foundation for efficiently and accurately restoring the original design intent of the rebar in the target document.

[0087] Specifically, step S103, which involves obtaining the target contour information of the target wall node and comparing it with the source contour information parsed from the node data packet, includes the following steps:

[0088] Step B1: Determine the source profile geometry of the source wall node based on the family identifier and source profile parameter information of the source profile family parsed from the source profile information.

[0089] By substituting the source contour parameter information into the geometric definition of the source contour family, the complete source contour geometric dimensions of the source wall node can be determined through parametric calculation or by directly reading the instantiation results.

[0090] Step B2: Obtain the target outline geometry of the target wall node from the target BIM document.

[0091] Since the target wall nodes have already been drawn in the target BIM document, the outline geometry of the target wall nodes can be read directly from the database or object properties of the target BIM document without the need for additional calculations or derivations.

[0092] Step B3: Compare the geometric dimensions of the target contour with the geometric dimensions of the source contour.

[0093] Step B4: When the geometric dimensions of the target contour are inconsistent with the geometric dimensions of the source contour, determine that the target contour information is inconsistent with the source contour information, and terminate the import process; or,

[0094] When the geometric dimensions of the target contour are consistent with those of the source contour, it is determined that the target contour information is consistent with the source contour information, and it is checked whether there is a target contour family in the family manager of the target BIM document that is consistent with the family identifier of the source contour family; if so, when the definition of the target contour family is inconsistent with the definition of the source contour family, a new identifier is generated for the source contour family, and the definition of the source contour family is written into the family manager of the target BIM document with the new identifier; if not, the definition of the source contour family is written into the family manager of the target BIM document with the family identifier of the source contour family.

[0095] In this embodiment, the target wall node may use a contour family with the same name as the source contour family but a different definition. Although the same geometric dimensions can be temporarily obtained through parameter adjustment, the underlying definition of the target contour family is inconsistent with that of the source contour family. If it is directly used, the current node will lose its association with the source design intent during subsequent editing or family parameterization adjustments. To solve this technical problem, after the geometric dimensions are compared, the system further checks whether there is a target contour family with the same identifier as the source contour family in the family manager of the target BIM document. When there is a target contour family with the same identifier but a different definition, it means that there is already a contour family with the same name in the target document but a different substance. If it is directly overwritten, it will destroy the original design of the target document. If it is abandoned, the complete definition of the source contour family cannot be introduced. Therefore, the system generates a new identifier for the source contour family and writes its definition into the family manager with the new identifier. This avoids naming conflicts with existing resources and introduces the complete definition of the source contour family into the target document, providing a standardized resource for creating new instances using the contour family in the future. When there is no target contour family with the same identifier, it can be written directly with the original identifier, ensuring that the definition of the source contour family is completely preserved in the target document. This approach achieves two effects: on the one hand, although the current target wall node uses the original outline instance, the source outline family has been stored as an independent resource in the family library, laying the foundation for future reuse; on the other hand, resource conflicts are avoided by dynamically adjusting the identifier, maintaining the integrity and stability of the original data of the target document.

[0096] Preferably, in step B4, detecting whether a target contour family exists in the family manager of the target BIM document that matches the family identifier of the source contour family; if yes, then when the definition of the target contour family is inconsistent with the definition of the source contour family, a new identifier is generated for the source contour family, and the definition of the source contour family is written into the family manager of the target BIM document with the new identifier; if no, then the definition of the source contour family is written into the family manager of the target BIM document with the family identifier of the source contour family, specifically including:

[0097] Step B41: Instantiate a conflict detector and input the family identifier of the source profile family and the identifier information of the target BIM document into the conflict detector;

[0098] Step B42: Traverse the family manager of the target BIM document through the conflict detector to detect whether there is a target profile family in the family manager that matches the family identifier of the source profile family;

[0099] Step B43: When there is a target contour family with the same family identifier, obtain the definition of the target contour family and compare the definition of the source contour family with the definition of the target contour family;

[0100] If the comparison result indicates that the two definitions are consistent, the conflict detector generates a conflict-free identifier and sends the conflict-free identifier to an import option configurator; in response to receiving the conflict-free identifier, the import option configurator generates an abandon import strategy and instructs an element importer not to perform a write operation, and directly adopts the target contour family already in the target BIM document.

[0101] If the comparison result indicates that the two definitions are inconsistent, the conflict detector generates a conflict identification information and sends the conflict identification information to the import option configurator; in response to receiving the conflict identification information, the import option configurator generates a new identifier for the source contour family according to the preset conflict handling rules and sends the new identifier to the element importer; the element importer writes the definition of the source contour family with the new identifier into the family manager of the target BIM document;

[0102] Step B44: When no target contour family with the same family identifier exists, the conflict detector returns a conflict-free identifier to the import option configurator; in response to receiving the conflict-free identifier, the import option configurator generates a direct import strategy and sends the family identifier of the source contour family to the element importer; the element importer writes the definition of the source contour family into the family manager of the target BIM document using the family identifier of the source contour family.

[0103] Step B45: After the element importer completes the write operation, it returns the write result information.

[0104] In this embodiment, by introducing three dedicated components—a conflict detector, an import option configurator, and an element importer—the handling of contour family resource conflicts is automated and intelligent. The conflict detector accurately identifies whether contour families with the same name or definition exist in the target document, avoiding the tediousness and oversight of manual searching. The import option configurator dynamically generates differentiated import strategies (abandon import, generate a new identifier for import, or import directly) based on the detection results, ensuring the accuracy and consistency of decisions. The element importer executes specific write operations according to the configurator's instructions, guaranteeing the standardization and reliability of resource import. Working together, these three components automatically resolve contour family naming conflicts and definition inconsistencies without manual intervention. This protects the integrity of the original resources in the target document and ensures that source contour families can be imported in an appropriate manner, providing a standardized resource foundation for subsequent reuse.

[0105] Furthermore, in step S104, when the target contour information matches the source contour information, a corresponding rebar model is generated on the target wall node according to the source rebar scheme information parsed from the node data packet. This specifically includes:

[0106] Step C1: Parse the source reinforcement scheme information and the auxiliary information from the node data packet, and create a corresponding reinforcement instance on the target wall node based on the auxiliary information and the reinforcement details of each reinforcement element in the source reinforcement scheme information.

[0107] Step C2: Iterate through each rebar instance sequentially, and based on the target style resource information and target copy strategy corresponding to the currently iterated target rebar instance, perform the following conflict resolution operations:

[0108] If the target copy strategy is a forced copy strategy, then it checks whether there is a style resource with the same name as the target style resource information in the corresponding manager of the target BIM document; when there is a style resource with the same name and the same definition, the style resource with the same name in the target BIM document is directly used to assign to the target rebar instance; when there is a style resource with the same name but the definition is different, a new name is generated for the target style resource information, and the definition of the target style resource information is written into the corresponding manager of the target BIM document with the new name, and then the style resource written with the new name is assigned to the target rebar instance; when there is no style resource with the same name, the definition of the target style resource information is written into the corresponding manager of the target BIM document with the original name of the target style resource information, and the style resource written with the original name is assigned to the target rebar instance.

[0109] If the target copy strategy is a simplified copy strategy, then it is detected whether there is a style resource with the same name as the target style resource information in the corresponding manager of the target BIM document; when there is a style resource with the same name, the style resource with the same name in the target BIM document is directly used to assign to the target rebar instance; when there is no style resource with the same name, the definition of the target style resource information is written into the corresponding manager of the target BIM document with the original name of the target style resource information, and the style resource written with the original name is assigned to the target rebar instance.

[0110] In this embodiment, when a style resource of a rebar element is marked with a forced copy strategy, it means that the style is crucial to the core display or structural definition of the rebar and must be accurately presented after import. Taking the line style of the rebar element as an example, the system first checks whether a line style with the same name as the source line style used by the rebar exists in the line style manager of the target BIM document. If a line style with the same name exists and their definitions (such as color, line width, and line type) are completely identical, the existing line style in the target BIM document is directly used and assigned to the current rebar instance. If a line style with the same name exists but the definition is inconsistent, a new name is generated for the source line style (such as adding a suffix to the original name), and then the complete definition of the source line style is written to the line style manager of the target BIM document with the new name. Finally, the newly written line style is assigned to the rebar instance. If a line style with the same name does not exist in the target document, the complete definition of the source line style is directly written to the target BIM document with its original name, and the line style is assigned to the rebar instance. This process ensures that the style resource corresponding to the forced copy strategy can be correctly applied to the rebar instance regardless of whether there is a conflict in the target BIM document, thereby completely restoring the display effect of the source rebar.

[0111] Furthermore, when a style resource for a rebar element is marked as a simplified copy strategy, it means that the style primarily affects the visual appearance of the rebar rather than its core definition. Therefore, during import, compatibility with existing resources in the target BIM document should be prioritized. Taking the text style used for rebar annotations as an example, the system first checks if a text style with the same name as the source text style used by the rebar exists in the target BIM document's text style manager. If a text style with the same name exists, regardless of whether its definition (such as font, font height, and aspect ratio) is completely consistent with the source text style, the existing text style in the target BIM document is directly adopted and assigned to the current rebar instance to maintain the consistency of style usage in the target document and reduce redundant resource imports. Only when a text style with the same name does not exist in the target BIM document is the complete definition of the source text style written to the target document's text style manager with its original name, and the style assigned to the rebar instance. This strategy maximizes the reuse of style resources in the target document while ensuring the basic readability of the rebar annotations.

[0112] It should be noted that the forced copy strategy prioritizes "ensuring complete restoration of the source style." Even when the target BIM document contains style resources with the same name but different definitions, it insists on importing the source style completely with the new name to ensure that the core display attributes of the reinforcement are completely consistent with the original design. The simplified copy strategy, on the other hand, prioritizes "prioritizing compatibility with existing resources in the target document." It directly uses any style resource with the same name as it exists, and only imports the source style when it is completely missing. The technical problem that the two copy strategies solve is that during cross-document migration, reinforcement style resources may have a strong binding relationship with their structural definitions (such as material or specific line type), or they may only have a weak relationship at the visual level (such as annotation font). If a unified processing logic is used, either the forced import of all styles will lead to redundancy and naming conflicts in the target document resources, or excessive compatibility will lead to the loss of strongly dependent styles and distortion of reinforcement display. By distinguishing between strong and weak dependencies and pre-setting differentiated copy strategies, the following technical effects were achieved: On the one hand, it ensured that style resources strongly related to the core definition of rebar could be completely preserved and accurately restored, maintaining the rigor of structural design; on the other hand, it achieved intelligent local compatibility for weakly related style resources, minimizing unnecessary style resource imports and naming conflicts, and improving the resource utilization efficiency of the target document while ensuring the display effect of rebar.

[0113] Preferably, step C1, which involves creating a corresponding rebar instance on the target wall node based on the supplementary information and the rebar details of each rebar element in the source rebar scheme information, specifically includes:

[0114] Step C11: Parse the rebar type identifier, geometric parameter information, and host association information of each rebar element from the source rebar scheme information; wherein, the host association information is used to characterize the structural member type to which the rebar element is attached in the source BIM document and its spatial constraint relationship with adjacent members;

[0115] Step C12: Parse the view information to which the source wall node belongs, the annotation information associated with the source wall node, the offset of the reinforcing bar relative to the outline, and the display status of the auxiliary lines from the attached information;

[0116] Step C13: Construct a topological relationship diagram of the surrounding components of the target wall node. The topological relationship diagram of the surrounding components includes at least the identification information, geometric boundaries, and spatial occupancy areas of the target wall node and adjacent structural components that have physical connections or spatial interference with the target wall node.

[0117] Step C14: Perform spatial semantic matching between the host association information of each rebar element and the topology diagram of the surrounding components to determine the target host component of the rebar element in the target BIM document;

[0118] Step C15: When the spatial semantic matching is successful, based on the geometric boundary of the target host component, the geometric parameter information of the reinforcing bar element, and the offset of the reinforcing bar relative to the contour, calculate the adaptive positioning parameters of the reinforcing bar element within the target host component. The adaptive positioning parameters include the starting coordinates, ending coordinates, bending point coordinates, and the net distance between the reinforcing bar and the boundary of the target host component; or,

[0119] When the spatial semantic matching fails, all candidate host components in the target BIM document that match the host association information of the rebar element are traversed. A virtual rebar instance is generated for each candidate host component, and the spatial coupling degree between the virtual rebar instance and the target wall node is calculated. The spatial coupling degree includes at least the angular deviation between the rebar extension direction and the main axis direction of the component, the distance between the rebar end and the intersection surface of the component, the Boolean judgment result of whether the rebar as a whole falls into the interior of the component entity, and the offset matching degree between the virtual rebar instance and the contour boundary of the target wall node. The candidate host component whose spatial coupling degree meets the preset threshold is selected as the target host component of the rebar element, and the adaptive positioning parameters of the rebar element are recalculated according to the geometric boundary of the target host component and the offset of the rebar relative to the contour.

[0120] Step C16: Based on the rebar type identifier, detect whether there is a target rebar family type in the rebar family manager of the target BIM document that matches the rebar type identifier. If it exists, call it directly. If it does not exist, obtain the definition of the source rebar family type corresponding to the rebar type identifier from the node data packet and write it into the rebar family manager of the target BIM document.

[0121] Step C17: Based on the determined target host component, adaptive positioning parameters, and the type of target rebar family called, generate a rebar instance of the rebar element in the target BIM document, and establish a belonging association relationship between the rebar instance and the target host component;

[0122] Step C18: Generate corresponding auxiliary geometric elements for the rebar instance based on the auxiliary line display status;

[0123] Step C19: Based on the view information and annotation information, pre-create annotation anchor points for the rebar instance in the target BIM document, and associate the annotation anchor points with the geometric feature points of the rebar instance. The annotation anchor points are used to automatically generate dimension annotations and text annotations for the rebar instance in the target view of the target BIM document.

[0124] In this embodiment, intelligent adaptive creation of rebar instances in the target BIM document is achieved by introducing host association information, surrounding component topology diagrams, and spatial semantic matching mechanisms. Instead of simply copying the absolute coordinates of the rebar, this embodiment dynamically identifies the most matching target host component in the target document based on the host association information of the rebar in the source document. The adaptive positioning parameters of the rebar are then recalculated based on the actual geometric boundaries of the target host component, ensuring accurate embedding of the rebar into the current structural environment. When a direct match is not possible, the optimal candidate host component is selected by calculating spatial coupling, further improving the accuracy and robustness of rebar positioning. Furthermore, compatibility issues with rebar family types are automatically handled, and auxiliary primitives and annotation anchor points are generated for the rebar instances based on the auxiliary line display status, view information, and annotation information, achieving comprehensive restoration from geometric shape to display style. This process significantly reduces the workload of manually adjusting rebar positions and repairing annotations, greatly improving the intelligence level and design fidelity of cross-document migration.

[0125] This embodiment has the following beneficial effects:

[0126] (1) Achieving integrated reuse of all elements of "wall node geometric contour - node internal reinforcement scheme" to eliminate repetitive work: This embodiment strongly binds and encapsulates the complex steel reinforcement layout design with the geometric contour. Designers only need to draw the path and call the standard contour in the target BIM project, and the system can automatically restore the complete set of detailed steel reinforcement models. This shortens the node detailing work that originally took several hours or even days to minutes, significantly improving design efficiency.

[0127] (2) Construct a security verification mechanism based on contour matching to eliminate the risk of misuse: Before loading reinforcement, the system will automatically compare the geometric features (such as cross-sectional dimensions) of the target contour with those of the source data. Loading is only allowed when the two are completely consistent; otherwise, it will be forcibly blocked and an alarm will be triggered. This verification mechanism ensures the security of reuse from the data layer and avoids design errors caused by human negligence.

[0128] (3) Promote the accumulation of enterprise-level digital assets and drive the standardization of design: This embodiment provides a standardized data encapsulation and transfer format (.gqmd), which enables enterprises to easily build their own standard wall node library. Complex nodes that have been verified can be stored in the library once and reused by all employees, which not only ensures the consistency of design output quality across the company, but also transforms personal experience into the core digital assets of the enterprise, greatly enhancing the overall technical competitiveness and knowledge management level of the enterprise.

[0129] Example 2

[0130] This application provides a cross-document migration device for wall nodes, such as... Figure 2As shown, the device specifically includes the following components:

[0131] The export module 201 is used to respond to the export command for the source wall node in the source BIM document, obtain the source outline information of the source wall node and the source reinforcement scheme information adopted by the source wall node, and associate and encapsulate the source outline information and the source reinforcement scheme information to generate a node data package.

[0132] The parsing module 202 is used to obtain and parse the node data packet in response to an import instruction that imports the node data packet into the target wall node of the target BIM document;

[0133] The comparison module 203 is used to obtain the target contour information of the target wall node and compare the target contour information with the source contour information parsed from the node data packet;

[0134] Import module 204 is used to generate a corresponding rebar model on the target wall node according to the source rebar scheme information parsed from the node data packet when the target contour information is consistent with the source contour information.

[0135] Specifically, the export module 201 includes:

[0136] The contour unit is used to obtain the family identifier of the source contour family used by the source wall node and the source contour parameter information instantiated based on the source contour family, and associate the family identifier of the source contour family and the source contour parameter information to form source contour information.

[0137] The reinforcement unit is used to obtain the reinforcement details of each steel element arranged in the source wall node to form the source reinforcement scheme information;

[0138] An auxiliary unit is used to acquire auxiliary information associated with the source wall node, wherein the auxiliary information includes at least one of the following: view information to which the source wall node belongs, annotation information associated with the source wall node, offset of the reinforcing bar relative to the outline, and auxiliary line display status;

[0139] The processing unit is used to serialize the source contour information, the source reinforcement scheme information, the auxiliary information, and the relationships between the information according to a preset data structure to generate a structured node data packet.

[0140] Furthermore, the reinforcement unit is specifically used for:

[0141] A global correlation search is performed on each rebar element in the source rebar scheme information to determine the style resource information referenced by each rebar element in the source BIM document; wherein the global correlation search includes at least one of the following: obtaining the source line style information used by the rebar element from the line style manager of the source BIM document, obtaining the source text style information used by the rebar element from the text style manager of the source BIM document, obtaining the source line type information used by the rebar element from the line type manager of the source BIM document, and obtaining the source material information used by the rebar element from the material manager of the source BIM document;

[0142] Analyze the reference relationship types between each rebar element and its corresponding style resource information, and set a corresponding copy strategy for each style resource information according to the reference relationship type. Specifically, when the reference relationship type is a strong dependency, a forced copy strategy is set for the corresponding style resource information, which requires that the style resource information be written into the target BIM document during import. When the reference relationship type is a weak dependency, a simplified copy strategy is set for the corresponding style resource information, which requires that the style resource information with the same name in the target BIM document be used first during import.

[0143] The style resource information and corresponding copy strategy of each rebar element are associated and stored in the source rebar scheme information.

[0144] Furthermore, the comparison module 203 is specifically used for:

[0145] Based on the family identifier and source profile parameter information of the source profile family parsed from the source profile information, the source profile geometry of the source wall node is determined.

[0146] Obtain the target outline geometry of the target wall node from the target BIM document;

[0147] The geometric dimensions of the target contour are compared with those of the source contour.

[0148] When the geometric dimensions of the target contour are inconsistent with the geometric dimensions of the source contour, it is determined that the target contour information is inconsistent with the source contour information, and the import process is terminated.

[0149] When the geometric dimensions of the target contour are consistent with those of the source contour, it is determined that the target contour information is consistent with the source contour information, and it is checked whether there is a target contour family in the family manager of the target BIM document that is consistent with the family identifier of the source contour family; if so, when the definition of the target contour family is inconsistent with the definition of the source contour family, a new identifier is generated for the source contour family, and the definition of the source contour family is written into the family manager of the target BIM document with the new identifier; if not, the definition of the source contour family is written into the family manager of the target BIM document with the family identifier of the source contour family.

[0150] Furthermore, the import module 204 is specifically used for:

[0151] The source reinforcement scheme information and the auxiliary information are parsed from the node data packet, and a corresponding reinforcement instance is created on the target wall node based on the auxiliary information and the reinforcement details information of each reinforcement element in the source reinforcement scheme information;

[0152] Iterate through each rebar instance sequentially, and based on the target style resource information and target copy strategy corresponding to the currently iterated target rebar instance, perform the following conflict resolution operations:

[0153] If the target copy strategy is a forced copy strategy, then it checks whether there is a style resource with the same name as the target style resource information in the corresponding manager of the target BIM document; when there is a style resource with the same name and the same definition, the style resource with the same name in the target BIM document is directly used to assign to the target rebar instance; when there is a style resource with the same name but the definition is different, a new name is generated for the target style resource information, and the definition of the target style resource information is written into the corresponding manager of the target BIM document with the new name, and then the style resource written with the new name is assigned to the target rebar instance; when there is no style resource with the same name, the definition of the target style resource information is written into the corresponding manager of the target BIM document with the original name of the target style resource information, and the style resource written with the original name is assigned to the target rebar instance.

[0154] If the target copy strategy is a simplified copy strategy, then it is detected whether there is a style resource with the same name as the target style resource information in the corresponding manager of the target BIM document; when there is a style resource with the same name, the style resource with the same name in the target BIM document is directly used to assign to the target rebar instance; when there is no style resource with the same name, the definition of the target style resource information is written into the corresponding manager of the target BIM document with the original name of the target style resource information, and the style resource written with the original name is assigned to the target rebar instance.

[0155] Furthermore, the import module 204 is also used for:

[0156] Instantiate a conflict detector and input the family identifier of the source profile family and the identifier information of the target BIM document into the conflict detector;

[0157] The conflict detector traverses the family manager of the target BIM document to detect whether there is a target profile family in the family manager that matches the family identifier of the source profile family.

[0158] When there is a target contour family with the same family identifier, the definition of the target contour family is obtained, and the definition of the source contour family is compared with the definition of the target contour family.

[0159] If the comparison result indicates that the two definitions are consistent, the conflict detector generates a conflict-free identifier and sends the conflict-free identifier to an import option configurator; in response to receiving the conflict-free identifier, the import option configurator generates an abandon import strategy and instructs an element importer not to perform a write operation, and directly adopts the target contour family already in the target BIM document.

[0160] If the comparison result indicates that the two definitions are inconsistent, the conflict detector generates a conflict identification information and sends the conflict identification information to the import option configurator; in response to receiving the conflict identification information, the import option configurator generates a new identifier for the source contour family according to the preset conflict handling rules and sends the new identifier to the element importer; the element importer writes the definition of the source contour family with the new identifier into the family manager of the target BIM document;

[0161] When no target contour family with the same family identifier does not exist, the conflict detector returns a conflict-free identifier to the import option configurator; in response to receiving the conflict-free identifier, the import option configurator generates a direct import strategy and sends the family identifier of the source contour family to the element importer; the element importer writes the definition of the source contour family into the family manager of the target BIM document using the family identifier of the source contour family.

[0162] The element importer returns the writing result information after the writing operation is completed.

[0163] Example 3

[0164] This embodiment also provides a computer device, such as a smartphone, tablet computer, laptop computer, desktop computer, rack server, blade server, tower server, or cabinet server (including a standalone server or a server cluster composed of multiple servers), etc., capable of executing programs. Figure 3As shown, the computer device 30 in this embodiment includes, but is not limited to, a memory 301 and a processor 302 that are communicatively connected to each other via a system bus. It should be noted that... Figure 3 Only a computer device 30 with components 301-302 is shown; however, it should be understood that it is not required to implement all of the components shown, and more or fewer components may be implemented instead.

[0165] In this embodiment, the memory 301 (i.e., the readable storage medium) includes flash memory, hard disk, multimedia card, card-type memory (e.g., SD or DX memory), random access memory (RAM), static random access memory (SRAM), read-only memory (ROM), electrically erasable programmable read-only memory (EEPROM), programmable read-only memory (PROM), magnetic memory, magnetic disk, optical disk, etc. In some embodiments, the memory 301 may be an internal storage unit of the computer device 30, such as the hard disk or memory of the computer device 30. In other embodiments, the memory 301 may also be an external storage device of the computer device 30, such as a plug-in hard disk, smart media card (SMC), secure digital (SD) card, flash card, etc., equipped on the computer device 30. Of course, the memory 301 may include both the internal storage unit and the external storage device of the computer device 30. In this embodiment, the memory 301 is typically used to store the operating system and various application software installed on the computer device 30. In addition, the memory 301 may also be used to temporarily store various types of data that have been output or will be output.

[0166] In some embodiments, processor 302 may be a central processing unit (CPU), controller, microcontroller, microprocessor, or other data processing chip. This processor 302 is typically used to control the overall operation of the computer device 30.

[0167] Specifically, in this embodiment, the processor 302 is used to execute the program for the cross-document migration method for wall nodes stored in the memory 301. When the program for the cross-document migration method for wall nodes is executed, it performs the following steps:

[0168] In response to the export command for the source wall node in the source BIM document, the source outline information of the source wall node and the source reinforcement scheme information adopted by the source wall node are obtained, and the source outline information and the source reinforcement scheme information are associated and encapsulated to generate a node data package;

[0169] In response to an import command to import the node data packet into the target wall node of the target BIM document, the node data packet is obtained and parsed;

[0170] Obtain the target contour information of the target wall node, and compare the target contour information with the source contour information parsed from the node data packet;

[0171] When the target contour information is consistent with the source contour information, a corresponding rebar model is generated on the target wall node according to the source rebar scheme information parsed from the node data packet.

[0172] For a detailed description of the above method steps, please refer to Example 1. This example will not be repeated here.

[0173] Example 4

[0174] This embodiment also provides a computer-readable storage medium, such as flash memory, hard disk, multimedia card, card-type memory (e.g., SD or DX memory), random access memory (RAM), static random access memory (SRAM), read-only memory (ROM), electrically erasable programmable read-only memory (EEPROM), programmable read-only memory (PROM), magnetic memory, disk, optical disk, server, app store, etc., which stores a computer program. When the computer program is executed by a processor, it implements the following method steps:

[0175] In response to the export command for the source wall node in the source BIM document, the source outline information of the source wall node and the source reinforcement scheme information adopted by the source wall node are obtained, and the source outline information and the source reinforcement scheme information are associated and encapsulated to generate a node data package;

[0176] In response to an import command to import the node data packet into the target wall node of the target BIM document, the node data packet is obtained and parsed;

[0177] Obtain the target contour information of the target wall node, and compare the target contour information with the source contour information parsed from the node data packet;

[0178] When the target contour information is consistent with the source contour information, a corresponding rebar model is generated on the target wall node according to the source rebar scheme information parsed from the node data packet.

[0179] For a detailed description of the above method steps, please refer to the first embodiment. This embodiment will not repeat the details here.

[0180] It should be noted that, in this document, the terms "comprising," "including," or any other variations thereof are intended to cover non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements includes not only those elements but also other elements not expressly listed, or elements inherent to such a process, method, article, or apparatus. Unless otherwise specified, an element defined by the phrase "comprising one..." does not exclude the presence of other identical elements in the process, method, article, or apparatus that includes that element.

[0181] The sequence numbers of the embodiments in this application are for descriptive purposes only and do not represent the superiority or inferiority of the embodiments.

[0182] Through the above description of the embodiments, those skilled in the art can clearly understand that the methods of the above embodiments can be implemented by means of software plus necessary general-purpose hardware platforms. Of course, they can also be implemented by hardware, but in many cases the former is a better implementation method.

[0183] The above are merely preferred embodiments of this application and do not limit the patent scope of this application. Any equivalent structural or procedural transformations made using the content of this application's specification and drawings, or direct or indirect applications in other related technical fields, are similarly included within the patent protection scope of this application.

Claims

1. A cross-document migration method for wall nodes, characterized in that, The method includes: In response to the export command for the source wall node in the source BIM document, the source outline information of the source wall node and the source reinforcement scheme information adopted by the source wall node are obtained, and the source outline information and the source reinforcement scheme information are associated and encapsulated to generate a node data package; In response to an import command to import the node data packet into the target wall node of the target BIM document, the node data packet is obtained and parsed; Obtain the target contour information of the target wall node, and compare the target contour information with the source contour information parsed from the node data packet; When the target contour information is consistent with the source contour information, a corresponding rebar model is generated on the target wall node according to the source rebar scheme information parsed from the node data packet; The step of obtaining the target contour information of the target wall node and comparing the target contour information with the source contour information parsed from the node data packet includes: Based on the family identifier and source profile parameter information of the source profile family parsed from the source profile information, the source profile geometry of the source wall node is determined. Obtain the target outline geometry of the target wall node from the target BIM document; The geometric dimensions of the target contour are compared with those of the source contour. When the geometric dimensions of the target contour are inconsistent with the geometric dimensions of the source contour, it is determined that the target contour information is inconsistent with the source contour information, and the import process is terminated. When the geometric dimensions of the target contour are consistent with those of the source contour, it is determined that the target contour information is consistent with the source contour information, and it is checked whether there is a target contour family in the family manager of the target BIM document that is consistent with the family identifier of the source contour family; if so, when the definition of the target contour family is inconsistent with the definition of the source contour family, a new identifier is generated for the source contour family, and the definition of the source contour family is written into the family manager of the target BIM document with the new identifier; if not, the definition of the source contour family is written into the family manager of the target BIM document with the family identifier of the source contour family.

2. The cross-document migration method for wall nodes according to claim 1, characterized in that, The process of obtaining the source contour information of the source wall node and the source reinforcement scheme information adopted by the source wall node, and associating and encapsulating the source contour information and the source reinforcement scheme information to generate a node data packet includes: Obtain the family identifier of the source profile family used by the source wall node and the source profile parameter information instantiated based on the source profile family, and associate the family identifier of the source profile family and the source profile parameter information to form source profile information; Obtain detailed information on the reinforcement details of each reinforcement element arranged in the source wall node to form source reinforcement scheme information; Obtain the auxiliary information associated with the source wall node, wherein the auxiliary information includes at least one of the following: the view information to which the source wall node belongs, the annotation information associated with the source wall node, the offset of the reinforcing bar relative to the outline, and the display status of the auxiliary line; The source contour information, the source reinforcement scheme information, the auxiliary information, and the relationships between each piece of information are serialized according to a preset data structure to generate a structured node data packet.

3. The cross-document migration method for wall nodes according to claim 2, characterized in that, The step of obtaining the reinforcement details of each reinforcement element arranged in the source wall node to form source reinforcement scheme information also includes: A global correlation search is performed on each rebar element in the source rebar scheme information to determine the style resource information referenced by each rebar element in the source BIM document; wherein the global correlation search includes at least one of the following: obtaining the source line style information used by the rebar element from the line style manager of the source BIM document, obtaining the source text style information used by the rebar element from the text style manager of the source BIM document, obtaining the source line type information used by the rebar element from the line type manager of the source BIM document, and obtaining the source material information used by the rebar element from the material manager of the source BIM document; Analyze the reference relationship types between each rebar element and its corresponding style resource information, and set a corresponding copy strategy for each style resource information according to the reference relationship type. Specifically, when the reference relationship type is a strong dependency, a forced copy strategy is set for the corresponding style resource information, which requires that the style resource information be written into the target BIM document during import. When the reference relationship type is a weak dependency, a simplified copy strategy is set for the corresponding style resource information, which requires that the style resource information with the same name in the target BIM document be used first during import. The style resource information and corresponding copy strategy of each rebar element are associated and stored in the source rebar scheme information.

4. The cross-document migration method for wall nodes according to claim 3, characterized in that, When the target contour information matches the source contour information, a corresponding rebar model is generated on the target wall node according to the source rebar scheme information parsed from the node data packet, including: The source reinforcement scheme information and the auxiliary information are parsed from the node data packet, and a corresponding reinforcement instance is created on the target wall node based on the auxiliary information and the reinforcement details information of each reinforcement element in the source reinforcement scheme information; Iterate through each rebar instance sequentially, and based on the target style resource information and target copy strategy corresponding to the currently iterated target rebar instance, perform the following conflict resolution operations: If the target copy strategy is a forced copy strategy, then it checks whether there is a style resource with the same name as the target style resource information in the corresponding manager of the target BIM document; when there is a style resource with the same name and the same definition, the style resource with the same name in the target BIM document is directly used to assign to the target rebar instance; when there is a style resource with the same name but the definition is different, a new name is generated for the target style resource information, and the definition of the target style resource information is written into the corresponding manager of the target BIM document with the new name, and then the style resource written with the new name is assigned to the target rebar instance; when there is no style resource with the same name, the definition of the target style resource information is written into the corresponding manager of the target BIM document with the original name of the target style resource information, and the style resource written with the original name is assigned to the target rebar instance. If the target copy strategy is a simplified copy strategy, then it is detected whether there is a style resource with the same name as the target style resource information in the corresponding manager of the target BIM document; when there is a style resource with the same name, the style resource with the same name in the target BIM document is directly used to assign to the target rebar instance; when there is no style resource with the same name, the definition of the target style resource information is written into the corresponding manager of the target BIM document with the original name of the target style resource information, and the style resource written with the original name is assigned to the target rebar instance.

5. The cross-document migration method for wall nodes according to claim 2, characterized in that, The step of detecting whether a target contour family exists in the family manager of the target BIM document that matches the family identifier of the source contour family; if so, then when the definition of the target contour family is inconsistent with the definition of the source contour family, a new identifier is generated for the source contour family, and the definition of the source contour family is written into the family manager of the target BIM document with the new identifier; if not, then the definition of the source contour family is written into the family manager of the target BIM document with the family identifier of the source contour family, including: Instantiate a conflict detector and input the family identifier of the source profile family and the identifier information of the target BIM document into the conflict detector; The conflict detector traverses the family manager of the target BIM document to detect whether there is a target profile family in the family manager that matches the family identifier of the source profile family. When there is a target contour family with the same family identifier, the definition of the target contour family is obtained, and the definition of the source contour family is compared with the definition of the target contour family. If the comparison result indicates that the two definitions are consistent, the conflict detector generates a conflict-free identifier and sends the conflict-free identifier to an import option configurator; in response to receiving the conflict-free identifier, the import option configurator generates an abandon import policy and instructs an element importer not to perform a write operation. If the comparison result indicates that the two definitions are inconsistent, the conflict detector generates a conflict identification information and sends the conflict identification information to the import option configurator; in response to receiving the conflict identification information, the import option configurator generates a new identifier for the source contour family according to the preset conflict handling rules and sends the new identifier to the element importer; the element importer writes the definition of the source contour family with the new identifier into the family manager of the target BIM document; When no target contour family with the same family identifier does not exist, the conflict detector returns a conflict-free identifier to the import option configurator; in response to receiving the conflict-free identifier, the import option configurator generates a direct import strategy and sends the family identifier of the source contour family to the element importer; the element importer writes the definition of the source contour family into the family manager of the target BIM document using the family identifier of the source contour family. The element importer returns the writing result information after the writing operation is completed.

6. A cross-document migration device for wall nodes, characterized in that, The device includes: The export module is used to respond to the export command for the source wall node in the source BIM document, obtain the source outline information of the source wall node and the source reinforcement scheme information adopted by the source wall node, and associate and encapsulate the source outline information and the source reinforcement scheme information to generate a node data package. The parsing module is used to obtain and parse the node data packet in response to an import instruction that imports the node data packet into the target wall node of the target BIM document; The comparison module is used to obtain the target contour information of the target wall node and compare the target contour information with the source contour information parsed from the node data packet; The import module is used to generate a corresponding steel reinforcement model on the target wall node according to the source steel reinforcement scheme information parsed from the node data packet when the target contour information is consistent with the source contour information. The comparison module is used for: Based on the family identifier and source profile parameter information of the source profile family parsed from the source profile information, the source profile geometry of the source wall node is determined. Obtain the target outline geometry of the target wall node from the target BIM document; The geometric dimensions of the target contour are compared with those of the source contour. When the geometric dimensions of the target contour are inconsistent with the geometric dimensions of the source contour, it is determined that the target contour information is inconsistent with the source contour information, and the import process is terminated. When the geometric dimensions of the target contour are consistent with those of the source contour, it is determined that the target contour information is consistent with the source contour information, and it is checked whether there is a target contour family in the family manager of the target BIM document that is consistent with the family identifier of the source contour family; if so, when the definition of the target contour family is inconsistent with the definition of the source contour family, a new identifier is generated for the source contour family, and the definition of the source contour family is written into the family manager of the target BIM document with the new identifier; if not, the definition of the source contour family is written into the family manager of the target BIM document with the family identifier of the source contour family.

7. The cross-document migration device for wall nodes according to claim 6, characterized in that, The export module is used for: Obtain the family identifier of the source profile family used by the source wall node and the source profile parameter information instantiated based on the source profile family, and associate the family identifier of the source profile family and the source profile parameter information to form source profile information; Obtain detailed information on the reinforcement details of each reinforcement element arranged in the source wall node to form source reinforcement scheme information; Obtain the auxiliary information associated with the source wall node, wherein the auxiliary information includes at least one of the following: the view information to which the source wall node belongs, the annotation information associated with the source wall node, the offset of the reinforcing bar relative to the outline, and the display status of the auxiliary line; The source contour information, the source reinforcement scheme information, the auxiliary information, and the relationships between each piece of information are serialized according to a preset data structure to generate a structured node data packet.

8. A computer device, the computer device comprising: A memory, a processor, and a computer program stored in the memory and executable on the processor, characterized in that the processor, when executing the computer program, implements the steps of the method according to any one of claims 1 to 5.

9. A computer-readable storage medium having a computer program stored thereon, characterized in that, When the computer program is executed by a processor, it implements the steps of the method according to any one of claims 1 to 5.

Images