we would very much like the possibility to have full control over which parameters to export. I know this is possible through other IFC exporters for Revit, like MagiCAD's.
The way we would like it to work is through an option to include / exclude individual properties or Psets, were we could filter and map which properties to export to IFC. This way we could create custom property tabs particular to a specific project, choose to override IfcBuilding in order to be able to have more than one building pr. Revit model, exclude all unwanted info etc.
This should preferrably be done through a GUI that lists the possible parameters / sets pr. model but could also be done through a text file, the way the class mapping is done today - which btw, also should have a GUI and an override function like this ;-)
Thanks
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
That's a new request. Note that while IFC files in theory can have multiple IfcBuildings, in practice for the common MVDs it is expected that there is only one. Are you trying to export a campus from one Revit file?
Thanks,
Angel
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Sorry for my late response.
I'm trying to export kind of campus.
It's about a projekt in early DD with several buildings. We try to connect to our cost-estimator via IFC. He needs to able to seperate the different buildings in his
software (Bim4You). It's to early for us to split the project into different Revit files.
At the moment we try to use differen worksets for different buildings. But we also use
worksets to subdivide each building. So it is starting to get complex and it's
a lot of work to ensure everyone worked on the right workset.
I think it could be useful to have a parameter apart from the workset to be able to differentiate between different buildings. And IfcBuilding would make sense to me.
The structural engineer is working with Allplan. There you have the option to distinguish between different buildings. This works fine for the cost-estimator an his software.
Thanks,
Philipp
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Can you be more specific about this new parameter? In particular, where would you set that a particular wall belonged to a particular building? At the instance, type, workset level, or all of the above?
Thanks,
Angel
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
At the end it should be at the instance level. That`s why we use worksets at the moment.
It is quite comfortable to work with. You just choose the (right) worset and each element gets the workset-information attached to at the instance level.
Attaching an instance parameter manually to each element would not work. It would be too timeconsuming and too error-prone.
At the type-level it would not make much sense, because you would have to generate a lot of types. Which you don't want. Especially not in early DD. And a huge number of types make the interpretation and structuring of your data very difficult. For yourselfe and, in our case, for the cost estimator.
The use of worksets for the task works. But it occupies a very powerful funktion of the software which we would love to use for other things.
We would appreciate a level which is above in hirachy to the workset and the phasing.
Lets say you decide to work at "building 1" or "building-part 1". You could activate it like a workset. But within this "building 1" you can use the workset and the phasing aswell. The effect would be, that each element wich is created in "building 1" gets a parameter on instance-level with the value "building 1".
Im sorry for the long and awkward explanation, but my english is not the best...
I hope you got my point.
1.Building or building-part
2.Workset / Phasing
1 and 2 documented at instance-level of each element and room.
It could work like a "timer" while it runns, each element gets the tag of the active "building" or "building-part"...
To check visualy you could use filters to color the elements depending on the Building. (like the function to color worksets).
Thanks,
Philipp
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
This sounds more of a Revit request than an IFC one, to have a way to group Revit objects into Buildings, which would have behaviors in Revit (such as visibility, scheduling, etc.) One of those behaviors would then be that they would be exported into IFC as IfcBuilding, and that presumably on import we'd create these Revit objects from IfcBuildings in return. Does that capture what you are looking for?
Regards,
Angel
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Hi,
we would very much like the possibility to have full control over which parameters to export. I know this is possible through other IFC exporters for Revit, like MagiCAD's.
The way we would like it to work is through an option to include / exclude individual properties or Psets, were we could filter and map which properties to export to IFC. This way we could create custom property tabs particular to a specific project, choose to override IfcBuilding in order to be able to have more than one building pr. Revit model, exclude all unwanted info etc.
This should preferrably be done through a GUI that lists the possible parameters / sets pr. model but could also be done through a text file, the way the class mapping is done today - which btw, also should have a GUI and an override function like this ;-)
Thanks
Hi,
I'll file a request for that. As you can imagine, that isn't a trivial task, but I agree that it would be useful.
Thanks,
Angel
Hi,
I'm also looking for a way to be able to have more than one IfcBuilding per Revit model.
Is there already a solution for this request?
Thanks,
Philipp
Hi Philipp,
That's a new request. Note that while IFC files in theory can have multiple IfcBuildings, in practice for the common MVDs it is expected that there is only one. Are you trying to export a campus from one Revit file?
Thanks,
Angel
Hi Angel
Sorry for my late response.
I'm trying to export kind of campus.
It's about a projekt in early DD with several buildings. We try to connect to our cost-estimator via IFC. He needs to able to seperate the different buildings in his
software (Bim4You). It's to early for us to split the project into different Revit files.
At the moment we try to use differen worksets for different buildings. But we also use
worksets to subdivide each building. So it is starting to get complex and it's
a lot of work to ensure everyone worked on the right workset.
I think it could be useful to have a parameter apart from the workset to be able to differentiate between different buildings. And IfcBuilding would make sense to me.
The structural engineer is working with Allplan. There you have the option to distinguish between different buildings. This works fine for the cost-estimator an his software.
Thanks,
Philipp
Hi Philipp,
Can you be more specific about this new parameter? In particular, where would you set that a particular wall belonged to a particular building? At the instance, type, workset level, or all of the above?
Thanks,
Angel
Hi Angel
At the end it should be at the instance level. That`s why we use worksets at the moment.
It is quite comfortable to work with. You just choose the (right) worset and each element gets the workset-information attached to at the instance level.
Attaching an instance parameter manually to each element would not work. It would be too timeconsuming and too error-prone.
At the type-level it would not make much sense, because you would have to generate a lot of types. Which you don't want. Especially not in early DD. And a huge number of types make the interpretation and structuring of your data very difficult. For yourselfe and, in our case, for the cost estimator.
The use of worksets for the task works. But it occupies a very powerful funktion of the software which we would love to use for other things.
We would appreciate a level which is above in hirachy to the workset and the phasing.
Lets say you decide to work at "building 1" or "building-part 1". You could activate it like a workset. But within this "building 1" you can use the workset and the phasing aswell. The effect would be, that each element wich is created in "building 1" gets a parameter on instance-level with the value "building 1".
Im sorry for the long and awkward explanation, but my english is not the best...
I hope you got my point.
1.Building or building-part
2.Workset / Phasing
1 and 2 documented at instance-level of each element and room.
It could work like a "timer" while it runns, each element gets the tag of the active "building" or "building-part"...
To check visualy you could use filters to color the elements depending on the Building. (like the function to color worksets).
Thanks,
Philipp
Hi Philipp,
This sounds more of a Revit request than an IFC one, to have a way to group Revit objects into Buildings, which would have behaviors in Revit (such as visibility, scheduling, etc.) One of those behaviors would then be that they would be exported into IFC as IfcBuilding, and that presumably on import we'd create these Revit objects from IfcBuildings in return. Does that capture what you are looking for?
Regards,
Angel