Odd thing happened,...
 
Notifications
Clear all

Odd thing happened, points staked about 4.5' off

25 Posts
14 Users
0 Reactions
2 Views
(@mark-o)
Posts: 175
Estimable Member Registered
Topic starter
 

First time occurence and it scared the .... out of me. I staked about half dozen points using RTK and only learned today (a month later) they were all off by about 4.5' to the north-northwest. Fortunately this wasn't a costly mistake. I went back out with both RTK receivers I have and same points staked in correct locations.?ÿ I'm guessing maybe a default setting may have changed? Maybe "Convert WGS84 to NAD83" was checked, or somehow it loaded an older geoid model?

I initially thought maybe it could be a US/International Survey foot issue, but that doesn't seem to be the case.

If anyone has ever had this experience and knows what may have happened, I'm all ears.?ÿ?ÿ

 
Posted : 22/10/2018 7:58 pm
 Norm
(@norm)
Posts: 1290
Noble Member Registered
 

It's not the geoid. I'm betting on wrong datum designation. And yes we have seen it before. In our software it's the difference between (NAD83 No_Trans) and NAD83. It may be called something else in your software.

Always check into a known point before, after and during RTK sessions.

?ÿ

 
Posted : 23/10/2018 2:49 am
(@john-hamilton)
Posts: 3347
Famed Member Registered
 

Sounds like ITRF versus NAD83(2011). Trimble had a poorly named transformation that confused people, but sometime ago they changed the name to be more clear. You don't say what DC you are using.?ÿ

 
Posted : 23/10/2018 2:50 am
(@stlsurveyor)
Posts: 2490
Famed Member Registered
 

Do you use C3D to calc your points? Check to make sure your base file and xrefs are all set to US Survey feet - and don't forget to look for units. In 2018 you have feet and US Survey feet...If units are not set to US Survey feet your referenced blocks will be off about 4.5 feet.

 
Posted : 23/10/2018 2:59 am
(@lee-d)
Posts: 2382
Noble Member Registered
 

4.5' sounds more like feet / international feet to me; ITRF - NAD83 isn't usually that much in the horizontal (assuming the error was Hz). We see this from time to time with Civil 3D, you have to be very careful that everything is in US feet.

 
Posted : 23/10/2018 4:19 am
(@mark-mayer)
Posts: 3363
Famed Member Registered
 

It could be any of the things already suggested but I'm thinking that you had an autonomous position at the base.?ÿ

My procedure after setting up is to check into a known point before proceeding.?ÿ And to check into another known point at the end. That has saved my bacon many times.?ÿ?ÿ

 
Posted : 23/10/2018 5:12 am
(@mark-o)
Posts: 175
Estimable Member Registered
Topic starter
 

I multiplied my state plane coordinates by the international/US survey point ratio and got a much larger discrepancy (roughly about twice ~9'), although the ratio of northing/easting was close, so that could explain it,?ÿ

I'm going to go back out to the site and try the NAD8 Nno-trans vs NAD 83 toggle and see if I get the same discrepancy and post my results.

Lesson learned, like others have said, best to make a habit of checking into a known point or two before setting out.?ÿ

?ÿ

Thanks for all the help!

 
Posted : 23/10/2018 5:46 am
(@jim-frame)
Posts: 7277
 

ITRF - NAD83 isn't usually that much in the horizontal

Around here (NorCal) it's about 4.8 feet.

 
Posted : 23/10/2018 5:51 am
(@lee-d)
Posts: 2382
Noble Member Registered
 

Wow that's quite a bit more than here; around here it's around 3' - 3.5'.

 
Posted : 23/10/2018 5:57 am
(@mightymoe)
Posts: 9920
Illustrious Member Registered
 

It won't be a unit error like US feet vs. International feet. If you think about that, it would cause the point to be off either Northeast or Southwest depending on the foot getting smaller or larger.?ÿ

 
Posted : 23/10/2018 6:13 am
(@john-putnam)
Posts: 2150
Noble Member Customer
 

The difference between FT & USFT is about 2ppm.?ÿ The difference depends on the coordinate system your using.?ÿ In the Portland area the difference is around 14 Ft using Oregon State Plane, North Zone but less than a foot when using the Oregon Coordinate Reference System, Portland Zone.?ÿ It all has to do with your location in reference to the grid origin of your projection.

?ÿ

 
Posted : 23/10/2018 6:13 am
(@lee-d)
Posts: 2382
Noble Member Registered
 

Specifically on a point at our office the NAD83 - ITRF difference is 2.675' Hz (1.942N, 1.84E) and 4.582' V

US feet - Int feet and feet - meters are?ÿalways easy to identify here in LA South?ÿbecause our eastings are much larger than our northings.

 
Posted : 23/10/2018 6:14 am
 ken
(@ken)
Posts: 229
Reputable Member Registered
 

I ran into this in WA state a few years ago.?ÿ Using a Topcon GR5 with Magnet on a network.?ÿ You have to be using NAD83 No Trans with it, or it's double correcting the baselines.?ÿ ?ÿThat would have been handy info to have when picking it up from Topcon!?ÿ Now I always check into a nail in my driveway that I've run static on to compare to when fussing with geoids and settings.?ÿ?ÿ

 
Posted : 23/10/2018 6:14 am
(@lee-d)
Posts: 2382
Noble Member Registered
 

As John stated above, when Trimble first put the transformation in they called it NAD83(2011) or something like that. Our VRS was already broadcasting NAD83 so if you chose that one you were double correcting. They subsequently changed?ÿthe name?ÿto ITRF - NAD83.

 
Posted : 23/10/2018 6:21 am
(@john-putnam)
Posts: 2150
Noble Member Customer
 

I would venture to say that very few people, working in the USA, on this list should be using a transformation from WGS84 to NAD83 in their collector.?ÿ For decades the manufacturers have been telling us to use enter our control as WGS84, the trouble is that with the exception of the military, our control is provided in some flavor of NAD83.?ÿ The NSRS is currently NAD83[2011 epoch2010] and I do not know of any real time networks that are broadcasting in WGS84 / ITRF.?ÿ If your WGS84 and local geodetic values are different then you should definitely check your settings.

 
Posted : 23/10/2018 7:17 am
Page 1 / 2
Share: