Hello,
I am new in using IES<VE> and, thus, full of questions. I tried to import a 3D model made in Revit and when the import process was fulfilled it looked like building information was set by default by IES<VE>. Is it possible to import building information apart from just the geometry?
Also, is there a specific reason why you use gbXML instead of IFC? I have noticed that you have linked to Vectorworks when it comes to IFC. Why is this? Is there another way to import IFC files?
Regards,
Emily
Why do you use gbXML instead of IFC?
Re: Why do you use gbXML instead of IFC?
Hi,
When you bring a gbXML into VE you are presented with Set Model Properties which gives some options to assign preconfigured data to the imported model. data such as thermal templates, schedules, constructions, simple systems are all available to assign to whole building or room by room and are intended to allow easy fast early stage analysis. As your analysis becomes more complex and you seek greater accuracy using VE Pro for Archs or Engineers then you are into the full applications and can customise and define all of your own input data for assignment.
I am aware that some simple thermal/energy analysis data can be define din Revit for example lighting schedules etc but as there is no guarantee what data can be applied in Revit and no possibility of a one to one mapping with the data the VE requires for a robust simulation then there is no real link there.
gbXML was selected as we worked closely with Autodesk to define a link between our packages after they identified the VE as one with a great capability for analysis on the kinds of building models that were being create din Revit. gbXML was simply the BIM file format at the time and we were able to optimize that process by working on both sides. There is a growing hunger for IFC these days but it is still early days in terms of IFC sources outputting geometry data in a way that is usable for analysis packages, we continue to work on this both by educating and informing the source packages who are willing to make this work and also by adding tidying algorithms to improve (as much as possible) the geometry when it is exported in flawed forms (gaps between rooms, undefined analysis space volumes, missing surfaces etc)
This happens to be an area I've been involved in over the years here at IES so that's the history on it up until now, the future is most likely to be improved IFC import and hopefully if source packages get on board and we see a real shift in industry to using this one file format then we can start with great robust geometry and explore all of the other possibilities regarding other performance data that could be stored in the file and communicated between software packages.
Phil
When you bring a gbXML into VE you are presented with Set Model Properties which gives some options to assign preconfigured data to the imported model. data such as thermal templates, schedules, constructions, simple systems are all available to assign to whole building or room by room and are intended to allow easy fast early stage analysis. As your analysis becomes more complex and you seek greater accuracy using VE Pro for Archs or Engineers then you are into the full applications and can customise and define all of your own input data for assignment.
I am aware that some simple thermal/energy analysis data can be define din Revit for example lighting schedules etc but as there is no guarantee what data can be applied in Revit and no possibility of a one to one mapping with the data the VE requires for a robust simulation then there is no real link there.
gbXML was selected as we worked closely with Autodesk to define a link between our packages after they identified the VE as one with a great capability for analysis on the kinds of building models that were being create din Revit. gbXML was simply the BIM file format at the time and we were able to optimize that process by working on both sides. There is a growing hunger for IFC these days but it is still early days in terms of IFC sources outputting geometry data in a way that is usable for analysis packages, we continue to work on this both by educating and informing the source packages who are willing to make this work and also by adding tidying algorithms to improve (as much as possible) the geometry when it is exported in flawed forms (gaps between rooms, undefined analysis space volumes, missing surfaces etc)
This happens to be an area I've been involved in over the years here at IES so that's the history on it up until now, the future is most likely to be improved IFC import and hopefully if source packages get on board and we see a real shift in industry to using this one file format then we can start with great robust geometry and explore all of the other possibilities regarding other performance data that could be stored in the file and communicated between software packages.
Phil
IES Worldwide Technical Support
Re: Why do you use gbXML instead of IFC?
That was a very quick reply! Thank you for the info!