Default Elevation for Add Surface Point

[AllenJessup]

I'm looking for support for an idea I posted a year ago.

https://forums.autodesk.com/t5/civil-3d-ideas/default-elevation-for-add-point/idi-p/8780589

When adding a point to a Surface I don't often want it to default to the the Surface Elevation. So every time I want to add a point from an object that has an elevation. I have to select the point an either type in the elevation or list it beforehand and use copy/paste.

My opinion is that it should default to the elevation of the selected point with options to use the Surface Elevation or pick another point for the elevation.

[wfberry]

Allen:

Does OSNAPZ have any effect?

Bill

[AllenJessup]

Bill,

OSnapZ would have an effect. Just not the one I want. I want the pick to default to the elevation of what I'm snapping too. Most often a Node snap to a Cogo Point but possibly an EndPoint on a Featureline on another object or entity. Even possibly a NEArest or Center on a Circle.

[Anonymous]

Is this what you are trying to do? Sorry tried to upload a screencast. It didn't take.

[AllenJessup]

This is what is happening. I'd like to be able to set it to grab the objects elevation.

[Joe-Bouza]

Hi Allen

I am confused your original post says you are getting the snapped elevation which you dont want, and  3 of five says something different. Maybe Im reading wrong.

[Anonymous]

Since you are using the Surface point option it is hard coded to extract the elevation of the surface. I would just created a point group of the cogo points you want and add the group to the surface. I know that is not what you want to do but you're limited the short comings of the software

[Joe-Bouza]

I am very confused. if I snap to an object the cogo point takes the object elevation. What am I misunderstanding?

if you adding point to the surface is it to supplement data in the surface or labeling?

[Anonymous]

If you have cogo pts and you want to create feature lines at the elevations of the points, having your osnapz on works. But in the post Allen if using the point from a "Surface" command so where ever you pick as long as there is "surface" there it will extract the elevation from the surface (period) even if you pick an entity with elevation not associated the the "surface". The key word is Surface here.  If you want a certain elevation at your pick point, you will have to type in in.

[AllenJessup]

Joe,

I'm sorry if I've been unclear. This is the first line from the wish I posted "When using the Edit Surface to Add Point. I think it should default to the elevation of the selected location rather than the existing Surface elevation".  I've since modified my opinion to that it should be an option for picking the object elevation or the Surface elevation.

---

@Joe-Bouza wrote:

if you adding point to the surface is it to supplement data in the surface or labeling?

---

No. It's to replace a point that should exist but doesn't. Mostly this shouldn't be necessary but is with the Surface I'm dealing with. Why would you add a point to a Surface if the Surface elevation at that point is already the elevation you want? 

[AllenJessup]

---

@Anonymous wrote:

where ever you pick as long as there is "surface" there it will extract the elevation from the surface (period) 

---

Yes. But that's why I posted it as an Idea. So the program could be changed to allow the object elevation.

[AllenJessup]

---

@Anonymous wrote:

I would just created a point group of the cogo points you want and add the group to the surface. 

---

Yes. That is (in most cases) the correct way to do it. In my case it's a Catch 22. I'd have to establish all the correct points first then export them to a point file. It's a long and dirty story on how I've gotten to this point with the Surface.

[AllenJessup]

---

@Joe-Bouza wrote:

Hi Allen

I am confused your original post says you are getting the snapped elevation which you dont want, and  3 of five says something different. Maybe Im reading wrong.

---

I'm probably not expressing myself well. This is from my first post in the thread. "I don't often want it to default to the the Surface Elevation".

So what I'd like is to have an option to get the snap point elevation as the default.

[Anonymous]

The command doesn't do that. I get what you are asking for. But at this time and version that is not possible, which I think you know that now.

[AllenJessup]

---

@Anonymous wrote:

The command doesn't do that. I get what you are asking for. But at this time and version that is not possible, which I think you know that now.

---

Yup. That's why I posted in the Idea forum. I just thought i anyone else would like to see this in a future version. They might give it an upvote. 

[AllenJessup]

BTW. If I use Insert PI on a Featureline. It defaults to the snap point elevation and has an option to use the Surface Elevation. That's how I'd like any command when editing anything to do with a Surface or Grading. There isn't a lot of consistency in the way the commands work. IMHO

[Anonymous]

Yup, you are right. I use running object snaps a lot and on some feature lines commands the node setting I have set is ignored and I have to re-select it for every new vertex. Annoying but that's the short comings of the programmers who program and don't do what we do all day.

[Joe-Bouza]

Then shouldn't you use random point instead of point from surface?

[AllenJessup]

Joe,

I think we're still confused. I'm adding a Surface Point, _AeccAddSurfacePoint. I need to add them at points where I would expect one but it's dissapeared.

[Joe-Bouza]

Yes we are. First I didn't recognize you were adding TIN points. I thought you were adding a COGO and could not get the COGO elevation from the Line work.

No w I  don't understand Why you aren't adding that cogo point to a group in the surface?