Therefore, in terms of Revit they need applying to both instance and type properties.
This is where it gets a little complicated as both these parameters are to be used to export to both IFC occurrence and type. In blog post 03 we mentioned three of these override parameters (IfcExportType, IfcElementType, IfcObjecttype), I’m now going to mention two more: Please see blog post 01 if you need to remind yourself about the differences between IFC attributes and properties. (there is an exception to this, but we will cover properties in a future blog post)
To export IFC properties = Any parameter + the custom property set mapping file To export IFC attributes = Specified Revit override parameters If there is one thing you should take away from this blog post it should be… Many people get confused and think that the custom property set mapping file (which you specify in the IFC Exporter) is the magic file which exports everything, this is however only for IFC properties.
#Revit 2011 topography software#
Referring back to the first image from blog post 02 family and type names are an example of what belongs in the Revit environment, their creation is to support the software they are created in (However they should still be named consistently).įortunately, we can override the default setting so that we can choose what name will be exported for both IFC occurrences and IFC types.įor anything IFC attribute related in Revit you must use specify parameters which have been named by Autodesk, as these have been coded into the IFC Exporter. Now we want to refer to the doors in the IFC export by those same names/numbers, so we can then reference back to the other deliverables – so it all matches.īy default, Revit uses its own family and type names in the IFC export, in my experience these typically aren’t used on drawings or schedules and are therefore, pretty much meaningless outside the software.Įxample: ABC_LightingFixtures_Spotlight_FaceBased_RecessedCircular duplicates information within the object’s properties, uses Revit based terminology and it’s too long for drawings. This is a great example of coordinated information which we do without even thinking about it. A great example is the humble door typically, we have plans which show every door number, door type drawings which show what each type looks like, then both the door numbers and door type names are used in the door schedule. This information will contain names and descriptions of elements. This information can also be contained in a whole manner of deliverables from drawings to schedules to reports. Remember IFC is a way of transferring information from one place to another. OwnerHistory is automatically populated and relates back to IfcPerson, I will talk about this in a later blog post.įor Name and Description, we have a little bit of work to do to get these as we want them. GlobalId is automatically populated on export by using ID data held in the Autodesk Revit database. In blog post 01 we described what Attributes are and listed the four core ones:
0 kommentar(er)
