I am in the process of evaulating/puchasing a new GPS static receiver. I have observed two occupations with it, and am having a heck of a time submitting the files to OPUS.
My first task was to observe a point in my backyard using one of my Hiper units. I downloaded the data and submitted the file to OPUS. It came back with no issues.
The first submission with the new receiver was returned with the message that the files were too noisy. I have never had that error message before, so I figured that something crazy was going on, and really did not think too much about it.
The weather has been less than ideal the past week, so I have not had a chance to reoccupy the point a second time until today. I re-observed the point today with the new receiver, and when I submit to OPUS, I get the following message:
FILE: 016902_13_357_A0.13O OP1387847881964
2005 NOTE: The IGS precise and IGS rapid orbits were not available
2005 at processing time. The IGS ultra-rapid orbit was/will be used to
2005 process the data.
2005
6014 OPUS-RS cannot find three reference stations within 250 km of
6014 your position and with suitable data for use with your dataset.
6014 OPUS-RS requires at least three reference stations and is
6014 currently limited to a maximum distance of 250 km. If you wish
6014 to use reference stations more than 250 km from your rover station,
6014 you may use the User Selected Base Station feature on the OPUS
6014 Options page.
6014
6014 If your data set is recent, it is likely that data from the nearby
6014 CORS stations have not yet been uploaded to the CORS archive. You
6014 may want to try again later.
I waited about an hour after I ended the session before I submitted the file. That is the quickest I have ever submitted a file to OPUS, so it is very possible that it is too soon for OPUS to have the necessary data.
How long should I wait until submitting a static observation to OPUS after observing the files?
Thanks in advance,
Jimmy
You may have submitted both too soon. I would try resubmitting your first observation again and see if the data comes back without the noise.
Two things could be going on: too soon (you have wait 17 hours to get rapid orbit), and the noise could be a solar storm (had one this summer that gave me a couple bad opus).
Just some things a have run into, hope it helps.
Had those messages many times before. Wait and submit later.
Steve Ward Had OPUS Problems In Eastern TN Last Week
Partly due to TN CORS, but all very confusing.
Paul in PA
Steve Ward Had OPUS Problems In Eastern TN Last Week
The data from the TDOT CORS is supposedly available hourly but with my sessions from the other day I had to wait 24 hours before OPUS-RS would use any of the TN CORS or give a solution. My second session crossed GPS midnight so I had to wait 48+hours to get a solution and I still need to go back and clean the data to get a better solution.
I think if you look at the instructions on the OPUS site you will see information about timing for submitting data. My rule of thumb is to always wait just over 24 hours. The timing is not a matter of collection from CORS sites, but the timing that NGS processes the data.
I forget the exact terminology, but there are 3 levels by NGS:
IMMEDIATE - data based on ephemeris forecast
PROCESSED - data available after 24 hours after NGS processes it
REPROCESSED - data available after a couple of weeks when they have reprocessed
I know I don't have the terms right and my explanation may not be perfectly on the mark, but this is the way my simple mind remembers things.
Steve Ward
I removed satellites 13 and 23 L1 only data and resubmitted. I found out that OPUS-RS had itself filtered them out before processing and did not even count them in the observations not used.
Paul in PA
> ...you have wait 17 hours to get rapid orbit...
In fact, according to OPUS, you have to wait until 17:00 UTC the next day. That is 11am CST, which would be around 17 hours after the previous day's quitting time.