topic Re: IDS import creates IFC Properties as Archicad properties in Collaboration with other software

IDS import creates IFC Properties as Archicad properties

stefan — Wed, 04 Dec 2024 18:11:01 GMT

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

Re: IDS import creates IFC Properties as Archicad properties

Zoltan Vale — Thu, 12 Dec 2024 07:27:54 GMT

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.

Re: IDS import creates IFC Properties as Archicad properties

davdelven — Wed, 07 May 2025 15:58:08 GMT

@Zoltan Vale How to ask Graphisoft to add the new entry for IDS import implementation on buildingSMART International website? https://technical.buildingsmart.org/ids-software-implementations/

Re: IDS import creates IFC Properties as Archicad properties

davdelven — Wed, 07 May 2025 15:57:41 GMT

@Zoltan Vale What about the properties you already have defined within through the IFC Translator Property Mapping setting (or IFC Project Manager / Object Setting bottom dialogue)?

Re: IDS import creates IFC Properties as Archicad properties

Zoltan Vale — Thu, 08 May 2025 07:28:00 GMT

Hi @davdelven ,

I have added Graphisoft Archicad to the list of implementers on the buildingSmart site. They only provide options for IDS authoring or IDS based checking. So in the situation where importing is not explicitly separated I have added IDS authoring to the list and also updated some other missing information there.

In regards to the properties, when we import from IDS:

First we try to create the native Archicad properties. If any already exist then we consider the user created one "stronger" and we do not overwrite or change it.
Then we try to create IFC properties and mappings accordingly, but it is the same case here. If there is an already existing property or mapping with the same name then we do not touch that. We only create data that is new, since we think user defined data is stronger.
If you already created some IFC data and mappings and would like to only extend that with some IDS source based data, then select an already existing IFC mapping preset when importing the IDS, instead of creating a new one, so this way you will keep your already set up data and also extend it with some additional new ones coming from the IDS requirements.

Hope this helps to clarify a bit,
Have a great day.

Re: IDS import creates IFC Properties as Archicad properties

davdelven — Thu, 08 May 2025 07:54:02 GMT

Thank you for the clarification, @Zoltan Vale

So if I understand correctly, the optimal workflow would be to select one of my existing IFC mapping presets when importing an IDS file, rather than creating a new preset. This way Archicad will preserve all my current IFC property configurations while only adding the new properties from the IDS requirements that don't already exist in my setup.

This incremental approach makes sense as it allows me to maintain my carefully configured mappings while still benefiting from the standardized properties in the IDS specification.

Have you considered adding an option in future versions to visualize which properties would be added versus preserved before completing the import? This could help users make more informed decisions about which existing preset to use.

Re: IDS import creates IFC Properties as Archicad properties

stefan — Thu, 08 May 2025 08:07:28 GMT

@davdelven That seems to be a good suggestion. I was already hoping that the IFC mappings could be recovered, but I didn't fully grasp the most optimal workflow, hence my post.