This might have been covered before, but I can't find anything here, so my question is I'm trying to import rinex "o" files from a Hemisphere 321+ receiver into gnss solutions to process but get a message "invalid raw data file". Help.
?ÿ
Do you have a companion "n" file? If not create one by using another "n" from that day and match the name except use ".n" instead of ".o". If you do not have one from other observations go to NGS.NOAA.GOV/CORS find data products, RINEX pick the day and download a broadcast.n file, unzip and change the name. Put in the same folder as the "o" and GNSS Solutions will find and use it.
If you send me the "o" file I give you an opinion if it is something else, which may require "teqc" filtering.
Paul in PA
just sent you the files
No joy. Getting the same comment and not seeing anything wrong in file. I ran the file through teqc to remove the Glonass and teqc made no complaints. I also tried it in Ashtech Solutions, and it created all the Ashtech files but would not open the file as useable???
Paul in PA
ok thanks for trying
?ÿ
It has been my experience that once you import the 2nd file into GNSS Solutions, if the file was collected after the GLO Week Number Roll Over (earlier in 2019) that GNSS Solutions will crash. And there is not much you can do about it.
So you may be on a road to nothing...
Yep, one raw data file at a time. Do you have GNSS Solutions Rinex Converter 4.7.2?
I imported it into GNSS Solutions this morning. I downloaded NCNA CORS and opened it first, then closed GNSS Solutions. I found this to be neccessary with Ashtech Solutions last year as you are now able to open or download only 1 file a session. (I recently found out I could download multiple observations from 1 receiver before it locked up, but lately I have been doing fewer multiple sessions.) Reopen the last project I worked on and loaded NCWR CORS to make sure GNSS Solutions was working. Closed it a second time. I made sure I used the newer RINEX converter on your chip file and when I imported the "b" file I got a different message. Then I checked out my project folder and found the "e" file empty, copied one of the CORS "e" files and renamed it to Echipa20.031 and "voila" it woeks.
Paul in PA
Mark, if you close Solutions and reopen it, you can import a second file, Close and reopen until yu import them all. It is slow and painful but it works.
Paul in PA
I imported it into GNSS Solutions this morning. I downloaded NCNA CORS and opened it first, then closed GNSS Solutions. I found this to be necessary with Ashtech Solutions last year as you are now able to open or download only 1 file a session. (I recently found out I could download multiple observations from 1 receiver before it locked up, but lately I have been doing fewer multiple sessions.) Reopen the last project I worked on and loaded NCWR CORS to make sure GNSS Solutions was working. Closed it a second time. I made sure I used the newer RINEX converter on your chip file and when I imported the "b" file I got a different message. Then I checked out my project folder and found the "e" file empty, copied one of the CORS "e" files and renamed it to Echipa20.031 and "voila" it works.
Paul in PA
?ÿ
