Setting COGO point elevations on a terrain model (draping) in ORD Connect

Does ANYONE know how to set a the elevations of a collection of civil geometry points (COGO points??) to be that of a named terrain model in ORD Connect?! I see the question asked many times, with the answers all coming from "If you use the InRoads tool _____," or "Using GEOPAK tool _______" — but I am NOT using those products; I am using ORD 2019 R1 and am desperately trying to find out how to do this seemingly very simple task.

Alternately, I would appreciate it if someone would simply say "You can't do that in ORD/Connect" if that is indeed the case. Seems a simple enough task, though.

Thanks to all in advance.

  • So, I managed to stumble my way into creating points and getting them onto a surface. That part worked ok, if slightly hidden in the workflows. What I was needing was to drape the points on a surface (worked for the first instance), then re–drape them onto two other surfaces (the "MODIFY POINTS" command would NOT reset them to a different surface no matter what I tried!). Turns out that I had to "MODIFY POINTS" by method of "VALUE" and set them all to a particular elevation (didn't matter what value), and THEN I could "MODIFY POINTS" by method of "SURFACE/MESH" and it would reset them to the alternate surface.

    Seems like once they were set to one surface, then "MODIFY POINTS" would not modify to the alternate surface without the intervening "VALUE" modification first. Plus, there were no messages indicating that they weren't going to change unless I did that step. I would request a fix to this behavior, or at least some documentation that you have to "UN–MODIFY" the points that have been associated to a surface before they will switch to the alternate surface.

    What a journey . . .

  • Certainly true as to what I needed. But getting back to the original question as an aside worth chasing down . . . shouldn't it be a fairly common surveying practice to set a bunch of COGO points to a new surface to derive a new set of elevations? This is usually how we compute stakeout points, by taking what were either 2D or previous Existing Ground 3D points and elevating them to a final grade surface so we can establish cut and fill when we stake out the points.

    Seems it should eb a bit more straightforward than it seems to be.

    Thanks, all, and I will keep investigating.

  • All I did what use MicroStation Place Active Point (or SmartLine, for that matter), selected the elements and ran the report - as I thought that the terrain elevations were wanted (Ken did say "I don't really need the points in the design model").



  • Well, perhaps this is the crux of the issue: I created the points in a fieldbook as Survey elements (COGO points, perhaps??) because I had to select the centers of a series of circular steel pipe piles (in the file as cylinder solids). This set their elevations forever and always to the elevation of those centers, and I wanted to be able to update their elevations with a terrain model. Much like the Geometry tools suggest. I suppose I needed to create them using the Geometry tools, but I didn't know that when I started. 92 points later, I was hoping to just pick a tool to let me drape them on a surface. Like InRoads (and presumably GEOPAK, MX as well) used to let me do. I was looking for that tool.

    Plus when I have the points in a fieldbook, I can very easily dump them, or turn off their visibility, etc.

    Thanks, I'll check things out and try to always use the geometry tools. 

  • One more thought occurs: did you do this with points added to a terrain? I was trying to do it with points I added into a fieldbook (Survey elements). Not sure if that's an issue, but worth investigating.

    Thanks!