ashtech conversion to RINEX with teqc
Posted By john Hamilton on 12/27/2001 at 2:05 PM

I am using teqc from UNAVCO to batch convert a few hundred files from Ashtech download format (i.e. B-file, E-file, S-file).

The files all seem to convert OK, but when I import into TGO, many of them do not import correctly. For example, day 019 of 2001, I have 8 files. Three files imported OK. The rest had error messages like:
"Could not find two records with at least 5 SVs in RINEX file", and "Unable to locate User Position: C:\projects\01122\data\019\B0043a01.01o"

I don't see anything wrong with the rinex files that fail to import.

Are there other Ashtech rinex converters that can be run from the command line (so I can create a batch file)?

I do have ashtorin, but it is an interactive program.

Thanks, john



Re: ashtech conversion to RINEX with teqc
Posted By Brian D. Ewing, PLS on 12/28/2001 at 9:34 PM

John, this sounds like a f/w vs s/w version incompatibility. You might try the Berne rinex converters instead of the UNAVCO. I don't have the URL handy.




Re: ashtech conversion to RINEX with teqc
Posted By john Hamilton on 12/29/2001 at 6:56 PM

Thanks, Brian. I had thought about that, but have never used the Berne converter.

I wound up having to do them all (about 400) by hand in ashtorin. The one good thing is that I was able to put in the operator initials, receiver sn, and antenna sn (it's for a bb project, so I need all that).



Re: ashtech conversion to RINEX with teqc
Posted By Don Mulcare on 12/30/2001 at 11:13 AM

If you are sure that the problem is not with the ability of your software to deal with a correctly formatted RINEX file, I hope you'll report your teqc problem to Lou Estey at UNAVCO:

http://www.unavco.ucar.edu/data_support/software/teqc/contact.html



Re: ashtech conversion to RINEX with teqc
Posted By john Hamilton on 12/31/2001 at 1:35 PM

Well, Don, I wouldn't say it's NOT the software's fault. I am using TGO 1.5, and I know there have been some issues in the past. Trimble recently released a .dll that was supposed to fix that problem.

Although I haven't contacted Trimble, I can see the conversation:
Trimble: you are using a third party program to convert another manufacturer's data file, is that correct?
Me: that's right
Trimble: Sorry, we can't support that!

Once I used ashtorin, the data imported just fine. So, maybe I will try the unavco route, and send them a file. To me, though, the files look OK.