What Marcin really wanted to say is the following:
But when you create the IFC tree, the hierarchy of the entities IFCrailway, IFCRoad, etc. does not depend on IFC Facility, as it is another entity with the same rank (I use it when I have a tunnel).
the 'grey area' I mentioned earlier is the one referring to IfcBridgePart
for this particular case some nesting should be allowed provided that it respect the CompositionType ELEMENT, COMPLEX, PARTIAL
maybe the same should be also allowed to IfcRoad and IfcRailway, nested *Part make far more sense than IfcSpace, which looks suited for buildings not infraworks (my 2c)
sorry about number of posts but the topic is not that simple to handle in one go
this is a representation of IfcRoad decomposition in Marcin's webpage, but maybe IfcFacilityPart should be replaced with IfcRoadPart to avoid confusion
Not there yet ;)
another question came up in connection with IfcAssembly and IfcAlignment. Can I assign imported objects to fresh created IfcAssemblies and IfcAlignment objcets to be able to document properties in that "grouping" level? We now use "real" 3D objects as dummies as placeholders.
thanks!
Comments
What Marcin really wanted to say is the following:
But when you create the IFC tree, the hierarchy of the entities IFCrailway, IFCRoad, etc. does not depend on IFC Facility, as it is another entity with the same rank (I use it when I have a tunnel).
@BimETS
nice one, thanks
So something like this should work
the 'grey area' I mentioned earlier is the one referring to IfcBridgePart
for this particular case some nesting should be allowed provided that it respect the CompositionType ELEMENT, COMPLEX, PARTIAL
maybe the same should be also allowed to IfcRoad and IfcRailway, nested *Part make far more sense than IfcSpace, which looks suited for buildings not infraworks (my 2c)
more from the same author author
sorry about number of posts but the topic is not that simple to handle in one go
this is a representation of IfcRoad decomposition in Marcin's webpage, but maybe IfcFacilityPart should be replaced with IfcRoadPart to avoid confusion
I think I got it:
now ... next task is to move 3D objects from different IFCs into these structure. wish me luck :)
Not there yet ;)
another question came up in connection with IfcAssembly and IfcAlignment. Can I assign imported objects to fresh created IfcAssemblies and IfcAlignment objcets to be able to document properties in that "grouping" level? We now use "real" 3D objects as dummies as placeholders.
thanks!