It seems that the mapping of a parameter to a Common Pset isn't working anymore.
In the attached sample the walls and the space have a parameter IfcObjectType (with value = value_override_IfcObjectType). By export (making use of the mapping txt file) they should be mapped to the Reference in the Pset_XxxCommon, but it seems that this isn't working anymore (compared to 18.2.0).
I just hope that I'm not too much a pain in ...
(completely off topic) IfcAsset would be a nice addition :-)
A temporary solution at the moment is to add a Reference parameter = {$this("IfcObjectType")}
It does the job at the moment, except for Generic Models, Railings, Structural Area Reinforcement.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Misusing this topic,
just to add that it seems that also the automatic mapping of "Function" to IsExternal in the Pset_XxxCommon isn't working anymore (for Walls and Floors).
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Good catch. We added some code to automatically generate property set lists - the calculator needed to change names from ExternalCalculator to IsExternalCalculator. Amazing how much trouble 2 missing characters can cause!
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I appreciate very much your willingness to make all these improvements or corrections.
Version 18.4 is really something to look forward to, but I understand that testing will need its time before it can be released.
Some wellknown viewers aren't making it easy to evaluate or test the export results, since they have their own rarities (or bugs or issues). In many cases only notepad++ will clear things out.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Yes, but no (hm, it sounds a bit like Vicky Pollard)
v.18.4
IFC4RV1: indeed for IfcSpace its fixed that the objecttype can be mapped again to the reference in the Pset_SpaceCommon. But it seems that this mapping is automatically done by the exporter, even when the 'mapping' is unchecked.
But in the sample as posted, I don't see it working for IfcWall. Even if I add a generic model with IfcExportAs=IfcWall, it's not doing anything at all.
I tried a lot of the other entities ... with no luck
IFC2x3CV2: for IfcSpace the mapping seems not to work (and also not for other entities)
So, I'm very in doubt that it is fixed... but of course I could overlooked something.
I retested it with R2018 (18.4) and R2019 (19.1) for IFC2x3CV2 and IFC4RV1:
the mapping is indeed fixed!
I discovered an issue in my mapping file.
While the custom mapping file allows multiple mappings to the same parameter (where the first match is exported), this isn't allowed (anymore?) in the mapping file for common parameters.
Regards,
Dirk
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
R2018.3 exporter 18.3.2
IFC2x3CV2.0
It seems that the mapping of a parameter to a Common Pset isn't working anymore.
In the attached sample the walls and the space have a parameter IfcObjectType (with value = value_override_IfcObjectType). By export (making use of the mapping txt file) they should be mapped to the Reference in the Pset_XxxCommon, but it seems that this isn't working anymore (compared to 18.2.0).
Regards,
Dirk
Last edit: Dirk Van Rillaer 2018-04-28
we will check that. v18.4 has much more rigorous testing.
I just hope that I'm not too much a pain in ...
(completely off topic) IfcAsset would be a nice addition :-)
A temporary solution at the moment is to add a Reference parameter = {$this("IfcObjectType")}
It does the job at the moment, except for Generic Models, Railings, Structural Area Reinforcement.
Misusing this topic,
just to add that it seems that also the automatic mapping of "Function" to IsExternal in the Pset_XxxCommon isn't working anymore (for Walls and Floors).
Thanks for all of the detailed checking!
Good catch. We added some code to automatically generate property set lists - the calculator needed to change names from ExternalCalculator to IsExternalCalculator. Amazing how much trouble 2 missing characters can cause!
I appreciate very much your willingness to make all these improvements or corrections.
Version 18.4 is really something to look forward to, but I understand that testing will need its time before it can be released.
Some wellknown viewers aren't making it easy to evaluate or test the export results, since they have their own rarities (or bugs or issues). In many cases only notepad++ will clear things out.
Checking back in - looks like the issue at the top of this thread is fixed in the 18.4 exporter.
Hi Andy,
Yes, but no (hm, it sounds a bit like Vicky Pollard)
v.18.4
IFC4RV1: indeed for IfcSpace its fixed that the objecttype can be mapped again to the reference in the Pset_SpaceCommon. But it seems that this mapping is automatically done by the exporter, even when the 'mapping' is unchecked.
But in the sample as posted, I don't see it working for IfcWall. Even if I add a generic model with IfcExportAs=IfcWall, it's not doing anything at all.
I tried a lot of the other entities ... with no luck
IFC2x3CV2: for IfcSpace the mapping seems not to work (and also not for other entities)
So, I'm very in doubt that it is fixed... but of course I could overlooked something.
Regards,
Dirk
Hi Andy,
I retested it with R2018 (18.4) and R2019 (19.1) for IFC2x3CV2 and IFC4RV1:
the mapping is indeed fixed!
I discovered an issue in my mapping file.
While the custom mapping file allows multiple mappings to the same parameter (where the first match is exported), this isn't allowed (anymore?) in the mapping file for common parameters.
Regards,
Dirk