I've been using the RinexDates program to revise the dates in the rinex files and until monday this had been working without a hitch. On monday, when processing rinex files from our receivers and from NGS CORS, when queryed in TGO, the base lines from our receivers showed the revised date of 05 11 11, but the date for the base lines from the CORS stations were a week ahead (05 18 11). In the rinex files the revised dates appeared correct (05 11 11) in most places, the start and end times were shown as this years date. For some reason TGO is having difficulty with something and advancing the date of observation for the CORS files one week into the future from the receivers date. ??????
If I recall, RinexDates requires that the data within the file is from a single GPS day, ie no observations past midnight Greenwich. I suspect that your CORS data encroaches this limit. In the western US and Canada we often see files that cross midnight Greenwich.
The workaround is to examine the date/time stamps in the RINEX files and remove the records past that time.
Your files were collected on Saturday so data past midnight would result in results referenced to the next GPS week.
Of course this is a wild ass guess on my part...
Scott
Christof and I have been working with Jeff to try to solve his problem. We have a new version of Rinex dates now and we have successfully converted Jeff's files. I have loaded the converted files into TGO and processed the data but Jeff is having problems with his copy of TGO not working correctly.
I think Wendell will have the new version posted soon, assuming Christof has sent it to him.
