<html><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8"></head><body>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.<div><br></div><div>And TARPN doesn't itself provide applications to share the information; it only provides a communications infrastructure.</div><div><br></div><div>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.</div><div><br></div><div>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.</div><div><br></div><div>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.</div><div><br></div><div>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.</div><div><br></div><div>Andrew, KA2DDO</div><div>author of YAAC</div><div>professional software engineer</div><br><br>-------- Original message --------<br>From: kk4kfg <kkf4kfg@jarsprep.net> <br>Date: 12/3/19 07:10 (GMT-05:00) <br>To: aprssig@lists.tapr.org <br>Subject: Re: [aprssig] Multi control station situational awareness - How's
this supposed to work? <br><br>Seems like a perfect fit for TARPN to me.<br><br><br>http://tarpn.net/t/packet_radio_networking.html<br><br><br><br>On Tue, 2019-12-03 at 02:24 +0000, Eric H. Christensen via aprssig<br>wrote:<br>> I second Michael's thoughts here. Old packet systems really were<br>> great for handling this type of information. Nothing fancy; it just<br>> got the job done.<br>> <br>> Really, what might be good in your situation is a hybrid approach. A<br>> list of information that is passed around via BBSs and real time<br>> information about where supplies can be found on APRS. Putting the<br>> information on APRS allows everyone the ability to see what resources<br>> are available (and where) without having to call into a net and<br>> asking. As one net control signs off and another signs on, they can<br>> adopt the objects from the retiring station to keep the objects<br>> flowing and up to date (make sure you keep the hops down). The bulk<br>> lists, check-ins, and other resources can be passed around on the BBS<br>> where it's easier to make that information available in long text<br>> form.<br>> <br>> Oh, and while you have the BBS up, make sure you make use of its<br>> capabilities of handling personal messages as well!<br>> <br>> 73,<br>> Eric WG3K<br>> <br>> _______________________________________________<br>> aprssig mailing list<br>> aprssig@lists.tapr.org<br>> http://lists.tapr.org/mailman/listinfo/aprssig_lists.tapr.org<br><br><br>_______________________________________________<br>aprssig mailing list<br>aprssig@lists.tapr.org<br>http://lists.tapr.org/mailman/listinfo/aprssig_lists.tapr.org<br></body></html>