IDS import creates IFC Properties as Archicad properties

[stefan]

When you import an IDS file, every property/property set as specified in the IDS, will be included to get imported. However, this way, your Archicad model gets a bunch of Pset_WallCommon and Pset_DoorCommon etc... with no distinction based on classification. This way, a carefully planned model can be filled with "noise".

Now EVERY object gets the Pset_WallCommon and other properties as custom Archicad properties. This means you have to painstakingly redo the classification mappings. Is this the intended workflow?

Operating system used: Mac Apple Silicon

[Zoltan Vale · Accepted solution]

Hi @stefan ,

This is somewhat intended, yes. As the first iteration of IDS support we wanted to give users the ability to work with IDS files, even if that means that some post-import configuration has to be done, it is still faster than manually adding the data from an excel sheet. But your point is valid, so we are already working on making the imported properties available for only the classifications specified in the IDS specification applicability and not set them to "All" by default.