Changeset 1117 in ntrip

Timestamp:

Sep 12, 2008, 8:04:02 PM (16 years ago)

Author:

weber

Message:

* empty log message *

File:

• trunk/BNC/todo.txt (modified) (1 diff)

trunk/BNC/todo.txt

@@ -1 +1 @@
 BNS 
 =========================
-(*) Allow dummy clock values 999999.999999 coming from RTNet
+(*) DLR started (and unfortunately meanwhile stopped) sending 30sec
+SP3 in realtime to euref-ip.bkg.bund.de:7777. Andre Hauschild promised
+to restart sending SP3 again after the upcoming ION once he is back in Germany.
+
+(*) Allow dummy clock values 999999.999999 as input?
 Reason: DLR real-time engine (Oliver Montenbruck) uses dummies.
+The general question behind this is: Could it be done that the
+input for BNS(from RTNet) is more closely coming in SP3 format?
+The differences to SP3 we have today are just the 999999.999999
+and the 2i/3i integers for orbit and clock corrections.
+However, this touches RTNet's output.
 
 (*) How about clocks and orbits coming in sampling rates .ne. 1sec? 
 Does it make sense to support i.e. 3sec/5sec/10sec?
 Reason: DRL provides clocks and orbits with 30sec sampling.
-
-(*) DLR started (and unfortunately meanwhile stopped) sending 30sec
-SP3 in realtime to euref-ip.bkg.bund.de:7777. Andre Hauschild promised
-to restart sending SP3 again after the upcoming ION once he is back in Germany.
 
 (*) Outlier in orbit corrections, concerning only GLONASS.