We are pursuing this workflow within the context of revit. I am not a revit user, so I don’t know if this is a good idea. but I think it fits within the roadmap of all the products. Would love for anyone to provide their prospective.
@ddrennen2QDK2 the best end-game result is to create real toposolid in Revit, which is defined by points. These are the nodes you can choose from there:
You can essentially choose to use either an outline, points or both to generate a TopoSolid in Revit 
This means the TopoSolid will behave as expected and play nicely with other elements. The current approach will get the geometry in, but will not be editable in the ways that someone may expect or want.
1 Like
The other option to consider (as I know you are a Civil 3D user), would be using the link topography feature. The overall workflow would be to transfer the topography data from Forma into Civil 3D, and then link that into Revit. This would ensure the Revit users have access to the topography, while simultaneously allowing the benefits of advanced topography features of Civil 3d as the result is a link to published data, which means as the topography model’s detail increases you don’t have to reconfigure content.
The process for linking topography can be found here: Help
1 Like
Here is the points and boundary method….interesting.
We civil users are “offering” this type of content in the revit domain to test if users prefer this by comparison with other existing methods (like linked topography)
2 Likes
If this data is coming from Forma, then it will have a z-value above sea level associated. For Revit, you’ll want to remove that in some heuristic fashion.