I updated my TSC7 yesterday about 3pm. And the update made all of my coordinates off about?ÿ0.177?ÿsouth &?ÿ0.033?ÿwest elevation?ÿ0.008 high. It differs a little bit from point to point. This has me scratching my head as to why this is happening. So I'm going to go out and shoot 12 control points through out the City to see how well they land. Then check OPUS and compare data. I don't know what else to do. Any ideas would be helpful. I'm using Oklahoma North 3501 United States NAD83 GEOID12B (Conus) if this helps.?ÿThanks in advance.?ÿ
Older versions of Access had a simple transformation from ITRF2014 to NAD83 (2011). The mismatch of this transformation increased as one went from east to west across the US. My solution was to transform the ITRF2014 coordinates using HTDP in the office after the survey (I didn't need real time).
The version of Access released last year uses the HTDP (NGS program Horizontal Time Dependent Positioning) model, which is "more correct". This affects the horizontal component, not the vertical. This is a more complicated transformation which takes into account plate tectonics, location, earthquakes, etc.?ÿ
Using the updated version should match NAD83(2011) epoch 2010.0 (HARN/CORS/etc) more closely. But it will show a difference versus positions determined using the "pre-HTDP" transformation.?ÿ?ÿ
As far as it varying slightly, of course it will, that is the uncertainty in the RTX solution.?ÿ
?ÿ
Do you have a new rod? Have you checked the bubble on it lately? How often have you checked into these points previously before they?changed?? Do you have an R12i ?ÿ With a rod that is off? Have you shot them facing multiple different directions to verify it??s not the rod? ?ÿConsidering it??s GPS, 0.18?? isn??t great, but 0.03?? and .008?? is pretty negligible. ?ÿInteresting for sure though. ?ÿI only ran a trial of RTX so my experience with it is limited. ?ÿWill follow this thread though to see what comes of it. Best of luck resolving the issue!
@john-hamilton Yes sir, you are correct. That is what I was using before the upgrade. So are you saying that I can use the "Untied States/State Plane 1983" local datum NAD83(Conus) (Mol) Global Ref datum NAD83(2011) instead of using "United States/ITRF to NAD83" local datum ITRF to NAD1983 (2011) (7p) global Ref datum WGS 1984? And if so that would also mean that I would have to change all of my previous jobs to "Untied States/State Plane 1983" instead of "United States/ITRF to NAD83".
@absurveyor18548 The rod is about 6 months old. It was checked last week and my guys are saying that they had about a 1/16 on the bubble. I have a surveyor that has a primary job of checking control points from one side of the city to the other. Then bring in the Ground Control Reports every time the city is finished.?ÿ
This is what you want to see when you're setting up a project:
@member_of_the_patriot_fam Not sure about exactly what each is called, but you could try it. I believe everything is stored as ITRF, and when you pick a transformation it applies it to the displayed/downloaded coordinates. So it should work if you can get the correct transformation set.?ÿ
?ÿ
As Rover83 shows, the setup page should show whether HTDP is being used or not.?ÿ
?ÿ
I should add (repeat) that using HTDP gets you closer to NAD83 (2011). But, if you are trying to match previous work you might want to keep the old transformation.?ÿ
I just ended up finishing the old jobs in the old 2020.11. Then starting new jobs in 2021.11. Thank you guys! ???? ?ÿ
