A method for generating a data converter, a data conversion method and apparatus

Abstract

The application discloses a data converter generation method, a data conversion method and a device, and the data converter generation method comprises the following steps: obtaining source data and target data, the source data is GFC data, and the target data is application data; at least one mapping relationship between the source data and the target data is established by using an auxiliary tool, and each mapping relationship corresponds to an association condition; at least one code logic is converted from the at least one mapping relationship; at least one data converter is generated by organizing and compiling the at least one code logic by using a data conversion framework, the data conversion framework supports data reading and writing in at least one format, and has an automatic code generation function. The data converter generated by the method can realize conversion between the source data and the target data, establish mapping and association between each product and the general standard GFC format, synchronously establish a standard format import, export and sharing mechanism, and realize model data sharing and intercommunication in the whole life cycle of BIM.

Description

TECHNICAL FIELD

[0001] The present application relates to the technical field of data processing, and in particular to a building engineering-based data converter generation method, data conversion method and device. BACKGROUND

[0002] As structured data, Building Information Modeling (BIM) has the advantages of visual display, convenient computer processing and the like, and brings a qualitative leap to engineering construction and information technology. Correspondingly, the engineering construction field needs a more complex and unified BIM data standard for model and data exchange in various scenarios.

[0003] At present, various BIM data standards used in the industry have different data formats due to various tool software, thus causing problems of unsmooth data exchange and data fragmentation. For example, based on the existing BIM data standard format on the market, the following categories are mainly divided:

[0004] First, the delivery format mainly based on a database file (Datebase, DB), mostly based on SQLite technology, which cannot be associated with drawings. Second, the delivery format mainly based on a data compression file format (ZIP), mostly a compressed package containing DB files, drawings and other contents. This type of format file delivery results are mixed, and there is no connection between them, only file format packaging and encapsulation. Third, the delivery format mainly based on Industry Foundation Classes (IFC), mostly complying with the IFC standard of the British Standards Institution (BSI), and also combining the recently released GB / T51447 standard, which is a relatively independent third-party BIM complete delivery, but it also has the problems of incomplete industry data and inability to associate drawings.

[0005] As can be seen, due to the certain differences between the above-mentioned various delivery format standards and the BIM application scenarios in the industry, the compatibility with other external standard systems is insufficient, so the standard cannot realize persistent storage, standard format import, export and sharing mechanism, and cannot meet the data application requirements of the whole project life cycle. SUMMARY

[0006] The present application discloses a data converter generation method, data conversion method and device for unifying data delivery format standards, thereby realizing the import, export and sharing of standardized format data. Specifically, the following technical solutions are disclosed:

[0007] In a first aspect, the embodiments of the present application disclose a method for generating a data converter, which comprises: obtaining source data and target data, wherein the source data is GFC data conforming to a digital building data exchange standard, and the target data is data conforming to an application data standard; establishing at least one mapping relationship between the source data and the target data by using an auxiliary tool, wherein each mapping relationship corresponds to an associated condition; converting the at least one mapping relationship into at least one code logic; and organizing and compiling the at least one code logic by using a data conversion framework to generate at least one data converter, wherein the data conversion framework supports data reading and writing in at least one format and has an automatic code generation function.

[0008] With reference to the first aspect, in a possible implementation manner of the first aspect, the establishing, by the auxiliary tool, of the at least one mapping relationship between the source data and the target data comprises: determining, by the auxiliary tool, a data object organization hierarchy; and establishing, according to the data object organization hierarchy, at least one mapping relationship between the source data and the target data in terms of components, attributes or attribute values.

[0009] With reference to the first aspect, in another possible implementation manner of the first aspect, the converting of the at least one mapping relationship into the at least one code logic comprises: analyzing, by a preprocessor, according to the at least one mapping relationship and in a preset target language, to obtain the at least one code logic, wherein the preprocessor comprises at least one of a component processor, an attribute processor, an attribute value processor and a geometric data processor.

[0010] Optionally, the at least one mapping relationship between the source data and the target data can comprise any one of the following: one source data corresponds to one target data; one source data corresponds to a plurality of target data; and a plurality of source data corresponds to a plurality of target data.

[0011] With reference to the first aspect, in still another possible implementation manner of the first aspect, before the obtaining of the source data, the method further comprises: formulating GFC data conforming to the data standard according to the GFC standard and an industry general model data format.

[0012] Optionally, the GFC data has a suffix *.gfc.

[0013] With reference to the first aspect, in a possible implementation of the first aspect, the GFC data conforming to the data standard is formulated according to the GFC standard and an industry common model data format, and includes: initiating standard creation work according to a version plan; editing and maintaining the data standard according to an application scenario; inheriting an association relationship between data in each version, generating standardized data of the association relationship and linkage update information; reviewing, answering questions of, and optimizing the standardized data to obtain a formal version of the GFC data; and publishing the formal version of the GFC data to associate and apply the GFC data with a product end.

[0014] Optionally, the content of the GFC data includes one or more of the following professions: architecture, structure, water supply and drainage, heating and ventilation, and electricity.

[0015] Optionally, the GFC data conforms to a GFC data business architecture, and the GFC data business architecture includes: project information, component classification, component attribute, space standard, and practice standard.

[0016] With reference to the first aspect, in a possible implementation of the first aspect, the method further includes: publishing the at least one mapping relationship; generating at least one mapping template according to the at least one mapping relationship; and performing import, export, and storage operations of source data or target data based on the at least one mapping template.

[0017] In the second aspect, an embodiment of the present application discloses a data conversion method, which is applied to the data converter in the first aspect or any possible implementation of the first aspect, and includes:

[0018] obtaining source data, wherein the source data is GFC data conforming to a digital building data exchange standard; determining a target converter in at least one data converter according to the GFC data, and converting the GFC data into target data by using the target converter, wherein the target data is data conforming to an application data standard, and the target converter contains a mapping relationship between the GFC data and the target data.

[0019] With reference to the second aspect, in a possible implementation of the second aspect, the conversion of the GFC data into the target data by using the target converter includes: converting the GFC data into the target data by using the target converter in a GFC standard format as an intermediate format.

[0020] In the third aspect, an embodiment of the present application discloses a data converter generation device, which includes:

[0021] An acquisition unit is configured to acquire source data and target data, the source data being GFC data conforming to a digital building data exchange standard, and the target data being data conforming to an application data standard;

[0022] A building unit is configured to build at least one mapping relationship between the source data and the target data by using an auxiliary tool, each mapping relationship corresponding to an association condition;

[0023] A conversion unit is configured to convert the at least one mapping relationship into at least one code logic;

[0024] A generation unit is configured to organize and compile the at least one code logic by using a data conversion framework to generate a data converter, the data conversion framework supporting data reading and writing in at least one format and having an automatic code generation function.

[0025] In addition, each unit / module in the data converter generation apparatus is further configured to implement the method described in other embodiments of the first aspect.

[0026] In a fourth aspect, an embodiment of the present application discloses a data conversion apparatus, and the apparatus comprises:

[0027] An acquisition unit is configured to acquire source data, the source data being GFC data conforming to a digital building data exchange standard;

[0028] A determination unit is configured to determine a target converter in at least one data converter according to the GFC data, the target converter containing a mapping relationship between the GFC data and target data;

[0029] A conversion unit is configured to convert the GFC data into the target data by using the target converter, the target data being data conforming to an application data standard.

[0030] In combination with the fourth aspect, in a possible implementation manner of the fourth aspect, the conversion unit is specifically configured to convert the GFC data into the target data by using the target converter and taking the GFC standard format as an intermediate format.

[0031] In a fifth aspect, an embodiment of the present application further discloses an electronic device, which comprises at least one processor and a memory connected with the at least one processor.

[0032] The memory stores instructions executable by the at least one processor, and the instructions are executed by the at least one processor to enable the at least one processor to perform the data converter generation method of the first aspect or any implementation manner of the first aspect, or perform the data conversion method of the second aspect or any implementation manner of the second aspect.

[0033] In addition, the present application also discloses a computer readable storage medium, which stores a computer program, and the computer program is executed by a processor to implement the method according to the first aspect or any one of the implementation forms of the first aspect, or implement the method according to the second aspect or any one of the implementation forms of the second aspect.

[0034] The method provided by the embodiment establishes the mapping relationship between the source data conforming to the GFC standard and the application data of the target by using the auxiliary tool, and then generates the data converter by using the data conversion framework, so that the data converter can realize the conversion between the source data and the target data, establish the mapping and association between each product and the GFC format of the general standard, and synchronously establish the standard format import, export and sharing mechanism, thereby realizing the model data sharing and intercommunication in the whole life cycle of BIM. BRIEF DESCRIPTION OF DRAWINGS

[0035] In order to more clearly illustrate the technical solutions in the embodiments of the present application or the prior art, the following will briefly introduce the drawings needed to be used in the description of the embodiments or the prior art. Obviously, the drawings in the following description are some embodiments of the present application, and for those skilled in the art, other drawings can also be obtained without creative labor on the basis of these drawings.

[0036] Figure 1 A flow chart of a data converter generation method provided by the embodiment of the present application is shown in the figure.

[0037] Figure 2 A schematic diagram of constructing data mapping relationship provided by the embodiment of the present application is shown in the figure.

[0038] Figure 3 A schematic diagram of constructing data conversion provided by the embodiment of the present application is shown in the figure.

[0039] Figure 4 A flow chart of formulating data mapping standard provided by the embodiment of the present application is shown in the figure.

[0040] Figure 5 A flow chart of mapping data standard provided by the embodiment of the present application is shown in the figure.

[0041] Figure 6 A flow chart of data import and export provided by the embodiment of the present application is shown in the figure.

[0042] Figure 7 A schematic diagram of GFC data service framework provided by the embodiment of the present application is shown in the figure.

[0043] Figure 8 A flow chart of data conversion method provided by the embodiment of the present application is shown in the figure.

[0044] Figure 9 A structural schematic diagram of a data converter generation device provided by an embodiment of the present application is shown in the figure.

[0045] Figure 10 A structural schematic diagram of a data conversion device provided by an embodiment of the present application is shown in the figure.

[0046] Figure 11 A structural schematic diagram of an electronic device provided by an embodiment of the present application is shown in the figure. DETAILED DESCRIPTION

[0047] The technical solutions of the present application will be described clearly and completely below with reference to the drawings. Obviously, the described embodiments are part of the embodiments of the present application, but not all the embodiments. Based on the embodiments in the present application, all other embodiments obtained by those skilled in the art without creative labor fall within the scope of protection of the present application.

[0048] The technical solutions provided by the embodiments of the present application can be applied to a BIM modeling environment, and are related to the production, conversion, exchange and other scenes of BIM data in the field of construction engineering, especially the data definition, specification and requirements of models in various scenes. For the convenience of the following description, the terms involved in the embodiments of the present application are first explained and described.

[0049] The embodiments of the present application are to establish a common data exchange standard and format (such as IFC) so that various fields and software can share and exchange through IFC. The main problem is how to establish the mapping and association of various products and general standard formats, wherein the general standard format refers to a relatively general and localized data standard format, such as GFC standard format, and then overcome the data intercommunication and sharing problem when there is a difference between IFC and BIM application scenarios.

[0050] Specifically, GFC (General Foundation Classes, digital building data exchange standard) is a set of self-prepared data standards, and the industry general model data format developed based on this standard. The files based on the GFC data standard format can be exported or imported through unified conversion plug-ins. The goal of the GFC data standard is to unify the data exchange interface between various products, create a common consistent language, and form a reliable open data exchange format.

[0051] Among them, the GFC format is an industry general model data format developed based on the GFC standard, and the suffix is “*.gfc”.

[0052] In addition, multiple data standards can be a multi-dimensional mapping relationship formed with the GFC standard as an intermediate format, and are continuously maintained and managed in some form, and the GFC data standard is a universal data exchange format.

[0053] In order to achieve persistent storage of multiple types of BIM software formats and simultaneously establish a standard format import, export, and sharing mechanism, it is necessary to convert source data, such as GFC data, and application data. In specific application scenarios, it is necessary to map the GFC standard and the application data standard to build a data converter between GFC data and application data.

[0054] An embodiment of the present invention provides a method for generating a data converter. The method can be performed by an electronic device, which can be a server or a terminal device. The server can be a standalone physical server, a server cluster or distributed system composed of multiple physical servers, or a cloud server providing cloud computing services. The terminal device can be, but is not limited to, a smartphone, a tablet computer, a desktop computer, a smart wearable device, or the like.

[0055] See also Figure 1 , is a method for generating a data converter provided in this embodiment, the method comprising the following steps:

[0056] 101: Acquire source data and target data, wherein the source data is data that complies with the digital building data exchange standard GFC, and the target data is data that complies with the application data standard.

[0057] Furthermore, the source data can be a GFC data that complies with the GFC standard. The target data is application data that complies with the application data standard, such as Figure 2 As shown, the data converter can also be called "GFC application data converter". This converter is a data conversion tool based on the "extract-convert-write" method. It can extract data from source files, such as GFC data files, complete the conversion internally, and then output it to the target file, that is, the application data file.

[0058] Furthermore, the GFC data includes one or more of the following disciplines: architecture, structure, plumbing, HVAC, and electrical. Currently, the GFC standard includes 300 components, including 131 architectural components, 95 structural components, and 74 electromechanical (including plumbing, HVAC, and electrical) components. Each component can be coded according to the coding conventions of the Building Information Model Classification and Coding Standard.

[0059] Optionally, the source data file and the target data file may be GFC data files or application data files.

[0060] In addition, in step 101, the source data can be obtained by any one of the following ways: imported from a background storage medium, or from an Application Programming Interface (API) of an external database, or also from manual editing input. Similarly, the target data can also be obtained by any one of the above ways.

[0061] 102: establishing at least one mapping relationship between the source data and the target data by using an auxiliary tool, each of the mapping relationships corresponding to an association condition.

[0062] In this stage, the system provides a series of tools to help the user complete the schema mapping between a certain GFC data version and an application data standard version. Specifically, this step includes:

[0063] First, the data object organization hierarchy is determined by using an auxiliary tool; then, at least one of the mapping relationships between the components, attributes or attribute values of the source data and the target data is established according to the data object organization hierarchy. The data object organization hierarchy can be understood as a component organization mode, and the mapping relationship between the schema of a certain GFC data version and an application data standard version is established to form the organization hierarchy relationship between the components.

[0064] Further, in step 101, after the system loads the GFC data standards of each version and the user imports or newly creates the application data standard, step 102 is executed, the user first defines the data object organization hierarchy, and then defines the mapping relationship between the components, attributes and attribute values of the application data and the GFC data standard; finally, the user specifies the implementation standard of the component geometric data.

[0065] 103: converting the at least one mapping relationship into at least one code logic.

[0066] Specifically, this step includes: according to the at least one mapping relationship, using a preprocessor to analyze according to a preset target language to obtain the at least one code logic. The preprocessor includes at least one of a component processor, an attribute processor, an attribute value processor and a geometric data processor.

[0067] Referring to Figure 3 The generation method of the data converter includes three stages of configuration, relationship processing and generation of the data converter. This step involves the data mapping relationship conversion stage in the second "relationship processing" stage, in which the system converts the data mapping relationship into different code logics by using different preprocessors. These preprocessors include a component processor, an attribute processor, an attribute value processor, a geometric data processor, etc.

[0068] The various preprocessors described above generate at least one code logic after transforming at least one mapping relationship, and add the at least one code logic to the data transformation framework.

[0069] This stage is automatically scheduled by the system according to the input data mapping management, analyzes and outputs according to the preset target language, and adds to the data transformation framework. In some cases, manual intervention is required during the transformation process.

[0070] 104: Organize and compile the at least one code logic using the data transformation framework to generate at least one data converter.

[0071] The data transformation framework supports at least one format of data reading and writing, and has an automatic code generation function. In addition, the at least one format includes but is not limited to Express, XML, JSON, and the like. Different data converters can be used to implement the conversion of application data in different formats. In addition, each data converter is used to implement the relationship conversion from source data to target data.

[0072] In Figure 3 The third "data converter" generation stage shown in the figure, the output of at least one code logic will be organized by the data transformation framework, and under certain settings, such as conditions set by a small amount of manual participation, a runnable data converter is obtained through compilation.

[0073] For Express, XML, and JSON format data, the data transformation framework provides direct read-write support and can use automatic code generation technology to compile and generate a data converter. For other format data, manual code writing is required to complete the converter code, and after compilation, other data converters can be generated.

[0074] The method provided in this embodiment establishes the mapping relationship between the GFC data and the target application data by using an auxiliary tool, and then generates a data converter by using a data transformation framework, so as to realize the conversion between the source data and the target data, establish the mapping and association between each product and the general standard GFC format, and simultaneously establish a standard format import, export, and sharing mechanism, thereby realizing the model data sharing and intercommunication in the BIM full life cycle.

[0075] The method provided in this embodiment will be described in detail below with reference to examples.

[0076] Before establishing a mapping relationship between source and target data and generating a data converter, this embodiment first creates GFC data that complies with the GFC standard and industry-standard model data formats. This GFC data has the suffix *.gfc. Specifically, standardized business data can be developed based on business scenarios and instance data, while also referencing other existing business data standards. After consensus among all parties, a complete, uniform, and standardized data standard can be developed.

[0077] The development of standardized business data prioritizes business-centricity, discarding product-specific definitions to create a neutral standard independent of the product. To ensure uniqueness and consistency, the development of the standard utilizes a CDE (common data environment) process, creating a centrally shared document to avoid multiple versions of documents transferred between individuals. Furthermore, roles such as compilers, reviewers, and decision-makers are established to facilitate the development, review, and application of the standard.

[0078] See also Figure 4 , is a flow chart for formulating a data mapping standard, which can be applied to formulating the above-mentioned GFC data mapping standard, and the method includes the following steps:

[0079] 201: Initiate a version. This includes establishing a data standard architecture, obtaining a template framework, determining information scope, and initiating standard creation work according to the version plan.

[0080] 202: Editing. This specifically includes collecting various data, entering the collected data into the template framework, and editing and maintaining data standards based on the application scenario. This also includes preserving traces of changes made to various data or information during the editing process, including additions, deletions, modifications, and queries.

[0081] 203: Inheritance and Linked Updates. Due to the iteration of each version, there is an inheritance relationship between the data. Therefore, the association relationship between the data in each version is inherited, and the updated information is linked to generate standardized data.

[0082] 204: Confirmation. This includes reviewing, answering questions, and optimizing the standardized data generated in the previous step to obtain the official version of the GFC data.

[0083] 205: Release the standard. That is, release the official version of the GFC data so that the GFC data can be associated with and applied to the product side.

[0084] In this embodiment, a GFC data standard is constructed and formulated through steps 201-205, and source data is obtained under the data standard, thereby laying a foundation for import, export and sharing of data under a complete data standard mechanism. After the data standard is formulated, source data and target data are obtained according to the data standard, and then the method for generating the data converter shown in FIG. 8 is executed. Figure 1

[0085] One embodiment is to initiate mapping on the system, as shown in FIG. 9, a mapping data standard process includes: taking GFC as source data, manually or semi-automatically establishing association according to other target data, configuring association conditions, and publishing complete mapping relationship. Once the mapping relationship is established, it can be used as a template, and any subsequent update of two standards can be quickly adjusted, and this template can also be reused in other standard mapping. For example, associate source data A with target data C, configure association conditions, and publish new mapping relationship. Figure 5

[0086] In this example, it is assumed that the source data is A and the target data is B. After initiating the mapping relationship work, source data A and target data B are obtained through background import, or from an external database API, or manually edited input method. In the field of engineering construction BIM, generally, data A and B are tree structure data fields mainly in surface division method. The data standard is usually determined by a unique identifier in the form of a digital business code.

[0087] Then, the mapping relationship between source data A and target data B is established, which can be achieved by editing and recording the mapping association relationship of data. Since the granularity of each product is different, at least one mapping relationship between data A and B includes:

[0088] One source data corresponds to one target data, which can be represented as: 1-1.

[0089] One source data corresponds to multiple target data, which can be represented as: 1-n.

[0090] Multiple source data corresponds to multiple target data, which can be represented as: n-n.

[0091] Wherein, n≥2 and is a positive integer, n represents the number of products.

[0092] In this embodiment, in order to reduce the operation complexity, all mapping relationships are set to start with source data A, and the mapping relationship "n-n" includes the above-mentioned "1-1", "n-1" and "1-n", n≥1.

[0093] Before establishing the mapping relationship, the association conditions need to be configured, that is, under a certain condition, there is a mapping relationship between source data A and target data B. ​​

[0094] Example 1. Take the structural beam in GFC data and a new design data standard as an example for illustration.

[0095] In this example, a new data standard (NDS) is designed, and data conforming to the new data standard NDS is taken as target data. The system restores the frame beam, non-frame beam and coupling beam in the GFC data through business scene, and then establishes a mapping relationship between the three components and the component "structural beam" in the NDS data, and initiates a mapping application. Assuming that GFC is the source data (A) and NDS is the target data (B), the structural beam in GFC is divided into frame beam, non-frame beam and coupling beam, and there is only a single component type of structural beam in NDS. In view of this situation, when A is associated with B, a mapping relationship of n~1 is established, as shown in Figure 6 .

[0096] Table 1. Configuration relationship table of a structural beam

[0097]

[0098] When the association condition is configured, the mapping relationship between the target data B and the source data A is established according to the auxiliary tool as: B=A1+A2+A3. Among them, A1 represents the frame beam, A2 represents the non-frame beam, A3 represents the coupling beam, and B represents the structural beam. This mapping relationship can be shown in Table 2,

[0099] Table 2. Mapping relationship between structural beam and frame beam, non-frame beam and coupling beam

[0100] NDS relationship GFC relationship GFC relationship GFC structural beam B ＝ frame beam A1 + non-frame beam A2 + coupling beam A3

[0101] Among them, when the association condition of the mapping is configured, the conditions that can be set include the following algorithms / operations: addition (PLUS), subtraction (MINUS), multiplication (TIMES), division (DIVIDE), modulus (MOD), greater than (GREATER THAN), less than (LESS THAN), equal to (EQUAL).

[0102] Optionally, it also includes one or more of the following logics or characters: if (IF)..., then (THEN), or (OR), and (AND), contain (Contain) and not contain (not Contain) and the like.

[0103] Optionally, in the mapping relationship between another source data A and target data B, it also includes:

[0104] Example two, take the structural column in GFC data and the structural column in the newly designed data standard NDS as an example. Among them, the structural beam in GFC is divided into structural column, ladder column, structural column, and prefabricated concrete column. There is only structural column in NDS structure, which is a single component type. Due to the one-to-one mapping relationship required in the subsequent product business scenarios, according to the product business requirements, the mapping relationship of "component + attribute" can be used.

[0105] For example, one mapping relationship is: IF (the main material of structural beam (NDS) is reinforced concrete and the structural column type of structural beam (NDS) is ladder column), THEN A = B, and the detailed mapping relationship is shown in Table 3:

[0106] Table 3, a ladder column configuration association table

[0107] GFC component relationship NDS component relationship NDS attribute item relationship NDS attribute value ladder column ＝ structural column AND structural column type ＝ ladder column main body material ＝ reinforced concrete

[0108] Example three, take the structural wall and hidden column in GFC data as an example to demonstrate the structural wall and hidden column in the newly designed data standard NDS.

[0109] Suppose that both GFC source data and NDS target data contain structural walls and hidden columns. And the structural wall and hidden column in GFC are defined as entity components, that is, they can be seen in the three-dimensional model and are independent. Among them, the structural wall in NDS is an entity component, and the hidden column is in the form of a two-dimensional group in the three-dimensional model, that is, it can only be seen as part of the structural wall in the two-dimensional window, and it does not exist in the three-dimensional model. The hidden column part in the three-dimensional model still exists in the form of a structural wall. Therefore, in order to correctly express the relationship between the structural wall in GFC source data and the structural wall in NDS target data, when establishing the mapping relationship, the structured information of the hidden column in NDS is extracted, and through the extracted information, a virtual three-dimensional entity is established in reverse, and the NDS structural wall is deducted "-". The configuration relationship shown in Table 4 is obtained.

[0110] Table 4, a configuration relationship table of a structural wall

[0111] GFC component relationship NDS component relationship NDS component structural wall ＝ structural wall - hidden column

[0112] It should be understood that the mapping relationship established between various GFC components and NDS components includes but is not limited to the above examples one to three, and there can be other various implementation manners, such as the association relationship between building walls, building exterior walls, and building interior walls.

[0113] In the embodiment, after the mapping relationship established according to the configuration association condition is reviewed by the review group, it is determined that the association relationship is feasible and no objection, and further includes: publishing the at least one mapping relationship, generating at least one mapping template according to the at least one mapping relationship, performing import, export and storage operation of source data or target data based on at least one mapping template.

[0114] For example Figure 6 As shown in the figure, a flowchart for importing and exporting mapping relationship.

[0115] Specifically, in the "export process", based on the defined standard mapping relationship, a set of mapping table is output (corresponding to step 3). Various tool software can execute step 4, configuration check, make appropriate configuration and supplement to the mapping table, so as to quickly realize the mapping of standard and general GFC exchange standard in tool software. Finally, step 5, after doing various judgment check processing and through coding processing, compression and persistent storage operation are executed.

[0116] In the "import process", steps 5-8 are included. Since most BIM software can be imported through step 5 "end import", after mapping the GFC standard format data to the current model, step 6 is executed, configuration check, and through the online GFC standard and mapping relationship, the type mapping table is converted into instance mapping table, and finally the object is constructed in the software which can be recognized and applied, and the import is completed.

[0117] When step 7 "object construction" fails, mesh geometry and project basic attributes can be imported separately, so as to realize the import and sharing of part of the data, such as three-dimensional geometry, that is, step 8 "body import" is executed.

[0118] In the process of exporting and importing data files, the multi-source heterogeneous data is the source, the ontology part contains geometry, relationship and business attribute, and the extended part can contain unstructured data. Among the above generated standard mapping relationship, various data standards are formed into multi-dimensional mapping relationship with GFC standard as intermediate format, and are maintained and managed in specific form in subsequent import, export and sharing.

[0119] In this embodiment, by configuring the association condition between the GFC component and the NDS component, the mapping relationship between the GFC source data and the NDS target data is established, and finally the mapping relationship is published. When using the GFC data standard for compilation, since the data conforming to the GFC standard has good compatibility with the existing mainstream BIM software, such as supporting data exchange and adaptation with Revit, number of design software, etc.; at the same time, it also provides technical support for the docking with the city information model (CIM) platform, so it has good compatibility.

[0120] In addition, the construction of the GFC standard system follows a series of ISO international standards, and also interfaces with a series of GB standards in China, and also learns from the IFC architecture. The whole system is comprehensive and complete, and has industry advancement, and can be connected with international standards. The reasons include the following:

[0121] In the "technical framework", the GFC data standard learns from the framework and advantages of the mainstream standard and optimizes the relationship layer to form a complete technical framework system based on meeting the needs of multiple business scenarios: starting from housing construction, it is divided into five major specialties: architecture, structure, water supply and drainage, heating and ventilation, and electrical engineering; at the same time, the Express language is used to define the overall framework of the standard, including application layer, core layer and resource layer and other hierarchical structures.

[0122] For example Figure 7 As shown in the figure, the GFC standard at least includes the following contents: project information table, each professional component classification table, each professional component attribute table, component combination relationship table, each professional component & attribute mapping table, attribute code table, etc. Among them, the professional component attribute table includes the attributes of each component and the mutual association relationship.

[0123] In the field of construction engineering involved in this embodiment, in the GFC standard business architecture, each professional standard currently includes: project information table, each professional component classification table, each professional component attribute table, space standard table, and method standard table.

[0124] Among them, the project information in the project information table is an attribute common to a GFC project, and is not distinguished by specialty or component. The component classification table is based on business scenarios and makes a detailed classification of components in the engineering field. The component attribute establishes a unique attribute set according to the component classification according to the characteristics of the component. The space standard table divides different types of space types according to the building use function. The method standard table combines industry standard drawings and local guidelines to standardize the main engineering methods of buildings.

[0125] In the GFC standard service architecture described above, 300 components are designed, including 131 building components, 95 structural components, and 74 mechanical and electrical (water supply, heating, and electrical) components. Each component includes the following basic information: specialty, code, and English description. The code can be coded according to the Building Information Modeling Classification and Coding Standard. The English description is used to describe the first category, the second category, the third category, and the like. For example, the code “14-07.00.00” and the name “concrete structure” have the English description “Concrete structure”.

[0126] In addition, the attribute information such as the project attribute, the building attribute, and the structural attribute can be freely set according to the business requirements and the component environment, and the embodiment is not limited in this regard.

[0127] The embodiment of the application also provides a data conversion method, which is applied to the data converter generated by the above embodiment, so as to realize the conversion between source data and target data. Specifically, as shown in the following Figure 8 The method comprises the following steps:

[0128] 301: Obtain source data, which is GFC data conforming to the digital building data exchange standard.

[0129] The source data can be obtained by external import, or from a database API, or by manual input.

[0130] 302: Determine a target converter in at least one data converter according to the GFC data, wherein the target converter contains a mapping relationship between the GFC data and target data.

[0131] Each data converter can realize the conversion between at least one source data and target data. The converter with the GFC data is searched in all data converters, and the converter is used as the target data converter.

[0132] 303: Convert the GFC data into the target data by using the target converter, wherein the target data is data conforming to the application data standard.

[0133] In step 303, the GFC data is converted into the target data by using the target converter in the GFC standard format as an intermediate format.

[0134] Optionally, the target data is NDS data.

[0135] For example, in Example 1 described above, based on the frame beam A1, the non-frame beam A2, and the coupling beam A3 contained in the source data A, the target data B, which is a structural beam, is obtained after conversion by the data converter.

[0136] In the embodiment, the data converter is used to convert source data conforming to the GFC standard into target data conforming to another format standard, so as to solve the incompatibility problem between data of different standard formats.

[0137] The GFC standard constructed in the embodiment is a set of full-cycle BIM data standards fully conforming to industrial production, supports BIM lightweight browsing of triangular nets in terms of BIM lightweight rendering, supports accurate geometric description, has complete definitions of component classification, component attributes and data relationships in terms of data description, has complete Geometry definition in terms of geometric description, supports Brep and Swept, and supports general shape description; and supports Express, Binary, XML and json formats in terms of format layer support. In addition, the data file of the GFC standard also supports object and field extension.

[0138] The technical scheme of the embodiment of the application formulates a unified standard, that is, the GFC standard, and realizes the application requirements of full-cycle online, digitization and intelligentization of BIM data standards by formulating data standards, mapping data standards, importing / exporting standard formats, and subsequent checking standard formats.

[0139] The embodiment of the application further provides a data converter generation device, which is used to generate a data converter and execute all or part of the steps of the data converter generation method of the foregoing embodiments.

[0140] As shown in Figure 9 The device includes an acquisition unit 401, an establishment unit 402, a conversion unit 403 and a generation unit 404, and can further include other more or fewer modules, such as a storage unit, a sending unit and the like.

[0141] The acquisition unit 401 is configured to acquire source data and target data, the source data being GFC data conforming to a digital building data exchange standard, and the target data being data conforming to an application data standard, such as NDS data.

[0142] The establishment unit 402 is configured to establish at least one mapping relationship between the source data and the target data by using an auxiliary tool, each mapping relationship corresponding to an associated condition.

[0143] The conversion unit 403 is configured to convert the at least one mapping relationship into at least one code logic.

[0144] The generating unit 404 is configured to organize and compile the at least one code logic by using a data transformation framework to generate a data transformer, the data transformation framework supports data reading and writing in at least one format and has an automatic code generation function.

[0145] Optionally, in a specific implementation of the embodiment, the establishing unit 402 is specifically configured to determine a data object organization hierarchy by using an auxiliary tool, and establish the mapping relationship of at least one of components, attributes or attribute values between the source data and the target data according to the data object organization hierarchy.

[0146] Optionally, in another specific implementation of the embodiment, the transforming unit 403 is specifically configured to analyze the at least one code logic according to the at least one mapping relationship by using a preprocessor in a preset target language. The preprocessor includes at least one of a component processor, an attribute processor, an attribute value processor and a geometric data processor.

[0147] The at least one mapping relationship between the source data and the target data includes any one of the following: one source data corresponds to one target data, one source data corresponds to multiple target data, and multiple source data corresponds to multiple target data.

[0148] Optionally, in still another specific implementation of the embodiment, the obtaining unit 401 further includes a formulating unit before obtaining the source data. Figure 9 The formulating unit is configured to formulate GFC data conforming to a data standard.

[0149] Specifically, the formulating unit is configured to initiate a standard creation work according to a version plan, edit and maintain the data standard according to an application scenario, inherit the association relationship between data in each version, generate standardized data by updating the information in linkage, review, answer questions and optimize the standardized data to obtain the GFC data of a formal version, and release the GFC data of the formal version to associate and apply the GFC data with a product end.

[0150] Optionally, the content of the GFC data includes one or more of the following specialties: building, structure, water supply and drainage, heating and ventilation, and electricity.

[0151] In addition, the GFC data conforms to a GFC data business architecture, and the GFC data business architecture includes project information, component classification, component attribute, space standard and practice standard.

[0152] Optionally, in still another specific implementation manner of the embodiment, the method further includes a publishing unit configured to publish the at least one mapping relationship; the generating unit 404 is further configured to generate at least one mapping template according to the at least one mapping relationship; and the source data or the target data is imported, exported, and stored based on the at least one mapping template.

[0153] In addition, the embodiment further provides a data conversion device configured to implement the method steps as described above. Figure 8 As shown in the method steps as described above. Figure 10 The device includes an obtaining unit 501, a determining unit 502, and a converting unit 503, and can further include more or fewer modules or units, which are not limited in the embodiment.

[0154] The obtaining unit 501 is configured to obtain source data, and the source data is GFC data conforming to a digital building data exchange standard. The determining unit 502 is configured to determine a target converter in at least one data converter according to the GFC data, and the target converter includes a mapping relationship between the GFC data and target data. The converting unit 503 is configured to convert the GFC data into the target data by using the target converter, and the target data is data conforming to an application data standard.

[0155] The device provided by the embodiment establishes a mapping relationship between GFC data and target application data by using an auxiliary tool, and then generates a data converter by using a data conversion framework, so as to convert the source data and the target data by using the data converter, establish mapping and association between each product and the general standard GFC format, synchronously establish a standard format import, export, and sharing mechanism, and realize model data sharing and intercommunication in a BIM full life cycle.

[0156] The embodiment of the application further provides an electronic device, as shown in the electronic device. Figure 11 The electronic device can include a processor 601 and a memory 602, wherein the processor 601 and the memory 602 can be connected through a bus or other manners, Figure 11 and the bus connection is taken as an example. In addition, the electronic device further includes at least one interface 603, which can be a communication interface or other interface, and the embodiment is not limited in this regard.

[0157] The processor 601 can be a central processing unit (CPU). The processor 601 can also be other general-purpose processors, a digital signal processor (DSP), an application-specific integrated circuit (ASIC), a field-programmable gate array (FPGA) or other programmable logic device, discrete gate or transistor logic device, discrete hardware component, or a combination of the above.

[0158] The memory 602, as a non-transitory computer-readable storage medium, can be used to store non-transitory software programs, non-transitory computer-executable programs and modules, such as program instructions / modules corresponding to the data converter generation method and the data conversion method in the embodiments of the present application. The processor 601 performs various functional applications and data processing of the processor by running the non-transitory software programs, instructions and modules stored in the memory 602, that is, implements the data converter generation method and the data conversion method in the above method embodiments.

[0159] The memory 602 can include a program storage area and a data storage area. The program storage area can store an operating system and at least one application required by a function; the data storage area can store data created by the processor 601 and the like. In addition, the memory 602 can include a high-speed random access memory, and can also include a non-transitory memory, such as at least one magnetic disk storage device, a flash memory device, or other non-transitory solid-state memory device. In some embodiments, the memory 602 can optionally include a memory disposed remotely with respect to the processor 601, and these remote memories can be connected to the processor 601 through a network. Examples of the above network include but are not limited to the Internet, an intranet, a local area network, a mobile communication network, and a combination thereof.

[0160] In addition, the at least one interface 603 is used for communication between the electronic device and an external device, such as communication with a server and the like. Optionally, the at least one interface 603 can also be used to connect peripheral input / output devices, such as a keyboard, a display screen and the like.

[0161] The non-transitory computer-readable storage medium stores computer program instructions, which, when executed by the processor 601, can implement the data converter generation method and the data conversion method in the above embodiments.

[0162] Those skilled in the art can understand that all or part of the processes in the above-mentioned embodiment methods can be completed by instructing the relevant hardware through a computer program. The program can be stored in a computer readable storage medium. When the program is executed, the program can include the processes of the above-mentioned embodiment methods. The storage medium can be a magnetic disc, an optical disc, a read-only memory (ROM), a random access memory (RAM), a flash memory, a hard disk drive (HDD) or a solid-state drive (SSD), etc. The storage medium can also include a combination of the above-mentioned types of memories.

[0163] Although the embodiments of the present application are described in conjunction with the drawings, various modifications and changes can be made by those skilled in the art without departing from the spirit and scope of the present application, and such modifications and changes fall within the scope defined by the appended claims.

Claims

1. A method for generating a data converter, characterized in that: The method comprises: Acquire source data and target data, wherein the source data is data that complies with the digital building data exchange standard GFC, and the target data is data that complies with the application data standard; Using an auxiliary tool to establish at least one mapping relationship between the source data and the target data, each mapping relationship corresponding to an association condition; Converting the at least one mapping relationship into at least one code logic; Organizing and compiling the at least one code logic using a data conversion framework to generate at least one data converter, the data conversion framework supporting data reading and writing in at least one format and having an automatic code generation function; The step of establishing at least one mapping relationship between the source data and the target data using an auxiliary tool includes: Use auxiliary tools to determine the organizational hierarchy of data objects; Establishing at least one mapping relationship among components, attributes or attribute values ​​between the source data and the target data according to the data object organization hierarchy; The step of converting the at least one mapping relationship into at least one code logic includes: According to the at least one mapping relationship, a preprocessor is used to analyze according to a preset target language to obtain the at least one code logic; wherein the preprocessor includes: at least one of a component processor, an attribute processor, an attribute value processor and a geometric data processor.

2. The method according to claim 1, characterized in that The at least one mapping relationship between the source data and the target data includes any one of the following: One source data corresponds to one target data; One source data corresponds to multiple target data; Multiple source data correspond to multiple target data.

3. The method according to claim 1, characterized in that Before obtaining the source data, the method further includes: According to the GFC standard and the industry-wide model data format, GFC data that complies with the data standard is formulated, and the suffix of the GFC data is *.gfc.

4. The method according to claim 3, characterized in that According to GFC standards and industry-wide model data formats, develop GFC data that complies with data standards, including: Initiate standard creation work according to the version plan; Edit and maintain data standards based on application scenarios; Inherit the association relationship between data in each version, link the updated information, and generate standardized data; Review, answer questions, and optimize the standardized data to obtain the official version of GFC data; The official version of the GFC data is released so that the GFC data is associated with and applied to the product side.

5. The method according to any one of claims 1 to 4, characterized in that The content of the GFC data includes one or more of the following specialties: Architecture, structure, water supply and drainage, HVAC, and electrical.

6. The method according to any one of claims 1 to 4, characterized in that The GFC data complies with the GFC data service architecture; The GFC data service architecture includes: project information, component classification, component attributes, space standards and practice standards.

7. The method according to any one of claims 1 to 4, characterized in that The method further comprises: Publishing the at least one mapping relationship; generating at least one mapping template according to the at least one mapping relationship; Importing, exporting, and storing operations of source data or target data are performed based on the at least one mapping template.

8. A data conversion method, characterized in that: The method is applied to the data converter according to any one of claims 1 to 7, and the method includes: Acquiring source data, wherein the source data is GFC data that complies with the digital building data exchange standard; determining a target converter in at least one data converter according to the GFC data, wherein the target converter includes a mapping relationship between the GFC data and the target data; The target converter is used to convert the GFC data into the target data, where the target data is data that complies with an application data standard.

9. The method according to claim 8, characterized in that Converting the GFC data into the target data using the target converter includes: The target converter converts the GFC data into the target data using the GFC standard format as an intermediate format.

10. A data converter generating device, characterized in that: The device comprises: An acquisition unit, configured to acquire source data and target data, wherein the source data is data conforming to the digital building data exchange standard GFC, and the target data is data conforming to the application data standard; an establishing unit, configured to establish at least one mapping relationship between the source data and the target data using an auxiliary tool, each mapping relationship corresponding to an association condition; a conversion unit, configured to convert the at least one mapping relationship into at least one code logic; a generating unit, configured to organize and compile the at least one code logic using a data conversion framework to generate a data converter, wherein the data conversion framework supports reading and writing data in at least one format and has an automatic code generation function; The establishing unit is specifically configured to determine a data object organization hierarchy using an auxiliary tool, and establish at least one mapping relationship among components, attributes, or attribute values ​​between the source data and the target data according to the data object organization hierarchy; The conversion unit is specifically used to analyze the at least one code logic according to the preset target language using a preprocessor based on the at least one mapping relationship; wherein the preprocessor includes: at least one of: a component processor, an attribute processor, an attribute value processor and a geometric data processor.

11. A data conversion device, characterized in that: The device is used to implement the data conversion method according to claim 8 or 9, and the device includes: An acquisition unit, configured to acquire source data, wherein the source data is GFC data that complies with the digital building data exchange standard; a determining unit, configured to determine a target converter in at least one data converter according to the GFC data, wherein the target converter includes a mapping relationship between the GFC data and the target data; The conversion unit is configured to convert the GFC data into the target data using the target converter, where the target data is data that complies with an application data standard.

12. An electronic device, characterized in that: The system comprises a processor and a memory, wherein the processor and the memory are coupled, and the memory stores computer-readable program instructions; When the processor reads the instructions in the memory, the method according to any one of claims 1 to 7 or any one of claims 8 to 9 is executed.

13. A computer-readable storage medium having a computer program stored thereon, characterized in that: When the computer program is executed by a processor, the method according to any one of claims 1 to 7 or any one of claims 8 to 9 is implemented.

Images