CN115904552A - Highway engineering information model data derivation method - Google Patents
Highway engineering information model data derivation method Download PDFInfo
- Publication number
- CN115904552A CN115904552A CN202310113305.2A CN202310113305A CN115904552A CN 115904552 A CN115904552 A CN 115904552A CN 202310113305 A CN202310113305 A CN 202310113305A CN 115904552 A CN115904552 A CN 115904552A
- Authority
- CN
- China
- Prior art keywords
- language
- entity
- information model
- model data
- highway engineering
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Granted
Links
Images
Abstract
The invention relates to a highway engineering information model data derivation method. The highway BIM modeling software supports C # language development, and does not support or supports the C + + language development. The method comprises the steps of creating and deriving a highway engineering IFC entity by using a C + + language, packaging a BREP geometric entity and packaging a general attribute set template; forming a highway engineering information model data storage class library by using C + + language packaging, and supporting the function of creating highway engineering information model data by using C + + language; a highway engineering information model data storage interface library is formed by using managed C + + language packaging, and the function of creating highway engineering information model data by C # language is supported; and calling a highway engineering information model data storage interface library by using a managed C + + language, and supporting the function of creating and exporting IFC files by using a C # language. The method has the advantages of high performance of C + + language and development convenience of C # language, and can be adapted to BIM modeling software of different roads.
Description
Technical Field
The invention relates to the technical field of highway engineering information, in particular to a highway engineering information model data derivation method.
Background
With the wider application of the Building Information Modeling (BIM) technology in the road industry, the road engineering project pays more and more attention to the delivered Information model, and the file formats of the Information models derived by different road BIM Modeling software are different. Based on IFC (Industry Foundation Classes) data format specified by highway Industry standard, the expanded IFC entity is used for representing highway engineering objects, attribute information is used for representing the characteristics of the highway engineering objects, and the incidence relation is used for representing the relation between two or more highway engineering objects.
At present, most of the existing highway BIM modeling software only supports the development of C # language, and does not support or support the development of C + + language, so that a highway engineering information model data export method which maintains the common characteristics of C + + language and C # language is required to be provided in order to maintain the high performance of the development of C + + language, reduce the development difficulty and cost and shorten the development period.
Disclosure of Invention
The invention aims to provide a highway engineering information model data exporting method, which provides a universal interface for highway BIM modeling software to export highway engineering information model data and can adapt to different highway BIM modeling software to export highway engineering information model files.
In order to achieve the purpose, the technical scheme adopted by the invention is as follows:
the method for deriving the highway engineering information model data comprises the following steps:
creating and deriving a highway engineering IFC entity by using C + + language to realize the creating function of the highway engineering IFC entity;
packaging the BREP geometric entity by using C + + language to realize the creating function of the BREP geometric entity;
packaging a universal attribute set template by using C + + language to realize the creating function of the attribute set;
forming a highway engineering information model data storage class library by using C + + language packaging, and supporting the function of creating highway engineering information model data by using C + + language;
a highway engineering information model data storage interface library is formed by using managed C + + language packaging, and the function of creating highway engineering information model data by using C # language is supported;
and calling a road engineering information model data storage interface library by using a managed C + + language, and supporting the function of creating and exporting IFC files by using a C # language.
Further, a road engineering IFC entity is created and derived by using a C + + language, and the creating function of the road engineering IFC entity is realized, wherein the creating function comprises the following steps:
on the basis of the existing ifcplus plug-in, a road engineering IFC entity is created and derived from a space structure entity and a civil element entity by using a C + + language;
and realizing the establishment function of the road engineering IFC entity according to the purpose of the road engineering information model data storage.
Further, encapsulating the BREP geometric entity by using the C + + language to realize the creating function of the BREP geometric entity, including:
encapsulating BREP geometric entities by using C + + language;
the encapsulated BREP geometric entity has parameters and a function interface for creating the BREP geometric entity, and can realize the creating function of the BREP geometric entity.
Further, a C + + language is used to package a generic attribute set template, so as to implement a function of creating an attribute set, including:
packaging a universal attribute set template by using C + + language;
the encapsulated universal attribute set template has attribute parameters and a function interface for creating the attribute set, and can realize the creating function of the attribute set.
Further, a highway engineering information model data storage class library is formed by using C + + language encapsulation, and the function of creating highway engineering information model data in C + + language is supported, and the method comprises the following steps:
and calling a highway engineering IFC entity, a BREP geometric entity and a general attribute set template by using the C + + language, packaging to form a highway engineering information model data storage class library, and supporting the function of creating highway engineering information model data by using the C + + language.
Further, a highway engineering information model data storage interface library is formed by using managed C + + language packaging, and the function of creating highway engineering information model data in C # language is supported, and the method comprises the following steps:
and packaging the highway engineering information model data storage class library by using a managed C + + language to form a highway engineering information model data storage interface library and support the function of creating highway engineering information model data by using a C # language.
Furthermore, a managed C + + language is used for calling a road engineering information model data storage interface library to support the function of creating and exporting IFC files in a C # language, and the function comprises the following steps:
and calling a highway engineering information model data storage interface library by using a managed C + + language, supporting the function of creating highway engineering information model data by using a C # language, and finally exporting the IFC file.
Compared with the prior art, the invention has the following beneficial effects:
the method expands the existing ifcplus plug-in, creates and derives a highway engineering IFC entity by using C + + language, encapsulates a BREP geometric entity, a general attribute set template and a highway engineering IFC entity by using C + + language to form a highway engineering information model data storage class library, encapsulates the highway engineering information model data storage class library by using managed C + + language to form a highway engineering information model data storage interface library, supports C # language to call the highway engineering information model data storage interface library, and realizes the function of exporting IFC files from highway engineering information model data.
The highway engineering information model data exporting method provided by the invention not only maintains the high performance of C + + language development, but also maintains the convenience of C # language development, reduces the development difficulty and cost, shortens the development period, can be effectively adapted to different highway BIM modeling software, provides a universal interface for different highway BIM modeling software to export highway engineering information model data, and realizes the export of highway engineering information model data based on IFC.
Drawings
In order to more clearly illustrate the embodiments of the present invention or the technical solutions in the prior art, the drawings used in the description of the embodiments or the prior art will be briefly described below, it is obvious that the drawings in the following description are only some embodiments of the present invention, and for those skilled in the art, other drawings of the embodiments can be obtained according to the drawings without creative efforts.
FIG. 1 is a flow chart of a method in an embodiment of the invention.
FIG. 2 is a three-dimensional diagram of a road engineering information model derived by the method of the embodiment of the invention.
Detailed Description
To facilitate an understanding of the invention, the invention will now be described more fully with reference to the accompanying drawings. Preferred embodiments of the present invention are shown in the drawings. This invention may, however, be embodied in many different forms and should not be construed as limited to the embodiments set forth herein. Rather, these embodiments are provided so that this disclosure will be thorough and complete.
It should be noted that like reference numerals and letters refer to like items and, thus, once an item is defined in one embodiment, it need not be further defined and explained in subsequent embodiments. Moreover, the terms "comprises," "comprising," or any other variation thereof, are intended to cover a non-exclusive inclusion, such that a process, method, system, article, or apparatus that comprises a list of steps or modules is not necessarily limited to those steps or modules explicitly listed, but may include other steps or modules not expressly listed or inherent to such process, method, article, or apparatus.
In addition, the steps "S1", "S2", and the like in the embodiment of the present invention are only for convenience of description of the technical solution, so as to facilitate understanding of the specific steps and contents of the embodiment, and should not be construed as limiting the sequence of the steps, and any change only to the sequence of the steps should be within the protection scope of the present invention.
The invention provides a highway engineering information model data exporting method, which provides a universal interface for highway BIM modeling software to export highway engineering information model data and can effectively adapt to different highway BIM modeling software to export highway engineering information model files. As in fig. 1, the method comprises:
s1: the method for creating and deriving the road engineering IFC entity by using the C + + language realizes the creating function of the road engineering IFC entity, and specifically comprises the following steps:
the existing ifcplus plug-ins only include the IFC entities related to the construction engineering, not the IFC entities related to the road engineering defined in the unified standard for road engineering information model application (JTGT 2420-2021).
S101, on the basis of the existing ifcplusplaus plug-in, creating an derived facility entity (IfcFacity) from a space structure entity (IfcSpatialStrectureElement) by using a C + + language, and creating a derived highway entity (IfcRoad), a bridge entity (Ifcbridge), a tunnel entity (IfcTunnel) and the like from the facility entity (IfcFacity). A derivative sub-facility entity (ifcfacilititopart) is created from the space structure entity (ifcfacilitigation element), a derivative road-based surface entity (ifcfoadpart), a bridge structure entity (ifcfidge part), a tunnel segment entity (ifcttunnelpart), and the like are created from the sub-facility entity (ifcfacilititopart).
S102, on the basis of the existing ifcpplupplus plug-in, a roadbed element entity (IfcSubggradedelement), a pavement element entity (IfcPavementelement), a slope element entity (IfcSlope), an arch element entity (Ifcarc), a tunnel element entity (IfcTunnelElement) and the like are created and derived from a civil element entity (IfcCivilElement) by using C + + language. The field entity (IfcSite), the canal element entity (ifcpipeesegment), the pool element entity (IfcTank), the beam element entity (IfcBeam), the wall element entity (IfcWall), the plate element entity (ifcstab), the column element entity (IfcColumn), the foundation element entity (ifcfoting), the pile element entity (IfcPile), the guard rail element entity (ifcrraiing), the telescoping device element entity (ifcfastenerer), the corbel element entity (ifcmeber), etc. exist in the existing ifcplus plug-in, and the method follows the above entities.
In summary, the step S101 and the step S102 of creating the derived road engineering IFC entity include: highway entity (IfcRoad), bridge entity (ifcrbridge), tunnel entity (ifcttunnel), roadbed and road surface entity (IfcRoadPart), bridge structure entity (ifcrbridgepart), tunnel segment entity (ifcttunnelpart), roadbed element entity (ifcsubgradedeelement), road surface element entity (IfcPavementElement), side slope element entity (IfcSlope), arch element entity (ifcalch), tunnel element entity (ifcttunnelelement) and the like. The road entity (Ifcroad), the bridge entity (Ifcbridge), the tunnel entity (IfcTunnel), the road bed and road surface entity (IfcRoadPart), the bridge structure entity (IfcBridgePart) and the tunnel segment entity (IfcTunnelPart) are space structure entities, and the road bed element entity (IfcSubggradeElement), the road surface element entity (IfcPavementElement), the slope element entity (IfcSlope), the arch element entity (IfcEmrch) and the tunnel element entity (IfcTunnelElement) are physical entities.
S103: according to the purpose of highway engineering information model data storage, the building functions of highway engineering IFC entities such as highways, bridges, tunnels and the like are realized, and the building functions comprise the building functions of positions, attributes, geometry, incidence relations and the like.
The position is the relative position of the road engineering IFC entity instantiation object in the belonged space structure entity object, and is used for creating and positioning the local coordinate system where the instantiation object is located.
The attribute is derived from the attribute content of road engineering design information model application standard (JTGT 2421-2021), road engineering construction information model application standard (JTGT 2422-2021) or project customization.
The geometry is derived from the unified Standard for information model application for road engineering (JTGT 2420-2021), and the method is only suitable for the creation of a BREP (Boundary surface model) geometric entity.
The incidence relation is originated from the unified Standard for information model application of Highway engineering (JTGT 2420-2021), and mainly comprises an inclusion relation and a polymerization relation. The site entity (IfcSite) has the function of aggregating spatial structure entities such as a road entity (IfcRoad), a bridge entity (ifcrdge), a tunnel entity (ifcttunnel), and the like, and the site entity (IfcSite) has an aggregation relationship with the aggregated road entity (IfcRoad), the bridge entity (ifcrdge), the tunnel entity (ifcttunnel), and the like. The highway entity (Ifcroad) has the function of aggregating roadbed and road surface entities (IfcRoadpart), and the highway entity (Ifcroad) has an aggregation relation with the aggregated roadbed and road surface entities (IfcRoadpart). The bridge entity (Ifcbridge) has the function of an aggregation bridge structure entity (Ifcbridge part), and the bridge entity (Ifcbridge) has an aggregation relation with the aggregated bridge structure entity (Ifcbridge part). The tunnel entity (ifcTunnel) has the function of an aggregation tunnel segment entity (ifcTunnel Part), and the tunnel entity (ifcTunnel) has an aggregation relationship with the aggregated tunnel segment entity (ifcTunnel Part). The roadbed and road surface entity (IfcRoadpart) has functions of including roadbed element entity (IfcSubggradedelement), road surface element entity (IfcPavementelement), side slope element entity (IfcSlope), canal element entity (IfcPipeSegment), pool element entity (IfcTank), and the like, and the roadbed and road surface entity (IfcRoadpart) has an inclusion relationship with the included roadbed element entity (IfcSubggradedelement), road surface element entity (IfcPavementElement), side slope element entity (IfcSlope), canal element entity (IfcPipeSegment), pool element entity (IfcTank), and the like. The bridge structure entity (ifcbridge part) has a function of containing arch element entity (ifc arch), beam element entity (IfcBeam), wall element entity (IfcWall), plate element entity (ifcSlab), column element entity (ifcColumn), base element entity (ifcFooting), pile element entity (ifcPile), guard rail element entity (ifcRailing), telescoping device element entity (ifcFastener), corbel element entity (ifcJember), etc., and the bridge structure entity (ifcBridge part) exists with contained arch element entity (ifcArch), beam element entity (ifcBeam), wall element entity (ifcWall), plate element entity (ifcSlab), column element entity (ifcColumn), base element entity (ifcFasten), pile element entity (ifcFastfoam), telescoping device element entity (ifcFalberg). The tunnel segment entity (ifcttunnelpart) has a function of containing a tunnel element entity (ifcttunnelelement), a wall element entity (IfcWall), an arch element entity (ifcach), a slope element entity (IfcSlope), a base element entity (ifcfoting), a canal element entity (ifcpipeesegment), and the like, and has an inclusion relationship with the contained tunnel element entity (ifcttunnelelement), the wall element entity (IfcWall), the arch element entity (ifcach), the slope element entity (ifcplope), the base element entity (ifcpoting), the canal element entity (ifcpipeesegment), and the like.
S2: the method for creating the BREP geometric entity by packaging the BREP geometric entity by using the C + + language specifically comprises the following steps:
s201: the BREP geometric entities are encapsulated by using the C + + language, and the encapsulated BREP geometric entities comprise face entities (IfcFace), closed shell entities (ifcfosedshell), manifold entities (ifcfacedbrep) and the like.
S202: the encapsulated BREP geometric entity has parameters and a function interface for creating the BREP geometric entity, and can realize the creating function of the BREP geometric entity.
S3: the method for creating the attribute set by using the C + + language encapsulation general attribute set template specifically comprises the following steps:
s301: the method comprises the steps of packaging a universal property set template by using C + + language, enabling the universal property set template to support a custom property item (IfcProperty), enabling the property item to support data types such as floating point type (IfcReal), integer type (IfcInteger), label type (IfcLabel), text type (IfcText) and Boolean type (IfcBoolean), and automatically generating a property set (IfcPropertySet) through the custom property item (IfcProperty).
S302: the encapsulated universal attribute set template has parameters and function interfaces for creating the attribute set, and can realize the creating function of the attribute set.
S4: the method is characterized in that a highway engineering information model data storage class library is formed by using C + + language encapsulation, the function of creating highway engineering information model data in C + + language is supported, and the method specifically comprises the following steps:
s401: and (3) calling the BREP geometric entity in the step (S2) and the general attribute set template in the step (S3) by using a C + + language, and encapsulating the road engineering IFC entity created and derived in the step (S1), wherein the encapsulated space structure entity has the functions of entity relative position and attribute set, and defining aggregation relation with the space structure entities belonging to the upper and lower levels. The encapsulated physical entity has the functions of entity relative position, attribute set, geometric entity, inclusion relation with the space structure entity, and the like.
In order to meet the regulations of the unified Standard for application of Highway engineering information models (JTGT 2420-2021), the data storage class library of the highway engineering information models formed by packaging needs to do the following operations:
(1) packaging a Road entity (Ifcroad) by a Road class (Road), setting a composition type (composionType) of the Road entity (Ifcroad) as an ELEMENT enumeration item (ELEMENT), and representing a Road; the road segment class (RoadSegment) encapsulates the road entity (IfcRoad), and the composition type (composiontype) of the road entity (IfcRoad) is set as a PARTIAL enumeration item (part) to represent a section of road; the road surface type (Pavement) packages a road-based road surface entity (IfcRoadPart), the composition type (compositionType) of the road-based road surface entity (IfcRoadPart) is set as an ELEMENT enumeration item (ELEMENT), and the object type (ObjectType) is set as the classification code of the road surface and represents all the road surfaces of a section of road; the road segment class (PavementSegment) packages a road-based road entity (IfcRoadpart), the composition type (composotion type) of the road-based road entity (IfcRoadpart) is set as a PARTIAL enumeration item (PARTIAL), and the object type (Objecttype) is set as a classification code of a road segment to represent a section of road; the method comprises the steps that a road base class (Subgrade) encapsulates a road base pavement entity (IfcRoadpart), and the composition type (compositionType) of the road base pavement entity (IfcRoadpart) is set as an ELEMENT enumeration item (ELEMENT) to represent all roadbeds of a section of road; packaging a roadbed road surface entity (IfcRoadpart) by a roadbed earth stone side class (subgradedbody), setting a composition type (composition type) of the roadbed road surface entity (IfcRoadpart) as a PARTIAL enumeration item (PARTIAL), and setting an object type (Objecttype) as a classification code of a roadbed earth stone side to represent a section of roadbed earth stone side; the method comprises the steps that a road base pavement entity (IfcRoadpart) is packaged by a road base protection class (subgrade protection), the composition type (CompositionType) of the road base pavement entity (IfcRoadpart) is set to be a part enumeration item (PARTIAL), and an object type (Objecttype) is set to be a classification code of the road base protection to represent a section of road base protection; the roadbed drainage class (subgradedDrainage) packages the roadbed pavement entity (IfcRoadpart), the composition type (CompositionType) of the roadbed pavement entity (IfcRoadpart) is set as a PARTIAL enumeration item (PARTIAL), and the object type (Objecttype) is set as a classification code of roadbed drainage and represents a section of roadbed drainage.
Roadbed element (subgradienelement) packages roadbed element entities (IfcSubgradeElement), pavement element (pavementElement) packages roadbed element entities (IfcPavementElement), side Slope (Slope) packages side Slope element entities (IfcSlope), wall (Wall) packages Wall element entities (Ifcwall), pipe trench (pipe segment) packages pipe trench element entities (IfcPipeSegment), and pool element (IfcTank) packages pool element entities (IfcTank).
The highway class (Road) has a function of creating a Road section class (Road segment), the Road section class (Road segment) has a function of creating a Road surface class (Road) and a Road bed class (Subgrade), the Road surface class (Road) has a function of creating a Road surface section class (Pavement segment), and the Road bed class (Subgrade) has a function of creating a Road foundation earth and stone side class (Subgrade body), a Road bed protection class (Subgrade protection) and a Road bed drainage class (Subgrade drainage). The road surface segment class (pavement segment) has a function of creating a road surface element class (pavement element), the subgrade earth and stone body class (subgrade body) has a function of creating a road surface element class (subgrade element), the subgrade protection class (subgrade protection) has a function of creating a Slope class (Slope), a Wall class (Wall) and the like, and the subgrade drainage class (subgrade drainage) has a function of creating a pipe ditch class (pipeline segment), a pool class (Tank) and the like.
(2) Packaging a bridge entity (Ifcbridge) by a COMPLEX bridge class (Complexixbridge), setting a composition type (ComositionType) of the bridge entity (Ifcbridge) as a COMPLEX enumeration item (COMPLEX) to represent a COMPLEX bridge formed by combining a plurality of bridges; encapsulating the Bridge entity (Ifcbridge) by the single Bridge class (Bridge), and setting the composition type (compositionType) of the Bridge entity (Ifcbridge) as an ELEMENT enumeration item (ELEMENTS) to represent a Bridge; the upper structure class (SuperStruct) encapsulates the bridge structure entity (IfcBridgePart), the composition type (ComponsitionType) of the bridge structure entity (IfcBridgePart) is set as an ELEMENT enumeration item (ELEMENT), and the object type (ObjectType) is set as the classification code of the upper structure to represent the bridge upper structure; the method comprises the steps that an infrastructure class (SubStrect) encapsulates a bridge structure entity (IfcBridgePart), a composition type (composionType) of the bridge structure entity (IfcBridgePart) is set as an ELEMENT enumeration item (ELEMENT), an object type (ObjectType) is set as classification coding of the infrastructure, and the bridge infrastructure is represented; packaging a bridge structure entity (IfcBridgePart) by a bridge deck system and an auxiliary project class (Access), setting a composition type (compositionType) of the bridge structure entity (IfcBridgePart) as an ELEMENT enumeration item (ELEMENT), and setting an object type (ObjectType) as a classification code of the bridge deck system and the auxiliary project to represent the bridge deck system and the auxiliary project; the bridge structure entity (IfcBridgePart) is encapsulated by a bridging class (BridgeUnit), the composition type (composiontype) of the bridge structure entity (IfcBridgePart) is set as a PARTIAL enumeration item (PARTIAL), and the object type (Objecttype) is set as a bridging classification code to represent bridging; the bridge class (BridgeSpan) encapsulates the bridge structure entity (ifcrbridgepart), and the composition type (composiontype) of the bridge structure entity (ifcrbridgepart) is set as a PARTIAL enumeration item (part), and the object type (ObjectType) is set as a classification code of the bridge, representing the bridge.
The guardrail type (Railing) encapsulates the guardrail element entity (IfcRailing), the expansion device type (Fastener) encapsulates the expansion device element entity (IfcFastener), and the bracket type (Member) encapsulates the bracket element entity (IfcMember).
The complex Bridge class (ComplexBridge) has a function of creating a single Bridge class (Bridge), the single Bridge class (Bridge) has a function of creating an upper structure class (SuperStruct), a lower structure class (SubStruct), a Bridge deck and an auxiliary engineering class (Access), the upper structure class (SuperStruct) has a function of creating a Bridge class (Bridge unit), the Bridge class (Bridge unit) has a function of creating a Bridge span class (Bridge), the Bridge span has a function of creating a Beam class (Beam), an Arch class (Arch) and a plate class (Slab), the lower structure class (SubStruct) has a function of creating a Beam class (Beam), a Column class (Column), a foundation class (Footing), a Pile class (Pile) and the like, and the Bridge deck class and the auxiliary engineering class (Access) has a function of creating a Beam class (Rail), a telescopic device (telescopic device), a bracket class (cow), a Beam class (Meter) and the like.
(3) The COMPLEX tunnel type (complexttunnel) encapsulates the tunnel entity (IfcTunnel), and the composition type (composiontype) of the tunnel entity (IfcTunnel) is set as a COMPLEX enumeration item (COMPLEX) to represent COMPLEX tunnels such as double holes; the single-hole Tunnel type (Tunnel) encapsulates the Tunnel entity (IfcTunnel), and the composition type (composionType) of the Tunnel entity (IfcTunnel) is set as an ELEMENT enumeration item (ELEMENT) to represent a single-hole Tunnel; the Tunnel section entity (IfcTunnelPart) is encapsulated by the Tunnel portal class (Tunnel 2E), the composition type (ComplexitionType) of the Tunnel section entity (IfcTunnelPart) is set as an ELEMENT enumeration item (ELEMENT), and the object type (ObjectType) is set as the classification code of the Tunnel portal and represents the Tunnel portal; a tunnel body and auxiliary channel type (Tunnel body) packages a tunnel segment entity (IfcTunnel part), a composition type (ComositionType) of the tunnel segment entity (IfcTunnel part) is set as an ELEMENT enumeration item (ELEMENT), and an object type (ObjectType) is set as a classification code of the tunnel body and the auxiliary channel to represent the tunnel body and the auxiliary channel; the tunnel segment class (tunnel segment) encapsulates the tunnel segment entity (ifctunnel part), the composition type (composiontype) of the tunnel segment entity (ifctunnel part) is set as a PARTIAL enumeration item (part), and the object type (ObjectType) is set as a classification code of the tunnel segment, which represents the tunnel body and the tunnel segment of the auxiliary channel.
The complex Tunnel class (ComplexTunnel) has a function of creating a single-hole Tunnel class (Tunnel), the single-hole Tunnel class (Tunnel) has a function of creating a Tunnel portal class (Tunnel 2E), a Tunnel body and an auxiliary channel class (Tunnel body), and the Tunnel body and the auxiliary channel class (Tunnel body) has a function of creating a Tunnel segment class (Tunnel segment). The Tunnel portal class (Tunnel 2E) has functions of creating a Wall class (Wall), a Slope class (Slope), a pipe ditch class (pipe segment), and the like. The tunnel segment class (tunnel segment) has functions of creating an Arch class (Arch), a foundation class (foundation), a pipe ditch class (pipe segment), and the like.
S5: the method is characterized in that a highway engineering information model data storage interface library is formed by using managed C + + language encapsulation, the function of creating highway engineering information model data by C # language is supported, and the method specifically comprises the following steps:
and (4) packaging the highway engineering information model data storage class library in the step (S4) by using a managed C + + language, realizing all functions of the highway engineering information model data storage class library, forming a highway engineering information model data storage interface library and supporting the function of creating highway engineering information model data by using a C # language.
S6: the method uses a managed C + + language to call a highway engineering information model data storage interface library, supports the function of creating and exporting IFC files in a C # language, and comprises the following steps:
and calling the highway engineering information model data storage interface library in the step S5 by using a managed C + + language to generate highway engineering information model data, realizing the export function of the IFC file, and finally exporting the IFC file. The method can be secondarily developed by using C # language based on BIM modeling software such as Revit, openRoads, dassault and the like, and provides a derivation interface of highway engineering information model data for the BIM modeling software.
The invention uses C + + language to extend and package ifcplus plug-in units to form a highway engineering information model data storage class library, uses managed C + + language to package the highway engineering information model data storage class library to form a highway engineering information model data storage interface library, realizes the function of exporting highway engineering information model data, provides a universal interface for different highway BIM modeling software to export highway engineering information model data, provides a highway engineering information model data export interface which can be developed by using C # language, is universal, convenient and fast and accords with the professional habits of China, and provides convenience for different highway BIM modeling software to export highway engineering information model files.
The present invention has been described in terms of specific examples, which are provided to aid understanding of the invention and are not intended to be limiting. Numerous simple deductions, modifications or substitutions may also be made by those skilled in the art in light of the present teachings.
Claims (3)
1. The IFC-based highway engineering information model data derivation method is characterized by comprising the following steps of:
the method comprises the following steps:
the method for creating and deriving the road engineering IFC entity by using the C + + language realizes the creating function of the road engineering IFC entity, and comprises the following steps:
on the basis of the existing ifcplus plug-in, a road engineering IFC entity is created and derived from a space structure entity and a civil element entity by using a C + + language;
according to the purpose of storing highway engineering information model data, the establishment function of a highway engineering IFC entity is realized;
encapsulating the BREP geometric entity by using C + + language to realize the creating function of the BREP geometric entity, comprising the following steps:
encapsulating BREP geometric entities by using C + + language;
the encapsulated BREP geometric entity has parameters and a function interface for creating the BREP geometric entity, and can realize the creation function of the BREP geometric entity;
the C + + language is used for packaging a universal attribute set template to realize the creating function of the attribute set, and the creating function comprises the following steps:
packaging a universal attribute set template by using C + + language;
the encapsulated universal attribute set template has attribute parameters and a function interface for creating the attribute set, and can realize the creating function of the attribute set;
the method uses C + + language encapsulation to form a highway engineering information model data storage class library, supports the function of creating highway engineering information model data in C + + language, and comprises the following steps:
calling a highway engineering IFC entity, a BREP geometric entity and a general attribute set template by using a C + + language, packaging to form a highway engineering information model data storage class library, and supporting the function of creating highway engineering information model data by using the C + + language;
a highway engineering information model data storage interface library is formed by using managed C + + language packaging, and the function of creating highway engineering information model data by C # language is supported;
and calling a highway engineering information model data storage interface library by using a managed C + + language, and supporting the function of creating and exporting IFC files by using a C # language.
2. The method of claim 1, wherein:
the method is characterized in that a managed C + + language is used for packaging to form a highway engineering information model data storage interface library, and the function of creating highway engineering information model data by using a C # language is supported, and the method comprises the following steps:
and packaging the highway engineering information model data storage class library by using a managed C + + language to form a highway engineering information model data storage interface library and support the function of creating highway engineering information model data by using a C # language.
3. The method of claim 2, wherein:
the method uses a managed C + + language to call a highway engineering information model data storage interface library, supports the function of creating and exporting IFC files in a C # language, and comprises the following steps:
and calling a highway engineering information model data storage interface library by using a managed C + + language, supporting the function of creating highway engineering information model data by using a C # language, and finally exporting the IFC file.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202310113305.2A CN115904552B (en) | 2023-02-15 | 2023-02-15 | Highway engineering information model data export method |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202310113305.2A CN115904552B (en) | 2023-02-15 | 2023-02-15 | Highway engineering information model data export method |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN115904552A true CN115904552A (en) | 2023-04-04 |
| CN115904552B CN115904552B (en) | 2023-05-23 |
Family
ID=85744695
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202310113305.2A Active CN115904552B (en) | 2023-02-15 | 2023-02-15 | Highway engineering information model data export method |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN115904552B (en) |
Citations (7)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| GB9501402D0 (en) * | 1995-01-25 | 1995-03-15 | Univ College Of London | Modelling,analysis and measurement of architectural and other systems |
| US20070168383A1 (en) * | 2005-12-29 | 2007-07-19 | Ulf Fildebrandt | Restrictive visualization of a stereotype construct for entities in a visual modeling environment |
| US20130338972A1 (en) * | 2012-06-13 | 2013-12-19 | International Business Machines Corporation | Building information management (bim) enablement platform of bim data model, data management services apis, restful apis for bim content and meta data hosting, format exchange, and workflow enablement |
| CN106528760A (en) * | 2016-11-04 | 2017-03-22 | 成都希盟泰克科技发展有限公司 | IFC-standard-based analysis model working method applied to engineering project |
| CN109635485A (en) * | 2018-12-24 | 2019-04-16 | 大连海事大学 | Tunnel Dynamic Construction information model component entity extended method based on IFC standard |
| CN110321320A (en) * | 2019-04-01 | 2019-10-11 | 中国核工业二三建设有限公司 | PDMS threedimensional model is converted to the method and device of IFC formatted file |
| CN113221297A (en) * | 2021-03-29 | 2021-08-06 | 湘潭大学 | Method for converting power grid information model into FBX three-dimensional model and storing attributes |
-
2023
- 2023-02-15 CN CN202310113305.2A patent/CN115904552B/en active Active
Patent Citations (7)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| GB9501402D0 (en) * | 1995-01-25 | 1995-03-15 | Univ College Of London | Modelling,analysis and measurement of architectural and other systems |
| US20070168383A1 (en) * | 2005-12-29 | 2007-07-19 | Ulf Fildebrandt | Restrictive visualization of a stereotype construct for entities in a visual modeling environment |
| US20130338972A1 (en) * | 2012-06-13 | 2013-12-19 | International Business Machines Corporation | Building information management (bim) enablement platform of bim data model, data management services apis, restful apis for bim content and meta data hosting, format exchange, and workflow enablement |
| CN106528760A (en) * | 2016-11-04 | 2017-03-22 | 成都希盟泰克科技发展有限公司 | IFC-standard-based analysis model working method applied to engineering project |
| CN109635485A (en) * | 2018-12-24 | 2019-04-16 | 大连海事大学 | Tunnel Dynamic Construction information model component entity extended method based on IFC standard |
| CN110321320A (en) * | 2019-04-01 | 2019-10-11 | 中国核工业二三建设有限公司 | PDMS threedimensional model is converted to the method and device of IFC formatted file |
| CN113221297A (en) * | 2021-03-29 | 2021-08-06 | 湘潭大学 | Method for converting power grid information model into FBX three-dimensional model and storing attributes |
Non-Patent Citations (5)
| Title |
|---|
| CHRISTOPH EMUNDS等: "SpaRSE-BIM: Classification of IFC-based geometry via sparse convolutional neural networks", ADVANCED ENGINEERING INFORMATICS * |
| 南春丽;张生瑞;严宝杰;: "异构数据源城市道路仿真模型接口", 计算机工程与应用 * |
| 徐照;张路;索华;迟英姿;: "基于工业基础类的建筑物3D Tiles数据可视化", 浙江大学学报(工学版) * |
| 邱勇云;邱相武;赵志安;: "工程软件中C++与FORTRAN之间数据传递方法研究", 计算机与数字工程 * |
| 陈远;康虹;张静雅;: "基于IFC标准的BIM模型编程语言解析方法研究", 土木建筑工程信息技术 * |
Also Published As
| Publication number | Publication date |
|---|---|
| CN115904552B (en) | 2023-05-23 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN110222445B (en) | BIM and design information based integration, collaborative design and delivery method and system | |
| CN109711052A (en) | Tunnel model creation method based on Revit+Dynamo | |
| Amann et al. | A refined product model for shield tunnels based on a generalized approach for alignment representation | |
| Choa et al. | Corsim, paramics, and vissim: What the manuals never told you | |
| CN111368437A (en) | Railway roadbed engineering design method based on BIM technology | |
| Huang et al. | Design of track alignment using building information modeling | |
| KR20160113512A (en) | Method for Hierarchical Schema Representation for 3-Dimensional Information Model of Civil Facilities | |
| Scarponcini | OGC® Land and Infrastructure Conceptual Model Standard (LandInfra), Version 1.0. | |
| JP6194160B2 (en) | Process management data generation device, process management data generation method, process management data generation program, and recording medium | |
| CN115904552A (en) | Highway engineering information model data derivation method | |
| CN110765541A (en) | Method and device for establishing BIM (building information modeling) model of subway station enclosure structure and storage medium | |
| Georgoula et al. | Development of an Autodesk Revit Add-in for the Parametric Modeling of Bridge Abutments for BIM in Infrastructure | |
| Schnell et al. | Evaluation of Traffic Flow Analysis Tools Applied to Work Zones Based on Flow Data Collected in the Field | |
| Eslahi et al. | BIM and Contribution to IFC-Bridge Development: Application on Raymond Barre Bridge | |
| Borrmann et al. | The IFC-Tunnel project–Extending the IFC standard to enable high-quality exchange of tunnel information models | |
| Zhou et al. | Application of building information modeling technology in the design phase of municipal interchange project | |
| Yue et al. | Road network model for vehicle navigation using traffic direction approach | |
| Malaikrisanachalee et al. | Lane-based network for flow analysis and inventory management of transportation networks | |
| Wallbank et al. | Collision Prediction Model for the Irish National Road Network: Phase 2 Report | |
| de Oliveira et al. | Linking infrastructure IFC models with databases | |
| CN117290936A (en) | BIM+GIS-based railway interval house total image design method and system | |
| Campodonic et al. | Integrating a modern light rail transit (LRT) system into an historic city centre | |
| McNichol | Devil’s Slide Tunnel | |
| Hecox | A Majestic Showcase | |
| Shake | Recycled material web map: Connecting consumers and producers |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |