It appears IfcGeographicElement doesn't have something like a Pset_GeographicElementCommon pset--and thus no status property.
How does one go about phasing things? new/existing/demolish, etc?
If custom, would think a custom pset like Pset_GeographicElementCommon, along with an enumerated list of values such as ["NEW", "EXISTING", "DEMOLISH", etc.], would be best, as I would think you can use a value like r"Pset_.*Common" in the EPset_Drawing.Metadata and have it export out the same CSS classes as the other objects that have the Pset_.*Common Pset.
I guess most of the IfcBuildingElement has status in pset_common. But yes, would love to know how this is being done for the like IfcDistributionElement @theoryshaw did custom pset work out well
Comments
Related thread:
https://community.osarch.org/discussion/1030/blenderbim-versioning-phasing/p1
I would think a Custom Pset?

Also, why can't I edit the
StringProperty
name?If custom, would think a custom pset like
Pset_GeographicElementCommon
, along with an enumerated list of values such as ["NEW", "EXISTING", "DEMOLISH", etc.], would be best, as I would think you can use a value liker"Pset_.*Common"
in the EPset_Drawing.Metadata and have it export out the same CSS classes as the other objects that have the Pset_.*Common Pset.Also, does anyone know how to phase
IfcDistributionElement
?https://ifc43-docs.standards.buildingsmart.org/IFC/RELEASE/IFC4x3/HTML/lexical/IfcDistributionElement.htm
BuildingSmart stopping me from just creating a custom pset to make phasing simpler...
I guess most of the
IfcBuildingElement
has status in pset_common. But yes, would love to know how this is being done for the likeIfcDistributionElement
@theoryshaw did custom pset work out well
I guess add IfcSpace, to the list. :\
IfcVirtualElement
related:
related:
