I ran a short test session after dinner, to verify if my Z-Xtreme is having the same problems as other older Ashtech receivers.
Well at least not yet, but teqc told me it had to ignore a Leap Second error.
However I could not get an OPUS-RS solution because fewer than 3 stations were available. I decided to grab some data and check it myself. That did not work as the 6 nearest CORS did not have data available in my time period. It appears there is some GPS conspiracy as those I checked all have been turned of at 22:00 UTC or earlier for the last few days.
Paul in PA
The budget for these things could stand some improvement, but huge tax cuts for the 1% are apparently more socially desirable.
Paul in PA, post: 403343, member: 236 wrote: the 6 nearest CORS did not have data available
Do you maybe just need to wait a little longer for the data to show up? Is it usually near real time?
I have a bunch of sites with 22:00 - 24:00 data missing for at least the past three days. That missing two hours today is what I need. Typically holes in data do not get filled in. Other sites did not yet have data. I will get a solution tomorrow but no as good without the local sites.
Paul in PA
Got an OPUS-RS solution this morning and the four nearest CORS were not used.
Because there are so many surrounding CORS I quite often can get an OPUS-RS in a few hours. If I really need the data fast, I will extend my observations for an OPUS fix.
Paul in PA
I'm just nosy--does the same organization run those CORS sites?
OK Nosy Rosy,
The three closest PennDOT CORS sites have 6 days in a row of no data from 22:00-24:00 UTC. That time indicates someone is throwing the switch at 5 pm EST. The closest site LUMT is operated by Lehigh University and has no data at all for quite some time. The next closest site is in the New Jersey network and has at least seven days in a row of missing data in and around that same time of day.
Paul in PA
Is there a list of requirements, to make, and maintain a cors site?
Yes Nate, there is:
http://geodesy.noaa.gov/CORS/Establish_Operate_CORS.shtml
http://geodesy.noaa.gov/PUBS_LIB/CORS_guidelines.pdf
I'm getting impatient for the final orbits to be posted so I can run some comparisons and not want to do them over later. The JPL site https://igscb.jpl.nasa.gov/components/prods_cb.html
says "The final combinations are available at 12 days latency." That would mean 19 days if your session was in the early part of the week.
Well, it's been over thirteen days and 16 hours since week 1925 ended and the precise data still doesn't show up.
Thanks, SPM, That was what I was looking for.
N
At 15 days after the week ended, the final orbits are up.