CN117171866B - Building information model data management method, system and medium based on Rhinoceros - Google Patents

Building information model data management method, system and medium based on Rhinoceros Download PDF

Info

Publication number
CN117171866B
CN117171866B CN202311452509.5A CN202311452509A CN117171866B CN 117171866 B CN117171866 B CN 117171866B CN 202311452509 A CN202311452509 A CN 202311452509A CN 117171866 B CN117171866 B CN 117171866B
Authority
CN
China
Prior art keywords
information
data
json
attribute
level
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Active
Application number
CN202311452509.5A
Other languages
Chinese (zh)
Other versions
CN117171866A (en
Inventor
张静
张�成
梁逍
孙浩
高飞
姜卓
刘乔
李斌
朱驰浩
王强
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
China Southwest Architectural Design and Research Institute Co Ltd
Original Assignee
China Southwest Architectural Design and Research Institute Co Ltd
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by China Southwest Architectural Design and Research Institute Co Ltd filed Critical China Southwest Architectural Design and Research Institute Co Ltd
Priority to CN202311452509.5A priority Critical patent/CN117171866B/en
Publication of CN117171866A publication Critical patent/CN117171866A/en
Application granted granted Critical
Publication of CN117171866B publication Critical patent/CN117171866B/en
Active legal-status Critical Current
Anticipated expiration legal-status Critical

Links

Landscapes

  • Management, Administration, Business Operations System, And Electronic Commerce (AREA)

Abstract

The invention discloses a building information model data management method, a system and a medium based on Rhinoceros, which are used for establishing a multi-level and multi-class data standard system according to the depth requirement of a country or a place on model unit attribute information in a building information model delivery standard; creating a data dictionary for reflecting attribute information based on the data standard system, binding the data dictionary with a building information model object, and storing and managing the attribute information; and carrying out file format conversion on the attribute information, and deriving attribute values of the attribute information in various file formats on the Rhinoceros, wherein the file formats comprise Json and Csv. The method can store and manage the building information model data in a hierarchical and classified mode on the Rhinoceros, can derive the Json format file to meet the transmission requirement of a building information model system management platform, and is more in line with project management requirements and convenient to use.

Description

Building information model data management method, system and medium based on Rhinoceros
Technical Field
The invention belongs to the field of building information model management, and particularly relates to a building information model data management method, system and medium based on Rhinoceros.
Background
The Rhinoceros is three-dimensional modeling software based on Nurbs, is widely applied to the fields of building design, industrial manufacturing, mechanical design, scientific research and the like, can efficiently create various fine and complex 3D Nurbs models, can output different formats of 3dm, obj, fbx, stl and the like, is suitable for almost all 3D software, and has obvious effect on improving modeling productivity.
Rhinoceros provides a Key-Value Store (KVS) system that facilitates a user to add attribute information, such as manufacturing date, material information, size, etc., to a model component based on the data and label categories that they provide. A Key-Value Store (KVS) is one of the non-relational databases (nosqls) that uses simple Key-Value pairs (Key-Value) to Store and retrieve data. In a Key-Value store system, each data item consists of a unique Key (Key) and an associated Value (Value). This data model is similar to a dictionary or mapping structure, where each key corresponds to a value. In this way, rhinoceros helps the user quickly identify a particular portion of the model. The desired content is located in a large model by assigning meaningful names or labels to the objects. Ensuring that team members can accurately understand the different parts of the model.
When using Rhinoceros software to add attribute information to Building Information Model (BIM) components, it is necessary to add keys (keys), values (values) to the model components in the "custom attribute text" of the "attribute" toolbar, associate the attribute information with the model components and store them, and also allow the output of the table file of. Txt or.csv.
However, the development and application of the traditional Rhinoceros software have the following problems:
(1) The information input mode is single, the attribute Value cannot be preset, the Rhinoceros only provides the Key Value pair (Key-Value) to add attribute information for Building Information Model (BIM) components, and for different model components, the corresponding Key (Key) and Value (Value) need to be input again. Because the building information model contains the whole process data information from design to construction of the whole life cycle, the information data volume is huge, and the mode of inputting attribute information for the model component by a Key Value pair (Key-Value) has the problems of long time consumption, more repeated operation and large manpower loss.
(2) The attribute information is lack of standardization and difficult to manage in stages and categories, the attribute information contained in the Building Information Model (BIM) has complex relation and structure, the attribute information of a corresponding level is added to the Building Information Model (BIM) according to the requirements of countries or places on the delivery standards of the building information model, different construction stages (such as design stages, construction stages and the like) of projects, the attribute information to be added cannot be input and managed in stages and categories in the existing Key Value pair (Key-Value) mode, so that the information data is tedious and disordered, and the difficulty of later review and use of the information data is increased.
(3) The Key-Value Store (KVS) system provided by Rhinoceros can only export entered attribute information without supporting JSON format output, and the JSON (JavaScript Object Notation) format cannot be directly output in the. Txt or.csv format. The JSON format can use arrays and nested objects to construct complex data structures that can be conveniently represented by Building Information Model (BIM). JSON is applied to transmission and sharing of structured data as a lightweight, easily parsed data exchange format by the Building Information Model (BIM) collaborative management platform commonly found in the market, such as: the method comprises the following steps of applying the construction method to the construction equipment, wherein the application scenarios comprise attribute and geometric information of the components, project planning and progress data, construction progress and state updating, material and equipment list, design change and problem tracking, simulation and analysis results and the like.
Disclosure of Invention
The invention aims to secondarily develop the existing Rhinoceros software, and provides a Rhinoceros-based building information model data management method, a Rhinoceros-based building information model data management system and a Rhinoceros-based building information model data management medium, wherein a multi-level and multi-class data standard system is established, and input specifications are set, so that all participants of an project can acquire required attribute information from a building model when the project progresses along with the project, and the attribute information can be shared and updated in the whole period of the project; the Json format file with the complex nested structure can be exported, so that the analysis of the building information model on the building information model collaborative management platform is facilitated.
In order to achieve the above object, the present invention provides the following technical solutions:
a building information model data management method based on Rhinoceros comprises the following steps:
establishing a multi-level and multi-category data standard system;
creating a data dictionary for reflecting attribute information based on the data standard system, and binding the data dictionary and the building information model object;
traversing the data dictionary of the building information model object, converting file formats, and deriving attribute values of the attribute information in various file formats on the Rhinoceros, wherein the file formats comprise Json and Csv.
As a preferable scheme of the invention, the data standard system comprises a first level, a second level, a third level and a fourth level, which are sequentially corresponding to a planning stage, a design stage, a construction stage and an operation and maintenance stage of the project.
As a preferred aspect of the present invention, the first hierarchy includes item information, identity information, and location information; the project information comprises project identification, construction description, engineering and other categories, technical economic indexes, design description, construction unit information and construction participant information; the identity information comprises basic description and coding information; the positioning information comprises subordinate positioning, coordinate positioning and occupation size.
As a preferred aspect of the present invention, the second hierarchy includes system information and technology information; the system information comprises system classification and association relation; the technical information comprises construction size, component constitution, design parameters and technical requirements.
As a preferred embodiment of the present invention, the third level includes construction information; the building information comprises civil construction, greening construction and electromechanical equipment installation.
As a preferred aspect of the present invention, the fourth hierarchy includes asset information and maintenance information; the asset information includes asset registration, asset management; the maintenance information comprises inspection information, maintenance prediction and spare parts.
As a preferred scheme of the present invention, the specific steps of binding the data dictionary and the building information model object include: and storing the data hierarchical level and the data classification recorded according to the data standard system into the corresponding positions of the data dictionary, and then attaching the data dictionary to the appointed model object.
As a preferred embodiment of the present invention, the specific step of deriving the attribute information in the Json format includes: and constructing a Json export object, storing attribute values of attribute information bound with the building information model object in the Json export object according to the hierarchy and the category of the attribute values in the data standard system to obtain a character string in a Json format conforming to the data standard system, and exporting a file in the Json format on the Rhinoceros.
Based on the same conception, a building information model data management system based on Rhinoceros is also provided, comprising:
the data standardization module is used for establishing a multi-level and multi-category data standard system;
the attribute information binding module is used for creating a data dictionary, attaching the input attribute information to the specified model object and completing the binding of the attribute information and the building information model;
the attribute information management module is used for registering the response of the event monitor to the model and attribute information panel operation events and monitoring on the Rhinoceros, and completing the calling and updating of the attribute information when the creation, modification and storage operation of the attribute information are executed;
and the file format export module is used for exporting the attribute information from the Rhinoceros into files with various formats, wherein the file formats comprise Json and Csv.
Based on the same conception, a building information model data management medium based on Rhinoceros is also provided, comprising at least one processor and a memory in communication connection with the at least one processor; the memory stores instructions executable by the at least one processor to enable the at least one processor to perform a Rhinoceros-based building information model data management method of any of the above.
Compared with the prior art, the invention has the beneficial effects that:
according to the invention, secondary development is carried out on original Rhinoceros software, a data standard system is established, and a user is standardized to input and manage attribute information in stages and in different categories, so that all participants of a project can directly acquire information required by each participant and share and update the attribute information in the whole period of the project without frequently consulting relevant national and local standards, the redundancy and disorder of information data are avoided, and the problems of great difficulty in later consulting and application of the information data are solved; the invention establishes a data standardization system for attribute information and binds the attribute information and the building information model object, so that a Json format file with a specific complex nested structure can be exported in the Rhinoceros software, and the analysis of a building information model in a building information model coordination management platform is greatly facilitated.
Drawings
Fig. 1 is a flow chart of a building information model data management method based on Rhinoceros in embodiment 1 of the present invention;
FIG. 2 is a flowchart of a registration event listener according to embodiment 2 of the present invention;
FIG. 3 is a schematic flow chart of registering document operation event according to embodiment 2 of the present invention;
fig. 4 is a flowchart illustrating a registration object operation event according to embodiment 2 of the present invention.
Detailed Description
The present invention will be described in further detail with reference to test examples and specific embodiments. It should not be construed that the scope of the above subject matter of the present invention is limited to the following embodiments, and all techniques realized based on the present invention are within the scope of the present invention.
Example 1
The building information model data management method based on the Rhinoceros as shown in fig. 1 comprises the following steps:
establishing a multi-level and multi-category data standard system according to the information level of model units in the national or local building information model delivery standard and the project plan;
specifically, the data standard system divides the attribute information of the building information model into 4 layers and 7 categories, which are respectively:
the first-level information hierarchy, with the code LOI-100, corresponds to the project planning stage and comprises project information PJ, identity information ID, positioning information LC and 3 major categories. The project information PJ comprises a PJ-100 project identifier, a PJ-200 construction description, a PJ-300 engineering and other categories, a PJ-400 technical and economic index, a PJ-500 design description, PJ-600 construction unit information and PJ-700 construction participant information; the identity information ID comprises ID-100 basic description and ID-200 coding information; the positioning information LC includes LC-100 slave positioning, LC-200 coordinate positioning, LC-300 placeholder dimensions.
The second-level information level, the code LOI-200, corresponds to the project design stage and comprises the major categories of system information ST and technical information TC, 2. Wherein, the system information ST comprises ST-100 system classification and ST-200 association relation; technical information TC includes TC-100 construction dimensions, TC-200 component construction, TC-300 design parameters, and TC-400 specifications.
The three-level information level, with the code LOI-300, corresponds to the project construction stage and comprises building information CS and 1 major class. Wherein CS-100 civil construction, CS-200 greening construction and CS-3 electromechanical equipment installation.
Four-level information hierarchy, code LOI-400, corresponding to project operation and maintenance stage, asset information AM, maintenance information FM,2 categories. Wherein the asset information AM comprises AM-100 asset registration and AM-200 asset management; the maintenance information FM comprises FM-100 inspection information, FM-200 maintenance information, FM-300 maintenance prediction and FM-400 spare parts.
The method comprises the steps of establishing a multi-level and multi-class data standard system for a building information model, wherein the data standard system not only comprises all attribute information required by the whole project, but also layers the attribute information according to the project stage in which the attribute information is positioned, and further classifies the attribute information of each layer.
Meanwhile, in the prior art, project management personnel are required to endow attribute information for the building information model through a mode of manually inputting key value pairs, and due to lack of the specification of a data standard system, the types, names, units and filling modes of information input by different personnel are extremely non-uniform, so that information data are tedious and disordered, and further the difficulty of later consulting and using the information data is increased.
In order to effectively store and manage attribute information data of the building information model, after the data standard system is established, an input specification is set, and a function that a user can edit and import by himself is established.
Specifically, according to the data characteristics of the attribute information category, the input and preset modes of different types of attribute information are confirmed, wherein the input and preset modes comprise a completely self-defined text, list options, a digital progress bar and the like. The original Rhinoceros software only provides a key value pair mode to construct and add attribute information for a building information model, corresponding keys and values are needed to be input again for different model components, the building information model contains whole-process data information from design to construction of a full life cycle, the information data amount is huge, the mode of inputting attribute information for the model components by the key value pair mode consumes a long time and contains a large number of repeated operations, the labor loss is great, the embodiment creates a friendly attribute information panel in Rhinoceros software according to the established data standard system of the attribute information, and corresponding elements, icons, buttons, text boxes, menus and the like are added for a user UI component in Rhinoceros software through a custom toolbar in a toolbar manager, so that a user can conveniently execute operations, input data or acquire information through the elements, and input information can be managed in a hierarchical and classified mode.
The embodiment creates a custom class inherited to the 'rhino.PlugIns' class, instantiates the attribute information panel by rewriting the 'OnLoadPlugIn' method and adds the attribute information panel to the easy-to-access area on the Rhinoceros operation interface, thereby facilitating the easy access of the panel function by the user.
After entering information according to the data standard system specification of the attribute information, a data Dictionary for embodying the attribute information is created in the rhinocommon api 'UserData', wherein the data Dictionary is Dictionary < string, object > type, wherein string is a unique identifier for identifying a value associated therewith, and object is any data type associated with the identification. In this embodiment, string represents all attribute names contained in LOI-100 through LOI-400; the object represents the attribute value corresponding to the object, and if string is greenfield rate, the object is any value of 0-100%.
Information input or selected by the user on the attribute information panel is acquired by accessing the ' Text ' attribute in the Text box ', and the data is saved to a corresponding location of the data dictionary. The data dictionary is attached to the specified model object by using the rhinoobject. In 'UserData', by rewriting the 'Serialize' and 'Deserialize' methods, serialization and deserialization between the user data dictionary and the building information model are facilitated, ensuring that the data dictionary is correctly stored and loaded in the model. The data dictionary bound with the model object is acquired through the method of 'GetUserText', and the acquired data dictionary is displayed at a proper position on a user attribute panel by using 'Label', so that a user can intuitively view custom data information associated with the model.
Specifically, when the software is applied, the step of storing and managing the attribute information includes: registering on Rhinoceros an event listener monitors and responds to model and attribute information panel operation events, completing the invocation and updating of attribute information when executing creation, modification and storage operations of the attribute information.
In the event of the monitor object export, when the user triggers the export operation on the attribute panel, the software provides two export format options, namely an export Json format and an export Csv format.
Specifically, the specific step of deriving the Json format includes: the Userdata of the object is converted to a string in Json format by using the newtonsft. The specific method is that a model object with Userdata data is obtained through a custom function of GetObjectWithUserData', and an empty dictionary is created, namely: and constructing a Json export object, storing attribute values of attribute information bound with the model object in the Json export object according to the hierarchy and the category of the Json export object, serializing the Json export object into a string in a JSON format by using a JSOnConvertet. SerialzeObject method of a Json. NET library, and storing the string in a JSON variable.
The reason that the newtonsft.json library is selected to perform Serialization operation on Userdata data is that the json.net library supports data structures such as nested objects, sets and dictionaries with complicated hierarchical relationships and complicated category building information model attribute relationship expression, meanwhile, when the data structures are serialized by using the 'Serialization' method, the values of the 'formatting.induced' parameters are set as tube, the generated Json character string can be formatted in a more readable manner, including indentation, line-changing and space, so that the Json character string is more readable, the created data standard system comprises a data structure with a multi-hierarchical relationship, neither csv nor txt can effectively and intuitively represent the data structures, and the Json format can use the arrays and the nested objects to construct the complicated data structure, so that the complicated data structure can be conveniently represented. When the Building Information Model (BIM) collaborative management platform analyzes the building information model, the csv or txt document cannot be directly read, but the Json format file can be directly read.
Specifically, the specific steps of deriving the derived Csv format include: the method for exporting the Json format is the same as the method for exporting the Json format, firstly, a model object with Userdata is obtained through a custom function of 'GetObjectWithUserData', a file stream is created by using 'streamWriter', the user data is used for writing the Userdata into a Csv file, an object list of the Userdata is traversed, and Description and conversion of the Userdata into data in a CSV format are written into the CSV file through a method of 'Description' and 'ToCsv'.
Example 2
A Rhinoceros-based building information model data management system comprising:
the data standardization module is used for establishing a multi-level and multi-category data standard system;
the attribute information binding module is used for creating a data dictionary, attaching the input attribute information to the specified model object and completing the binding of the attribute information and the building information model;
the attribute information management module is used for registering the response of the event monitor to the model and attribute information panel operation events and monitoring on the Rhinoceros, and completing the calling and updating of the attribute information when the creation, modification and storage operation of the attribute information are executed;
specifically, the workflow of the attribute information management module includes:
the event monitor is registered according to the flow shown in fig. 2, in the event monitor is registered according to the flow shown in fig. 3, the document operation event is registered according to the flow shown in fig. 4, the operation event of the model and attribute information panel is monitored and responded through the event monitor, when the user performs operations such as selecting, deselecting, modifying, losing selecting, saving, reading, exporting and the like, the corresponding event is triggered, and a predefined event processor, namely a callback function, is called, so that predefined operations are executed.
Specifically, when the user selects the model object in the event of searching and creating UserData of the object and monitoring object selection, the software checks whether data exists in 'UserData' of the model object. One model object is selected through the 'GetObject' function, and the ID thereof is acquired, whether data exists in 'UserData' of the object is checked through 'check_userdata_exists', and if so, the data is extracted through 'getuserstext' and displayed on the attribute information panel. If not, a new data dictionary is created in 'UserData' and attached to the model object; when the user modifies the numerical value or the content on the control of the attribute information panel, the modified control value is written back to userdta of the object through a custom function of 'update_userdata_from_control_value'. The goal of this process is to achieve automatic updating. When the user modifies the values of the controls, the program will automatically update these values into UserData for the object without manual intervention by the user; when the object is not selected, updating the Userdata of the object when the object is in a non-selected state through a custom function of 'update_userdata_on_deselect'. The program first obtains the currently selected objects, then traverses the objects, examines the Userdata of each object, and writes the data back to the Userdata of the object. In this step, the 'EnableRedraw' function will be used to control the automatic redraw function of Rhinoceros, so that disabling redrawing can reduce interface flicker and improve update efficiency when multiple Userdata updates are performed. The 'EnableRedraw' is controlled by a Boolean value, and when the user data is updated, an automatic redrawing function is started by setting a parameter value to be Ture.
Specifically, when the user stores the attribute information on the attribute information panel and writes the attribute information in the model object or reads the attribute information in the model object in the event of storing and reading the Userdata of the object, the program sequences or deserializes the data format in the Userdata into a sustainable storage and transmission data format. In Rhinoceros, serialization and deserialization operations are performed using a binary file I/O tool (input/output) provided by software. The specific operation is that firstly, data in Userdata is stored in the data dictionary through 'rho. Collection. Archbledictionary', then the data is written into a model object in a binary format by using a 'binaryarchevewriter' tool, and the reverse serialization is that a binary format file in the model object is Read by using a 'binaryarchevereader', and the data in the file is Read by using a 'Read' method.
And the file format export module is used for exporting the attribute information from the Rhinoceros into files with various formats, wherein the file formats comprise Json and Csv.
The foregoing description of the preferred embodiments of the invention is not intended to be limiting, but rather is intended to cover all modifications, equivalents, and alternatives falling within the spirit and principles of the invention.

Claims (3)

1. A building information model data management method based on Rhinoceros is characterized by comprising the following steps:
establishing a multi-level and multi-category data standard system;
the data standard system comprises a first level, a second level, a third level and a fourth level, which are sequentially corresponding to a planning stage, a design stage, a construction stage and an operation and maintenance stage of the project;
the first hierarchy includes item information, identity information, and positioning information; the project information comprises project identification, construction description, engineering grade, technical economic index, design description, construction unit information and construction participant information; the identity information comprises basic description and coding information; the positioning information comprises subordinate positioning, coordinate positioning and occupation size;
the second hierarchy includes system information and technology information; the system information comprises system classification and association relation; the technical information comprises construction size, component constitution, design parameters and technical requirements;
the third level includes as-built information; the building information comprises civil construction, greening construction and electromechanical equipment installation;
the fourth level includes asset information and maintenance information; the asset information includes asset registration, asset management; the maintenance information comprises inspection information, maintenance prediction and spare parts;
creating a data dictionary for reflecting attribute information based on the data standard system, storing the data hierarchical level and the data classification recorded according to the data standard system into corresponding positions of the data dictionary, and then attaching the custom data dictionary to a specified model object;
the creating step of the data dictionary comprises the following steps: creating a data Dictionary for embodying attribute information in the rhinocommon api 'UserData', the data Dictionary being Dictionary < string, object > type, wherein string is a unique identifier for identifying a value associated therewith, object being any data type associated with the identification;
traversing a data dictionary of the building information model object, converting file formats, and deriving attribute values of the attribute information in various file formats on the Rhinoceros, wherein the file formats comprise Json and Csv;
the specific steps of deriving the attribute information in the Json format include: constructing a Json export object, storing attribute values of attribute information bound with the building information model object in the Json export object according to the level and the category of the attribute values in the data standard system to obtain a Json format character string conforming to the data standard system, and exporting a Json format file on the Rhinoceros;
the step of converting the attribute value into a Json variable comprises: creating the data Dictionary in a rhinoCommonAPI 'UserData', the data Dictionary being of Dictionary < string, object > type, wherein string is a unique identifier identifying a value associated therewith, object being any data type associated with the identification; attaching the data dictionary to a specified building information model object by using a rhinoobject.attributes.userData.add method to finish binding of attribute information and a building information model; obtaining a model object with Userdata data through a custom function of 'GetObjectWithUserData', and constructing a Json export object, wherein the Json export object is initially empty of the data dictionary, attribute values of attribute information bound with a building information model object are stored in the Json export object according to the level and the category of the attribute values in the data standard system, and the Json export object is serialized into a character string in Json format by using a Json convert. Seriizer object method of a Json. Net library and is stored in Json variables.
2. A system for managing building information model data based on Rhinoceros, comprising:
the data standardization module is used for establishing a multi-level and multi-category data standard system;
the data standard system comprises a first level, a second level, a third level and a fourth level, which are sequentially corresponding to a planning stage, a design stage, a construction stage and an operation and maintenance stage of the project;
the first hierarchy includes item information, identity information, and positioning information; the project information comprises project identification, construction description, engineering grade, technical economic index, design description, construction unit information and construction participant information; the identity information comprises basic description and coding information; the positioning information comprises subordinate positioning, coordinate positioning and occupation size;
the second hierarchy includes system information and technology information; the system information comprises system classification and association relation; the technical information comprises construction size, component constitution, design parameters and technical requirements;
the third level includes as-built information; the building information comprises civil construction, greening construction and electromechanical equipment installation;
the fourth level includes asset information and maintenance information; the asset information includes asset registration, asset management; the maintenance information comprises inspection information, maintenance prediction and spare parts;
the attribute information binding module is used for creating a data dictionary for representing attribute information based on the data standard system, storing the data classification level and the classification category input according to the data standard system into the corresponding positions of the data dictionary, and then attaching the custom data dictionary to a specified model object;
the creating step of the data dictionary comprises the following steps: creating a data Dictionary for embodying attribute information in the rhinocommon api 'UserData', the data Dictionary being Dictionary < string, object > type, wherein string is a unique identifier for identifying a value associated therewith, object being any data type associated with the identification;
the file format export module is used for traversing the data dictionary of the building information model object and converting file formats, and exporting attribute values of the attribute information in various file formats on the Rhinoceros, wherein the file formats comprise Json and Csv;
the specific steps of deriving the attribute information in the Json format include: constructing a Json export object, storing attribute values of attribute information bound with the building information model object in the Json export object according to the level and the category of the attribute values in the data standard system to obtain a Json format character string conforming to the data standard system, and exporting a Json format file on the Rhinoceros;
the step of converting the attribute value into a Json variable comprises: creating the data Dictionary in a rhinoCommonAPI 'UserData', the data Dictionary being of Dictionary < string, object > type, wherein string is a unique identifier identifying a value associated therewith, object being any data type associated with the identification; attaching the data dictionary to a specified building information model object by using a rhinoobject.attributes.userData.add method to finish binding of attribute information and a building information model; obtaining a model object with Userdata data through a custom function of 'GetObjectWithUserData', and constructing a Json export object, wherein the Json export object is initially empty of the data dictionary, attribute values of attribute information bound with a building information model object are stored in the Json export object according to the level and the category of the attribute values in the data standard system, and the Json export object is serialized into a character string in Json format by using a Json convert. Seriizer object method of a Json. Net library and is stored in Json variables.
3. A Rhinoceros-based building information model data management medium comprising at least one processor and a memory communicatively coupled to the at least one processor; the memory stores instructions executable by the at least one processor to enable the at least one processor to perform a rhenoceros-based building information model data management method of claim 1.
CN202311452509.5A 2023-11-03 2023-11-03 Building information model data management method, system and medium based on Rhinoceros Active CN117171866B (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
CN202311452509.5A CN117171866B (en) 2023-11-03 2023-11-03 Building information model data management method, system and medium based on Rhinoceros

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
CN202311452509.5A CN117171866B (en) 2023-11-03 2023-11-03 Building information model data management method, system and medium based on Rhinoceros

Publications (2)

Publication Number Publication Date
CN117171866A CN117171866A (en) 2023-12-05
CN117171866B true CN117171866B (en) 2024-02-23

Family

ID=88947308

Family Applications (1)

Application Number Title Priority Date Filing Date
CN202311452509.5A Active CN117171866B (en) 2023-11-03 2023-11-03 Building information model data management method, system and medium based on Rhinoceros

Country Status (1)

Country Link
CN (1) CN117171866B (en)

Citations (7)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
KR101885089B1 (en) * 2017-01-26 2018-08-03 홍익대학교세종캠퍼스산학협력단 Excel export method for bim design files
US11119990B1 (en) * 2020-04-14 2021-09-14 Bank Of America Corporation Systems for extracting data from XML-based digital process automation and management platforms to databases
CN114139261A (en) * 2021-12-02 2022-03-04 浙江华东工程数字技术有限公司 Method and system for standard programming of BIM model data
CN115713161A (en) * 2022-11-25 2023-02-24 深圳市佳泰业建设有限公司 Building information management system based on BIM technology
CN115774893A (en) * 2022-10-25 2023-03-10 中国铁道科学研究院集团有限公司电子计算技术研究所 Railway full-life-cycle multi-source data integration correlation method, system and storage medium
CN116126809A (en) * 2023-04-19 2023-05-16 中亿丰数字科技集团有限公司 Building information model data storage conversion method based on national standard
CN116720243A (en) * 2023-05-25 2023-09-08 中铁工程设计咨询集团有限公司 Building information model processing method and device

Patent Citations (7)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
KR101885089B1 (en) * 2017-01-26 2018-08-03 홍익대학교세종캠퍼스산학협력단 Excel export method for bim design files
US11119990B1 (en) * 2020-04-14 2021-09-14 Bank Of America Corporation Systems for extracting data from XML-based digital process automation and management platforms to databases
CN114139261A (en) * 2021-12-02 2022-03-04 浙江华东工程数字技术有限公司 Method and system for standard programming of BIM model data
CN115774893A (en) * 2022-10-25 2023-03-10 中国铁道科学研究院集团有限公司电子计算技术研究所 Railway full-life-cycle multi-source data integration correlation method, system and storage medium
CN115713161A (en) * 2022-11-25 2023-02-24 深圳市佳泰业建设有限公司 Building information management system based on BIM technology
CN116126809A (en) * 2023-04-19 2023-05-16 中亿丰数字科技集团有限公司 Building information model data storage conversion method based on national standard
CN116720243A (en) * 2023-05-25 2023-09-08 中铁工程设计咨询集团有限公司 Building information model processing method and device

Also Published As

Publication number Publication date
CN117171866A (en) 2023-12-05

Similar Documents

Publication Publication Date Title
CN111460575B (en) Method for converting aircraft assembly process tree based on MBOM tree structure
US20230274045A1 (en) Building information modeling (bim)-based intelligent drafting method for prefabricated buildings
Abel et al. The systems integration problem
US8612397B2 (en) System and method for a computer based forms language
US7822795B2 (en) Apparatus and methods for displaying and determining dependency relationships among subsystems in a computer software system
CN116225429A (en) Pulling type component frame-based ipage webpage type low-code development platform
Cursi et al. Linking external knowledge to heritage BIM
CN104049957A (en) Rapid modeling frame of general business model based on star structure
CN112256238B (en) Modeled demand item management method based on FMEA
US20090049025A1 (en) System and method for harvesting service metadata from an architecture diagram into a metadata repository
Antović et al. Model and software tool for automatic generation of user interface based on use case and data model
CN116627418B (en) Multi-level form interface visual generation method and device based on recursion algorithm
Condotta et al. BIM-based method to inform operation and maintenance phases through a simplified procedure
CN108170855B (en) CityGML and IFC data unified query and data extraction method
Bai et al. Developing a common library of prefabricated structure components through graphic media mapping to improve design efficiency
Alzraiee Cost estimate system using structured query language in BIM
JP2022093293A (en) Online report preparation system using excel tool
CN111124938B (en) Method for generating componentized test case
CN111709601B (en) Data processing method and device
CN117171866B (en) Building information model data management method, system and medium based on Rhinoceros
US10140387B2 (en) Model for managing variations in a product structure for a product
CN116450110A (en) Automatic generation method and system for access codes of database based on custom attributes
Pantelios Development of a QGIS plugin for the CityGML 3D City Database
CN107844639B (en) Project standard structure automatic generation method and system
Pavan et al. Development of BIM Management System

Legal Events

Date Code Title Description
PB01 Publication
PB01 Publication
SE01 Entry into force of request for substantive examination
SE01 Entry into force of request for substantive examination
GR01 Patent grant
GR01 Patent grant