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.

Parents
  • 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 . . .

Reply
  • 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 . . .

Children
No Data