RINEX file will not import to TBC 5.20
The attached RINEX file was converted from Leica .M00 format (MDB) by TEQC. Have followed this procedure a few times with no problem.
For some reason this RINEX file is not recognised. “TBC cannot find a suitable input converter”
Another RINEX file downloaded from CORS imports fine, as do the almanac files TEQC produced.
I’m stumped!
Cannot attach file – can download using link. For some reason it thinks it’s an audio file and tries to play it! Just click on download in top right corner.
https://drive.google.com/file/d/1oOBhbGlXJROR-HyFVBGJSsulTkW1quab/view?usp=sharing
- 7 Replies
I downloaded it, gave it a proper RINEX file name and submitted it to OPUS-RS. NGS says it does not recognize the file, but it looks like a RINEX file to me. You might try removing the Glonass with teqc and resubmitting to OPUS-RS, but I have no time to play with it.
You do have a matching n file in the same folder, don’t you.
Paul in PA
The initial XYZ in the file indicates somewhere north of Falmouth, Cornwall, UK (and the user’s profile says England), so it is unlikely to process in OPUS regardless of format issues.
Several lines begin with -Unknown- instead of specifying something. Is that similar to your files that do process?
I’m not familiar with the formatting when there are so many satellites, but I note that many lines have something like R18R19 spilling over to a new line-is that standard?
I find it strange the antenna offsets given in the file header are 0.0000 0.0000 0.0000, thus asking for the position of the ARP and not a monument unless it is sitting directly on such monument. That shouldn’t affect processing, though, unless your software is like OPUS in not liking perfect 0.0000 height.
.
@bill93 thanks I did have the antenna height typed over the 0.000, but thought this might be the problem with import so reprocessed and tried import with an unmodfied file. You can enter the station name and antenna height when importing to TBC
yes there is an “n” file (and a “g”) that both import into TBC fine.
I notice that the file uses 2-byte (16-bit) characters, whereas my files are 8-bit characters under Win7. Is that the case with your files that do work?
.@bill93 well spotted that was it.
The encoding was UCS-2 on that file. Converted it back to UTF-8 and it worked fine.
For some reason, running TEQC in Windows Powershell produces UCS-2 files, whereas running it in the command window produces UTF-8
Heck of a catch!!!
Log in to reply.