Extending the FBX-export with some properties From inside InfraWorks

[scheel]

FBX export should include some more data from the object like a SAP No, a description or a comment.

Also user defined properties will be a good idea.

We can use this properties to identify the object in other autodesk and foreign applications and for other cases.

Today only the InfraWorks internal object-Id is exported, all other like description or comment are ignored.

This Id is generated internal inside InfraWorks and therefor not really useable outside of InfraWorks.

[Eric_Chappell]

Discussing this with product team...

[Eric_Chappell]

Due in part to low community support, we're not considering this idea at this time but we'll keep it on the list for future consideration.

[Anonymous]

Hello everyone

as already mentioned in this post From Infra to Navis, in the future would be great to export all properties from Infra to Navis. the idea of having an exchange between the two software is very interesting.

Thanks

Michele

[Anonymous]

Interoperability between IW and Navisworks is becoming more and more important. We use object codes and properties all the time, which can be added in Revit, C3D etc. But when we need 3D object from Infraworks we cannot add them with the properties we want. We have the 2d objectcodes in C3D but after loaded in IW to get the 3d export and export them to NWS its gone. Hope support for this will increase!

[dthirlwell]

"Interoperability between IW and Navisworks is becoming more and more important."  @Anonymous 

I strongly concur.  We are using IW heavily for construction pursuits regarding site logistics, viewpoint simulation, and fast georeferencing.  We are often importing orthomosaic 2D maps, 3D meshes, and point clouds, some of which are conveniently georeferenced as well. However, IW is often not the presentation system, but more of a working charet platform.  In order to make IW much more useful, being able to export-to and/or synchronize-with Navisworks would be of great value to many people in the Construction industry (as well as many of the Architects that we are now seeing using Navisworks and IW).

[ramesh_sridharan]

@dthirlwell and others, This is one of the item we are currently checking it out. Would you be willing to provide more details to clearly understand what aspects are lacking on this FBX exports to make it more valuable for your workflow? You can post it here or email me (ramesh.sridharan@autodesk.com) or we can have a session to discuss.

Thank you very much for your help.

[dthirlwell]

Hi @ramesh_sridharan, I guess I was not specifically discussing FBX.  I would prefer an object-based format to a surface mesh, but it is important to us that whatever the format, there are distinct divisions that could retain some basic information: particularly the "category" (or whatever it is called in the schema such as road or building), Name, and possibly roof height. What I'm personally more concerned with is a format that allows me to show/hide individual objects inside of Navisworks and a more-fluid way to pass changes between IW and Navisworks.

[Wojtek_Garczewski]

HI @ramesh_sridharan,

I see some situations where extended properties included in exported geometry are very helpful. 
For instance:

1. Import the SHP dataset to InfraWorks to model Pipelines. 
2. Fill objects attributes.
3. Export 3D Pipeline geometry for model coordination. 

Would be useful to have all the properties (e.g. material, sizes, diameters, utility type, etc.) included in the Exported file.

If not possible to include such in FBX, maybe other formats?

Thanks,
Wojtek

[ramesh_sridharan]

I agree, @Wojtek_Garczewski. Let me add it to roadmap and discuss with tech folks. Thanks,