[aprssig] WIDE2-1 vs WIDE1-1,WIDE2-1 was WB2PAY etal

[Gregg Wonderly]

I think that it would logically come from a local high level digi.  I think the best choice would be for it to be a "well formatted" announcement message.  That would keep it readable on all clients, and then those that supported the "standard" could set their path from that announcement.  The user should be able to say something like "I only want to use direct path announcements", so that there isn't the ability to contaminate an area from afar.

On the jeaprs project on java.net. I have some partial work on an OpenTrac implementation in my old Java client that I wrote back in 2001.  I've not done much on it because everyone  has been largely ignoring Java for the past decade…

Gregg Wonderly
W5GGW

On Feb 19, 2013, at 6:21 PM, Andrew P. <andrewemt at hotmail.com> wrote:

> Who decides what the preferred local path is, and who sends it? It's an interesting idea. 
> 
> Incidentally, there are now two APRS clients that natively support OpenTrac: Xastir and YAAC. I don't know about the innards of Xastir, but YAAC has a full AX.25 stack in it, so it can support multiple PID's simultaneously; one more PID wouldn't be an issue.
> 
> Note that APRS itself could have an application-level message to announce recommended local paths, since the paths can be shoved in at the application level on some clients (a 'P' message, sort of like the 'T' message for telemetry).
> 
> Just my $.02.
> 
> Andrew Pavlin, KA2DDO
> ------Original Message------
> From: Gregg Wonderly
> To: aprssig at tapr.org
> Sent: Feb 19, 2013 6:39 PM
> Subject: Re: [aprssig] WIDE2-1 vs WIDE1-1,WIDE2-1 was WB2PAY etal
> 
> 
> We are getting to the point that we actually need a "local path" announcement, which can cause the mobile software to change it's path dynamically.  Heck, I'd even say, that the software should use a PID that listens for its packets, and if they don't occur, it should adjust the path dynamically to go through some variations to find something that works.  Fixed paths are really something that doesn't make sense any longer.
> 
> About time for everyone to just have a raspberry-pi that provides a full APRS stack, connected as a "mic" to the radio.  It should have a passthrough mic circuit and a flexible mic plug mechanism that would allow a pi->radio cable and a "mic adapter" cable to be purchased for each radio type.
> 
> That would allow us to focus on a "ubiquitous" APRS software platform that did the right things, was updatable and maintainable as well as extendable.  
> 
> Ohhh wait, we were having a conversation about doing this with OpenTrac. Now, that would be a great evolution and improvement in the usability of APRS!
> 
> Gregg Wonderly
> 
> On Feb 19, 2013, at 4:15 PM, Bill Vodall <wa7nwp at gmail.com> wrote:
> 
>>> The one size fits all mobile path of W1-1,W2-1 may have been fine back during the change over to the new paridigim. But with the explosion of digipeaters in good locations, especially in New England, it's excessive. IMHO
>> 
>> Having one standard, set and forget, path is a really good thing...
>> (Unless it includes RELAY and goes every 15 seconds but that's
>> another issue.)
>> 
>> Technology has improved and we now have software that makes the
>> fill-in systems smarter so they don't generate unnecessary repeats.
>> 
>> Check out:   http://wiki.ham.fi/Viscous_APRS_Digipeater
>> 
>> 73
>> Bill, WA7NWP
>> _______________________________________________
>> aprssig mailing list
>> aprssig at tapr.org
>> http://www.tapr.org/mailman/listinfo/aprssig
> 
> _______________________________________________
> aprssig mailing list
> aprssig at tapr.org
> http://www.tapr.org/mailman/listinfo/aprssig
> 
> 
> Sent from my Verizon Wireless BlackBerry
> _______________________________________________
> aprssig mailing list
> aprssig at tapr.org
> http://www.tapr.org/mailman/listinfo/aprssig