search

LaurensJN / IFC

IFC schema management and versioning repository
https://technical.buildingsmart.org/
3 stars 1 forks source link

Is there any way to add a Pset as column definition instead of a single property? #5

Open LaurensJN opened 3 years ago

LaurensJN commented 3 years ago

See title. When adding a column definition to a model view, only single properties can be added from Psets. Is there any way to define multiple properties at once? Or should that be avoided?

LaurensJN commented 3 years ago

@pjanck I know we talked about this issue today and that the answer will probably be in the use of templates. I will leave it here and post the answer if I discovered it myself.

SergejMuhic commented 3 years ago

There is yes. The only problem with that is that I did not implement the partial templates yet. Consequently, you are not able to access individual properties from the UI. It is possible to set them in the mvdxml but the UI does not support this. Please post your request on the bSI forums. The more requests there are, the more bSI is under pressure to do something. I could do this but I do not have any spare "free" time to devote to bSI.

LaurensJN commented 3 years ago

Thanks for the reply.

I added a topic to the forum! See https://forums.buildingsmart.org/t/ifcdoc-add-property-set-as-column-definition-instead-of-a-single-properties/3416/2

I now worked around this by preparing my own template and adding this one to the column definitions

SergejMuhic commented 3 years ago

I now worked around this by preparing my own template and adding this one to the column definitions

Why not use the existing templates? Defining own templates only ensures that it will never be supported as no software vendor will implement it.

LaurensJN commented 3 years ago

In that case I'm not entirely sure how to use existing templates. I also was under the impression you were encouraged to make your own concept templates.

Next to that, there is the issue of referencing the right class. If I would want to add the Property Sets for Objects template as a column definition for the IfcElement class, it will change the main element to IfcObject instead of IfcElement. See here. image

Also, where should I define the actual properties in the propertyset? If I would change the tree in the Query tab, the template itself changes too (which I do not think should happen). image

Should I add them in the Parameters tab? Like this: image

There is also no way to add complex properties like that (only single value / enumeration / bounded / list etc.). Should these be added in a different way?

It's a lot of questions, I hope I'm not bugging too much :smile:

pjanck commented 3 years ago

The properties template is applicable to IfcObject, which in turn makes it applicable to IfcElement. You can specify that you only wish to check for IfcElement in the "ApplicableEntity" attribute within mvdXML, I'm not sure where to set that in IfcDoc - I assume it gets set as you apply the template to a specific entity. And this would allow you to use the template. The Query screenshot seems familiar from the mvdXML structure.