Stakeout... The old kind...

Nate The Surveyor

Well-Known Member
In cogo, we should have a manual stakeout routine.
For total station use.

Backsite (height of target)
(slope dist and zenith)
Inst@
Foresite (height of rod)
Desc of set point.
This to easily use a total sta, and set a corner, off of 2 nails, in the field.

It would get used occasionally.
I know it would be done via manual data entry. I had a bunch of shots, close to each other today. Total sta would have worked well.
N
 

Matt Johnson

Well-Known Member
5PLS
Of course, we can use 2 inverses, and subtract the angles... but a simple "Total Station Stk" routine has it's place.
N

We have the CoGo Triangle function that will calculate the angles and distances between 3 points. The biggest problem with it for this purpose is that it still does not have an option for "Angle Right". @Andrey Zhiganov please consider adding a Angle Right (clockwise) option.

COGO-TRIANGLE_20170602-13.08.46.png


Creating a dedicated Cogo Angle or Total Station Stakeout function would be even better. Inputs would be Occupation Point, Backsight Point and Stakeout Point. It would then output the angle right and distance to the stakeout point. We already have an old ticket for this (VSAPP-3400).
 

Vladimir Prasolov

Well-Known Member
JAVAD GNSS
I modified the VSAPP-3400:

Create new COGO task that could be used for stakeout with total stations.
Screen is similar to "Traverse" with the following modifications:
Input parameters:
1. Horizontal angle (HZ). Turned to the right from a backsight.
2. Slope distance (SD).
3. Vertical angle (VA) or zenith angle (ZA). Instead of delta height, which is calculated.
4. Optional Corrections (check boxes):
4.1 Atmospheric refraction.
4.2 Earth curvature.
 

Matt Johnson

Well-Known Member
5PLS
I modified the VSAPP-3400:

Create new COGO task that could be used for stakeout with total stations.
Screen is similar to "Traverse" with the following modifications:
Input parameters:
1. Horizontal angle (HZ). Turned to the right from a backsight.
2. Slope distance (SD).
3. Vertical angle (VA) or zenith angle (ZA). Instead of delta height, which is calculated.
4. Optional Corrections (check boxes):
4.1 Atmospheric refraction.
4.2 Earth curvature.

This sounds good. There should be option to input either Slope Distance (SD) or Horizontal Distance (HD). If HD is the input then the 3rd input would be delta height. Any modern total station can calculate a display the horizontal distance and delta height. We would also need inputs of instrument height (HI) and target height (HT) to correctly calculate the heights when HI is not equal to HT.

This function should be able to work in both Survey and Stake modes or have 2 functions (Total Station Survey / Total Station Stake). What you described would be used for Survey mode. In Stake mode the inputs need to be 3 points (Occupation Point, Backsight Point and Stakeout Point). It would also be nice to include a Measured Distance input. It would then output Horizontal Angle and Delta (difference between the distance from the Occupation Point to the Stakeout Point minus the Measured Distance).
 

Matthew D. Sibole

Well-Known Member
5PLS
This sounds good. There should be option to input either Slope Distance (SD) or Horizontal Distance (HD). If HD is the input then the 3rd input would be delta height. Any modern total station can calculate a display the horizontal distance and delta height. We would also need inputs of instrument height (HI) and target height (HT) to correctly calculate the heights when HI is not equal to HT.

This function should be able to work in both Survey and Stake modes or have 2 functions (Total Station Survey / Total Station Stake). What you described would be used for Survey mode. In Stake mode the inputs need to be 3 points (Occupation Point, Backsight Point and Stakeout Point). It would also be nice to include a Measured Distance input. It would then output Horizontal Angle and Delta (difference between the distance from the Occupation Point to the Stakeout Point minus the Measured Distance).

I assume a ticket has been made for this item? I have a customer wanting to use this feature!
 

Matt Johnson

Well-Known Member
5PLS
It will be manual input at first and then later the possibility to receive data through a Bluetooth connection to total stations once the OS of the LS is changed to Linux.
 

Jim Frame

Well-Known Member
It will be manual input at first and then later the possibility to receive data through a Bluetooth connection to total stations once the OS of the LS is changed to Linux.

Is a J-Field-only box (i.e., an LS without the receiver and all its support systems) still under consideration? Having to haul the LS around to run a total station when all you need is the data collector and cogo functions of J-Field is going to be more than a little inconvenient.

(Is that what Victor-LS is for?)
 

Matt Johnson

Well-Known Member
5PLS
Is a J-Field-only box (i.e., an LS without the receiver and all its support systems) still under consideration? Having to haul the LS around to run a total station when all you need is the data collector and cogo functions of J-Field is going to be more than a little inconvenient.

(Is that what Victor-LS is for?)

Yes, this is what the Victor-LS is although its designed purpose was to control externally connected receivers.
 
Top