Revit export to .NWC using Navisworks Export 2023 includes Family and Type data

[hmaQ5RFD]

Good day,

We are working with .dwfx files in order to read element properties in the Cost-X application. In order to create these files the process that we use is exporting .RVT > .NWC > .DWFX through the use of Navisworks Manage 2023. A change that we've noticed in the upgrade from 2021 to 2023 is that each .NWC export includes the Family and Type data. See the difference in the two images I have added to this post. This is data that is clashing with the data structure that we use in Cost-X. So we would like to exclude this from the .NWC export.

Checking the API of NavisworksExportOptions for both 2021 and 2023 shows that there has not been any change to its members or properties. I have tried using different ConvertElementProperties and Parameters settings, but this is without luck so far. 

We are using:
Revit 2023

Navisworks Manage 2023

Does anyone else have experience with this? 

Current export settings Navisworks in Python:

# Boilerplate
import clr

clr.AddReference('ProtoGeometry')
from Autodesk.DesignScript.Geometry import *

clr.AddReference('RevitAPI')
from Autodesk.Revit.DB import *

clr.AddReference('RevitServices')
from RevitServices.Persistence import DocumentManager

import System
from System.Collections.Generic import *

doc = DocumentManager.Instance.CurrentDBDocument

# Dynamo input
folder = IN[0]
names = IN[1]

# Define the Navisworks Export settings
collector = FilteredElementCollector(doc).OfClass(View)
options = NavisworksExportOptions()
options.ExportScope = NavisworksExportScope.View
options.ExportLinks = False
options.ExportParts = True
options.DivideFileIntoLevels = False
options.FacetingFactor = 0.1

OUT = []

# get Workset name, read ThreeD views in Revit that align with that name
if IN[2]:
    for i in names:
        viewstring = i.Name
        OUT.append(viewstring)
        for view in collector:
            if (view.ViewType == ViewType.ThreeD and viewstring in view.Name):
                # prefix name with _ZJA and export to a .nwc file in folder
                options.ViewId = view.Id
                options.ExportRoomGeometry = False
                options.ExportParts = True
                options.ExportLinks = True
                options.ExportRoomAsAttribute = False
                options.FacetingFactor = 0.1
                name = view.Name
                options.Coordinates = NavisworksCoordinates.Internal
                doc.Export(folder, name + "_Internal_ZJA" + ".nwc", options)

[moturi.magati.george]

Hi @hmaQ5RFD,

I have shared this with the engineering team for more information. I will update you once I get some feedback from them.

[hmaQ5RFD]

Hi @moturi.magati.george ,

Thanks for your quick reply! Let me know if more information is needed.

Thank you,

Hidde

[moturi.magati.george]

Hi @hmaQ5RFD,

There is a response from the Engineering team.

The original change was done so that Family and Type properties were always available but dropped those properties from the Element nodes.

There might be another change to put those properties back on the Element nodes in the coming version.

There haven't been other requests so far to remove these properties from the Family and Type nodes, it would seem like the software consuming these properties is just making some bad assumptions about the data.
Also, note that even if we fixed this with another option in the RVT->NWC exporter the option would only appear in the UI dialog.

[hmaQ5RFD]

Hi @moturi.magati.george,

Thank you for the response. Understandable that it is more suitable to make its data available on its specific property. However since we're working with a model of around 140.000 elements it's quite tedious to deal with such an influx of extra parameters. Do you perhaps know a workaround to exclude this data in a .NWC model?

The weird thing is that it only applies to non-system families such as:
Curtain panels, Doors, Generic models, Special equipment and Stairs.

[moturi.magati.george]

Hi @hmaQ5RFD,

I would suggest that you use existing tools or even tweak the software you are using to filter out the unwanted data before consuming the same.

If you require new or enhanced functionality, the Revit Idea Station is the place to go.

Please search there for a corresponding wish list entry for the suggested functionality and add your comments to it, or create a new one, if none already exists:

https://forums.autodesk.com/t5/revit-ideas/idb-p/302

Tag it as an API wish:

https://forums.autodesk.com/t5/revit-ideas/idb-p/302/tab/most-recent/label-name/api

Ensure it gets as many votes as possible to underline its importance to you and the rest of the developer community.

The Revit Idea Station is currently one of the main driving input forces for Revit API enhancements.

The Revit development team look there. Your comment here in the discussion forum might be overlooked.

[davidburkeGQM7E]

same issue