I send another revit file, ifc file and custom parameter mapping file (Exported with 18.4.0 version). In the IFC file you can see that common property sets as Pset_SlabCommon is duplicated. This did not happen in former versions of the IFCExporter. This is quite annoying because some ifcviewers like navisworks show all this duplicated propertysets when you select an element.
I send Revit 18 file, Custom PropertySets mapping file, and IfcFile. You can see how slabs and walls have double CommonPropertySets, and double Custom PropertySets.
With the last version of IFCExporter (18.4.0) Custom property sets are duplicated and also CommonPropertySets. How can I solve It to not happen? Thanks
When you export A structural beam sistem to IFC it exports all the beams as a Assembly class and with Beam_GRID as Predefined Type. This is nice. When you export a Truss it exports all the Truss as an Assembly class (this is fine and correct) and exports the cords as IfcBeams and the rest (diagonals) as IfcMembers. I think cords should be also exported as IfcMembers. It would be nice if this is included in the code because using IfcExportAs parameter I need to create to types (if the same beam acts...
Seems like Revit when it comes to link a IFC uses the internal origin as (0,0,0). So if I have a IFC with real coordinates it does not "go" to the correct place, because if configure the site properties of the revit files indicating that the "internal origin" has coordinates (10,10,10), and I insert an IFC link with an object at coordinates (0,0,0) Revit send it to the internal origin so it is 10 units shifted. which is the correct way to link an IFC file so it is located in his real position? Thanks...
Dirk, it looks like CommonPropertySets of Project and Site are not suported by the IFC Exporter. I only manage to get commonpropertysets from IFCbuilding to the rest of building elements. Would be nice if IFC Exporter also suports Project and Site common propertysets. Miquel
Ok Dirk, I did not think about this method, but it's evident that this is the one that give us more guarantee to not have an error. Thanks Miquel
To edit the shared parameter file, any recomendation to create a new GUID for the parameter?. For example to copy the original one, and just change the last number? Miquel
Thanks Dirk for your help. I'm a structural engineer, so I do not care about doors ;). Thank you another time for your help. Miquel
HI another time, for the IfcName I solved it using NameOverride for the Instance parameter, but I would like to do the same with the IfcDescription, to have 2 different descriptions. With 2017 version it was possible. Thank you in advance Miquel
Simon, In the IfcExportType you have to type "exactly" the TypeEnum that is described in the BuildingSmart-tech.org website. Not all the classes accept the definition of the predefinedType. So probably walls does not accept this option. For IfcFootings it works, and for other categories also, probably for walls it is still not implemented. Miguel
In version 2017 I could define a IfcName parameter by Type in a Family (rfa) and I could control de EntityType.Name, and I could define a IfcName as a project parameter and I could control de Entity.Name. So this means, for example, a column I could control his name and his typename. Now with version 2018 it's not possible. Why? Miquel
I'm doing anything wrong or mapping table is still not working? I have a subcategory with this entry IfcFooting.PILE_CAP and it does not work, I have to put this information in the parameter IfcExportAs to get it right. I thing in older versions of IFC Exporter the mapping table did work.
If I want to map a parameter to a Custom Property set, and the name of the parameter has accents it is not exported. With custom parameters it's easy I just don't put accents, but what with Built in parameters. I can not change them. The only solution is to change the language of Revit every time. Is it possible to change this option to be able to export parameters with accent in his name? Miquel
Remco, I don't think it's a bug, think about it, ifcdescription is a parameter (or atribute) defined in the IFC Scheme and assigned to an element. So it has to be instance because it is not associated to a type. Miquel
I have a revit file where I have definied a survey point with coordinates. When I do the IFC export and check the coordinates in Navisworks everything is OK. If I link the IFC file in an other Revit file the insertion point considered is the File origin and not the shared coordinates. How can I do to get the correct position of my IFC file when I link it in Revit? Miquel
Instead of opening an IFC file try to link it. Afterwards if you need the elements to be in your model Bind the link and ungroup. In both cases (with elements ungrouped or with the linked IFC) if you select an element it will have the property IFCExportAs where you can see the ifcClass and Predefined Type if there is any.
You should export it as ifcFooting and FOOTING_BEAM as IfcExporType value. Or you can also export in the IfcExportAs parameter ifcFooting.FOOTING_BEAM. Regards Miquel
With IFCViewer of I see also those lines, with solibri, bim vision, navisworks no. I'm not sure what this lines represent. If you uncheck view lines you don't see them anymore. I can also not select them so it's difficult to check what they are. Regards Miquel
Maria, the assembly code will apear as a Classification. In Solibri look at the Classification Tab. If assembly code is filled it should be there. If you want to see the keynote you have to do as Arjan told you, or create a Custom Property Set where you can put all the parameters that you want (instead of exporting ALL revit parameters). Regards Miquel
Hi Maria, in the IFC Export table, in the IFC Export Class you have to put the name of the entity. If you check in: http://www.buildingsmart-tech.org/specifications look at IFC2x3 or IFC4 releases (online) and you will find all the ifc classes. It will be your decission in wich to feet each revit category. With the IAI export table you have already an orientation. In the second column IFC Type, if I'm not wrong, you have to put the PredefinedType. The values of this is fixed for each ifc entity....
sorry the rvt file Miquel
Hello, for the first, Yes, each time you export de IFC you must edit the txt, maybe with dynamo you can automate it. For the second one, you create a parameter called ClassificationCode and it must be a text type. Then for each type you type [MyClassificationName] XX.YY.ZZ: Description of the code, you type it just as I describe in the Properties-Palette in the field of the ClassificationCode. If you just write the same as I did you will see it in the IFC. I attach a file where you can see how it...
Maria, To change the word Uniclass I edit with Notepad my file.ifc file, just right click the file and choose open with notepad. On the other hand you are not using correctly the ClassificationCode method. You have to create one (until 10) parameter called ClassificationCode(x) and put there only the code. If you want to have a description in the IFC file and the name of your classification code you have to enter the values with this sintax [Classification name] Code: Description. Miquel
Andy, I tryed the same with subcategories for generic models and the mapping table does also not work. Everything is exported to the same type declared in the GenericModel category mapping not taking into account what the subcategories map. Miquel
Probably Angel can explain it better but I think the exporter automatically puts the word Uniformat. Just edit the IFC file and change it. It's easy. Miquel
Hello, check this software: https://www.nist.gov/services-resources/software/ifc-file-analyzer it exports IFC to Excel. What you can not see in the excel is not in the IFC. Some softwares show more or less information than IFC contains, so it is sometimes difficult to know if the information shown is in the IFC or is calculated by the IFC viewer. With the export to Excel you will see only and all the information in the IFC. Miquel
Hello, If you edit your IFC file with a text editor (like Notepad) search for "Uniformat". Change it to your Classification name and save. It's done. Miquel
I send Mapping table, Revit 2017 file and IFC file. Thank you for your work in advance....
I'm trying to export some elements that are in subcategories to several IFC Classes....