In the datagroup catalog you can define your own items. We have a dataset built from scratch, but it raises some questions. I'll use the Catalog Item "Concrete floor " as an example.
Using “Slabs” or “Floors”? How do I know which Catalog Type I use for this Catalog Item?
I defined the Catalog Item "Concrete Floor" in theCatalog Type "Slabs", which makes it show up using the commando "Slabs". So this works. But there is also a Catalog Type called "Floors". Should I use that one instead?
If not, why do we have "Floors" and "Roofs" if I have to define those as “Slabs”?
How are the Catalog Types/Items linked to the commandos? Where can I see which toolbar/button they are linked to?
If I have to use “Floors”, which commando do I use to place it? An Item defined in "Floors" it doesn't seem to show up in the place Slab commando, but I have no idea where else it would show up...
Is there a way to see only structural elements when using the structural toolbar?
My "Concrete floor" shows up in the Slabs using the "place Floor Slab" commando, in both the "Architectural Design" as the "Structural Modelling" buttons.
I would expect using the button in the structural toolbar, I would only see the slabs defined as 'structural' in the DataGroup Catalog".
Answer Verified By: StefanC
Ok, so seems the way I do it makes sense.
One question remains: how do I know which datagroup Type/Item is linked to which commando? Now I have this huge list with Types of which I only have to use Slabs and Walls to define like 95% of my architectural items.
For example: Catalog Item "Ramp", how do I know what it does, which commando uses this Item?
Windows 10 pro
OpenBuildings Designer Connect Edition 2023 | 23.00.00.114
Marc
hi Marc,
Ok I understand the concept of which drag and drop works and which not :-)
Still a weird thing:
1. I create a Subgroup (in Architectural) with a Type and Item:
2. Save and close the Editor, then reopen:
The Type and Item are still there, but the Subgroup is gone! The Type is now directly under Architectural...
EDIT: i tested the same thing in the Dataset_GB, and it worked fine. So it must be somewhere in our custom dataset...
Makes me wonder: If you built a dataset from scratch, you never now with each update what you need to change/add in your dataset to make sure it works fine. You can start to compare files but still you don't always know in which files you edited things to fit your own wishes.