Improvements in Revit exporter

Feature Requests
1

I’d like to use the direct Revit → Qonic exporter more, but because of a number of reasons this is not yet possible:

  1. First priority: better handling of multiple Revit models in the same project. Currently this works OK only if there is only 1 Revit to Qonic export per project. As soon as there is a second Revit model, it overwrites the previous one. Since a while, there is the possibility of creating a new model in Qonic. Which is OK the first time the second model is uploaded.
    We need a good recognition of model (by name, …?) and a better fallback to select to which of the existing models this Revit upload is a new version.

  2. Second priority: include more (all) categories. Currently, for example, Structural Rebar is not exported (maybe it’s the only category, but it is important for us in many of our own models)

  3. Allow for choosing a 3D view and only “export elements visible in view”. This is what we use for IFC export from Revit. Also Navisworks supports this. It makes it very easy to use for example ‘dummy’ elements in the Revit model that don’t need to be in the exported model.

  4. Retain assemblies: an assembly in Revit is not converted to an assembly in Qonic. For us, again, it is important for many of our models (prefabricated concrete).

  5. Recognize ifc class overrides: for each type we can “IFC Export Type as” in Revit. This works for the built-in IFC exporter (obviously), please use it also on the export to Qonic.

  6. Small graphic thing: I have a specific case with a column family that has the possibility for a chamfer. When the distance is set to 0, one side remains ‘split’ because of how the family is built up:

    SplitFacesMerging

    As you can see, the faces merge together after doing some manipulation. So it’d be nice if the Qonic exporter already recognizes them as being in the same plane and merges them directly.

Some of the reasons why I want to use the Revit → Qonic export instead of the current IFC route:

  • One less step to do => directly from within Revit
  • Better generation of geometry: many of our prefab items become “tesselated geometry” because of (round) openings and the IFC exporter from Revit that can’t handle that
  • Some more issues with geometry not in the correct location in Revit’s IFC export
  • All-round, I have more faith in Qonic’s ability to generate a proper IFC4 or IFC4x3 file than Revit’s exporter