I'm looking for support with Navisworks (AutoDesk) BIM data (.nwd .nwf .nwc). I need to extract the full 6D information from the model and output it to other formats but also update the 6D information back to the model. Navisworks imports IFC but does not seem to export it. DWF, which can be written with Navisworks, does not hold the 6D information.
Any help would be appreciated.
Best answer by kailinatsafe
edualarcong wrote:
Hello @kailinatsafe It would be a major step for BIM integration to have at least a NWD reader. We work on a daily basis with NWD from different sources (Autodesk Plant 3D, Smart Plant 3D, Aveva) to push into ArcGIS, and the workaround at the moment is to use a IFC exporter plugin, but it is time consuming and not useful when handling large models or lots of geometries.
Hello @edualarcong, thank you for commenting! This is great information, I have added a note about your potential use case. Please ensure to show your interest or vote on the FME Idea. Happy to help, Kailin!
Thanks for all the work done to add support for Navisworks, it will probably become one of my most used readers.
I have been trying out the Tech Preview of the Navisworks Reader, and I have some questions about elements in the selection tree hierarchy. I understand that because it is still in development, the reader will undergo changes, so I’m interested in understanding the reader’s behavior.
For example, the reader does not read ‘instanced groups’ but instead reads as a composite object inside the instance, so it loses all the group level properties (such as REVIT, GUID, Element, Level properties).
Similarly, it reads multiple geometries within a layer/level as a single fme_collection, so when they are disaggregated, they inherit the properties (e.g. GUID, Materials and Timeliner properties) of the layer and not their original geometry properties.
Hello @edualarcong, thanks for your patience! I believe the Navisworks Reader will try to read as much as much as possible, and try to present it in a reasonable manner within FME.
Because of this, some elements are manipulated slightly due to the formats hierarchical nature (there are elements with properties and child elements with geometry which we attempt to combine). However, we try to stay as true to the information presented by our third party library as possible.
If there are specific issues you’re seeing, I recommend sharing some sample data so we can see the behaviour and dig into it together. This way, we can explore why its happening and make improvements if needed. If you need to submit data privately, please consider submitting a support case with us. Hope this helps, Kailin.
For example, the way REVIT and Smart Plant 3D manage translucent “reserved volumes” (e.g. for walking, operating space, ...) is different, so combining child elements can create merged geometries of equipment and their volume spaces. Another example is the TimeLiner properties for 4D simulation, where properties are defined at different levels (geometry, composite object, group, ...) to represent events in a construction schedule, thus combining elements will create significant problems.
I will work to provide some sample data for a support case that might be of assistance.
Hello @edualarcong, after a bit more investigation, we became aware of some unintended behaviour in the current reading process. We have filed an issue (FMEENGINE-84674) to investigate and hopefully improve the situation. Will keep you updated, Kailin.
Thanks for the nwd/nwc -reader! I have some feedback on the new reader.
I face similar issue with the new tech preview Naviworks reader that I get verry few “FME-features” compared to a “find items” search in Navisworks Manage.
Navisworks reader get 49 features. Deaggregator with “preserve hierarchy” deaggregate to 148 features.
I was expecting about 171 features with a “GUID” attribute as Navisworks manage finds 171 “Naviswork-features” with GUID attribute and 60 “Navisworks-features” without any GUID (Item GUID).
The Navisworks reader should be able to deaggregate at reading, and read the relations and attributes on all geometry and non-geometry features.
There is also some difference in how FME interpret the “same” NWD regarding if IFC-conversion method V2/V3 and V4 was used on the same source-IFC -file. (This may be out of your hand to control).
Hello @arenei, so sorry for not reaching out sooner! Are you able to share a sample Navisworks file as well as attributes you are expecting to see, but aren’t present on read? It is possible that the re-architecting from FMEENGINE-84674 will address some of the issues you mentioned (projected 25.0 beta). If you are unable to share a sample dataset here, please create a case for us to chat further. Happy to help, Kailin
We use 3 different kinds of cookies. You can choose which cookies you want to accept. We need basic cookies to make this site work, therefore these are the minimum you can select. Learn more about our cookies.