<html><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8"></head><body>Bob,
<div><br></div><div>I could have something available for option#2 in a week or so, freely available. I've been working on this sort of usecase for some time now, but I haven't been in charge enough to deploy it.</div><div><br></div><div>And I'm still working on adding supplemental information to the reports from one-way trackers, like how many injured/exhausted bicyclists riding in a SAG vehicle.</div><div><br></div><div>Andrew, KA2DDO</div><div>author of YAAC</div><br><br>-------- Original message --------<br>From: Robert Bruninga <bruninga@usna.edu> <br>Date: 12/3/19 19:08 (GMT-05:00) <br>To: aprssig@lists.tapr.org <br>Subject: Re: [aprssig] Multi control station situational awareness - For
mobiles? or homes without power? <br><br>There sounds like two paths emerging.<br><br>- Come-as-you are with APRS radios in the mobile as the end terminal unit<br> Everybody has one<br><br>- Invent something new with PC's, clients, Pi's, displays, for use at home<br>(or front seat mobile?<br> Nobody has one<br><br><br>-----Original Message-----<br>From: aprssig <aprssig-bounces@lists.tapr.org> On Behalf Of Shawn Stoddard<br>Sent: Tuesday, December 3, 2019 7:01 PM<br>To: aprssig@lists.tapr.org<br>Subject: Re: [aprssig] Multi control station situational awareness - How's<br>this supposed to work?<br><br><br>Great sanity check. You’re thinking the same path I am.<br><br>On Tue, Dec 3, 2019, at 15:40, Greg Troxel wrote:<br>> I would urge you to step back and consider your requirements, think<br>> about the protocol that will be used at a high level, and then figure<br>> out how to use specific techniques to implement that protocol.<br>><br>> If what you want to do is publish infomration about status of<br>> particular places, then APRS probably is the best fit.<br>><br>> If you are trying to synchronize the list of checked-in stations among<br>> N NCS stations, then I think you want some sort of database sync<br>> protocol which is going to send messages among the participants, and<br>> you may or may not want to carry that over APRS.<br>><br>> I think you implied this, but from the "train like you'll fight" I<br>> would suggest using the over-the-air sync all the time, and not use any<br>> direct-to-APRS-IS internet-based injection. Gatewaying to APRS-IS is<br>> great for others to probably be able to see what's up, but I think you<br>> should plan on no internet, and thus operate that way routinely,<br>> because otherwise you are likely to be depending on it more then you<br>> think.<br>><br>> ALl of this is going to push you to protocols that are very terse and<br>> push just the data, with all formatting and UI local. This means<br>> writing a local implementation of the UI for the protocol.<br>><br>> 73 de n1dam<br>><br>><br>><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><br>_______________________________________________<br>aprssig mailing list<br>aprssig@lists.tapr.org<br>http://lists.tapr.org/mailman/listinfo/aprssig_lists.tapr.org<br></body></html>