Survey-led 3D utility data into Revit with metadata/parameters

Revit
, ,
1

Hi all,

I am looking for advice on the best way to import survey-led 3D underground utility and topographical data into Revit and retain the associated metadata.

Our current process is:

  • field capture

  • processing in N4CE

  • export to CAD

  • issue to client

We now want to develop a workflow that allows this data to be used properly within a Revit/BIM environment.

The geometry is only part of the issue. We also need the field-captured attributes to remain usable, including:

  • utility type

  • depth

  • diameter

  • material

  • PAS128 quality level

The goal is not to bring in CAD as background information only. We want to understand how best to convert or rebuild the utility data in Revit so that both the 3D geometry and the attribute data are available as structured model information.

The questions I am trying to solve are:

  • best import path from N4CE/CAD into Revit

  • whether Dynamo is the best tool for this

  • whether utilities should be represented as pipes, conduits, generic families, or another object type

  • how best to push survey attributes into shared parameters

  • whether Civil 3D, CSV, or another intermediate format is a better route before Revit

I would be very interested to hear from anyone who has dealt with topographical or utility survey data, especially where the requirement is to retain non-graphical information alongside the 3D model.

Thanks in advance.

2

This is the area where you’ll need to do some research as this isn’t integrated with Dynamo yet and the rather niche software has a heafty price tag to help you with the exploration. A quick search online indicates there is a Python based API, which means you may be able to access information from Dynamo’s Python node directly. If not and it requires its hosted Python engine then that can be used as an alternative to write out the complete information set that you are after, but if it has a built in export to a ‘information complete’ file (i.e. CSV, JSON) might be easier.

Once you can access the data by reading the file or directly via Dynamo’s Python node making object instances will be fairly straight forward for a skilled Dynamo user. But getting into those details is best left for after confirming the interop process.