Changeset 1117 in ntrip for trunk


Ignore:
Timestamp:
Sep 12, 2008, 8:04:02 PM (16 years ago)
Author:
weber
Message:

* empty log message *

File:
1 edited

Legend:

Unmodified
Added
Removed
  • trunk/BNC/todo.txt

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