I had 20 + hours static only needed a few hours but it was in a safe location so i just left till I had time to retrieve it.?ÿ When i submitted the .dat file it to OPUS i get?ÿ"1014 searching for "MARKER". OPUS will only process data taken from one............".?ÿ I used the trimlbe convert to rinex and i uploaded the file to OPUS and it processed the data.?ÿ ?ÿ
My question - does the Trimble Convert to RINEX clean up the data? I have no idea how to cut the data and process it in sections.?ÿ
Trimble converter just converts Trimble format files to RINEX, nothing more. You'd need to get familiar with a different set of tools.?ÿTEQC is what I use for parsing and cleaning up data.?ÿ There's a windows based GUI for it that makes it a bit more friendly to use. Works slick, but there is a learning curve.?ÿ?ÿIf you get stuck I can try and help you out. Good luck.
Trimble converter just converts Trimble format files to RINEX, nothing more. You'd need to get familiar with a different set of tools.?ÿTEQC is what I use for parsing and cleaning up data.?ÿ There's a windows based GUI for it that makes it a bit more friendly to use. Works slick, but there is a learning curve.?ÿ?ÿIf you get stuck I can try and help you out. Good luck.
I use teqc, but it functions the same as the trimble utility.?ÿ
?ÿ
Use a text editor (not MS word) to remove comment lines or other non-observation lines from anywhere past the header lines. For example, here are some lines near the end of a trimble .dat file....
?ÿ
I wish they would change OPUS to ignore this. I have files where there are comment lines at the very end of the file (nothing after them), and it of course rejects the file.?ÿ
?ÿ
?ÿ
I search for "COMMENT".?ÿ The lines above the highlighted area are the previous epoch data for two satellites, and the lines below are a new epoch. In this case I delete the highlighted lines and it runs fine in OPUS. There can be none, one, or multiple comment lines after the header lines.
It is probably a good idea to download the rinex specs and learn how the file is structured, it is simple ascii.?ÿ?ÿ
I use teqc, but it functions the same as the trimble utility.?ÿ
?ÿ
Use a text editor (not MS word) to remove comment lines or other non-observation lines from anywhere past the header lines. For example, here are some lines near the end of a trimble .dat file....
?ÿ
I wish they would change OPUS to ignore this. I have files where there are comment lines at the very end of the file (nothing after them), and it of course rejects the file.?ÿ
?ÿ
?ÿ
I search for "COMMENT".?ÿ The lines above the highlighted area are the previous epoch data for two satellites, and the lines below are a new epoch. In this case I delete the highlighted lines and it runs fine in OPUS. There can be none, one, or multiple comment lines after the header lines.
It is probably a good idea to download the rinex specs and learn how the file is structured, it is simple ascii.?ÿ?ÿ
John,
I doubt that the Comment line is the problem, it is the line with "YYYY MM DD Time" that indicate it is followed by data is the more probable problem. I would also expect OPUS should reject you for the L1 only data.
Interesting.?ÿ They advertise that you are allowed ONE crossing of 2400 UTC in a file, and otherwise no upper length limits. Is there anything else unusual in that file?
This isn't the time of year for leap seconds, which do mess things up for a session around 2400.
