Where Have You Been with Your LS Lately?

Adam

Well-Known Member
5PLS
Here's one from this week. It is a great example of why to take multiple shots and to use a minimum time of at least 180. I had three shots that I manually stored at 180. Validation did it's job but I stored the points without them finishing. I was at the point about thirty to forty five minutes total. I stepped away 15' and performed a dist dist intersect. I hit the 2nd point within .02'. The other two were dead wrong.
KIMG0404.JPG

I had permission from the owner to cut the limbs.
 

Adam

Well-Known Member
5PLS
They didn't check, I didn't expect them to. Longest shot was 800 seconds. I would need some more time on it to depend on the PPK solution. I was putting wood in the ground based off this corner so I needed RTK on it. The dist-dist intersection is a great routine if you can get in the open not to far from the point.
 

Mike Lacey

New Member
That's basically what we do. Take two-three shots for min 200 seconds, and if they don't validate, try a distance-distance intersection. Takes time, but still worth it.
 

Adam

Well-Known Member
5PLS
That's basically what we do. Take two-three shots for min 200 seconds, and if they don't validate, try a distance-distance intersection. Takes time, but still worth it.
Most of the time I wait it out. I stored these just to illustrate the 180 sec fix can be wrong in these hard to get places. I usually let the first shot go untouched until it completes then I follow up with a second shot that I usally stop manually and store when I feel like it.
 

Darren Clemons

Well-Known Member
I had one at 189 this week that turned out wrong. Did exactly as Adam describes. Stopped and stored (it didn’t validate) along with a 15 min PPK , then started another session. That second session ended up getting a 525 second RTK and I knew it was correct so stored it and left (with another 15 minute PPK). Both Ppk’s processed to match the second session RTK. The LS WILL get most anything, just takes a lot of cross checking.
I would expect Galileo, if we ever get it, to help out tremendously with these points. The super strong L5 signal they show should power through a lot more foliage.
 

Nate The Surveyor

Well-Known Member
I had mine get to 214 seconds, (RTK) with over 1000 seconds of PPK. It eventually got to over 1250 seconds of PPK, but I knew it was the right group, because it did several resets, before it got to 214, but AFTER 180". So, I let it cook,. After looking at the PPK answer, it agreed with the RTK answer, by 0.02'. The resets it does AFTER 180" are pretty important. They tell us that were are pretty good. When PPK agrees, well, it adds confidence.
N
 

Sean Joyce

Active Member
"The LS WILL get most anything, just takes a lot of cross checking".

Agree, when you have been using it as long as we have you develop a feel for reading the information being provided whether the position is good.
there are a lot of ways to check aside from verification although verification makes you feel 99.99% confident.
I have had more than a few unverified points that were good.
The common element is spending time on the point and being able to interpret what is being presented by the L.S..
On some bad points I collect the data, move on to another and on the way back through survey it again and check it against the previous position.
PDelta and distance to last are really helpful especially if you are retracing a previous survey and have already had good measurements on some other corners.
The awesome thing about the L.S for new users that rely completely on a completed action group is they can be confident.
What gets tricky is when setting corners in a bad spot, you can chase the correct point all over like
I did last week. (white Pine woods, massees of branches overhead)
I finally got it staked after 2 trips using offset points. I never even got to phase 2 in this particular spot, had to rely on long static sessions and check distances to 3 good surveyed corners. To traverse to this place would have been very time consuming. :oops:
 
Last edited:
1737 NC / SC boundary surveyors ran a line due west along what they believed to be the 35th parallel. When they hit the old Charleston- Salisbury road they realized they were 12 miles too far south of their target. In 1772 they took a turn north and went around lands granted to the Catawba Indian Nation and then south to the Carawba river.

This stone was set in an 1813 retracement of the 1772 line and marked NC SC AD 1813.

I was too close by not to give the LS a chance to take part in a little history!!
97B1E69B-AD2E-49A1-8F76-0C5EDF5D27CA.jpeg
C8CE6CD3-845A-4565-89F3-97920728CD87.jpeg
F9E35C7A-856E-4F5E-83CF-6A08C1C54FFC.jpeg
3413B687-7362-4B22-AB4D-8BF488DEB0B3.jpeg
DD2A26AF-E5EA-4361-B7D9-181F0CF64F50.jpeg
361035BF-3CCD-40AF-A19D-FF2B3B7019C1.jpeg
 

Adam

Well-Known Member
5PLS
1737 NC / SC boundary surveyors ran a line due west along what they believed to be the 35th parallel. When they hit the old Charleston- Salisbury road they realized they were 12 miles too far south of their target. In 1772 they took a turn north and went around lands granted to the Catawba Indian Nation and then south to the Carawba river.

This stone was set in an 1813 retracement of the 1772 line and marked NC SC AD 1813.

I was too close by not to give the LS a chance to take part in a little history!!View attachment 8536View attachment 8537View attachment 8538View attachment 8539View attachment 8540View attachment 8541
Very nice!
 
Oops...miss spelled Catawba river...
Not that anyone’s checkin’ ...Haha

Enjoy your Surveying Gents!
It’s an honorable thing we get to uphold!
 
Top