hey new member

I don't use that particular software or setup, but I'm pretty sure you can get by with a dummy HI and HT. It's worked for me before.

Why not go ahead and run with real numbers?

thank you for you response!:-)

If I recall correctly, the program will default to generating 2D coordinates if the occupy point does not have an elevation,
I have a habit of having an arbitrary elevation for the control points (usually 99.0)
Just so I would know later on that i did not observe hieghts i usually set HI to 0.0 and HR to 99.0

thank you sir:-)

> Why not go ahead and run with real numbers?

I would concur with this thought. We always ran in 3D regardless of the required outcome because:

• It was part of our routine already and so didn't really have an impact on our time on the job; and
• We might later need 3D for some reason and we wouldn't have to go back out there except maybe to run some checks.

I can tell you that the second point came true enough that it was worthwhile for us to continue with our "tradition" of always collecting in 3D.

Anyway, just food for thought. 🙂

3D Is A Great Check On Your Observations

I have had traverses where I actually checked in better Elev. on my closure than N & E.

Plus if you ever check against GPS, Elev is a vital comparison.

Even if odd tie shots have no Elev my traverse and survey points do. I would not think of a nearby curb or ep shot without elev, but the opposite side of the street may be laser shot without elev.

Paul in PA

If your slope distance is significant and your rods do not remain the same, or change throughout the project, you will be jeopardizing true 2D distance. Stay with your true required inputs and you can never be questioned if you did it the right way. Or.... Morally acceptable.

AzClif

:good:

I agree with Wendell, I always run in 3D.

If you, (new member) always ran in 3D, you wouldn't need to ask this question....B-)

3D Is A Great Check On Your Observations

I change the rod heights even on a strictly 2D topo because the last thing I want to do is run the rod up and down mindlessly. It is pretty disheartening to realize halfway through a 3D topo that you changed the rod height ten minutes ago by that tree on the other side of the parking lot, and all the shots since have the wrong elevation.

3d only, but
do not add any rod height to 2d, just 0.00

my codes are setup to have an NE suffix for shots that don't have a 3d value

PKNE
CBNE
IPNE

once in a while you don't have a 3d on the point, it happens to the best of us.

i have had a hard time convincing one of my employees that every time the equipment is setup it should be measured up. we often return to old control and many clients return with other projects. how often does the staking turn into a site plan? often enough. providing 2-d and having the 3-d done allows us to later provide the 3-d and we can charge for the establishment of 3-d. it's money in the bank for the insignificant increase of time it takes to input some measure ups.

3D Is A Great Check On Your Observations

It is pretty disheartening to realize halfway through a 3D topo that you changed the rod height ten minutes ago by that tree on the other side of the parking lot, and all the shots since have the wrong elevation.

Isn't that the truth! Unfortunately I've done that--but only once.
😉

Can you explain that a little more? I don't see it. If the instrument or data collector reduces each shot from slope distance to horizontal distance using the zenith angle, how can there be a 2-D problem? You should get the same answer with any rod height and that height isn't part of the equation.

The only way I see a problem is if something tries to process it with 3-D.

I use TDS and when I'm not carrying elevations, I do exactly what you said. I leave my heights on 5' just because it's easy to remember, but you can use any arbitrary height you want. I makes absolutely no difference. Just remember in the future that the elevation data is not reliable.

I may have answered a little quickly. I assumed you were referring to working with a total station, but with GPS I'm not sure that answer would be correct. I believe it would be, but some people will probably disagree.

I once saw a guy decide to run a 500' rod to work without elevations, the soft rejected the shots and he had to return to site to shoot it again.

Not TDS though, just thought I would share.

-thanks everyone for the input.
today we ran no elevations but did input rod and instrument height. dont think it was necessary, but better safe than sorry.

as far as running 3D when only 2D is required. we were working on sunday because they are chomping at the bit. i would have normally run 3D, but could not even afford the half day it would have cost to run in elevations and set them on the control points.

its been busting loose around here and all my guys are on the pipelines. days like today i especially miss them. they are some good guys.

ps total station:-)

> i would have normally run 3D, but could not even afford the half day it would have cost to run in elevations and set them on the control points.

You can always use assumed data and translate later,f you need to.....

> its been busting loose around here and all my guys are on the pipelines. days like today i especially miss them. they are some good guys.

It's good to be busy, isn't it......B-)