And I have not gotten back any solutions. It has been a while since I last GPSed, have I missed something?
Paul in PA
I just got back two solutions for the same file, one from GODZ which NGS says does not exist, 1 CORS in Connecticut and 1 Massachusetts DOT. The second solution used 2 Ohio DOT CORS and a different MassDOT CORS. The solutions appear agreeable and usable but what gives? I will check my raw location coordinates to see if that began the problem.
Just got a third solution back, 2 accepatble PA CORS and 1 NYDOT CORS, getting closer to home. I can give the CORS a day to get in all the data. My raw data position was OK and for this project I just need to om my ortho photo. Done for today!
Paul in PA
Just a happy update. Last night I meaned 2 OPUS solutions from CORS 200-380 miles away. Today I got results from my local CORS 25-35 miles away. Northing did not really change, Easting changed by 0.01' and Ortho height changed by 0.06'. Is not OPUS an amazing tool?
"OPUS Today" has good color to boot.?ÿ
Paul in PA
I think you submitted too early. Some CORS data is tardy by 10-12 hrs. I often get solutions from just couple of CORS from far away, at 2-3 hrs UTC. But, a few hrs layer and I get solutions from a much more expected array.?ÿ
I think it was just offline that day, and the 15th as, I too had issues with submissions and they seemed to clear up by the 17th (Sat) when I tried again.?ÿ Used NRCan as my temp solution.?ÿ?ÿ I also notice it is not using various IGS CORS stations (and therefore providing solutions) for locations near those stations that are outside of the US, perhaps there is a change in policy in that regard and I missed the memo.?ÿ It still claims it will just auto-default to rapid-static when needed (if your data is too fresh), but I have not tested that further.
