When exporting to the IFC, keep a different identification for each item.
When exporting the IFC, each element is identified by a default value. For example, all solids come out with an identification as smartsolid. This makes it very difficult to search for an element in the model.
Adding to the topic: in OpenRoads the name is defined from the feature definition, but not all elements can have a feature. And even this workflow constantly shows errors.
For example Solids. It's not capable to asign a feature to it, so there is no way to name it for the ifc. It always exports as "smart solid". Our workaround for now is to transform the solids into meshes, apply a feature def and then export.
The problem is that it adds a lot of workhours and makes the ifc way heavier (solids size << mesh size)
My suggestion is to improve the whole naming process for ifc and make it more clear as how it works: a SchemaMapping.json file is not intuitive or easy to scale to other users, this is a CAD software, users are far from being programmers and should not be required to.
An easy fix would be to respect an itemtype just like the IfcClassification one, but that is not ideal. It's would in fact be a very bad example of UI.
The picture shows an Opentunnel model in ifc. All elements are called smartsolid. In openroads there is a new option where you can call the components according to the feature definition.
Adding to the topic: in OpenRoads the name is defined from the feature definition, but not all elements can have a feature. And even this workflow constantly shows errors.
For example Solids. It's not capable to asign a feature to it, so there is no way to name it for the ifc. It always exports as "smart solid". Our workaround for now is to transform the solids into meshes, apply a feature def and then export.
The problem is that it adds a lot of workhours and makes the ifc way heavier (solids size << mesh size)
My suggestion is to improve the whole naming process for ifc and make it more clear as how it works: a SchemaMapping.json file is not intuitive or easy to scale to other users, this is a CAD software, users are far from being programmers and should not be required to.
An easy fix would be to respect an itemtype just like the IfcClassification one, but that is not ideal. It's would in fact be a very bad example of UI.
The picture shows an Opentunnel model in ifc. All elements are called smartsolid. In openroads there is a new option where you can call the components according to the feature definition.
Can you please post a screenshot? Thanks!