One way to do this is to check each call/grid against the last call/grid. If
the grid changes it must be mobile. And I've not seen anybody doing ground
mobile JT65/JT9 (yet). Even if that starts if would be so infrequent as to not
be a big deal on the server load I would think.
Keeping a hash list of them shouldn't take a whole lot of memory and don't need
to save anything. The reporting side has already been written for 1.6.0.
I could do this if I can be assured the patch would be accepted. I need a
project right now that would be accepted since I'm a touch frustrated my last
couple patches were rejected.
RRRMike W9MDB
From: Bill Somerville <g4...@classdesign.com>
To: wsjt-devel@lists.sourceforge.net
Sent: Tuesday, January 5, 2016 9:24 AM
Subject: Re: [wsjt-devel] Feature Request, JT9 to SNUS
On 05/01/2016 15:19, Michael Black wrote:
> Then that would sounds like a cooperative project with them providing
> an accessible list of active platforms that could be automatically
> updated.
> Betchya' they might go for that since it would improve their coverage.
Indeed, something like a little JSON file available from an HTTP URL on
their server that contained a list of all registered active "vehicles"
could be used to filter spots at source. This is assuming that there is
not already some easy way of identifying them from the data received.
73
Bill
G4WJS.
------------------------------------------------------------------------------
_______________________________________________
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel
------------------------------------------------------------------------------
_______________________________________________
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel
