Are you asking "why do we have to make these modifications when it should be standard?" Send us your modifications, and we'll see if they can be made standard :)
Thanks,
Angel
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Thanks Angel, sorry for being unclear, what I meen is, why is the file ParameterMappingTable.txt not included in the installation folder?
Another question, in the export UI on the Property Sets tab there is the option to "Export IFC common property sets" AND an option to set a path to the Paramter Maping Table. If that path is not set to a correct file, will the exporter then search for the mappingfile in the installation folder? My guess is that the option is there to centralize the file for all users on the network, am I right or does that path do something alse?
\PT
Last edit: Peter Tranberg 2017-09-15
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I see that, but wouldn't you rather use the the "Export User defined prperty sets" file for that? There is a sample file for that in the installation folder, thats why i wonder about the ParameterMapping.txt not existing in the installationfolder. Why do we have to search the internet for that? I know hov to make it, I just meen that it could be more clear with an example for inexperienced users.
\PT/
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Effectively, it is not clear for me on how to create User defined property sets using "ParameterMappingTable.txt" file instead of the "DefaultUserDefinedParameterSets.txt".
I thought it was only for the "supported" Psets properties listed in another wiki page.
I was not able to make it work. I don't know if it is a question of installation, even when pointing ParameterMappingTable in the UI dialog box.
Could you explain to me how to create these users user defined property sets in the parameter mapping table, and if this parametermappingtable.txt shall be installed somewhere specific in order to work.
Thanks in advance
Best Regards
Joao-Carlos
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Is there any mapping file or explanation for Export IFC common property sets process in Revit?
There is a lot of common Psets specified for each IfcEntity in BuildingSmart standard, especially for IFC 4.3, however, there's no clear guide how some of these Psets are exported and mapped from Revit since currently great number of Revit Categories don't have respective properties by default. (e.g. IsExternal). I'm really interested how Beams, Structural Columns, Windows, etc. get this property if "Export IFC common property sets" is enabled.
Last edit: Mileta Pejovic 2022-04-22
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
For the common property sets, only a few come from Revit internal properties, and they are on the Wiki here. In general, though, you can create shared parameters with the name PSet.Property (e.g. Pset_WallCommon.FireRating) and that value will be used for export. We provide a shared parameters file that has these values; moving forward, these properties will also be part of the Unified Parameters Service to make it easier to populate your Revit project with the right parameters.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Hello.
Regarding the Mapping from Revit "into" the common PSets, is there a way to override the hardcoded "builtin parameter" mapping? I mean, i.e. I would like the PSet.WallCommon FireRating to go into the IFC4 from an Instance Parameter instead of from the family parameter, but I can not find a way to override it using the PSet.txt and the Map.txt files.
And furthermore, where can I find the mentioned "reference table" of all these hardcoded built in parameter mappings?
Thanks in advance!!
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I understood from your question that you want to override the common property definition FireRating based on an Instance revit parameter and not a Type parameter. In Revit, the type parameter which will be exported to the FireRating IFC property is "Fire Rating" (with space) and this is a built-in parameter. To override this info you can create an Instance parameter "FireRating" which will override the Type parameter information and then you achieve what you want.
Thanks Joao. I think this really gives me a way to test things further. Thanks a lot!!
(I guess it was just logical that I was not the first to face this conundrum)
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
miguel, i hope i understand your question
my solution is to disable the export of standard psets and revit psets to only export user defined psets. ther you can setup whatever you want. (like changing the FireRating from a type parameter to instance)
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Thanks, Peter. This "workaround" have we already tried, and it works. The point is that we would very much like to adhere to the IFC standard PSets.Xcommon so our goal is to be able to extract the info from the source we want and not from the one Revit forces us to...
Is it somewhat possible?
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
To modify the Common Psets we use the ParameterMappingTable.txt, but why is it not a part of the installation???
Regards Peter
Are you asking "why do we have to make these modifications when it should be standard?" Send us your modifications, and we'll see if they can be made standard :)
Thanks,
Angel
Thanks Angel, sorry for being unclear, what I meen is, why is the file ParameterMappingTable.txt not included in the installation folder?
Another question, in the export UI on the Property Sets tab there is the option to "Export IFC common property sets" AND an option to set a path to the Paramter Maping Table. If that path is not set to a correct file, will the exporter then search for the mappingfile in the installation folder? My guess is that the option is there to centralize the file for all users on the network, am I right or does that path do something alse?
\PT
Last edit: Peter Tranberg 2017-09-15
the mapping table is not just for the common sets. You can create custom Psets with it.
I see that, but wouldn't you rather use the the "Export User defined prperty sets" file for that? There is a sample file for that in the installation folder, thats why i wonder about the ParameterMapping.txt not existing in the installationfolder. Why do we have to search the internet for that? I know hov to make it, I just meen that it could be more clear with an example for inexperienced users.
\PT/
Hello,
Effectively, it is not clear for me on how to create User defined property sets using "ParameterMappingTable.txt" file instead of the "DefaultUserDefinedParameterSets.txt".
I thought it was only for the "supported" Psets properties listed in another wiki page.
I was not able to make it work. I don't know if it is a question of installation, even when pointing ParameterMappingTable in the UI dialog box.
Could you explain to me how to create these users user defined property sets in the parameter mapping table, and if this parametermappingtable.txt shall be installed somewhere specific in order to work.
Thanks in advance
Best Regards
Joao-Carlos
Is there any mapping file or explanation for Export IFC common property sets process in Revit?
There is a lot of common Psets specified for each IfcEntity in BuildingSmart standard, especially for IFC 4.3, however, there's no clear guide how some of these Psets are exported and mapped from Revit since currently great number of Revit Categories don't have respective properties by default. (e.g. IsExternal). I'm really interested how Beams, Structural Columns, Windows, etc. get this property if "Export IFC common property sets" is enabled.
Last edit: Mileta Pejovic 2022-04-22
For the common property sets, only a few come from Revit internal properties, and they are on the Wiki here. In general, though, you can create shared parameters with the name PSet.Property (e.g. Pset_WallCommon.FireRating) and that value will be used for export. We provide a shared parameters file that has these values; moving forward, these properties will also be part of the Unified Parameters Service to make it easier to populate your Revit project with the right parameters.
Hello.
Regarding the Mapping from Revit "into" the common PSets, is there a way to override the hardcoded "builtin parameter" mapping? I mean, i.e. I would like the PSet.WallCommon FireRating to go into the IFC4 from an Instance Parameter instead of from the family parameter, but I can not find a way to override it using the PSet.txt and the Map.txt files.
And furthermore, where can I find the mentioned "reference table" of all these hardcoded built in parameter mappings?
Thanks in advance!!
Hi Miguel,
I understood from your question that you want to override the common property definition FireRating based on an Instance revit parameter and not a Type parameter. In Revit, the type parameter which will be exported to the FireRating IFC property is "Fire Rating" (with space) and this is a built-in parameter. To override this info you can create an Instance parameter "FireRating" which will override the Type parameter information and then you achieve what you want.
If this is really your objective than please take a look into https://forums.autodesk.com/t5/revit-structure-forum/manage-parameter-quot-pset-columncommon-isexternal-quot/m-p/10410847#M43946. The example is with "IsExternal"
I think you might want to have something like this https://github.com/xpt5/shareRevit/blob/main/revitCat_IfcEntities.ods. This is a work in progress table and is based on IFC2x3
Thanks Joao. I think this really gives me a way to test things further. Thanks a lot!!
(I guess it was just logical that I was not the first to face this conundrum)
miguel, i hope i understand your question
my solution is to disable the export of standard psets and revit psets to only export user defined psets. ther you can setup whatever you want. (like changing the FireRating from a type parameter to instance)
Thanks, Peter. This "workaround" have we already tried, and it works. The point is that we would very much like to adhere to the IFC standard PSets.Xcommon so our goal is to be able to extract the info from the source we want and not from the one Revit forces us to...
Is it somewhat possible?