Potentially missing psets / qtos for IfcFacility, IfcFacilityPart, IfcDeepFoundation, IfcCaissonFoundation, IfcVibrationDamper, IfcTendonConduit

[Moult]

Originally reported here by kevin nahaboo: https://forums.buildingsmart.org/t/ifc-4-2-pset-qto-missing-on-new-entities/2372

IFC 4x2 introduce new spatial and physical elements. My question is why there is no Pset/Qto for following entities : Spatial entities : IfcFacility, IfcFacilityPart. Physical entities : IfcDeepFoundation, IfcCaissonFoundation, IfcVibrationDamper, IfcTendonConduit.

Can we get a double check on the status of this? Here's my attempt:

• IfcFacility: no pset/qto found. Is this OK?
• IfcFacilityPart: found https://github.com/buildingSMART/IFC4.3.x-output/blob/master/psd/Qto_FacilityPartBaseQuantities.xml but the properties within don't make too much sense to me. Maybe I don't know the domain, but someone should take a look.
• IfcDeepFoundation: none found. Is this OK?
• IfcCaissonFoundation: none found. Is this OK?
• IfcVibrationDamper: none found. Is this OK?
• IfcTendonConduit: none found. Is this OK?

[berlotti]

@berlotti double check + close

[ccast1]

supposed to be closed

[aothms]

One thing that the Pset_XCommon provides minimally is the Status PEnum_ElementStatus field.

I know it's far from ideal to represent this kind of information scattered over many many psets, but it's how it's currently done.

An example of a minimal pset is for example for CivilElement http://ifc43-docs.standards.buildingsmart.org/IFC/RELEASE/IFC4x3/HTML/lexical/Pset_CivilElementCommon.htm

I see no reason why other leaf classes won't get this pset?

[Moult]

I don't think this is supposed to be closed.

Out of 137 total leaf classes of IfcElement, there are only 15 (excl. deprecated) with no properties or quantities:

• IfcNavigationElement
• IfcCaissonFoundation
• IfcConveyorSegment
• IfcLiquidTerminal
• IfcVoidingFeature
• IfcTransportElement - see bug #421 someone deleted it potentially by accident
• IfcBuildingElementPart
• IfcReinforcingBar - see bug #354 properties will likely be added
• IfcReinforcingMesh - see bug #354 properties will likely be added
• IfcTendon - see bug #354 properties will likely be added
• IfcTendonAnchor
• IfcTendonConduit
• IfcGeomodel
• IfcGeoslice
• IfcVoidStratum

The majority are infra additions (marked in bold). These seem like anomalies because they do not follow the rules of all the other leaf classes.

I ran the same analysis for IfcSpatialElement. Out of 15 total, there are 3 with no properties or quantities.

• IfcExternalSpatialElement
• IfcRailway
• IfcBridgePart

We probably won't get this solved in the next day for the deadline, but I hope the list above clarifies the issue.

[TLiebich]

for me those are perfectly fine issues for an updated submission in about two-months from now.