West Coast CORS Problem?

Looks like OPUS is down, at least as of this morning:

No green "completed" section at all, just "failed" and "waiting"...

Yeah, I just tried to resubmit the file and got the rejection notice that it's still in the queue.

Yesterday I submitted the same file (well, the one from which the RINEX file was derived) to Javad's DPOS tool and got a solution within a few minutes.?ÿ The Javad server was able to get data from 2 nearby PBO stations that NGS doesn't show, so it may be a problem with the NGS ftp site.

Are theses stations in areas with power outages? The stations themselves should have backup power, but if local internet is down the data is not going anywhere. Once it does not go automatically it usually requires human intervention and action. I would also surmise a lot of West Coast people are being paid not to be at work, so there may be no humans available to intervene on a timely basis.

If you are just looking to verify your data, pick some CORS 1,000 miles away in 3 directions. Way back when I played around a lot I got L1 only solutions (+/- 1') in my post processor from CORS a 1,000 miles away. L1/L2 should get you within +/- 0.1'.

Pauil in PA

Curious, do earthquakes and/or tremors effect CA CORS? Do they hit the "pause" button to assess if they moved??ÿ

I still don't know what the problem was, but a backup of submitted files appears to have been at least part of it.?ÿ OPUS is working normally now.

?ÿ

Posted by: @stlsurveyor

Curious, do earthquakes and/or tremors effect CA CORS? Do they hit the "pause" button to assess if they moved??ÿ

My understanding is that they're monitored and positions are updated when they pass a certain threshold.

Maybe affected by the fires Jim??ÿ I mean you are in the heart of it all.

Posted by: @jim-frame

My understanding is that they're monitored and positions are updated when they pass a certain threshold.

That is what has been stated, but actual practice shows otherwise. Not earthquake related, but take a look at the datasheet for P565, specifically the ellipsoid height. By 2015 it was approximately 25 cm lower than the published 2010.00 eh. It bottomed about 29 cm lower, then rebounded some. The currently published eh was "corrected" when the NGS pushed out the MYCS2 positions late last year. Look at the superseded data to compare ellipsoid heights. There is about a 23 cm difference.

https://www.ngs.noaa.gov/cgi-bin/ds_cors.prl?CorsSelected=|P565&CorsTypeSelected=Arp

That said, I have heard NGS state they need to improve in their CORS monitoring and updating positions as quickly as possible after events, such as earthquakes. The CSRC put out epoch 2019.55 positions for the stations (CORS and other CGPS stations) displaced by the Ridgecrest earthquakes in July of 2019 just a couple of months after the events, once the post-seismic movement settled down. An example of why the CSRC exists in California to augment the services of the NGS in a state that requires A LOT of positional maintenance.

?ÿ

@ric-moore?ÿ Alas, 'tis true.?ÿ That's why I felt it necessary to wear an N95 mask on a 95?øF day while doing this:

I found 2 T-posts and (finally!) a 2" pipe 3 feet down.?ÿ The T-posts made the Schonestedt nearly worthless, thus the extent of the dig.

?ÿ