1. Real-Time Working Group
Progress on recommendations made at the 2016 IGS workshop in Sydney, Australia
Presented to the IGS Governing Board and Associate Members on 11 December 2016

2. IGS RTS: general remarks
Availability is good: no outages in 2016
GLONASS ephemeris issues under consideration, corrupt old GLONASS ephemeris  large orbit errors, clocks look allright
GPS Block IIF orbit problems become very frequent (e.g. G24 and G30 in last three weeks)
Block IIF problem: might be related to solar pressure problems and attitude problems

3. IGS RTS: GPS performance

4. IGS RTS: GLONASS performance

5. IGS RTS: PPP performance (G+R)
PPP using IGS03 combined solution: cold start
PPP using IGS03 combined solution: warm start

6. <additional information about the session or workshop here>
Work to provide  validated real-time navigation message streams for: GPS,  GLONASS, Galileo, BeiDou and QZSS   Communicate with station operators and encourage them to adopt MSM type 7 types (also meta data types and output frequency)   Review and optimize the observation and correction data collection and distribution caster architecture to optimize performance and improve redundancy   Work with RT-ACC and RT-ACs to reduce combination latency from ~25 seconds to less than 10 seconds   Support the new IGMA constellation monitoring project
Axel Rülke
Real-Time Splinter Session Summary Recommendations
<additional information about the session or workshop here>

7. Progress since Sydney More receiver generated MSM messages available
Separate navigation streams for each constellation available
Some progress with regional RT data centers
Optimization of processed network in order to reduce latency is ongoing at BKG
New analysis software installed at BKG, which will allow 4G analyses in future (intensive testing ongoing)
Progress with 4G RT processing at GFZ AC  second MGNSS AC (in addition to CNES)

8. Progress since Sydney Progress at ESOC AC:
Updated orbit determination software for generating hourly predictions, with a significant improvement in orbit accuracy
Modified the ESOC2 solution so that it no longer uses the IGS rapids but computes an orbit solution every hour based on RINEX files generated from the Real Time streams
The ESOC2 solution now includes RT stations from the JPL network, obtained from the CDDIS caster. A latency issue with these stations has been resolved very quickly after it was highlighted.
Bug fixes and software enhancements have resulted in clock solution improvements

9. Receiver generated MSM obs.
Still not many stations which provide receiver generated MSM observations
But, there are some exceptions which could be included:
Australia
New Zealand
Brazil

10. Receiver generated MSM obs.
Australia
New Zealand
Brazil

11. Caster infrastructure
Regional RT networks grow rapidly (e.g. Australia 70 RT stations, Brazil, …)
Central IGS RT casters at BKG, IGS CB cannot host all those datastreams  global casters should focus on a global network for global products
Regional data centers become more and more important
Regional RT datacenters proposed for
Australia (Geoscience Australia), established soon
China (Wuhan University, established), additional DC at SHAO planned
North America
South America
Important: Primary RT source of a data stream should be listed in the station log

12. Usage at BKG casters

13. Multi GNSS processing at AC GFZ

14. Multi GNSS processing at AC GFZ

15. Multi GNSS RT PPP at GFZ: GREC vs. G

16. Future Work Concept for consistent mount point naming
Based on RINEX3 naming format (9 char names)
Coordination with regional networks needed (e.g. EUREF)
Validated RT navigation messages needed
Encouraging colleagues at SHAO to establish a RT DC
Complete set of global SSR corrections for all constellations
Limitating factor: standardization within RTCM, almost no progress within 2016
Software development for combination of SSR AR solutions at NRCan (see presentation by Ken MacLeod)

17. Contact: Axel Rülke axel.ruelke@bkg.bund.de
Thank You
Contact:
Axel Rülke