When exporting to gbXML from REVIT and importing to OS, instead of space names, surface names or any type of name of entity in OS, the generated iD is instead brought in.
ex. wall name is S-5-106-E-W-11673-W-1 but instead the following name is brought into OS aim275568.
Is there a setting that i am missing to use Names instead of IDs. TRACE 700 parses the correct name and not id.
Unfortunately, OpenStudio model objects do not have a field to store the id separately from the user name. The OpenStudio gbXML importer stores the CAD object id in the OpenStudio model object name, the idea is that id is a more reliable identifier to refer to objects in the gbXML file and in the future if the gbXML file is re-exported and merged with the OpenStudio model. If OpenStudio were merged to store user names then the ids would be lost. It is possible to make this change but we would need to consider how this would affect the workflow where a gbXML is re-exported in the future and merged with the current OpenStudio model (e.g. to pick up new geometry from Revit but preserve HVAC defined in OpenStudio).
@macumber this is something of significant interest to us. As practicing professionals continue to build workflows around BIM we need to create easily traceable objects that allow us to QC the import/export process and track down errors. As the BIM side gets closer I'd really be interested in seeing Openstudio working on closing their side.
Are you thinking that we can get by with either name or ID, or does OpenStudio need to import and preserve both?
Ideally both. The ID is best for insuring uniqueness during any type of automated process, but the end user will want to use the name to check the model against their design.
TRACE gets by with only bringing in Name. I have also not tested to see if the ID stays unique. It is easier to QC import/export like jmcneill indicated if it is based on name. We have floor plans in REVIT we can back check with. The ID is not a reportable item in revit and only comes about during the gbXML exchange process.
To add to this, Revit used to export the space name to the id attribute of spaces, but then changed this in Revit 2015 and the id attribute became a string of "aim" + a series of integers that do not correspond to an id within Revit - it's randomly generated. Changing the export to not include the name in the id affected many programs including their own green building studio as these programs relied on the id attribute to name each element (spaces, surfaces, etc.). As OpenStudio uses the id attribute for the import process is was affected too.
Asked: 9 years ago
Seen: 730 times
Last updated: Jan 25 '16
