Methods, apparatus, equipment and storage media for modifying BIM linked model data

Abstract

This invention provides a method, apparatus, device, and storage medium for modifying BIM linked model data, relating to the field of BIM design technology. The method, applied to BIM model linking scenarios, includes: loading the grid lines of the BIM linked model into the current document; prohibiting editing operations on the grid lines while they are in model state; switching the grid lines from model state to view state in response to a first state switching operation on the grid lines in the current view; and modifying the grid line view data corresponding to the current view in the second data area in response to an editing operation on the grid lines while remaining unchanged from the grid line model data in the first data area. Through this invention, in BIM model linking scenarios, flexible display and controlled editing of the linked model grid lines in a specific view of the current document are achieved without changing the basic grid line data in the linked document.

Description

Technical Field

[0001] This invention relates to the field of BIM design technology, and in particular to a method, apparatus, device, and storage medium for modifying BIM linked model data. Background Technology

[0002] Building Information Modeling (BIM) technology is widely used in the design and collaborative processes of architecture, structure, MEP (Mechanical, Electrical, and Plumbing) disciplines. As the fundamental positioning object in a BIM model, the grid serves as a unified layout reference for walls, columns, beams, doors, windows, and MEP components. Its display status and positioning accuracy affect the model's expressive quality and the efficiency of collaborative design.

[0003] In multidisciplinary collaborative design processes, models from different disciplines or different areas are typically created separately and loaded into the current document via model links. This allows for comprehensive viewing, location referencing, and design collaboration within a unified project environment. For these linked models, their model data is usually still stored in their respective external documents; the current document primarily serves to display and reference these linked models.

[0004] In this BIM model linking scenario, when designers need to adjust the grid lines in the linked models, the current approach is usually to first open the corresponding linked document, edit and save the grid lines, and then return to the current document to reload or update the linked model so that the changes take effect in the current document. In other words, the linked model loaded in the current document is generally difficult to edit directly in place, especially making it difficult to flexibly adjust the display of the grid lines in the linked model based solely on the current view.

[0005] On the other hand, in BIM design, at least in some software or related processing logic, object-related data can be distinguished into model-level data and view-level data. The former is more used to characterize the basic attributes of the object, while the latter is more used to characterize the display status of the object in a specific view. For grid lines, different disciplines and different views often have different display requirements. For example, some views need to display the complete grid lines for overall positioning, while some views only need to display local grid lines or make targeted adjustments to the displayed content such as grid numbers and lengths.

[0006] However, in existing technologies, the editing capabilities of linked model grids within the current document are relatively limited, with at least the following problems: First, when only the grid display status in a specific view needs to be adjusted, it is still necessary to open the linked document, edit, save, and reload, which is cumbersome and affects the efficiency of collaborative design. Second, it is difficult to independently control the display range, display length, or visibility status of linked model grids in the current view without changing the original grid data in the linked document, resulting in insufficient adaptability to different professional views. Third, in actual projects, to meet local display requirements, grids may need to be redrawn in the current document, leading to risks such as grid duplication, positional deviations, and inconsistent numbering, which is detrimental to the consistency maintenance of model data and subsequent model integration.

[0007] Therefore, how to achieve flexible display and controlled editing of the grid lines of the linked model in a specific view of the current document without changing the basic grid data in the linked document has become a technical problem that urgently needs to be solved in this field. Summary of the Invention

[0008] The purpose of this invention is to provide a method, apparatus, device, and storage medium for modifying BIM linked model data, in order to solve the aforementioned technical problems in the prior art.

[0009] On the one hand, in order to achieve the above objectives, the present invention provides a method for modifying BIM link model data.

[0010] This method for modifying BIM linked model data is applied to BIM model linking scenarios, where the BIM linked model is a loaded external BIM model. The method includes: loading the grid lines of the BIM linked model into the current document, wherein the grid lines have a model state and a view state; a first data area stores the grid line model data of the BIM linked model, and a second data area stores the grid line view data of the BIM linked model, with the grid line view data corresponding to the views in the current document; when the grid lines are in model state, editing operations on the grid lines are prohibited; in the current view, in response to a first state switching operation on the grid lines in the current view, the grid lines are switched from model state to view state; when the grid lines are in view state, in response to an editing operation on the grid lines, the grid line view data corresponding to the current view in the second data area is modified without changing the grid line model data in the first data area.

[0011] Furthermore, in response to the first state switching operation for the grid, the step of switching the grid from the model state to the view state includes: in response to the selection operation for the grid, determining the target grid whose state is to be switched; in response to the first state switching operation for the target grid, switching the target grid from the model state to the view state; outputting view editing prompts in the interactive interface; and displaying editing controls corresponding to the grid view data of the target grid in the editing panel.

[0012] Furthermore, in response to an editing operation on the grid lines, the steps for modifying the grid line view data corresponding to the current view in the second data area include: receiving a display / hide control operation on the axis lines of the target grid line through an axis line display / hide editing control, and determining the display / hide state of the axis lines in the current view; receiving a length control operation on the axis lines through an axis line length editing control, and determining the display length of the axis lines in the current view; receiving a display / hide control operation on the axis numbers of the target grid line through an axis number display / hide editing control, and determining the display / hide state of the axis numbers in the current view; receiving a position control operation on the axis numbers through an axis number position editing control, and determining the display position of the axis numbers in the current view; and writing the determined display / hide state of the axis lines, the display length of the axis lines, the display / hide state of the axis numbers, and the display position of the axis numbers in the current view into the grid line view data corresponding to the current view in the second data area.

[0013] Further, in response to a selection operation on a grid, the step of determining the target grid for the state to be switched includes: in response to a selection operation on multiple grids, determining multiple target grids for the state to be switched, wherein the multiple target grids are parallel grids; the step of receiving a length control operation on the axis through the axis length editing control and determining the display length of the axis in the current view includes: receiving a batch adjustment operation on the axes of the multiple target grids through the axis length editing control and determining the target display length of the axis of each target grid in the current view; the step of writing the display length of the axis in the current view into the grid view data corresponding to the current view in the second data area includes: batch modifying the axis length data of the multiple target grids corresponding to the current view in the second data area according to the target display length.

[0014] Furthermore, the axis display / concealment editing control includes a clipping box. The steps of receiving display / concealment control operations for the target axis grid through the axis display / concealment editing control and determining the display / concealment status of the axis in the current view include: receiving clipping box adjustment operations for the target axis grid through the clipping box to determine the target display range of the target axis grid in the current view; determining that local axis segments within the target display range of the target axis grid are visible, and local axis segments outside the target display range are hidden.

[0015] Furthermore, the method for modifying BIM linked model data also includes: in response to a second state switching operation for the grid, switching the grid from view state to model state; and when the grid is in model state, controlling the grid in the current view to be displayed according to the grid model data in the first data area, while keeping the grid view data corresponding to the current view in the second data area unchanged.

[0016] Furthermore, the method for modifying BIM linked model data also includes: when the grid model data in the linked document corresponding to the BIM linked model is updated, the first data area is updated while the grid view data in the second data area remains unchanged; for grids in the model state, the updated grid model data is read from the first data area and the display of grids in the model state is updated synchronously.

[0017] On the other hand, in order to achieve the above objectives, the present invention provides an apparatus for modifying BIM link model data.

[0018] This device for modifying BIM linked model data is applied to BIM model linking scenarios. The BIM linked model is a loaded external BIM model. The device includes: an interaction layer for providing users with an operation entry point; a core logic layer including a loading module for loading the grid of the BIM linked model into the current document, wherein the grid has a model state and a view state; a data layer including a first data area and a second data area, the first data area for storing the grid model data of the BIM linked model, and the second data area for storing the grid view data of the BIM linked model, the grid view data corresponding to the view in the current document; the core logic layer also includes: a processing module for prohibiting editing operations on the grid when it is in the model state; in the current view, in response to the first state switching operation of the grid in the current view, switching the grid from the model state to the view state; and in the view state, in response to the editing operation of the grid, modifying the grid view data corresponding to the current view in the second data area without changing the grid model data in the first data area.

[0019] On the other hand, to achieve the above objectives, the present invention also provides a computer device, including 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 above method.

[0020] On the other hand, to achieve the above objectives, the present invention also provides a computer-readable storage medium having a computer program stored thereon, which, when executed by a processor, implements the steps of the above method.

[0021] The present invention provides a method, apparatus, device, and storage medium for modifying BIM linked model data. First, the grid lines of an external BIM model are loaded into the current document. A first data area is set for storing grid model data, and a second data area is set for storing grid view data. The grid view data is associated with views in the current document, and the grid lines have both model and view states. Then, editing operations on the grid lines are prohibited while they are in model state. Next, in response to a first state switching operation on the grid lines in the current view, the grid lines are switched from model state to view state. Finally, while the grid lines are in view state, in response to an editing operation on the grid lines, the grid view data corresponding to the current view in the second data area is modified without changing the grid model data in the first data area. This invention separates and stores the model data and view data of the linked model grid, and controls editing permissions by switching between model and view states. This allows the linked model grid to be edited at the view level within the current document without opening the linked document to modify its model data. Simultaneously, since the editing results are confined to the grid view data corresponding to the current view in the second data area, the grid model data in the linked document remains unchanged, and the grid display effects in different views are independent of each other. This balances the consistency of the linked model data with the flexibility of editing the current view, improving the efficiency of grid adjustment and view adaptation capabilities in BIM collaborative design. Attached Figure Description

[0022] Various other advantages and benefits will become apparent to those skilled in the art upon reading the following detailed description of preferred embodiments. The accompanying drawings are for illustrative purposes only and are not intended to limit the invention. Furthermore, the same reference numerals denote the same parts throughout the drawings. In the drawings: Figure 1 This is a flowchart of a method for modifying BIM linked model data provided in Embodiment 1 of the present invention; Figure 2 This is a schematic diagram illustrating the data description of the grid object provided in an embodiment of the present invention; Figure 3 This is a block diagram of the device for modifying BIM linked model data provided in Embodiment 2 of the present invention; Figure 4 This is a hardware structure diagram of a computer device provided in Embodiment 3 of the present invention. Detailed Implementation

[0023] To make the objectives, technical solutions, and advantages of this invention clearer, the invention will be further described in detail below with reference to the accompanying drawings and embodiments. It should be understood that the specific embodiments described herein are merely illustrative and not intended to limit the invention. All other embodiments obtained by those skilled in the art based on the embodiments of this invention without inventive effort are within the scope of protection of this invention.

[0024] First, the following unified definitions are provided for the relevant terms mentioned in this application: The BIM model linking scenario addressed in this application refers to a scenario where at least one external BIM model is loaded into the current BIM document through the model linking function to achieve collaborative display and joint application of models from multiple disciplines or multiple zones. The data ontology of the loaded external BIM model is stored in the corresponding linked document, and the current document is mainly used for displaying, referencing, and view-level collaborative processing of the external BIM model.

[0025] Linked Model: Refers to an external BIM model loaded into the current document through the linking function of BIM software. Its core data (including grid model data) is stored in its own document, and the current document only loads and displays its complete data by default.

[0026] Grid model data: Belongs to the linked document and cannot be modified in the current document. It follows the architecture requirements of dual data state for grids and manages all six core elements of the grid, namely, axis length, axis number, axis number visibility, axis line type, and axis number position. It is the basic data of the grid and determines the essential attributes of the grid. Modification of any element in the model data is a global modification and will synchronously affect the model data of the current grid in all views.

[0027] Grid view data: Belongs to the current document, can be edited independently, follows the architecture requirements of dual data state for grids, and only manages the four core elements of grids, namely axis length, axis number visibility, axis number position, and axis number position. It only affects the current view and does not affect linked documents or other views; modification of any element in the view data only affects the display effect of the current grid in the current view and has no effect on other views.

[0028] Model Status: The default status of the grid. At this time, the grid only loads model data from linked documents, and the view data is consistent with the model data. The current document cannot edit any data of the grid (including view data), but can only view it. At this time, the six core elements of the grid all follow the global control rules of the model data.

[0029] View Status: The editable state of the grid. At this time, the grid retains the model data in the linked document (without modification or impact on the global view). The current document can independently edit its view data (only controlling the four main elements). The editing results are only saved in the corresponding view of the current document and are not synchronized to the linked document or affected by other views. At this time, the grid's model data remains globally consistent, and the view data only applies to the current view.

[0030] The core components of the grid are: axis length, axis number, axis number visibility, axis line type, and axis number position. These are the core control objects of the grid model data and view data. The model data controls all six elements, and the view data controls four elements, strictly matching the architecture design of dual data states.

[0031] Based on the above definitions, the various embodiments of this application are described in detail below.

[0032] Example 1 Embodiment 1 of the present invention provides a method for modifying BIM linked model data. This method enables view-level editing of the grid lines of an external BIM model within a BIM model linking scenario, while avoiding modifications to the grid line model data in the linked document. Specifically, Figure 1 The flowchart of the method for modifying BIM linked model data provided in Embodiment 1 of the present invention is as follows: Figure 1 As shown, the method for modifying BIM linked model data provided in this embodiment includes the following steps S101 to S104. This method is applicable to BIM design software environments with model linking functionality, grid management functionality, and view display functionality. A BIM model linking scenario refers to a scenario where an external BIM model is loaded into the current document via the linking function, and then displayed and collaboratively processed within the current document.

[0033] Step S101: Load the grid lines of the BIM linked model in the current document.

[0034] The grid system has a model state and a view state. The first data area is used to store the grid model data of the BIM linked model, and the second data area is used to store the grid view data of the BIM linked model. The grid view data corresponds to the view in the current document.

[0035] The BIM linked model can be an external BIM model loaded into the current document via the "link" function of BIM software, such as an architectural model, structural model, or MEP model. The current document can be the project master document, a collaborative document, or a comprehensive drawing document. By loading the grid lines of the BIM linked model into the current document, the current document can display the grid objects from the external BIM model, allowing for subsequent state switching and view-level editing. The core data of the external BIM model is stored within its own document.

[0036] In this embodiment, the first data area is used to store the grid model data of the BIM linked model. The grid model data is basic data belonging to the linked document and can be used to characterize the global attributes of the grid. Optionally, the grid model data includes basic attribute data such as axis length, axis number, axis number position, axis number visibility, axis visibility, and axis line type, etc. Figure 2 As shown. The second data area is used to store the grid view data of the BIM linked model. The grid view data is local data belonging to the current document and is associated with specific views in the current document. Different views can correspond to different grid view data. Optionally, the grid view data in the second data area includes at least one or more of the following: axis length, axis number position, axis number visibility, and axis visibility. That is to say, the first data area and the second data area are distinguished from each other in terms of data ownership, editability, and scope of influence. The former corresponds to model-level data in the linked document, while the latter corresponds to display-level data associated with views in the current document.

[0037] In one optional implementation, when loading the grid of the BIM linked model, the grid object identifier in the linked model can be read first, and a correspondence between the grid object identifier and the linked model identifier can be established in the current document. At the same time, an association between the view identifier and the grid view data can be established in the current document, which is used to locate the corresponding grid view data in the second data area according to the current view identifier and the grid object identifier. This ensures that the view data corresponding to the same linked grid in different views are stored independently.

[0038] The grid system has a model state and a view state. The model state is the non-editable state of the grid, in which the grid is displayed according to the model data in the linked document. The view state is the editable state of the grid, in which the grid retains the model data in the linked document and allows editing of the grid view data associated with the current view in the current document.

[0039] Step S102: When the grid is in model state, editing operations on the grid are prohibited.

[0040] In this embodiment, the model state is used to limit the grid lines to a read-only display state. When the grid lines are in model state, the current document only displays the grid line model data from linked documents, and editing operations on the grid lines are not allowed. That is, in model state, users can view the grid lines, but cannot directly change the display control parameters of the grid lines in the current view through the current document.

[0041] Optionally, in one implementation, prohibiting editing operations on grid lines can be achieved as follows: when a user initiates editing commands such as dragging, toggling visibility, adjusting endpoints, or adjusting grid number positions on grid lines in model mode, the grid line state management module intercepts the editing command and prevents the modification results from being written to the second data area; or, the corresponding editing controls can be directly set to an unavailable state at the interface layer, preventing the user from triggering view-level editing in model mode. This approach ensures the read-only nature of the model mode at the software level.

[0042] Step S103: In response to the first state switching operation for the grid in the current view, switch the grid from the model state to the view state.

[0043] The current view refers to the active view in the current document or the target view currently displaying the grid, such as a first-floor plan view, a second-floor plan view, a structural plan view, or a mechanical and electrical section view. The first state transition operation can be triggered by the user selecting the target grid in the current view, using a state transition button, a state transition menu item, a shortcut command, or other state transition instructions. This first state transition operation changes the target grid in the current view from an uneditable model state to an editable view state, thus providing a prerequisite for subsequent editing of view data specific to the current view.

[0044] In this embodiment, in response to the first state switching operation, the target grid and the current view can be determined first, and then the state identifier corresponding to the target grid can be updated, so that the target grid enters the view state within the current view. Optionally, after the state switch, view editing prompts can be output on the interactive interface to inform the user that the current modification only applies to the current view and does not affect linked documents or other view information. Further optionally, the editing panel only displays the editing controls corresponding to the grid view data after the switch.

[0045] Step S104: When the grid is in view state, in response to the editing operation on the grid, modify the grid view data corresponding to the current view in the second data area, without changing the grid model data in the first data area.

[0046] In this embodiment, once the target grid has been switched to view mode, the user can perform view-level editing operations on the grid. Editing operations refer to operations that only modify the grid view data corresponding to the current view in the second data area, rather than modifying the grid model data in a linked document. Optionally, editing operations include one or more of the following: dragging the endpoints of the axis lines to adjust their display length in the current view; adjusting the position of the axis numbers to change their display position in the current view; controlling the display or hiding of axis numbers to adjust their visibility; controlling the display or hiding of axes to adjust their visibility; or adjusting the grid display range in the current view using a clipping box to create a localized grid visibility effect. All of the above operations are view-level editing operations, and their modification results are written to the grid view data associated with the current view in the second data area.

[0047] Specifically, upon receiving an edit operation, the current view identifier and the target grid object identifier can be extracted to locate the grid view data record corresponding to the current view in the second data area. If the grid does not yet have an independent view data record in the current view, a grid view data associated with the current view can be initialized based on the corresponding grid model data in the first data area, and then an update can be performed on this initialized data. Subsequently, the edit result is written to the second data area, causing a change in the display effect in the current view. Since the writing target is limited to the grid view data corresponding to the current view in the second data area, the edit result only applies to the current view.

[0048] Modifications do not alter the grid model data in the first data area. In other words, writing to the grid view data corresponding to the current view in the second data area while in view mode will not be written back to the linked document, nor will it cause changes to the grid model data stored in the first data area. Therefore, the same linked grid can continue to be displayed in other views according to the view data or model data rules corresponding to their respective views, and the basic model attributes in the linked document remain unchanged. This approach simultaneously satisfies the local editability of the linked model grid in the current view and the global consistency of the linked document's model data.

[0049] In one optional implementation, the second data area can store corresponding grid view data for different views. Therefore, the same grid can have a first set of axis length, axis number position, axis number visibility, and axis visibility settings in the architectural plan view, while it can have another set of different settings in the electromechanical section view. This allows for adaptation to the differentiated needs of different professions and drawing scenarios for the display effect of the same linked grid.

[0050] In the method for modifying BIM linked model data provided in this embodiment, the grid of an external BIM model is first loaded into the current document, and a first data area for storing grid model data and a second data area for storing grid view data are set. The grid view data is associated with the view in the current document, and the grid has a model state and a view state. Then, when the grid is in the model state, editing operations on the grid are prohibited. In response to a first state switching operation on the grid in the current view, the grid is switched from the model state to the view state. Finally, when the grid is in the view state, in response to an editing operation on the grid, the grid view data corresponding to the current view in the second data area is modified, without changing the grid model data in the first data area. The method for modifying BIM linked model data provided in this embodiment separates and stores the model data and view data of the linked model grid, and controls editing permissions by switching between model and view states. This allows the linked model grid to be edited at the view level in the current document without opening the linked document to modify its model data. At the same time, since the editing results are limited to the grid view data corresponding to the current view in the second data area, the grid model data in the linked document remains unchanged, and the grid display effects in different views are independent of each other. This balances the consistency of linked model data and the flexibility of current view editing, improving the efficiency of grid adjustment and view adaptation capabilities in BIM collaborative design.

[0051] Optionally, in one embodiment, the step of switching a grid from a model state to a view state in response to a first state switching operation for the grid includes: determining a target grid whose state is to be switched in response to a selection operation for the grid; switching the target grid from a model state to a view state in response to the first state switching operation for the target grid; outputting view editing prompts on the interactive interface; and displaying editing controls corresponding to the grid view data of the target grid in the editing panel.

[0052] Specifically, in the current view, for the selection of grid lines, users can use the grid selection tool in the software to select the linked grid lines that need adjustment in the current view to determine the target grid line for the state to be switched. Optionally, the target grid line can be a single grid line, multiple grid lines, or all grid lines in the current view that need adjustment. By performing the selection operation first and then the state switching operation, the state switching object can be limited to the selected target grid line, rather than switching all linked grid lines in the current document at once, thereby improving the targeting of subsequent editing scope.

[0053] After the target grid is determined, a first state switching operation can be performed on the target grid to switch it from the model state to the view state. This first state switching operation can be initiated by the user clicking a state switching button in the graphical interface, executing a state switching command in the dynamic panel, or issuing a switching instruction through an interface operation equivalent to the state switching function. After the switch is complete, the target grid changes from an uneditable model state to an editable view state. In other words, in this embodiment, the state switching does not modify the grid model data in the first data area, but rather switches the editing permissions and data writing objects of the target grid, making subsequent editing operations executable instead of previously non-executable, and limiting the writing objects to the grid view data associated with the view in the second data area.

[0054] After the target grid is switched to view mode, a view editing prompt message is displayed on the interactive interface. This prompt message informs the user that the target grid has entered view mode, and subsequent modifications apply to the grid view data in the current view, not the grid model data in linked documents. Optionally, the prompt message can be displayed using a dialog box, status bar prompt, floating prompt, overlay text information, or other visual prompts. In one specific implementation, after the target grid is switched to view mode, the software can display a prompt box, such as "Entering grid view editing mode; all modifications only apply to the current view and do not affect linked documents or other views"; simultaneously, the target grid can be highlighted to further enhance the user's identification of the currently editable object. This approach helps users clearly understand the current data editing scope and its impact, reducing accidental operations.

[0055] Simultaneously or subsequently, editing controls corresponding to the grid view data of the target grid can be displayed in the editing panel. Editing controls refer to interface operation controls used to edit the grid view data corresponding to the target grid and target view in the second data area. Optionally, these editing controls may include one or more of the following: axis length editing control, axis number position editing control, axis number visibility editing control, and axis visibility editing control. Since these controls correspond to grid view data, the editing operations initiated by the user through these controls are written to the grid view data corresponding to the target view in the second data area, and not written back to the grid model data in the first data area. In a more specific implementation, the editing panel can automatically refresh after a state switch, displaying only controls related to the target grid view-level editing, so that the user can directly adjust the display length, axis number position, axis number visibility, and axis visibility in the current view.

[0056] The method for modifying BIM linked model data provided in this embodiment can identify the object to be edited before performing view-level editing, then clarify the current editing scope and scope of influence to the user through prompts, and provide the user with operation entry points corresponding to the grid view data through the editing panel. This makes the view-level editing process of the target grid more intuitive and controllable, reduces the risk of users mistakenly interpreting view-level modifications as model-level modifications, and improves the editing efficiency and operational accuracy of linked model grids in the current view.

[0057] Optionally, in one embodiment, the step of modifying the grid view data corresponding to the current view in the second data area in response to an editing operation on the grid includes: receiving a display / hide control operation on the axis of the target grid through an axis display / hide editing control, and determining the display / hide state of the axis in the current view; receiving a length control operation on the axis through an axis length editing control, and determining the display length of the axis in the current view; receiving a display / hide control operation on the axis number of the target grid through an axis number display / hide editing control, and determining the display / hide state of the axis number in the current view; receiving a position control operation on the axis number through an axis number position editing control, and determining the display position of the axis number in the current view; and writing the determined display / hide state of the axis, the display length of the axis, the display / hide state of the axis number, and the display position of the axis number in the current view into the grid view data corresponding to the current view in the second data area.

[0058] Specifically, after the switch is complete, the editing panel automatically displays the four key control elements of the view data. Among them, the axis visibility editing control is used to receive visibility control operations for the target axis grid to determine the visibility status of the axis in the current view. This visibility control operation can be triggered by the user by clicking the axis, toggling the visibility button, or selecting a local axis segment. Through the axis grid visibility function, the visibility of axes can be individually set for the current axis grid, taking effect only in the current view and unaffected by other views; the display range of the axis grid can also be adjusted using a clipping box to achieve visibility of local axes. In other words, the axis visibility editing control in this embodiment can correspond to the control entry point for overall axis visibility or visibility, or to the control entry point for local axis segment visibility. The operation results received through this control can form the axis visibility status data of the target axis grid in the current view.

[0059] The axis length editing control receives length control operations for axes to determine their displayed length in the current view. Length control operations may include, but are not limited to: selecting an axis endpoint and dragging it to a target position, or changing the displayed length of the axis in the current view through numerical input, dragging, or other methods. For example, selecting the right endpoint of axis A and dragging it to the target position can adjust the displayed length of the axis in the current view from 10m to 8m. This adjustment only modifies the axis length element in the view data, without changing the model data in linked documents or affecting other views. Furthermore, modifying the length does not change the position of the axis; it only modifies its length. Therefore, in this embodiment, the axis length editing control receives and determines the displayed length parameter of the target axis in the current view, rather than making a global modification to the model-level geometric datum.

[0060] The axis number display / hide editing control receives control operations for the display / hide of axis numbers in a target grid, determining the axis number's visibility status in the current view. This control operation can be, for example, selecting an axis number object under the grid display / hide function and clicking hide or show, or restoring visibility to a grayed-out axis number object. For instance, the A-axis number in the current view may be hidden, while the A-axis number in other views may still be displayed normally; to restore visibility, the operation can be repeated to make the grayed-out axis number object visible again. Therefore, the axis number display / hide editing control controls the display status of axis numbers in the current view, and its processing result belongs to view-level data.

[0061] The axis number position editing control receives position control operations for axis numbers to determine their display position in the current view. This position control operation can be achieved by clicking the axis number grip and adjusting its position. For example, selecting axis A, clicking the axis number grip, and modifying its position allows the axis number to be repositioned, and this modification only applies to the current view. Therefore, in this embodiment, the axis number position editing control can correspond to grip drag controls, offset adjustment controls, or position fine-tuning controls, all aimed at obtaining and determining the display position parameters of the axis numbers in the current view. Since this parameter is only written to the axis grid view data corresponding to the current view in the second data area, it will not cause changes to the axis number model data in the linked document.

[0062] After determining the visibility status of axes, their display length, the visibility status of axis numbers, and their display position in the current view, these parameters can be written into the grid view data corresponding to the current view in the second data area. Specifically, the corresponding record in the second data area can be located based on the current view identifier and the target grid identifier. If no corresponding record exists, a grid view data corresponding to the current view is first initialized based on the grid model data in the first data area, and then the determined view parameters are written into it. If a corresponding record already exists, the corresponding fields in the existing record are directly updated. After writing, the target grid in the current view is displayed according to the updated grid view data, while the target grid in other views is still displayed according to its respective view data or model data.

[0063] The method for modifying BIM linked model data provided in this embodiment can specifically implement grid editing in the view state to four types of implementable and controllable view parameters: axis visibility, length adjustment, axis number visibility, and axis number position adjustment. This allows for fine-tuning of the display effect of the target grid in the current view, while keeping the grid model data in the first data area unchanged. Thus, while ensuring the global consistency of the linked model, it further improves the flexibility, accuracy, and operability of grid display control in the current view.

[0064] Optionally, in one embodiment, the step of determining the target grid for the state to be switched in response to a selection operation on the grid includes: determining multiple target grids for the state to be switched in response to a selection operation on multiple grids, wherein the multiple target grids are parallel grids; the step of determining the display length of the grid in the current view by receiving a length control operation on the grid through the grid length editing control includes: receiving a batch adjustment operation on the grids of the multiple target grids through the grid length editing control to determine the target display length of the grid of each target grid in the current view; the step of writing the display length of the grid in the current view into the grid view data corresponding to the current view in the second data area includes: batch modifying the grid length data of the multiple target grids corresponding to the current view in the second data area according to the target display length.

[0065] Specifically, in this embodiment, the objects of batch adjustment are not arbitrary numbers of grid lines, but rather multiple parallel target grid lines. That is, before performing batch length adjustments, the user can first select multiple grid lines to be processed in the current view, thereby determining the multiple target grid lines whose states need to be switched. Limiting the multiple target grid lines to parallel grid lines helps ensure consistency and coordination in the graphic representation of the results after batch length adjustments. For example, in an architectural plan view, the user can select several parallel axes at once, treating these axes as the same batch of editing objects, thus avoiding the repetitive operations caused by adjusting each axis line individually.

[0066] After identifying multiple target grid lines, batch adjustment operations can be performed on the axes of these target grid lines using the axis length editing controls to determine the target display length of each target grid line in the current view. These batch adjustment operations can include, but are not limited to: dragging the endpoints of multiple parallel grid lines in a unified direction, entering a unified target length parameter in the batch editing panel, or synchronously adjusting the display range of multiple target grid lines using the group length adjustment controls. The result of the batch adjustment operation can be that multiple target grid lines have the same target display length; or, based on the relative relationship between the original display lengths of multiple target grid lines, their respective target display lengths are obtained on a unified adjustment basis. Regardless of the method used, the common point is that what is modified is the axis line display length in the current view, not the model-level axis line length in the linked document.

[0067] After determining the target display length of each target grid in the current view, the axis length data of multiple target grids corresponding to the current view in the second data area can be modified in batches according to the target display length. Specifically, based on the current view identifier and the object identifiers of each target grid, the data records corresponding to these target grids and the current view in the second data area can be located. For existing view data records, the axis length field can be directly updated. For target grids for which view data records have not yet been created, the corresponding view data records can be generated first based on the grid model data in the first data area, and then the target display length can be written into them. After batch writing is completed, multiple target grids in the current view can be displayed according to their updated axis length data, while the same grids in other views retain their original display effect, and the grid model data in the first data area remains unchanged. Thus, batch view-level length adjustment of multiple parallel grids can be achieved in the current view.

[0068] The method for modifying BIM linked model data provided in this embodiment enables batch view-level editing of multiple parallel grids, reducing repetitive work caused by operating each grid individually, while ensuring consistency and coordination in the length adjustment of multiple target grids in the current view, thereby further improving the editing efficiency and drawing adjustment efficiency of linked model grids in the current view.

[0069] Optionally, in one embodiment, the axis display / hide editing control includes a clipping frame. The step of receiving display / hide control operations for the axes of the target grid through the axis display / hide editing control and determining the display / hide state of the axes in the current view includes: receiving clipping frame adjustment operations for the target grid through the clipping frame to determine the target display range of the target grid in the current view; determining that local axis segments within the target display range of the target grid are visible, and local axis segments outside the target display range are hidden.

[0070] Specifically, in this embodiment, the clipping box can be used as a specific implementation of the axis display / hiding editing control to partially clip the display range of the target axis grid in the current view. That is, unlike setting the entire axis grid to be visible or hidden, this embodiment limits the target display range in the current view using the clipping box, thus allowing some axis segments in the target axis grid to continue to be displayed, while others are not displayed in the current view. This processing method still belongs to view-level editing, only affecting the current view, without changing the axis grid model data in the first data area, and without affecting the display results in other views.

[0071] Users can first select the target grid line already in view in the current view, and then enable the clipping box editing mode. The clipping box can correspond to a draggable, scalable, or repositionable graphic range object. By receiving adjustment operations on this clipping box, such as dragging the clipping box boundaries, scaling the clipping box size, or moving the clipping box position, the target display range of the target grid line in the current view can be determined. This target display range is used to define the area of ​​axis segments that are allowed to be displayed in the current view. Optionally, based on the spatial relationship between the clipping box and the target grid line, the portion of the axis segment falling within the clipping box range and the portion falling outside the clipping box range can be calculated, thereby providing a basis for subsequent local display and concealment control.

[0072] After determining the target display range, the local axis segments within the target display range are further defined as visible, while those outside the target display range are defined as hidden. In other words, this embodiment does not modify the overall geometric definition of the target grid, but rather sets the visibility of only local axis segments based on the display range control results in the current view. Specifically, the visibility results of the local axis segments can be written into the second data area as part of the grid view data corresponding to the current view, so that the target grid is displayed in the current view according to the adjusted display range, while the same grid in other views retains its original display state.

[0073] The method for modifying BIM linked model data provided in this embodiment can further refine the control of axis visibility from overall visibility to local display range control, so that the display effect of the linked model axis grid in the current view can better fit different professional views and different drawing requirements. At the same time, since only the view data in the second data area is modified, the global consistency of the axis grid model data in the linked document can still be guaranteed while improving the flexibility of drawing adaptation.

[0074] Optionally, in one embodiment, the method for modifying BIM linked model data further includes: in response to a second state switching operation for the grid, switching the grid from a view state to a model state; and when the grid is in the model state, controlling the grid in the current view to be displayed according to the grid model data in the first data area, while keeping the grid view data corresponding to the current view in the second data area unchanged.

[0075] Specifically, in this embodiment, the second state switching operation is used to return the target grid from the editable view state to the model state, which is uniformly displayed according to the model data, after view-level editing is completed. The second state switching operation can be triggered, for example, by the user selecting the target grid in the current view and then using a right-click menu, a state switching button, or other equivalent interactive commands. The second state switching operation, in conjunction with the aforementioned first state switching operation, constitutes a bidirectional switching mechanism between the model state and the view state.

[0076] After switching the grid system to model mode, the grid system in the current view can be displayed according to the grid model data in the first data area. In other words, in model mode, the target grid system in the current view is no longer displayed according to the view-level editing results in the second data area, but instead reverts to a display state consistent with the model data in the linked document. For example, if the axis length, axis number visibility, axis number visibility, or axis number position in the current view are adjusted in view mode, then after switching back to model mode, the immediate display of these view-level results in the current view can be restored to follow the grid model data in the first data area.

[0077] Meanwhile, in this embodiment, the grid view data corresponding to the current view in the second data area remains unchanged. "Remaining unchanged" here means that after performing the second state switching operation, the grid view data already saved in the current view is not deleted, cleared, or overwritten with model data; instead, the view data records previously formed in the view state are retained. This way, when the first state switching operation is performed again on the grid to re-enter the view state, the grid view data already saved in the current view can be called again, so as to inherit the previous view-level editing results.

[0078] The method for modifying BIM linked model data provided in this embodiment can achieve both the effect of instantly restoring the unified state of the model in the current view and continuing to save the existing view-level editing results. This allows users to flexibly switch between unified model display and local view editing at different design stages and avoid the operational burden caused by repeated editing.

[0079] Optionally, in one embodiment, the method for modifying BIM linked model data further includes: when the grid model data in the linked document corresponding to the BIM linked model is updated, updating the first data area while keeping the grid view data in the second data area unchanged; for grids in the model state, reading the updated grid model data from the first data area and synchronously updating the display of grids in the model state.

[0080] Specifically, in this embodiment, an update to the grid model data in the linked document refers to a modification of the basic grid data in the linked document corresponding to the external BIM model. For example, this could be a change in the axis line type, a change in grid spacing, or other model-level, global changes to the grid model data. For instance, opening the linked document, modifying the model data for axis A by changing the axis line type from solid to dashed and the grid spacing from 3m to 4m, saving and closing the linked document, and then returning to the current document and clicking "Update Link" triggers the linked model update synchronization process.

[0081] After detecting an update to the grid model data in the linked document, the first data area can be updated first. Since the first data area stores the grid model data of the BIM linked model, when the grid model data in the linked document changes, the first data area in the current document corresponding to that linked model should also be updated synchronously with the updated model data. Meanwhile, the grid view data in the second data area remains unchanged. That is, the view-level display control results already saved in the current document, such as axis lengths, axis number positions, axis number visibility, and axis visibility in the current view, will not be cleared or reset due to model-level updates in the linked document.

[0082] After the first data area is updated, for the grid lines in model mode, the updated grid line model data can be read from the first data area, and the display of the grid lines in model mode will be updated synchronously. In other words, for the grid lines in model mode in the current document, their display is directly refreshed based on the updated model data in the first data area. Therefore, once the model data in a linked document is updated, these grid lines in model mode will automatically display the updated results synchronously in the current document, without requiring the user to edit them one by one.

[0083] In one optional implementation, the status of each grid object in the current document can be identified first. Grid objects in the model state are added to the synchronous refresh queue, and their display is refreshed uniformly based on the updated model data in the first data area. For grid objects that have already saved the view-level display results in the second data area, their data in the second data area is not overwritten. In this way, after the model-level data is updated, it is possible to ensure that the display results in the model state reflect the latest linked document data in a timely manner, while continuing to retain the previously saved independent view-level settings.

[0084] The method for modifying BIM linked model data provided in this embodiment can automatically refresh the display results of the grid in the model state when the linked model is updated, and avoid overwriting the saved view-level editing results. This ensures timely synchronization of global data of the linked model while retaining the local view settings already formed in the current document, reducing the workload of repeated adjustments and improving the collaborative design efficiency after the BIM linked model is updated.

[0085] Example 2 Corresponding to Embodiment 1 above, Embodiment 2 of the present invention provides a device for modifying BIM linked model data. The corresponding technical features and effects are detailed in Embodiment 1 and will not be repeated here. This device is applied to a BIM model linking scenario, where the BIM linked model is a loaded external BIM model. Figure 3 This is a block diagram of the device for modifying BIM linked model data provided in Embodiment 2 of the present invention, as shown below. Figure 3 As shown, the device includes an interaction layer 301, a core logic layer 302, and a data layer 303. The core logic layer 302 includes a loading module 3021 and a processing module 3022. The data layer 303 includes a first data area 3031 and a second data area 3032.

[0086] Interaction layer 301 is used to provide users with operation entry points.

[0087] The core logic layer 302 includes a loading module 3021, which is used to load the grid of the BIM link model in the current document, wherein the grid has a model state and a view state.

[0088] The data layer 303 includes a first data area 3031 and a second data area 3032. The first data area 3031 is used to store the grid model data of the BIM link model, and the second data area 3032 is used to store the grid view data of the BIM link model. The grid view data corresponds to the view in the current document.

[0089] The core logic layer 302 further includes: a processing module 3022, configured to prohibit editing operations on the grid when it is in the model state; in the current view, in response to a first state switching operation on the grid in the current view, switch the grid from the model state to the view state; and when the grid is in the view state, in response to an editing operation on the grid, modify the grid view data corresponding to the current view in the second data area 3032 without changing the grid model data in the first data area 3031.

[0090] Optionally, in one embodiment, the step of switching the grid from a model state to a view state in response to a first state switching operation for the grid includes: determining a target grid to be switched state in response to a selection operation for the grid; switching the target grid from a model state to a view state in response to the first state switching operation for the target grid; outputting view editing prompts on the interactive interface; and displaying editing controls corresponding to the grid view data of the target grid in the editing panel.

[0091] Optionally, in one embodiment, the step of modifying the grid view data corresponding to the current view in the second data area in response to the editing operation on the grid includes: receiving a display / hide control operation on the axis of the target grid through an axis display / hide editing control, and determining the display / hide state of the axis in the current view; receiving a length control operation on the axis through an axis length editing control, and determining the display length of the axis in the current view; receiving a display / hide control operation on the axis number of the target grid through an axis number display / hide editing control, and determining the display / hide state of the axis number in the current view; receiving a position control operation on the axis number through an axis number position editing control, and determining the display position of the axis number in the current view; and writing the determined display / hide state of the axis, the display length of the axis, the display / hide state of the axis number, and the display position of the axis number in the current view into the grid view data corresponding to the current view in the second data area.

[0092] Optionally, in one embodiment, the step of determining the target grid for the state to be switched in response to the selection operation for the grid includes: determining multiple target grids for the state to be switched in response to the selection operation for multiple grids, wherein the multiple target grids are parallel grids; the step of determining the display length of the axis in the current view by receiving a length control operation for the axis through an axis length editing control includes: receiving a batch adjustment operation for the axes of the multiple target grids through an axis length editing control to determine the target display length of the axis of each target grid in the current view; the step of writing the display length of the axis in the current view into the grid view data corresponding to the current view in the second data area includes: batch modifying the axis length data of the multiple target grids corresponding to the current view in the second data area according to the target display length.

[0093] Optionally, in one embodiment, the axis display / concealment editing control includes a clipping frame. The step of receiving a display / concealment control operation for the axis of the target grid through the axis display / concealment editing control and determining the display / concealment state of the axis in the current view includes: receiving a clipping frame adjustment operation for the target grid through the clipping frame; determining the target display range of the target grid in the current view; and determining that local axis segments within the target display range of the target grid are visible, and local axis segments outside the target display range are hidden.

[0094] Optionally, in one embodiment, the processing module is further configured to: switch the grid from a view state to a model state in response to a second state switching operation for the grid; and when the grid is in the model state, control the grid in the current view to be displayed according to the grid model data in the first data area, and maintain the grid view data corresponding to the current view in the second data area unchanged.

[0095] Optionally, in one embodiment, the processing module is further configured to: update the first data area and keep the grid view data in the second data area unchanged when the grid model data in the linked document corresponding to the BIM linked model is updated; for grids in the model state, read the updated grid model data from the first data area and synchronously update the display of the grids in the model state.

[0096] Optionally, in one embodiment, the existing BIM software's model linking and grid management modules are extended to include a device for modifying BIM linked model data. The overall architecture is divided into three layers, each operating independently yet interconnected, adhering to the general dual-data state architecture requirements to ensure functional stability and compatibility, while precisely matching the control rules for the six core elements of the grid. The data layer is responsible for the storage and separate management of grid dual data (model data and view data), divided into a linked document data area (i.e., the first data area) and a current document data area (i.e., the second data area), strictly matching the control scope of the six core elements of the grid. The linked document data area stores grid model data, controlling axis length, axis number, axis number position, axis number visibility, axis visibility, and axis line type; it is read-only. The current document data area stores grid view data, controlling axis length, axis number position, axis number visibility, and axis visibility; it is read-write and bound to specific views; different views can save different grid view data, ensuring the local independence of view data.

[0097] The core logic layer comprises three main components: state switching logic, data isolation logic, and view data editing logic, closely aligned with the architecture design of a dual-data-state grid system. The state switching logic handles the switching between model and view states, synchronously triggering changes in data permissions and automatically matching the control scope of the corresponding data after the switch. The data isolation logic ensures that editing view data does not affect model data; modifications to model data (only within linked documents) synchronously update the basic grid display of the current document (all views). The view data editing logic handles specific editing operations such as visibility, length, and position, strictly limited to view data.

[0098] The interaction layer provides designers with intuitive operation entry points, including state switching buttons, view data editing panels, and grid selection tools. At the same time, the editing panel clearly distinguishes the control elements of model data and view data to avoid misoperation, which is in line with the design requirements of the architecture layer.

[0099] Example 3 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 4 As shown, the computer device 01 in this embodiment includes, but is not limited to, a memory 012 and a processor 011 that can be interconnected via a device bus. It should be noted that... Figure 4 Only a computer device 01 with component memory 012 and processor 011 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.

[0100] In this embodiment, the memory 012 (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, disk, optical disk, etc. In some embodiments, the memory 012 may be an internal storage unit of the computer device 01, such as the hard disk or memory of the computer device 01. In other embodiments, the memory 012 may also be an external storage device of the computer device 01, such as a plug-in hard disk, smart media card (SMC), secure digital (SD) card, flash card, etc., equipped on the computer device 01. Of course, the memory 012 may include both the internal storage unit and its external storage device of the computer device 01. In this embodiment, the memory 012 is typically used to store the operating system and various application software installed on the computer device 01, such as the program code of the device for modifying BIM linked model data in Embodiment 2. In addition, memory 012 can also be used to temporarily store various types of data that have been output or will be output.

[0101] In some embodiments, processor 011 may be a central processing unit (CPU), controller, microcontroller, microprocessor, or other data processing chip. Processor 011 is typically used to control the overall operation of computer device 01. In this embodiment, processor 011 is used to run program code stored in memory 012 or process data, such as methods for modifying BIM linked model data.

[0102] Example 4 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 application store, etc., which stores a computer program. When the program is executed by a processor, it implements the corresponding function. The computer-readable storage medium of this embodiment is used to store a device for modifying BIM linked model data, and when executed by a processor, it implements the method for modifying BIM linked model data of Embodiment 1.

[0103] 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.

[0104] The sequence numbers of the above embodiments of the present invention are for descriptive purposes only and do not represent the superiority or inferiority of the embodiments.

[0105] 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.

[0106] The above are merely preferred embodiments of the present invention and do not limit the scope of the patent. Any equivalent structural or procedural transformations made based on the description and drawings of the present invention, or direct or indirect applications in other related technical fields, are similarly included within the scope of patent protection of the present invention.

Claims

1. A method of modifying BIM-linked model data, characterized by, Applied to BIM model linking scenarios, where the BIM linking model is a loaded external BIM model, the method includes: Load the grid of the BIM link model in the current document. The grid has a model state and a view state. The first data area is used to store the grid model data of the BIM link model, and the second data area is used to store the grid view data of the BIM link model. The grid view data corresponds to the view in the current document. When the grid is in model state, editing operations on the grid are prohibited. In the current view, in response to a first state switching operation for the grid in the current view, the grid is switched from a model state to a view state, including: in response to a selection operation for the grid, determining a target grid whose state is to be switched; in response to a first state switching operation for the target grid, switching the target grid from a model state to a view state; outputting view editing prompts on the interactive interface; and displaying editing controls corresponding to the grid view data of the target grid in the editing panel. When the grid is in view state, in response to an editing operation on the grid, the grid view data corresponding to the current view in the second data area is modified without changing the grid model data in the first data area. This includes: receiving a display control operation on the axis of the target grid through an axis display / hide editing control to determine the display / hide state of the axis in the current view; receiving a length control operation on the axis through an axis length editing control to determine the display length of the axis in the current view; receiving a display control operation on the axis number of the target grid through an axis number display / hide editing control to determine the display / hide state of the axis number in the current view; receiving a position control operation on the axis number through an axis number position editing control to determine the display position of the axis number in the current view; and writing the determined display / hide state of the axis, the display length of the axis, the display / hide state of the axis number, and the display position of the axis number in the current view into the grid view data corresponding to the current view in the second data area.

2. The method for modifying BIM linked model data according to claim 1, characterized in that, The step of determining the target grid to be switched in response to the selection operation for the grid includes: determining a plurality of target grids to be switched in response to the selection operation for a plurality of grids, wherein the plurality of target grids are grids that are parallel to each other; The step of receiving a length control operation for the axis through an axis length editing control and determining the display length of the axis in the current view includes: receiving a batch adjustment operation for the axes of the plurality of target axis grids through an axis length editing control and determining the target display length of the axis of each target axis grid in the current view; The step of writing the display length of the axis in the current view into the grid view data corresponding to the current view in the second data area includes: batch modifying the axis length data of the multiple target grids corresponding to the current view in the second data area according to the target display length.

3. The method of claim 1, wherein, The axis display / hide editing control includes a clipping box. The step of receiving the display / hide control operation for the axis of the target grid through the axis display / hide editing control and determining the display / hide state of the axis in the current view includes: The clipping frame receives clipping frame adjustment operations for the target grid, and the target display range of the target grid in the current view is determined. Local axis segments within the target display range of the target axis grid are determined to be visible, while local axis segments outside the target display range are determined to be hidden.

4. The method of claim 1, wherein, The method further includes: In response to a second state switching operation for the grid, the grid is switched from a view state to a model state; and When the grid is in model state, the grid in the current view is controlled to be displayed according to the grid model data in the first data area, while the grid view data corresponding to the current view in the second data area remains unchanged.

5. The method of claim 1, wherein, The method further includes: When the grid model data in the linked document corresponding to the BIM linked model is updated, the first data area is updated while the grid view data in the second data area remains unchanged. For a grid in model state, the updated grid model data is read from the first data area, and the display of the grid in model state is updated synchronously.

6. An apparatus for modifying BIM-linked model data, characterized by Applied to BIM model linking scenarios, where the BIM linking model is a loaded external BIM model, the device includes: The interaction layer is used to provide users with access points for operations; The core logic layer includes a loading module for loading the grid of the BIM linked model in the current document, wherein the grid has a model state and a view state; The data layer includes a first data area and a second data area. The first data area is used to store the grid model data of the BIM link model, and the second data area is used to store the grid view data of the BIM link model. The grid view data corresponds to the view in the current document. The core logic layer further includes: a processing module, configured to: prohibit editing operations on the grid when it is in model state; in the current view, in response to a first state switching operation on the grid in the current view, switch the grid from model state to view state; and when the grid is in view state, in response to an editing operation on the grid, modify the grid view data corresponding to the current view in the second data area without changing the grid model data in the first data area, including: in response to a selection operation on the grid, determining a target grid whose state is to be switched; in response to a first state switching operation on the target grid, switching the target grid from model state to view state; outputting view editing prompts on the interactive interface; and displaying grid view data corresponding to the target grid in the editing panel. The corresponding editing controls receive display / hide control operations for the axes of the target grid through the axis display / hide editing control, determining the display / hide state of the axes in the current view; receive length control operations for the axes through the axis length editing control, determining the display length of the axes in the current view; receive display / hide control operations for the axis numbers of the target grid through the axis number display / hide editing control, determining the display / hide state of the axis numbers in the current view; and receive position control operations for the axis numbers through the axis number position editing control, determining the display position of the axis numbers in the current view. The determined display / hide state of the axes, the display length of the axes, the display / hide state of the axis numbers, and the display position of the axis numbers in the current view are written into the grid view data corresponding to the current view in the second data area.

7. A computer device comprising a memory, a processor, and a computer program stored on the memory and executable on the processor, characterized in that, When the processor executes the computer program, it implements the steps of the method according to any one of claims 1 to 5.

8. A computer readable storage medium having stored thereon a computer program, 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