Import Points to Zero Elevation

Anonymous · ‎04-27-2010

Under the point style I have it set to flatten points to elevation. However when I import points and draw a line between two points a "Z" elevation is still at each end of the line. This is unacceptable for survey work. What am I doing wrong, or what am I missing to force the points to flatten to a zero elevation.

I want this to work just like LDD did. Import points using point elevation, or import points and place on Zero elevation.

Anonymous · ‎04-27-2010

Try creating a new point style and changing your points to that style. Maybe there is a problem with the style you are using. I created a new style and changed the points, since the points were inserted all ready and that worked for drawing the line at zero elevation for point node to point node.

Anonymous · ‎04-27-2010

azrdgldr's solution should work. We had the same initial problem. By
changing the toggle in the point style we're able to get the points in 2d.

Just wait until you get to use survey figures. No matter what we try they
always come in in 3d, it's a royal pain.

wrote in message news:6381485@discussion.autodesk.com...
Try creating a new point style and changing your points to that style.
Maybe there is a problem with the style you are using. I created a new
style and changed the points, since the points were inserted all ready and
that worked for drawing the line at zero elevation for point node to point
node.

Anonymous · ‎04-27-2010

Did you change the "osnapz" command ?

Bill

wrote in message news:6381426@discussion.autodesk.com...
Under the point style I have it set to flatten points to elevation. However
when I import points and draw a line between two points a "Z" elevation is
still at each end of the line. This is unacceptable for survey work. What
am I doing wrong, or what am I missing to force the points to flatten to a
zero elevation.

I want this to work just like LDD did. Import points using point elevation,
or import points and place on Zero elevation.

Anonymous · ‎04-27-2010

Both solutions worked. Thanks.

One cookie awarded for the Osnapz command. Never knew it existed.

Just need to verify it is giving me horizontal distance and not slope distance now.

Anonymous · ‎04-27-2010

The osnapz toggle does not work as intended. When we try to obtain a
distance from the object in 3d to a 2d object the distance comes out
correctly as horizontal only, no slope distance no change in Z. However
when we reverse the command and pick the 3d object last the distance comes
out as a slope distance and it shows a change in Z value. I've duplicated
this on 4 machines in our office.

The odd thing is that if we draw a line to or from the 3d object it does
work as intended and has no vertical/slope values associated with the line.
Odd behavior if you ask me.

wrote in message news:6381588@discussion.autodesk.com...
Both solutions worked. Thanks.

One cookie awarded for the Osnapz command. Never knew it existed.

Just need to verify it is giving me horizontal distance and not slope
distance now.

Sinc · ‎04-27-2010

> {quote:title=Guest wrote:}{quote}
> The osnapz toggle does not work as intended. When we try to obtain a
> distance from the object in 3d to a 2d object the distance comes out
> correctly as horizontal only, no slope distance no change in Z. However
> when we reverse the command and pick the 3d object last the distance comes
> out as a slope distance and it shows a change in Z value

The DIST command has been that way for some time now. It's come up at least a couple of times already in these discussion groups.

-- Sinc
http://www.ejsurveying.com
http://www.quuxsoft.com

Sinc

Anonymous · ‎04-27-2010

Thank dei-feif. Least I know it's not just me. Is this fixed in 2011?

wrote in message news:6381650@discussion.autodesk.com...
> {quote:title=Guest wrote:}{quote}
> The osnapz toggle does not work as intended. When we try to obtain a
> distance from the object in 3d to a 2d object the distance comes out
> correctly as horizontal only, no slope distance no change in Z. However
> when we reverse the command and pick the 3d object last the distance comes
> out as a slope distance and it shows a change in Z value

The DIST command has been that way for some time now. It's come up at least
a couple of times already in these discussion groups.

-- Sinc
http://www.ejsurveying.com
http://www.quuxsoft.com

Sinc · ‎04-27-2010

> {quote:title=Guest wrote:}{quote}
> Thank dei-feif. Least I know it's not just me. Is this fixed in 2011?

It looks like it was, mostly. If you have Dynamic Input turned on, it looks like that's still displaying the 3D distance. But once you click on the 3D object, it displays the 2D distance in the command window.

However, I notice that the PERP Osnap is as funky as ever on 3D Polylines.

And while I was looking, I also checked to see if the background masks had been fixed for curved text yet. Unfortunately, no. (We've been waiting for this one to be fixed since C3D 2007, and it looks like we're disappointed again...)

-- Sinc
http://www.ejsurveying.com
http://www.quuxsoft.com

Sinc

Sinc · ‎04-27-2010

On the plus side, we finally got the ability to group digits in large numbers without resorting to those torturous expressions... 🙂

-- Sinc
http://www.ejsurveying.com
http://www.quuxsoft.com

Sinc

Anonymous · ‎04-28-2010

I was not able to duplicate your findings. There was no change on my end
whether I had dynamic input off or on. Personally I never use that setting.

wrote in message news:6381706@discussion.autodesk.com...
> {quote:title=Guest wrote:}{quote}
> Thank dei-feif. Least I know it's not just me. Is this fixed in 2011?

It looks like it was, mostly. If you have Dynamic Input turned on, it looks
like that's still displaying the 3D distance. But once you click on the 3D
object, it displays the 2D distance in the command window.

However, I notice that the PERP Osnap is as funky as ever on 3D Polylines.

And while I was looking, I also checked to see if the background masks had
been fixed for curved text yet. Unfortunately, no. (We've been waiting for
this one to be fixed since C3D 2007, and it looks like we're disappointed
again...)

-- Sinc
http://www.ejsurveying.com
http://www.quuxsoft.com

Sinc · ‎04-28-2010

> {quote:title=Guest wrote:}{quote}
> I was not able to duplicate your findings. There was no change on my end
> whether I had dynamic input off or on. Personally I never use that setting.

Not sure I follow you... Maybe we had a communication failure here?

I was saying that in 2011, the problem seems to be fixed, in that the DIST command will return the 2D distance if you have OSNAPZ=1. However, if you have Dynamic Input turned on in 2011, the DI will still show the 3D distance, even if OSNAPZ=1.

So it looks like Autodesk partially fixed the problem in 2011. Unless the INTENDED Dynamic Input to ignore OSNAPZ... That seems confusing to me, but maybe it's what they intend. It's sometimes hard to determine if Autodesk does something intentionally, or if it's an oversight.

-- Sinc
http://www.ejsurveying.com
http://www.quuxsoft.com

Sinc

Anonymous · ‎04-28-2010

Ok, gotcha. We're on the same page now.

Thanks again.

wrote in message news:6382024@discussion.autodesk.com...
> {quote:title=Guest wrote:}{quote}
> I was not able to duplicate your findings. There was no change on my end
> whether I had dynamic input off or on. Personally I never use that
> setting.

Not sure I follow you... Maybe we had a communication failure here?

I was saying that in 2011, the problem seems to be fixed, in that the DIST
command will return the 2D distance if you have OSNAPZ=1. However, if you
have Dynamic Input turned on in 2011, the DI will still show the 3D
distance, even if OSNAPZ=1.

So it looks like Autodesk partially fixed the problem in 2011. Unless the
INTENDED Dynamic Input to ignore OSNAPZ... That seems confusing to me, but
maybe it's what they intend. It's sometimes hard to determine if Autodesk
does something intentionally, or if it's an oversight.

-- Sinc
http://www.ejsurveying.com
http://www.quuxsoft.com