Noisy GNSS data or small time span

Aaron S

Active Member
I get the message "Noisy GNSS data or small time span" when send my base file to DPOS. I doubt it's too small of a time span, because the base file (according to the DPOS menu) is 25 MB and 5 hours long. I tried sending it to OPUS but got a similar message. I'll send the file to support, could someone check it for me?

I'd hate to have to reshoot the 13 points it's based on, it took me all day.
 

APADDEN07

Member
Got the same error today. Not a huge session, still testing t3 and LS+ trying to get our issues worked out. Session was +/- 1hr 20min, so not terribly short. In a location I use regularly at the office with no issues. Sent to support project 2020-07-27 A Test TLS+ 00998 T3 00121.
 
Support: I'm having the same issue: a long base session (almost 5 hours) in a very open site; I still get the message the the base file won't process because of 'Noisy Data' or a too short occupation time. I have sent the file to you; the Project number is : S452MK

Thanks,
 
Last edited:

Michael Stazhkov

Developer
Staff member
5PLS
Support: I'm having the same issue: a long base session (almost 5 hours) in a very open site; I still get the message the the base file won't process because of 'Noisy Data' or a too short occupation time. I have sent the file to you; the Project number is : S452MK

Thanks,
As I understood from the DPOS team it is hard to understand that we don't have CORS data yet and we just need to wait, usually there are some preliminary data on CORS ftp which can be used but cause the result with error. Usually it takes from several hours up to 1 day for CORS station to put final data on ftp.
 

Matt Johnson

Well-Known Member
5PLS
As I understood from the DPOS team it is hard to understand that we don't have CORS data yet and we just need to wait, usually there are some preliminary data on CORS ftp which can be used but cause the result with error. Usually it takes from several hours up to 1 day for CORS station to put final data on ftp.

Can the detection of this issue be improved and the error message changed to reflect that the CORS data is not available yet? I get a lot of questions about this error message.
 
I did try sending to DPOS later in the evening and it worked. In the past, I have gotten the message that the CORS data was not available so I know to wait and try later. This is the first time I got this message which led to the confusion.

Thanks.
 
Top