Problems converting gbXML to IDf
Hi,
I am exploring a workflow that involves exporting a gbXML file from a Revit model and converting the gbMXL file to an IDF file via OpenSudio. I encounter an empty required field problem that cause errors when running an EmergyPlus simulation using the converted IDF file.
I came across a forum post related to this problem and tried to follow the discussion; however, I still cannot find a solution. Here is the post: https://unmethours.com/question/16600.... In the discussion, I acknowledge that it's a known bug and has been solved in the late versions on OpenStudio. Furthermore, the conversation seems to focus on window problems. I basically encounter problems with the building shells (e.g., floors, wall, and roof), as well.
Regarding my workflow, I installed OpenStudio 1.11.5 which exports EnergyPlus 8.5. I imported a gbXML file via the OpenStudio extension installed inside SketchUp 2016. I exported an IDF file. I examined the IDF file via a text editing tool and found that the values for the 'Construction Name' fields are empty (please see an example below), which causes errors when running the simulation.
BuildingSurface:Detailed,
aim0149, !- Name
Wall, !- Surface Type
, !- Construction Name
aim0024 ThermalZone, !- Zone Name
...
Could anyone please share your insights regarding how to overcome this issue? I am very open to less-manual-editing ideas whether the issue should be solved in Revit, SketchUp, OpenStudio, IDFEditor, or other third-party software.
Thank you very much.
As far as I'm concerned, current release of OS does not read Constructions from gbXML files, as well as loads and even elements names (as you see it uses IDs instead). But NREL announced some months ago that they are going to make OS first software certified against working with gbXML schema. Look forward as I use Revit to create models too. So, the only way is to add constructions manually, but when you don't know what surface where... that's almost impossible...
Dinosaver, Thank you very much for sharing your insight. In a small test model, I was able to inspect the surfaces and manually assigned the construction names (actually ids). However, when it comes to the real project that I have to do the conversion, I agree that it seems almost impossible. I tried to create an instance of the OS:DefaultConstructionSet object and assigned it to a space. This helped remove errors quicker than assigning a construction to each surface; however, do you think this approach would work for a big multiple-space project?