Page 1 of 1
Does plug-in use gbXML?
Posted: Thu Sep 06, 2012 4:35 pm
by enerGwizz
I am curious if the SketchUp plug-in uses gbXML to translate information from the SketchUp model to the VE, or if the plug-in translates directly to a ModelIT file, or something else. In other words, is the gbXML schema useful for translating all of the necessary information or did IES avoid it for direct export to the VE?
I have the same question about the Revit plug-in if anybody knows the answer to that one.
And I am aware that you CAN export gbXML from both software packages, but am trying to better understand what the optimal way to move this data is.
Thanks!
Re: Does plug-in use gbXML?
Posted: Fri Sep 07, 2012 12:42 pm
by PCully
without giving too much away...
SketchUp exports a veXML, a modified version of gbXML that is required to get the model to VE so this route of transfer is the best to get the model from SketchUp to VE and there aren't many alternatives. The Find Rooms part of the plug-in workflow process is key here, by establishing the rooms that are required for the analytical model in VE and then working backwards to identify bounding surfaces, openings shades etc we get a far ore robust model.
Revit is slightly different as IES were able to work directly with Autodesk on that link so we were able to tap in to their native gbXML export and through the collaboration we made improvements to what is exported and also we have a better gbXML import process when the source of the gbXML is Revit. Key to this is the Room (Architecture) or Space (MEP) elements that allow the user to define the rooms prior to export to gbXML. This is why if you don't use the IESVE plug-in for Revit you will still find it is possible to get the same quality import to VE by the manual route.
In both cases the plug-in is still the easiest route I would say.
Phil