Topography from CSV file not all appearing

[Anonymous]

Hello!

We made a point file from QSGS which pulled its information from USGS. It was great. It imported into Revit fine and we had a topography but the scale was off by a few hundred feet. Not able to scale the topo in Revit we opened the point file in Rhino 6 and scaled the points there. We exported the points again as a text file and then converted the text file to a CSV and pulled it back in Revit 2019 (student edition). All of the points are still there and show up when I edit the topo but when I accept and click off the topo the lower points are no longer there. Is there a scaling issue which how much will actually appear when it's close to level or something? I tried simplifying the surface and use 1' rather than 3" but it did not make the lower points appear. In the attached image I have the correctly scaled topo to the far left next to the oversized version. On the right pane the correct scaled topo again but in edit mode so you can see that all of the points are still there they just go away when I'm not in edit mode. 

Anyone know what to do in this situation? We have tried many methods of making a topography at this point and need a very accurate and large version to make our massings.

[barthbradley]

I'm not understanding. Points are not visible outside of editing mode. If you want to display the triangulated surfaces that are created by Points, turn on Triangulation Edges Subcategory under Topography Parent Category.  

[Anonymous]

I guess my problem is not that the points are not appearing but that the changes in elevation from those points are not being detected at the smaller scale. In my image you can see that in the larger topo there are more visible changes in elevation below grade which are topography lines that I really need for my site. Does that make sense? In any view of the smaller version of topo you can see the entire left side is going pretty much flat but that is not what is happening real world. 

[Anonymous]

These are the messages I received when importing the correctly scaled, slightly smaller topo file.

[barthbradley]

Well, Revit does have a 10 radius limit. If the extents of your Toposurface exceed this limit, that would cause problems.  On top of that, a Toposurface that large would behave like a boat anchor.  

If the whole Toposurface is located extremely far away from your Project's Internal Origin (a.k.a. Project Base Point's Startup Location), then grab the Toposurface AND THE SURVEY POINT, and moved them both together closer to the Project's IO.  

[barthbradley]

Can you post the File?  

[Anonymous]

That is not the issue unfortunately. Again, the larger file shows more detail than the smaller file. I guess it must be too much down-conversion from going between revit to rhino and back again. ]Is there any better way to make a very detailed topography in Revit?

[barthbradley]

---

@Anonymous wrote:

Is there any better way to make a very detailed topography in Revit?

---

What do you mean?  You're creating via a point file. 

[bin]

Maybe it’s just not showing that much contour lines on the left because you scaled the topography.  Try the topo setting and change the primary/secondary stuff. 

Be careful if you need an accurate site. Not too sure about your process but if it’s me, I would try to find out why it’s not to scale rather than trying to scale it. 

[barthbradley]

According to your screen capture entitled warning 2 topo.PNG, the point file is not being fully translated. "Some rows from the file could not be used".  Each row not used represents a point not placed.  The problem lies with the point file; not with Revit.