Still Struggling With Localize

Adam

Well-Known Member
5PLS
I appreciate the cautions, but should note that -- to date, anyway -- my only use for localization is to search for existing points. For the specific job I'm playing with now I don't need it at all, I'm just using the job as an opportunity to get the procedure down pat.

The reason I was surprised by the 1° tilt is that this is a control job -- I was retained by a city to validate control established by another surveyor for a bridge construction project. The city wants to be sure that when the contractor starts building from both ends he'll meet himself in the middle. I don't have metadata yet, but I'm beginning to suspect that the first surveyor used RTK to position the points, rather than static and total station as I initially assumed. The fact that he set some flight control points right under trees is beginning to make me think I may have to do more than just check...
Anytime I am handed coordinates from someone else I run it thru localization to see how good those coordinates are. Localization is perfect for this.

Aerial targets under the trees. LOL even the name implies that they are supposed to be seen from the air.
 

Nate The Surveyor

Well-Known Member
I recently got a pile of spc from somebody. I started with an autonomous position for my base. I hit a couple of the points, and localized. Everything else I hit, fit within a few hundredths. Later, I refined it a little. After dpos, there was still a difference of 6 ft or so, but brgs were within a second. I wound up forcing the scale to match my ground, and rotation to be zero. But, that 6 ft remained. Either the coords were based on an autonomous base, or they were on international ft, instead of us survey ft.
I did not try to solve that. Didn’t really matter.
metadata is nice.
nate
 
Top