Opus is rejecting my submissions with the following error:
" The file contains data that is very noisy and probably has many data gaps."
My raw data was captured using a U-blox ZED module and used RTKLIB to convert to RINEX.
Will appreciate your help.
?ÿ
Thank you,?ÿ
Did your GNSS receiver antenna have a clear view of open sky?
Since you are an RTKLIB user, did you use RTKPLOT to examine your file for data gaps?
OPUS only uses GPS satellites, so the state of the GPS constellation is important. Did you check the almanac to see how many GPS satellites would be visible before you gathered the data?
Ublox chips are notorious for not recording data on even seconds. Instead of recording data on, say, second 15.000 they often record data on 15.005 for example. RTKLCONV has an option to align the times of the observations to even seconds. RTKLIBEXPLORER has a blog article about this.
Did you wait a day or two before submitting to OPUS? This often helps
OPUS only uses data for every 30 seconds, that is it wants observations at 0.000 and 30.000 If you’re submitting much more than that to OPUS you’re just slowing down the process of uploading and getting rejected.
Did you try the Canadian or Australia positioning services?
All of the above are well-documented in either the NGS webinars on using OPUS and/or by users and manufacturers of gear using the ublox chips. There’s lots of info out there.
I have had some issues lately this past week. Same file gets rejected wait a day send it and comes back fine. I had 3 different files this past week do the same exact thing and i just kept resending and finally it ran it through. On one I ended up re converting to rinex from original t04 file. I also have seen some messages when the crew logs as a rober bs base. I looked into it and on trimble side I believe it adds a message thats a ppk fix or something that opus rejects. So I alway tell them to log as a base. Not to say you’re having same issue but if at first you don’t succeed try try again.
