For the last month or so OPUS has been routinely talking over an hour to return results. This for data collected days to weeks earlier. What say you?
I say RTX
It has been slow for sure. I submitted a 2hr file this morning. It was a while before I got the results back. Over an hour. I had to switch gears and work on a different project while I was waiting. RTX is a decent option. I use it a lot almost every time I submit to OPUS I submit the same file to RTX just as a Check and keep up with differences which so far have been so small it would not matter. I do this also as a precaution if govt shuts down or I have to get something turned around very quickly and OPUS is being fussy.
Not only slow today, but also failing files that shouldn't fail.
If you use the NAD83 (2011) epoch 2010.0 coordinate returned by RTX it is not entirely correct because it is not accounting for time dependency (i.e. slow drift of the NA plate). If you want it to match OPUS you should run the ITRF2020 coordinate through HTDP using the correct epoch date for the ITRF coordinate and 2010.0 as the epoch for the output NAD83 (2011). Not a big deal, I have automated this process so no matter how many RTX solutions I have it is a simple process.
The difference is small on the east coast but gets larger as you go west.
Unless of course Trimble "fixed" that issue. I have not checked it for a few years, I just automatically use the ITRF coordinate and HTDP. That will get you within millimeters of OPUS, which processes in ITRF and then uses HTDP.
Note that if you are using RTX real time with trimble access it DOES use HTDP.
@john-hamilton Thats good to know. I have only seen a small difference here in va so far. About.02 .03 ft direct distance. But I will go back on a slow day and run it the other way and use hdtp and such. Be something else I can add to my spreadsheet lol. When I am using OPUS and not doing a full static to establish control it’s usually just to get close to a NSRS tie and everything else is relative. I usually do throw OPUS in a project just give the same point a different name as a way to look around the site and catch any dumb blunder i did etc.
Unless of course Trimble “fixed” that issue. I have not checked it for a few years, I just automatically use the ITRF coordinate and HTDP. That will get you within millimeters of OPUS, which processes in ITRF and then uses HTDP.
Trimble kinda-sorta "fixed" the problem...the website still does not use HTDP, but TBC will apply HTDP under the hood if you submit directly through the program (Send to RTX-PP tool on Survey tab) and pull the solution in as a GNSS Position (happens automatically).
You must, of course, have an NAD83(2011) system set up for it to apply HTDP.
I still like having the report, so I tend to submit and transform like John, but all of our employees who use it report seeing the same mm-level consistency between it and OPUS.
@rover83 That is how I have been doing it. I just started out doing it to see have yet to hold the Trimble value but has been a good quick check. Most of the time I am always logging data when we set up a base and its just a easy way to make sure i have not done something dumb as I learn these fancy off the shelf tools lol.
Do you mean 2 to 3mm? That's the type of "error" I might see between RTX and OPUS. I don't ever look at coordinates however, I only look at lat, long. numbers.
