You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Selecting IfcSpace elements in a model cannot be achieved using the Location filter since that particular class does not live in a Spatial Container but it is aggregated to it.
It would be easier to allow IfcSpace to be filtered by IfcBuildingStorey for data extraction and other purposes
The text was updated successfully, but these errors were encountered:
Hi,
I had similar thoughts. I would suggest to add new search facet/category - 'Agregated by' or 'Part of'. Just because, as you mentioned, according to ifc schema, we are talking about two different relationship types. We canot use IfcBuildingStorey as spatial container for IfcSpace, so we should not use Location facet to find IfcSpace, I think.
--
I believe that Selector can also be way to go, when it evolve into something less experimental (I cross fingers):
I found interesting introduction to Selector power, by Vukas Pajic @ BimVoice:
Selecting IfcSpace elements in a model cannot be achieved using the
Location
filter since that particular class does not live in a Spatial Container but it is aggregated to it.It would be easier to allow IfcSpace to be filtered by IfcBuildingStorey for data extraction and other purposes
The text was updated successfully, but these errors were encountered: