diff options
| author | Eric S. Raymond <esr@thyrsus.com> | 2011-09-01 16:27:06 -0400 |
|---|---|---|
| committer | Eric S. Raymond <esr@thyrsus.com> | 2011-09-01 16:27:06 -0400 |
| commit | b1bdc105ad28d582fdb746c403220dd78a1b1a3f (patch) | |
| tree | f23c48d7f4d74dbf3e27094782f388cc4d0a6df8 /TODO | |
| parent | ec7fa97c1ab8c46076ab6057a9b4fc8eedcbad77 (diff) | |
| download | gpsd-b1bdc105ad28d582fdb746c403220dd78a1b1a3f.tar.gz | |
Update NEWS and TODO lists for current reality.
Diffstat (limited to 'TODO')
| -rw-r--r-- | TODO | 15 |
1 files changed, 3 insertions, 12 deletions
@@ -32,8 +32,9 @@ different types in them, and a copy of the RTCM3 standard at latest revision **** Reporting code for specialized Type 6 and 8 AIS messages. -This one is mine and Kurt Schwehr's. Support is currently nearly complete -but untested. +This one is mine and Kurt Schwehr's. Support is currently nearly +complete; the only missing cases are a handful of IMO 236 and IMO 289 +message 6 and 8 subtypes. ** Ports @@ -145,16 +146,6 @@ required, and it is actually in use in production reference networks. RT-IGS is also a packet-oriented format, rather than a file-oriented format like RINEX. -*** RTCM3 support. - -Previous plans for more RTCM2 support seem to have been overtaken by -events, e.g. the world moving to RTCM3. We have support for analyzing -RTCM3 messages, but it's entirely theoretical - written from the -standard. We need to find a pair of files consisting of a -representative set of RTCM3 sentences and some sort of ASCII dump of -them so we can test whether our analyzer gets all the bitfield -boundaries right. - ** Future features (?) *** NOFLOAT build |