Survey Pro glitch???

Posted by: @t-ray

Yesterday I used the latest Survey Pro software in Ranger 3

Just a guess, and so there's some discussion, you're latest version of SP isn't;

Enabling your compensator

Applying the different corrections to your raw file

Taking into account the different corrections in calc your xyz

?ÿ

Stay tuned for more of the usual bromides.

?ÿ

I seem to recall one time when the "measure to" point got mixed up or didn't stay the same within different apps within Survey Pro.

Depending on the height of your leveling screws on your tribrach for an S series instrument (at the "0" line, or +/-), the height from the top of the tripod head to the "Bottom of Notch" on Trimble instruments is right around 0.25'.

post the raw data so we can see what might be going on.

Are we sure there's not a problem with the vertical on project control?

I too would like a crack at the raw data...

I was a long time Survey Pro user switched to magnet last year. Survey pro uses a 3d resection vs 2d+h. It will weight the V error vs the distance it could make a .1 error in 500ƒ?? look like .02 if the distances are drastically different.

@rover83 definitely not a problem.

?ÿ ?ÿHere is the RAW as a .txt BS points were 20 & 30

@t-ray?ÿ

I could be a big dummy here, but this file doesn't appear to contain the complete header info, nor the fixed coordinates for points 20 and 30?

@michigan-left yes the full raw was 124 pages so I just deleted everything prior to this day.

@mvanhank222 how do you like Magnet? Will it drive a Trimble Robot?

Magnet wonƒ??t run Trimble it is a Topcon product. I like it so far some small things I donƒ??t like but nothing insurmountable.

@t-ray

Do you have the coordinates for those 2 points, and some metadata about the coordinate system? (SPC? Zone? Survey Feet? Etc?)

It's kinda difficult to check a resection if we don't have those 2 points.

Or at least Trimble Business Center is yelling at me becuase it can't establish a back bearing.

20,2218210.97,2329070.45,2152.18,mini

30,2218201.41,2329838.54,2154.26,5REB-LSI-CTRL

?ÿ

These are ground coordinates Idaho West

I'm just part way through the raw but you seem to have a problem when sighting pn30 you have about 20 seconds difference in your zenith from the resection sighting to the backsight sighting resulting in 0.06' difference. This shouldn't be that different at only 627'. I'll continue looking at the raw. Why is there not a rod height when sighting the generic prism on pn20 during the resection?

So some assumptions I'm making; occupied points 31,32, and 33 are all the same point and instrument setup. The only difference is they are different solved resections. Just in considering all the observations from occupied to backsight at 30 you have various zenith angles 89-22-00, 89-22-32, 89-21-32, 89-23-29, 89-20-25, 89-19-37. This is way too much variation for a single stable set up. It looks as if something is wrong. Also, for some reason the instrument height changes from 5.79 to 5.74. Again I'm assuming the instrument was never moved during this whole time. I didn't evaluate what survey pro calced but without further explanation there appears to be something wrong with the raw observations.

The vertical circle of the instrument appears to be very reasonable but there is something influencing the vertical sighting to point 30 that is definitely not correct.

Posted by: @lurker

Again I'm assuming the instrument was never moved during this whole time. I didn't evaluate what survey pro calced but without further explanation there appears to be something wrong with the raw observations.

Agree. Looking at the raw data file, I don't see much in the way of additional checks, but maybe it got clipped out.

It's possible, but extremely rare, for the field software to record incorrectly values. I would suspect either bad control, a bust in the setup, or something going on procedurally.

?ÿ

Did I read correctly upthread that there was another set of observations taken with another instrument? If that is correct, and you were seeing the same problems, I would suspect bad vertical in the control.

If you really wanted to rule out Survey Pro, you could sight the points and book all the angles, then manually record the slope distance and reduce things in the office.

?ÿ

@lurker

I use these mounted on different objects for control and just call them 0.00 rod height

@lurker @rover83 The difference in the HI was the difference between the S5 and S6 setups. I didn't store any other checks because everything I shot was way off vertically but physically checked 4 other points including 2 control points and 2 previously set points. All the control has been run with a digital level and checked with the same S5. I am going to go through the raw this weekend because I staked out a bunch of points using and alignment then checked in bad vertically then got the gun to give me the correct vertical then reshot those points and put new grades on them. So basically I have 2 sets of data for each point so that should at least show me what's going on, still not sure why that would be happening. I appreciate the input from all..... stay tuned!

@t-ray

I'm kind of curious how you used a digital level to put an elevation on those prisms that you use 0 for the rod height.

Something needs to explain the different zenith angles back to pn30. I see that you had 2 different set ups so I would expect 2 groups of the zenith angles to be relatively close within themselves but it appears both setups had large variations when sighting pn30. A variation of 00-00-15 would equal 0.045' which should be easily accomplished at that distance. These variations are significantly greater so something is wrong with those observations.