[aprssig] Multi control station situational awareness - How's this supposed to work?

spam8mybrain spam8mybrain at yahoo.com
Tue Dec 3 09:31:41 EST 2019

Hmmm... point-to-point dedicated-frequency TARPN links improve throughput, but add failure points unless you have redundant paths through independent stations. If one routing station goes off the air, all its links go away.And TARPN doesn't itself provide applications to share the information; it only provides a communications infrastructure.On the other hand, someone could use a TARPN-styled backbone (with redundancy) to forward APRS-style data relatively long-range, possibly cross-connected to local HamWAN-type networks.I  know of at least one APRS app that supports bulletin board display mode. But it sounds like APRS bulletin boards in general needs a slight change from the protocol specification, so that a bulletin board line can be taken over by another station, just like APRS objects can be taken over when a station goes off the air for any reason.Also, how can we attach arbitrary data to objects and bulletin board lines? For example, for an Object representing a shelter, several different pieces of real-time variable data (capacity, remaining capacity, resource shortages, etc.) should be independently updated and shared across the network.This latter sounds like an interesting extension that could be added to APRS, using no-SQL style amorphous databases at each end-node station, updated by APRS traffic, and a UI displaying each record type as a separate spreadsheet-like table.Andrew, KA2DDOauthor of YAACprofessional software engineer

-------- Original message --------
From: kk4kfg <kkf4kfg at jarsprep.net> 
Date: 12/3/19  07:10  (GMT-05:00) 
To: aprssig at lists.tapr.org 
Subject: Re: [aprssig] Multi control station situational awareness - How's
  this supposed to work? 

Seems like a perfect fit for TARPN to me.http://tarpn.net/t/packet_radio_networking.htmlOn Tue, 2019-12-03 at 02:24 +0000, Eric H. Christensen via aprssigwrote:> I second Michael's thoughts here.  Old packet systems really were> great for handling this type of information.  Nothing fancy; it just> got the job done.> > Really, what might be good in your situation is a hybrid approach.  A> list of information that is passed around via BBSs and real time> information about where supplies can be found on APRS.  Putting the> information on APRS allows everyone the ability to see what resources> are available (and where) without having to call into a net and> asking.  As one net control signs off and another signs on, they can> adopt the objects from the retiring station to keep the objects> flowing and up to date (make sure you keep the hops down).  The bulk> lists, check-ins, and other resources can be passed around on the BBS> where it's easier to make that information available in long text> form.> > Oh, and while you have the BBS up, make sure you make use of its> capabilities of handling personal messages as well!> > 73,> Eric WG3K> > _______________________________________________> aprssig mailing list> aprssig at lists.tapr.org> http://lists.tapr.org/mailman/listinfo/aprssig_lists.tapr.org_______________________________________________aprssig mailing listaprssig at lists.tapr.orghttp://lists.tapr.org/mailman/listinfo/aprssig_lists.tapr.org
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.tapr.org/pipermail/aprssig_lists.tapr.org/attachments/20191203/50e5a408/attachment.html>

More information about the aprssig mailing list