Paul's Solution To Wrong Ashtech Dates, Not Guaranteed, But Try it.

First step, download the following link to your favorites:

http://www.gnsscalendar.com/

It is a handy GNSS calendar and utility. It will help you understand the date and filename issue. I suggest you rename each file to the standard protocol.

Next you need teqc from UNAVCO or WINteqc from Silkwerks. I will describe the steps in WINteqc.

We start with a wrongly named and dated Ashtech "B" file. Assume it is BPAULA97.104 collected on 11/28/2016.

Pick 11/28/2016 on the GNSS calendar and find the correct 2016 day of year = 333.

Open WINteqc, select "Ashtech", then "Get File", selecting "BPAULA97.104", it should show up looking like a RINEX file with date for each observation as 97 4 14.

Move down to the "Ad Hoc" window and type in "-week 1925"

Go up to the "Ouput File" window and change the file name to "PAUL3331.16O"

Hit "Execute" and that new and correct "O" file will be saved. It will also be displayed with each observation now being 16 11 28.

Now you need a new "N" file. I suggest going to the CORS ftp site, select RINEX, select 2016, and day of year 333 or by month and day Nov28.

Grab the broadcast orbit for that day "brdc3330.16n" put it in the folder with the new "O" file, unzip it and rename everything but the "n" to match the "O" file.

Convert each of your other "B" files and match the new "O" file with a copy of the "N" file.

Now you can import your RINEX data into your post processor and get a normal solution.

For whatever day you collect your data, the GNSS calendar will give you the correct day of year.

Good Luck

Paul in PA