# Gbxml room names for importing to TRACE700

**URL:** <https://discourse.pollination.solutions/t/gbxml-room-names-for-importing-to-trace700/4409>\
**Category:** Revit Plugin\
**Tags:** trace, gbxml, question\
**Created:** [October 16, 2024, 11:59am UTC](https://discourse.pollination.solutions/t/gbxml-room-names-for-importing-to-trace700/4409 "2024-10-16T11:59:09Z")\
**Posts on this page:** 11\
**Page:** 1

<div class="post-metadata">

**Author:** ![heathbaxa](https://discourse.pollination.solutions/user_avatar/discourse.pollination.solutions/heathbaxa/32/9769_2.png) [@heathbaxa](https://discourse.pollination.solutions/u/heathbaxa)\
**Post date:** [October 16, 2024, 11:59am UTC](https://discourse.pollination.solutions/t/gbxml-room-names-for-importing-to-trace700/4409/1 "2024-10-16T11:59:09Z")

</div>

How does Pollination create room names when exporting to gbXML?

The gbxml export results in room names that don’t match room naming in the Pollination file.

---

<div class="post-metadata">

**Author:** ![mostapha](https://discourse.pollination.solutions/user_avatar/discourse.pollination.solutions/mostapha/32/5761_2.png) [@mostapha](https://discourse.pollination.solutions/u/mostapha)\
**Post date:** [October 16, 2024, 1:27pm UTC](https://discourse.pollination.solutions/t/gbxml-room-names-for-importing-to-trace700/4409/2 "2024-10-16T13:27:54Z")

</div>

Hi @heathbaxa, can you be more specific about the issue here?

1. How do you export the gbXML from the model editor? Do you use any options?
2. What software are you using to import the gbXML file?

@chriswmackey can add more details here but we use a specific tag to include the `display name` in gbXML called `Name`. Not every tool imports that tag. If that’s the case, you must change the identifiers based on the display names using the Python Script Editor. I can provide you with an example if that is the case.

---

<div class="post-metadata">

**Author:** ![heathbaxa](https://discourse.pollination.solutions/user_avatar/discourse.pollination.solutions/heathbaxa/32/9769_2.png) [@heathbaxa](https://discourse.pollination.solutions/u/heathbaxa)\
**Post date:** [October 16, 2024, 2:34pm UTC](https://discourse.pollination.solutions/t/gbxml-room-names-for-importing-to-trace700/4409/3 "2024-10-16T14:34:47Z")

</div>

From the Pollination Editor, I select export to GBXML format. Full Geometry.

Importing the file to Trace700. I’m testing this to speed up inputs for my HVAC engineer colleagues who are still using Trace 700 for load calculations.

---

<div class="post-metadata">

**Author:** ![mostapha](https://discourse.pollination.solutions/user_avatar/discourse.pollination.solutions/mostapha/32/5761_2.png) [@mostapha](https://discourse.pollination.solutions/u/mostapha)\
**Post date:** [October 16, 2024, 3:37pm UTC](https://discourse.pollination.solutions/t/gbxml-room-names-for-importing-to-trace700/4409/4 "2024-10-16T15:37:45Z")

</div>

Nice! That’s helpful.

For TRACE700 workflow you should use the TRACEXML export option instead of the default gbXML. It creates a gbXML file that is compatible with the TRACE gbXML importer. There are also other simplification options that you should probably leave as is for your export to simplify the windows.

![image](https://discourse.pollination.solutions/uploads/default/original/2X/e/e98f554eafcba780f324abe63722393cfdd40c1e.png)

It should also fix the naming issue. Let us know otherwise!

We have been working with the TRACE TRANE team to develop the modified gbXML but we haven’t announced it officially yet. Let us know if you face any issues and we will be happy to help.

---

<div class="post-metadata">

**Author:** ![chriswmackey](https://discourse.pollination.solutions/user_avatar/discourse.pollination.solutions/chriswmackey/32/6207_2.png) [@chriswmackey](https://discourse.pollination.solutions/u/chriswmackey)\
**Post date:** [October 16, 2024, 3:48pm UTC](https://discourse.pollination.solutions/t/gbxml-room-names-for-importing-to-trace700/4409/5 "2024-10-16T15:48:46Z")

</div>

Thanks, @heathbaxa

You are right that exporting the TRACE gbXML will address the issue, @mostapha . In the default gbXML export, we write the room’s display\_name to the `<Name>` tag in the gbXML and we let the Space id be governed by the original Revit object id:

 ![image](https://discourse.pollination.solutions/uploads/default/original/2X/e/e78245031fad343dec73fae083a015887003815e.png)  
[Unnamed.xml](https://discourse.pollination.solutions/uploads/short-url/fjsGjW0Dw88PJYu4yeofRYlrXm5.xml) (345.5 KB)

But we learned that TRACE 700 (and TRACE 3D) just ignore this (pretty useful) `<Name>` tag and instead name all of the rooms with the id. `¯\_(ツ)_/¯`

When you export a **TRACE** gbXML from the model editor, we overwrite all of the IDs of the objects using a cleaned version of the names. So, instead, it looks like this:

 ![image](https://discourse.pollination.solutions/uploads/default/original/2X/5/595a04c4b4daa7a7f2da349575f125473392d7c9.png)  
[Unnamed\_TRACE.xml](https://discourse.pollination.solutions/uploads/short-url/3DhlQUHwK79VT4t1V8dSJO3XNgL.xml) (256.1 KB)

Which will look better when importing to TRACE.

---

<div class="post-metadata">

**Author:** ![heathbaxa](https://discourse.pollination.solutions/user_avatar/discourse.pollination.solutions/heathbaxa/32/9769_2.png) [@heathbaxa](https://discourse.pollination.solutions/u/heathbaxa)\
**Post date:** [October 16, 2024, 5:54pm UTC](https://discourse.pollination.solutions/t/gbxml-room-names-for-importing-to-trace700/4409/6 "2024-10-16T17:54:09Z")

</div>

Thanks! I have tried several of my projects. While I can export to several formats (GEM, INP, GBXML) without error, I get errors on all of them when I select TRACEXML.

---

<div class="post-metadata">

**Author:** ![chriswmackey](https://discourse.pollination.solutions/user_avatar/discourse.pollination.solutions/chriswmackey/32/6207_2.png) [@chriswmackey](https://discourse.pollination.solutions/u/chriswmackey)\
**Post date:** [October 16, 2024, 6:00pm UTC](https://discourse.pollination.solutions/t/gbxml-room-names-for-importing-to-trace700/4409/7 "2024-10-16T18:00:09Z")

</div>

Thanks, @heathbaxa .

> [@heathbaxa](#):
>
> I get errors on all of them when I select TRACEXML.

This sounds like a bug. What is the error that you are getting when you select TRACEXML? If you can get us the error message and/or a sample file to recreate the error on our end, we will fix it.

---

<div class="post-metadata">

**Author:** ![mostapha](https://discourse.pollination.solutions/user_avatar/discourse.pollination.solutions/mostapha/32/5761_2.png) [@mostapha](https://discourse.pollination.solutions/u/mostapha)\
**Post date:** [October 17, 2024, 4:26pm UTC](https://discourse.pollination.solutions/t/gbxml-room-names-for-importing-to-trace700/4409/8 "2024-10-17T16:26:01Z")

</div>

@heathbaxa, after thinking about this a little bit more, is it possible that you are using an older version of the Revit plugin/Model Editor that doesn’t have the latest SDK? Do you see this warning when you open the Model Editor?

> **[FAQ | Pollination Docs](https://docs.pollination.solutions/user-manual/model-editor/faq#why-do-i-see-the-the-model-editor-is-built-against-a-newer-version-of-the-revit-plugin.-warning-mess)**
>
> A list of frequently asked questions about the Model Editor.

Support for SDDXML was added in version 1.16.

> **[Changelog | Pollination Docs](https://docs.pollination.solutions/user-manual/model-editor/changelog#v1.16-september-9-2024)**
>
> List of most important changes between different versions of the Model Editor SDK.

---

<div class="post-metadata">

**Author:** ![heathbaxa](https://discourse.pollination.solutions/user_avatar/discourse.pollination.solutions/heathbaxa/32/9769_2.png) [@heathbaxa](https://discourse.pollination.solutions/u/heathbaxa)\
**Post date:** [October 17, 2024, 4:44pm UTC](https://discourse.pollination.solutions/t/gbxml-room-names-for-importing-to-trace700/4409/9 "2024-10-17T16:44:27Z")

</div>

I have the latest Model Editor. I was able to work through the issue and get a proper TRACEXML output on a couple of the test models. Prior to export I verified that the model was valid. I tried several things, but if I recall correctly after I solved adjacency, then the export to TRACEXML worked. I will let you know if I have issues again.

---

<div class="post-metadata">

**Author:** ![mostapha](https://discourse.pollination.solutions/user_avatar/discourse.pollination.solutions/mostapha/32/5761_2.png) [@mostapha](https://discourse.pollination.solutions/u/mostapha)\
**Post date:** [October 17, 2024, 4:47pm UTC](https://discourse.pollination.solutions/t/gbxml-room-names-for-importing-to-trace700/4409/10 "2024-10-17T16:47:09Z")

</div>

Thanks! Then I consider this topic as resolved for now. Let us know the feedback on TRACEXML quality.

One item that we have been thinking about is building some sort of report for people to be able to validate the imported model against how they would have put the numbers into TRACE manually. Let us know if your mechanical engineer thinks that can be helpful, and if yes, how would the report look like.

Thanks!

---

<div class="post-metadata">

**Author:** ![chriswmackey](https://discourse.pollination.solutions/user_avatar/discourse.pollination.solutions/chriswmackey/32/6207_2.png) [@chriswmackey](https://discourse.pollination.solutions/u/chriswmackey)\
**Post date:** [October 17, 2024, 6:43pm UTC](https://discourse.pollination.solutions/t/gbxml-room-names-for-importing-to-trace700/4409/11 "2024-10-17T18:43:52Z")

</div>

> [@heathbaxa](#):
>
> if I recall correctly after I solved adjacency, then the export to TRACEXML worked.

Ah, yea, I guess we haven’t really made a video about “how to format your Pollination Models for TRACE” but TRACE expects you to have a model with solved adjacencies just like EnergyPlus and DOE-2. It doesn’t have some internal mechanism to figure out adjacencies for you the way that IES-VE and IDA-ICE do.