It took me awhile to verify but this is per the RINEX 3.01 specifications.
"5.2 Satellite system-dependent list of observables"
"The order of the observations stored per epoch and satellite in the observation records is given by a list of observation codes in a header record. As the types of the observations actually generated by a receiver may heavily depend on the satellite system RINEX Version 3 requests system-dependent observation code list
(header record type SYS / # / OBS TYPES)."
So I took a better look at the snippet of file Mike Moran send me.
Observables are indeed reported in the header.
(header record type SYS / # / OBS TYPES) is in the form of
"G 8 C1C L1C D1C S1C C2W L2W D2W S2W SYS / # / OBS TYPES"
"G" for GPS is new, 8 is expected, following that are new codes for RINEX 3.01
the C after the first 4 indicates C/A code, the W after the last 4 indicates "Z-Tracking" or similar, and there are other posiible identifiers and it is very confusing.
OPUS would have expected to see in RINEX 2
"8 C1 (or P1) L1 D1 S1 P2 L2 D2 S2 SYS / # / OBS TYPES"
After each epoch date/time in the observations OPUS would be looking for the satellite list
RINEX 2 " 8 G31G23G32G20G29G06G27G16"
however in RINEX 3.01 there is simply "8 "
G31 precedes the first line of observation
G23 precedes the next line, etc. in Mike Moran's file it looks like this:
> 2013 07 11 14 36 25.0000000 0 8
G31 21979879.320 115505044.78608 -1967.871 47.750 21979879.700 90003932.90807 -1533.410 42.250
G23 21967099.340 115437885.85008 2689.238 48.000 21967098.520 89951596.03506 2095.508 39.250
G31 and G23 are each one line of data, word processors wrap it around but there is no carriage return within the line.
Version 3.01 is expecting submission of observations from multiple systems, so each epoch may have up to 5 satellite system types, plussatellite numbers.
satellite system identifier
G : GPS
R : GLONASS
S : SBAS payload
E : Galileo
C : Compass
Is there anyone on this board currently doing such multisystem processing?
Paul in PA
I don't have the new version of LGO, but wondering if there is an option to write 2.x RINEX still to get around this issue until OPUS can read 3.x RINEX?
SHG
Yes, it will write 2.11.
Does anyone know if and when NGS would switch. I believe the option is more for international or other than OPUS.
Would they rewrite PAGES and RSGPS or would it be easier to create an OPUS+ option.
I imagine it would be a long time and tons of money to upgrade 1,000+ OPUS receivers for GLONASS, full constellation now, and Galileo, GPS L2C and L5 sometime in the future.
It is my understanding that current receivers could receive L1 SBAS (WAAS) signals now and it is simply a receiver firmware upgrade. One of the big bonuses with L5 is that new WAAS will be L1/L5 capable allowing more precise ranging.
Paul in PA
Paul I posted a reply on this issue that cam up last week...
http://beerleg.com/index.php?mode=thread&id=215337
I think you hit one thing on the head in that NGS has limited funding. I am sure they have looked at this but I have heard a few NGS presentations lately and it seems they have allot of good things they want to work on but are limited in manpower and funding... which is a shame.
Just in case anyone reviewing this post needs to know the specifics in LGO to export ver 2.11 RINEX files...
OPUS will not except the new RINEX 3.01. So in the Export to RINEX when sending to OPUS only choose the ... Rinex files (version 2.11)option in the Save as type: field...
The other option you need to pay attention to is the option to export GPS Only or All GNSS observables. OPUS will only accept GPS. So in the GNSS Type filed only choose - GPS L1+L2 only
