Hi Bentley
Something that has been annoying me for years.
Within default OBD, if you were creating an infrastructure building, the catalogs are limited to what would typically be included within a real building, even if you were to design a house, it is limited
Each project we design, the dataset has to be enhanced to suit the building. it would be great if Bentley were to review the catalogs and actually add the missing data. as an example
Floors - almost next to useless
Roof - extremely poor, plus poor tool.
Structural concrete - limited to beams and columns, no option for bespoke precast concrete
Railing - US dataset has much better railings than UK dataset Stairs - very poor tool
To give this more context, if you have a bespoke roof, made up of numerous materials, trying to find the right catalog is painful, or is missing
We need tools that work out of the box, that give the users the functionality they need at the finger tips
Ian
| How frequently will feature be used? | Several times a day |
| How much time will you save? | Hours and hours |
@Guest We are always open to ideas improving the datasets and we recognize we face challenges. OBD is used across multiple project types in infrastructure. Even for a single use case, we would be hard-pressed to provide an extensive library of object definitions and examples that would be needed due to the sheer size of the dataset that would be created. We would hit performance issues with indexing the catalogs and preparing dialog boxes, etc. What we can do is take your suggestions if you would be more specific in your descriptions of what is needed to be out of the box. We maybe able then to create those definitions and deliver them as a part of the datagroup catalog backup libraries. That way, users could activate and deactivate samples as required. This approach would still increase the dataset folder size and subsequently downloads etc. but it would not necessarily impact dialog loading times and other activities.