I'm a construction guy, so apologies to the category police if erroneous.
Got the Hipers outta the shop (to the tune of $#1,900, bad radio in one) and Jim and I are off and running in Nome. WooHoo! Base starts fine, the rover and base are talking to each other again. Run out to localize on some of the control we have used over the years. Hit 4 points, residuals around 0.2 horizontaly and .04 or so vertically, spread out over about 2 miles, I can live with that. As a check, Jim "staked out" to one of our other control points, and missed by 2.3' Crap! Tried another, same distance 2.3' AND same direction, SW. Hmmm? Stake out to one of the points used for the localizing. 2.3', SW. WTF? Now, I can understand if one of the control points he was checking to was grossly disturbed or whatever, but the same distance and bearing? And shouldn't the point that was one of the localizing points still hit good? A bit puzzled. Jim has been out in the field, basically started over, so I'll see what came of that when he gets in. Days like this make me wanna grab a hiway chain and a T-2!
-JD-
sounds like the your setting for us survey foot or international foot got switched around. Try that out
I hear about a t-2 and chain!!!
I'll start with dumb question...no chance that one set of points is in is in U.S survey foot and another is in international feet?
the same distance and bearing sounds like there is a shift in a drawing or coordinate system....just a guess..
EDIT:...I been beaten to the punch..
I've had that to happen was when the point that we were using for control was found to not be the control, but one that resembled the actual control point and unfortunately fell too near the actual control point that was hidden from view by some clever camouflaging.
That made everything we set from that point to be the same bearing and distance wrong.
The only other time that happened was when we were given a set of point information where one monument location was listed 10 feet out N-S and 10 feet out E-W. I remember that because it added two paid days to our contract to fix because it was not our error.
> I've had that to happen was when the point that we were using for control was found to not be the control, but one that resembled the actual control point and unfortunately fell too near the actual control point that was hidden from view by some clever camouflaging.
>
> That made everything we set from that point to be the same bearing and distance wrong.
That's exactly what I was thinking.
Same thing has happen to me twice. Reason still unknown, but the common thing that pops in my head was I set up the base on one of the points in the calibration. I pulled the base out of the calibration and was able to hit my control. So I picked up and set a totally random point and started the calibration over so I could include the point I was on.
Given that you said that delta x,y and z were same .....
Could it be that you directly down loaded coordinates from survey data file for use in field and that some one had been previously nosing around in the file and done a block shift of some data , thus moving some of your control points?.
RADU
control may not adjust
Might be any one of those "GPS wtf", but it may be that if the point has already been used as "control" it will not adjust or move with your new localization. I try to occupy each control as a data collection point 'check shot' in case we screw with the localization at a later time we can see what moves and what doesn't. It seems the survey software modules work in their own mysterious ways, some move northing/easting some only adjust if it has Lat/Long. Last week I used a USCG BM (state plane coords) for vertical only then localized on property corners (5,000/5,000 coords), TDS didn't move the BM point horizontally (because it was control) so now my draftsman thinks the BM is 7,139,985.69' away (1,352 miles),oh but I shot it again as a check at the end of the day, whew.
Similarly for example w/TDS if you use the GPS offset routine and "occupy a reference point" then offset to a tree, say north azimuth 15', the reference point will move with localization (GPS geodetic coords) but the offset point tree(internal cogo XY)will not.
...some of my trial and error.
John Williams
at 8,500' it's still snow and winter in my part of California. June 3, 2011.