TRACEXML File Type Exports - Naming Conventions and other cool features?

Hi @mostapha and pollination team!

In the latest progression of our companies use of Pollination and IESVE, we are going to be hybrid on any projects that have existing to be pollination into Trace XML exports and New projects to be exported to the GEM.

On the topic of TRACE Exports, I am curious about the following options:

  1. Can wall names be given custom values? Right now, the walls are some string of smart terms - “Room_3cc0e08e-b531-46c7-abea-701626fc96cc-00926956Face1” which is great if you’re a computer program, but unnecessary for the user. My preference is that East oriented walls (Direction = 90) are named “E ###SF”, cardinal direction letter followed by area of the wall. If this is something that can be built in or given some custom option to define how walls are defined, that would be fantastic!
  2. Windows and doors are restricted to Revit architectural models. As far as I am aware, architects still have a healthy mix of Revit models vs CAD Background Models. In the cases of CAD background models, I am curious if it would be possible to define windows and doors while using Rooms, Spaces, or Areas with a Flat CAD reference instead of Revit elements. Right now, my solution is either build those architectural elements in the Revit model (exterior walls, windows, and doors) and then follow suite on the rest of the workflow for cleaning the pollination model. If there is a way to define doors as a standard to be 3’x7’ from ground level and windows to have parameters to give window sill height from ground, width of window, and height of window… that would make for some powerful modeling capabilities.
  3. Overhangs are still needing to be defined in TRACE700. This one seems rather impossible, consider how TRACE700 operates with Overhang libraries… So what if pollination could access the overhangs that are in TRACE700? This one seems more far fetched, but “what if” changed the world.

I’m happy to clarify any of my ideas above. Regardless, I am excited to have my colleagues now adopting pollination.
I appreciate all your efforts and look forward to future features and QoL updates!

1 Like