diff options
author | Eric S. Raymond <esr@thyrsus.com> | 2014-08-26 23:22:41 -0400 |
---|---|---|
committer | Eric S. Raymond <esr@thyrsus.com> | 2014-08-26 23:22:41 -0400 |
commit | 9c7341388346083bbb1bb1047246e9fc345c1c42 (patch) | |
tree | cae62187c87e35fa41dd9bbdb6225dbf14196c18 /TODO | |
parent | 6a33950efc638738f23698e703ea67adb85705cc (diff) | |
download | gpsd-9c7341388346083bbb1bb1047246e9fc345c1c42.tar.gz |
Add a feature request.
Diffstat (limited to 'TODO')
-rw-r--r-- | TODO | 15 |
1 files changed, 15 insertions, 0 deletions
@@ -37,6 +37,21 @@ confidence measure at a high level. We'd use the confidence level to control (a) whether gpsd ships to NTP, and (b) how it sets time uncertainty in output JSON. +*** Optionally use tag blocks in NMEA output + +Ed W. writes: +>Feature request: I would like to see an option to get the NMEA data +>out of gpsd, but augmented with a timestamp on each sentence and +>details of which input fed in the data. TAG blocks appear to solve +>that problem perfectly. So the feature request is simply an option +>that inserts a TAG block for each emitted sentence from GPSd with a +>timestamp and some handle which references the input method for the +>sentence. +> +>I think all this is effectively emitted with the JSON output (?), so +>really this is just adding it to the NMEA sentence output options via +>the TAG structure + *** RFC2783 bugs **** detangle TIOCMIWAIT and RFC2783 |