Method for generating LOD4-level GIS model through municipal road BIM design model based on ADE

Abstract

The invention discloses a method for generating an LOD4-level GIS model through a municipal road BIM design model based on ADE, and relates to the technical field of municipal road three-dimensional design and geographic information, and the method comprises the steps: reading a road IFC file; obtaining component codes; reading standard component code classification and an LOD level component list; classifying the road components according to the component codes and adding LOD level attributes; generating IFC models corresponding to different LOD levels; basic attributes required by the GML are added; geometric transformation is carried out; extracting a geometric object type required by the GML; the method comprises the following steps of: respectively defining Align elements, RoadPart elements and Facility elements on the basis of ADE (Advanced Definition Extensions); and generating the CityGML file. According to the method and the system, the integrity and the accuracy of integration of the LOD4-level GIS data and the municipal road BIM data can be improved.

Description

Technical Field

[0001] The present invention relates to the field of three-dimensional design of municipal roads and geographic information technology, and particularly relates to a method for generating a LOD4-level GIS model from a BIM design model of a municipal road based on ADE. Background Art

[0002] Converting a BIM design model of a municipal road into a LOD4-level GIS model based on Application Domain Extension (ADE) is the key means to solve the problem of the incompleteness of the CityGML standard mode in expressing municipal elements. As the standard for three-dimensional city models, CityGML provides relatively detailed definitions for buildings and other infrastructure, but its standard mode has significant deficiencies in the field of municipal roads, especially in the limited support for professional attributes such as road cross-sections, traffic facilities, and drainage systems. The LOD4-level model requires the expression of the external structure of buildings and the basic geometric form of roads, while the detailed information (such as pavement layers, curbs, drainage ditches, etc.) contained in the BIM design model of a municipal road lacks standardized semantic definitions in CityGML. Therefore, extending CityGML based on ADE and supplementing the specific semantics and geometric structures in the field of municipal roads is a necessary prerequisite for generating a high-quality LOD4-level GIS model.

[0003] From a technical perspective, the main difficulty faced in this conversion process lies in the semantic and geometric differences between the BIM model and the GIS model. The BIM design model focuses on details and engineering attributes, while the LOD4-level GIS model needs to be moderately simplified while retaining key geometric information. In addition, the limitations of the CityGML standard mode require developers to define new feature types and attributes through ADE to ensure the integrity and practicality of the municipal road model. This technical path not only improves the accuracy of model expression but also provides more efficient data support for smart city planning and infrastructure management. Summary of the Invention

[0004] The technical problem to be solved by the embodiments of the present invention is to provide a method for generating a LOD4-level GIS model from a BIM design model of a municipal road based on ADE, aiming at the above requirements and technical difficulties, especially the problem of LOD4-level model conversion, which can improve the integrity and accuracy of the integration of LOD4-level GIS data and BIM data of municipal roads, provide a technical route and feasible method for the integration of BIM and GIS data of municipal roads, and promote the informatization and intelligent management of municipal road projects.

[0005] In a first aspect, the present invention provides a method for generating a LOD4-level GIS model from a BIM design model of a municipal road based on ADE, including:

[0006] Parse the IFC element categories involved in road components from the road IFC file to obtain IFC elements classified by category that contain component and attribute data. The IFC elements are divided into two categories: one is component elements, and the other is attribute elements.

[0007] Query the extended attributes and extended attribute set data of the components, connect the extended attributes and extended attribute set data to the component elements, then filter out the component code data, and connect the component code data to the component elements.

[0008] According to the component elements connected with component codes, read the standard component code classification and LOD-level component list, classify the road components according to the component codes, and add LOD-level attributes.

[0009] Generate IFC models corresponding to different LOD levels, add the basic attributes required by GML, perform geometric transformation on the components after adding GML attributes, and extract the geometric object types required by GML.

[0010] After defining Alignment, RoadPart, and Facility elements respectively based on the ADE extension, generate a CityGML file.

[0011] In some instances, the step of parsing the IFC element categories involved in road components from the road IFC file to obtain IFC elements classified by category that contain component and attribute data includes:

[0012] Construct a road IFC file reading module to read the road IFC file, parse the IFC element categories involved in road components from the road IFC file, classify the component and attribute data according to the element categories, and output IFC elements classified by category that contain component and attribute data. The IFC elements are divided into two categories: one is component elements, which store various component geometric entities and basic attributes, and the other is attribute elements, which store the extended attributes and extended attribute set data of each component entity.

[0013] In some instances, the step of querying the extended attributes and extended attribute set data of the components, connecting the extended attributes and extended attribute set data to the component elements, then filtering out the component code data, and connecting the component code data to the component elements includes:

[0014] Construct a FeatureJoiner module, input various component elements and attribute elements, query the extended attributes and extended attribute set data of the component from the attribute element IfcPropertySet according to the ifc_property_set{} data of the component element, connect the extended attributes and extended attribute set data to the component element, and output the connected component element.

[0015] Construct a Tester module, input the connected component elements, and use ifc_property_set_name = basic properties as the screening condition. Among them, the property value of the basic property is the component code, so as to screen out the component elements with component codes.

[0016] Construct an AttributeManager module, input the component elements with component codes, add component code attributes, so as to add component code data to the component elements and output the component elements.

[0017] In some instances, reading the standard component code classification and LOD-level component list according to the component elements of the connected component codes includes:

[0018] Construct a component code classification table reading module, read the component classification and coding rules, and LOD classification rules. Among them, the component classification and coding rules comply with the requirements of the "Unified Standard for the Application of Highway Engineering Information Model" (JTG / T 2420-2021), and are divided into 4 major categories: route, subgrade components, pavement components, and traffic engineering and roadside facility components, and output the component classification and coding, and LOD classification.

[0019] In some instances, classifying the road components according to the component codes and adding LOD-level attributes includes:

[0020] Construct a FeatureJoiner module, input the component elements with added component codes, LOD classification rules, and component classification and coding, perform comparison queries through the component codes, so as to determine the LOD level of the component elements, add LOD-level attributes to the component elements and output.

[0021] In some instances, generating IFC models corresponding to different LOD levels includes:

[0022] Construct a TestFilterOfLod module, input the component elements with added LOD-level attributes, screen the LOD-level attribute information, and select the component elements with the LOD-level attribute value of LOD4 for output.

[0023] In some instances, adding the basic attributes required for GML includes:

[0024] Construct an AttributeCreator module, input the screened LOD4 component elements, add the basic attribute information required for the CityGML model, perform attribute mapping and output.

[0025] In some instances, performing geometric transformation on the components after adding GML attributes includes:

[0026] Build the ConvertGeometry module, input the LOD4 component elements, perform geometric transformation and output.

[0027] In some instances, the building of the ConvertGeometry module, inputting the LOD4 component elements, performing geometric transformation and outputting, includes:

[0028] Build the GeometryPartExtractor module, input the LOD4 component elements, extract the selected geometric elements based on geometric XQuery and output;

[0029] Build the GeometryCoercer module, input the selected geometric elements, reset the geometric object type of the elements and output;

[0030] Build the Deaggregator module, input the geometric elements with reset elements, decompose their aggregate elements, form their components and output;

[0031] Build the Aggregator module, input the decomposed geometric elements, merge the geometric figures of the elements into heterogeneous or homogeneous aggregates and output;

[0032] Build the GeometryRefiner module, input the merged geometric elements, refine the geometric figures of the elements and output.

[0033] In some instances, the extraction of the required geometric object types of GML includes:

[0034] Build the GeometryExtractor module, input the refined geometric elements, extract the geometric object types of the elements according to the geometric coding parameter settings and output.

[0035] In some instances, the definition of Alignment, RoadPart, and Facility elements respectively based on ADE extension includes:

[0036] Modify the underlying Schema file of the CityGML Transportation theme, inherit from the Road element, and newly create Alignment, RoadPart, and Facility elements to express the route elements of LOD4. Among them, the route components are expressed by the Alignment element, the subgrade components and pavement components are expressed by the RoadPart element, and the traffic engineering and roadside facility components are expressed by the Facility element.

[0037] In some instances, the generation of the CityGML file includes:

[0038] Import a custom Schema file, construct the Alignment, RoadPart, and Facility writing modules respectively, input elements for extracting geometric object types, write files, and generate the RoadADEOfLOD4.gml file, which is the GIS model at the LOD4 level.

[0039] Generally speaking, compared with the prior art through the above technical solutions conceived by the present invention, the following beneficial effects can be achieved:

[0040] For the components involved in the BIM design model of municipal roads in the present invention, classification and coding are carried out according to the provisions of the "Unified Standard for the Application of Highway Engineering Information Model" (JTG / T 2420-2021), and division is carried out according to the LOD level; on this basis, for the component models corresponding to the LOD4 level among them, a series of data converters are developed, and the Alignment, RoadPart, and Facility elements are respectively defined based on the CityGML ADE extension framework, and the BIM design model of municipal roads is generated into a GIS model at the LOD4 level. This method can improve the integrity and accuracy of the integration of LOD4-level GIS data and municipal road BIM data, and provides a technical route and feasible method for the integration of municipal road BIM and GIS data. BRIEF DESCRIPTION OF THE DRAWINGS

[0041] In order to more clearly illustrate the technical solutions in the embodiments of the present invention, the following will briefly introduce the drawings required for the description of the embodiments. Obviously, the drawings in the following description are only some embodiments of the present invention. For those skilled in the art, other drawings can be obtained based on these drawings without creative efforts.

[0042] Figure 1 is a schematic flowchart of the method provided by the embodiment of the present invention;

[0043] Figure 2 is a schematic diagram of the original model provided by the embodiment of the present invention;

[0044] Figure 3 is a schematic diagram of the GIS model at the LOD4 level provided by the embodiment of the present invention. DETAILED DESCRIPTION OF THE EMBODIMENTS

[0045] The following will clearly and completely describe the technical solutions in the embodiments of the present invention with reference to the drawings in the embodiments of the present invention. Obviously, the described embodiments are only some embodiments of the present invention, rather than all embodiments. Based on the embodiments of the present invention, all other embodiments obtained by those skilled in the art without creative efforts fall within the protection scope of the present invention.

[0046] In the following description, specific embodiments of the present invention will be described with reference to steps and symbols performed by one or more computers, unless otherwise specified. Therefore, these steps and operations will be referred to several times as being performed by a computer. As used herein, a computer performing includes operations of a computer processing unit that represents electronic signals in a structured form of data. This operation transforms the data or maintains its position in the memory system of the computer, which can reconfigure or otherwise change the operation of the computer in a manner well known to those skilled in the art. The data structure in which the data is maintained is a physical location in the memory, which has specific characteristics defined by the data format. However, the principles of the present invention are described in the above text, which is not intended to be a limitation, and those skilled in the art will understand that the following various steps and operations can also be implemented in hardware.

[0047] As used herein, the term "module" or "unit" can be regarded as a software object executed on the computing system. Different components, modules, engines, and services herein can be regarded as implementation objects on the computing system. The devices and methods herein are preferably implemented in software, but of course can also be implemented in hardware, all within the protection scope of the present invention.

[0048] Those skilled in the art of the present technology can understand that, unless specifically stated otherwise, the singular forms "a", "an", and "the" used herein can also include the plural forms. It should be further understood that the term "including" used in the description of the present invention means the presence of features, integers, steps, operations, elements, and / or components, but does not exclude the presence or addition of one or more other features, integers, steps, operations, elements, components, and / or groups thereof. It should be understood that when we say an element is "connected" or "coupled" to another element, it can be directly connected or coupled to other elements, or there may also be intermediate elements. In addition, the "connection" or "coupling" used herein can include wireless connection or wireless coupling. The phrase "and / or" used herein includes all or any unit and all combinations of one or more related listed items.

[0049] An embodiment of the present invention provides a method for generating a LOD4-level GIS model based on an ADE for a municipal road BIM design model, as Figure 1 shown, including the following steps:

[0050] S1. Read the road IFC file: Construct a road IFC file reading module, and the original model is as Figure 2As shown, read the road IFC file, parse out the IFC element categories involved in the road components from it, classify the components and attribute data according to the element category, and output the IFC elements classified by category containing the component and attribute data, such as IfcBuildingElement Proxy, IfcCivilElement, IfcPipeSegment, IfcWall, IfcSlab, IfcFooting, IfcSpace, IfcPropertySet, etc. The IFC elements are mainly divided into two categories. One is the component elements, such as IfcBuildingElement Proxy, IfcCivilElement, IfcPipeSegment, IfcWall, IfcSlab, IfcFooting, IfcSpace, which store geometric entities and basic attributes of various components. The other is the attribute elements, such as IfcPropertySet, which store extended attributes and extended attribute set data of each component entity.

[0051] S2. Obtain the component code: Construct multiple FeatureJoinerAndTester modules, input various component elements and attribute elements output from S1, query the extended attributes and extended attribute set data of the component from the attribute element IfcPropertySet according to the ifc_property_set{} data of the component element, connect the extended attributes and extended attribute set data to the component element, then filter out the component code data from it, and connect the component code data to the component element, so that in addition to storing the original component geometric entity and basic attribute data, the component element also stores the component code data, and output various component elements;

[0052] According to the above solution, in step S2, the FeatureJoinerAndTester module consists of multiple sub-modules, specifically:

[0053] S201. Construct a FeatureJoiner module, input various component elements and attribute elements output from S1, query the extended attributes and extended attribute set data of the component from the attribute element IfcPropertySet according to the ifc_property_set{} data of the component element, and connect the extended attributes and extended attribute set data to the component element, and output the connected component element;

[0054] S202. Construct a Tester module, input the component elements in S201, and use "ifc_property_set_name = basic attribute" as the filtering condition, where the attribute value of "basic attribute" is the component code, so as to filter out the component elements with the component code;

[0055] S203. Construct the AttributeManager module, input the component elements in S202, add the "component code" attribute, so as to add the component code data to the component elements, and output the component elements.

[0056] S3. Read the standard component code classification and the LOD-level component list. Specifically: construct a component code classification table reading module, read the component classification and coding rules, and the LOD classification rules. Among them, the component classification and coding rules comply with the requirements of the "Unified Standard for the Application of Highway Engineering Information Model" (JTG / T 2420-2021), and are divided into 4 major categories: route, subgrade components, pavement components, and traffic engineering and roadside facility components, and output the component classification and coding, and the LOD classification.

[0057] S4. Classify the road components according to the component code and add the LOD-level attribute. Specifically: construct a FeatureJoiner module, input the component elements in S203, the LOD classification rules, and the component classification and coding in S3, perform a comparison query through the component code, so as to determine the LOD level of the component elements, add the LOD-level attribute to the component elements and output.

[0058] S5. Generate the IFC models corresponding to different LOD levels. Specifically: construct a TestFilterOfLod module, input the component elements in S4, and by screening their LOD-level attribute information, select the component elements with the LOD-level attribute value of LOD4 for output.

[0059] S6. Add the basic attributes required by GML. Specifically: construct an AttributeCreator module, input the LOD4 component elements screened in S5, add the basic attribute information required by the CityGML model such as "citygml_lod_name, gml_id, gml_name", perform attribute mapping and output.

[0060] S7. Perform geometric transformation. Specifically: construct a ConvertGeometry module, input the LOD4 component elements in S6, perform geometric transformation and output.

[0061] According to the above solution, in step S7, the ConvertGeometry module is composed of multiple sub-modules. Specifically:

[0062] S701. Construct a GeometryPartExtractor module, input the LOD4 component elements in S6, extract the selected geometric elements (the geometric object name is Body) based on geometric XQuery and output;

[0063] S702. Construct a GeometryCoercer module, input the selected geometric elements in S701, reset the geometric object type of the elements and output;

[0064] S703. Construct a Deaggregator module, input the geometric elements in S702, decompose their aggregate elements, form their components and output;

[0065] S704. Construct an Aggregator module, input the geometric elements in S703, merge the geometric shapes of the elements into heterogeneous or homogeneous aggregates and output;

[0066] S705. Construct a GeometryRefiner module, input the geometric elements in S704, "refine" the geometric shapes of the elements and output.

[0067] S8. Extract the geometric object types required by GML. Specifically: construct a GeometryExtractor module, input the geometric elements in S705, and extract the geometric object types of the elements according to the geometric coding parameter settings (set to GML v3.2.1) and output.

[0068] S9. Define Alignment, RoadPart, and Facility elements respectively based on the ADE extension. Specifically: modify the underlying Schema file of the CityGML Transportation theme, inherit from the Road element, and create Alignment, RoadPart, and Facility elements to express the route elements at LOD4. Among them, the route components are expressed by the Alignment element, the subgrade components and pavement components are expressed by the RoadPart element, and the traffic engineering and roadside facility components are expressed by the Facility element.

[0069] S10. Generate a CityGML file. Specifically: import the custom Schema file in S9, respectively construct Alignment, RoadPart, and Facility write modules, input the elements in S8, write the file, and generate the RoadADEOfLOD4.gml file, which is the GIS model at LOD4 level, as Figure 3 shown.

[0070] In the embodiment of the present invention, for the four major categories of route, subgrade component, pavement component, and traffic engineering and roadside facility component, the route component is expressed by the Alignment element, the subgrade component and pavement component are expressed by the RoadPart element, and the traffic engineering and roadside facility component are expressed by the Facility element. The operations of steps S6, S7, S8, and S9 are respectively performed on each of them.

[0071] The above has introduced in detail a method for generating a LOD4-level GIS model based on the ADE for the BIM design model of municipal roads provided by the embodiments of the present invention. Specific examples are used in this article to elaborate on the principle and implementation manner of the present invention. The description of the above embodiments is only used to help understand the method and its core idea of the present invention; at the same time, for those skilled in the art, according to the idea of the present invention, there will be changes in the specific implementation manner and application scope. In summary, the content of this specification should not be construed as a limitation to the present invention.

Claims

1. A method for generating a LOD4 level GIS model from a municipal road BIM design model based on ADE, characterized in that: include: The IFC element categories involved in the road components are parsed from the road IFC file to obtain the IFC elements classified by category, which contain the component and attribute data. One type of IFC element is the component element, and the other type is the attribute element. Query the extended attributes and extended attribute set data of the component, and connect the extended attributes and extended attribute set data to the component elements, then filter out the component coding data, and connect the component coding data to the component elements; According to the component elements of the connection component code, read the standard component code classification and LOD level component list, classify the road components according to the component code and add LOD level attributes; Generate IFC models corresponding to different LOD levels, add basic attributes required by GML, perform geometric transformation on components after adding GML attributes, and extract geometric object types required by GML; After defining the Alignment, RoadPart, and Facility elements based on the ADE extension, the CityGML file is generated.

2. The method according to claim 1, characterized in that: The IFC element categories involved in the road components are parsed from the road IFC file to obtain the IFC elements classified by category and containing components and attribute data, including: Build a road IFC file reading module to read the road IFC file, parse the IFC feature categories involved in the road components from the road IFC file, classify the components and attribute data according to the feature category, and output the classified IFC features containing the components and attribute data. IFC elements are divided into two categories: one is component elements, which store various component geometric entities and basic attributes, and the other is attribute elements, which store the extended attributes and extended attribute set data of each component entity.

3. The method according to claim 2, characterized in that The querying of the extended attributes and extended attribute set data of the component, connecting the extended attributes and extended attribute set data to the component elements, then screening out the component coding data, and connecting the component coding data to the component elements, includes: Construct the FeatureJoiner module, input various component elements and attribute elements, query the extended attributes and extended attribute set data of the component from the attribute element IfcPropertySet according to the ifc_property_set{} data of the component element, connect the extended attributes and extended attribute set data to the component element, and output the connected component element; Construct the Tester module, input the connected component elements, and use ifc_property_set_name = basic property as the screening condition, where the attribute value of the basic property is the component code, thereby screening out the component elements with the component code; Build an AttributeManager module, input a component element with a component code, add a component code attribute to add the component code data to the component element, and output the component element.

4. The method according to claim 3, characterized in that The component elements according to the connection component coding, reading the standard component coding classification and LOD level component list, include: Build a component coding classification table reading module to read the component classification and coding rules and LOD classification rules. The component classification and coding rules comply with the requirements of the "Uniform Standard for the Application of Highway Engineering Information Model" (JTG / T 2420-2021) and are divided into four categories: routes, roadbed components, pavement components, traffic engineering and facilities along the line. Output component classification and coding, and LOD classification.

5. The method according to claim 4, characterized in that The road components are classified according to the component codes and LOD level attributes are added, including: Construct the FeatureJoiner module, input the component elements with component coding added, LOD classification rules, and component classification and coding, perform comparative query through component coding to determine the LOD level of component elements, add LOD level attributes to component elements and output them.

6. The method according to claim 5, characterized in that The generating of IFC models corresponding to different LOD levels includes: Build the TestFilterOfLod module, input the component elements to which the LOD level attributes are added, filter the LOD level attribute information, and select the component elements whose LOD level attribute value is LOD4 for output.

7. The method according to claim 6, characterized in that The basic attributes required for adding GML include: Construct the AttributeCreator module, input the filtered LOD4 component elements, add the basic attribute information required by the CityGML model, perform attribute mapping and output.

8. The method according to claim 7, characterized in that The geometric transformation of the component after adding the GML attribute includes: Build the ConvertGeometry module, input LOD4 component elements, perform geometry conversion and output.

9. The method according to claim 8, characterized in that The ConvertGeometry module is constructed to input LOD4 component elements, perform geometric conversion and output, including: Build the GeometryPartExtractor module, input the LOD4 component elements, extract the selected geometric elements based on geometric XQuery and output them; Build the GeometryCoercer module, input the selected geometric features, reset the geometric object type of the features and output; Construct the Deaggregator module, input the geometric elements of the reset elements, decompose its aggregate elements, form its components and output them; Construct the Aggregator module, input the decomposed geometric elements, merge the geometric figures of the elements into heterogeneous or homogeneous aggregates and output them; Build the GeometryRefiner module, input the merged geometric features, refine the feature geometry and output it.

10. The method according to claim 9, characterized in that The ADE-based extension defines the Alignment, RoadPart, and Facility elements, including: Modify the underlying Schema file of the CityGML Transportation theme, inherit from the Road element, and create new Alignment, RoadPart, and Facility elements to express LOD4 route elements. Among them, route components are expressed by Alignment elements, roadbed components and pavement components are expressed by RoadPart elements, and traffic engineering and facilities along the route are expressed by Facility elements.

Images