<html>
<head>
<meta content="text/html; charset=utf-8" http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
<div class="moz-cite-prefix">I'm not a big fan of the concept, but
since we're in the area and people are using them, how about
viscous digipeaters?<br>
<br>
V# - Viscous digpeater
(<a class="moz-txt-link-freetext" href="https://github.com/PhirePhly/aprx/blob/master/ViscousDigipeater.README">https://github.com/PhirePhly/aprx/blob/master/ViscousDigipeater.README</a>)<br>
<br>
I looked for a good web reference of what Viscous Digipeating
actually IS, but the best I found was the README from APRX which
is, AFAIK, the only APRS program currently implementing the
approach. If anyone knows of a better reference, I think it would
be good to include it in the symbol definitions?<br>
<br>
Lynn (D) - KJ4ERJ - Author of APRSISCE for Windows Mobile and
Win32<br>
<br>
On 10/18/2016 9:25 AM, Robert Bruninga wrote:<br>
</div>
<blockquote
cite="mid:fd0cc9426aee3edd0b0b3d68e8df0c9c@mail.gmail.com"
type="cite">
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
<meta name="Generator" content="Microsoft Word 15 (filtered
medium)">
<style><!--
/* Font Definitions */
@font-face
{font-family:"Cambria Math";
panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Times New Roman","serif";}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:purple;
text-decoration:underline;}
span.EmailStyle17
{mso-style-type:personal-reply;
font-family:"Calibri","sans-serif";
color:#1F497D;}
.MsoChpDefault
{mso-style-type:export-only;
font-family:"Calibri","sans-serif";}
@page WordSection1
{size:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
{page:WordSection1;}
--></style>
<div class="WordSection1">
<p class="MsoNormal"><span
style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1f497d">Excellent
feedback. I added the digipeaters to the symbols-new.txt
file</span></p>
<p class="MsoNormal"><span
style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1f497d">I
agree that L and P are mostly obsolete, but we need them in
the table because it will take decades before some people
change their symbol.</span></p>
<p class="MsoNormal"><span
style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1f497d"> </span></p>
<p class="MsoNormal"><span
style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1f497d">I
did add #W as a new one to cover the generic WIDEn-N, SSn-N
with path limiting as the overall digi we use today if
anyone wants to start using it.</span></p>
<p class="MsoNormal"><span
style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1f497d"> </span></p>
<p class="MsoNormal"><span
style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1f497d"><a
moz-do-not-send="true"
href="http://aprs.org/symbols/symbols-new.txt">http://aprs.org/symbols/symbols-new.txt</a></span></p>
<p class="MsoNormal"><span
style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1f497d"> </span></p>
<p class="MsoNormal"><span
style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1f497d">Would
that meet your suggestions?</span></p>
<p class="MsoNormal"><span
style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1f497d">Bob,
WB4aPR</span></p>
<p class="MsoNormal"><span
style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1f497d"> </span></p>
<p class="MsoNormal"><span
style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1f497d"> </span></p>
<p class="MsoNormal"><b><span
style="font-size:11.0pt;font-family:"Calibri","sans-serif"">From:</span></b><span
style="font-size:11.0pt;font-family:"Calibri","sans-serif"">
aprssig [mailto:<a moz-do-not-send="true"
href="mailto:aprssig-bounces@tapr.org">aprssig-bounces@tapr.org</a>]
<b>On Behalf Of </b>Kenneth Finnegan<br>
<b>Sent:</b> Tuesday, October 18, 2016 2:22 AM<br>
<b>To:</b> TAPR APRS Mailing List<br>
<b>Subject:</b> [aprssig] Digipeater Symbol Overlays</span></p>
<p class="MsoNormal"> </p>
<div>
<div>
<p class="MsoNormal">So like usual, based on the previous
comments on the sig, I spent a few hours down the rabbit
hole of lining up APRS specifications, articles, emails,
rumors, and ruminations, and have come back with what I
think is a more distilled piece of understanding. (and
another file in my APRS_notes repo: <a
moz-do-not-send="true"
href="https://github.com/PhirePhly/aprs_notes/blob/master/symbol_links.txt">https://github.com/PhirePhly/aprs_notes/blob/master/symbol_links.txt</a>
)</p>
</div>
<div>
<p class="MsoNormal"> </p>
</div>
<div>
<p class="MsoNormal">Being the maintainer of Aprx, I'm
particularly interested in the symbol overlays used for
digipeaters. Unfortunately, digipeaters aren't mentioned
in the overlay document. Digging through all of the "New
n-N paradigm" documents, and reading state working groups
+ personal third party articles on digipeater overlays, it
seems like the currently expected list of digipeater
overlays is as follows:</p>
</div>
<div>
<p class="MsoNormal"> /# - Generic digipeater</p>
</div>
<div>
<p class="MsoNormal"> 1# - WIDE1-1 digipeater</p>
</div>
<div>
<p class="MsoNormal"> A# - Alternate input (i.e. 144.990MHz)
digipeater</p>
</div>
<div>
<p class="MsoNormal"> I# - I-gate equipped digipeater</p>
</div>
<div>
<p class="MsoNormal"> L# - WIDEn-N with path length trapping</p>
</div>
<div>
<p class="MsoNormal"> P# - PacComm</p>
</div>
<div>
<p class="MsoNormal"> S# - SSn-N digipeater</p>
</div>
<div>
<p class="MsoNormal"> X# - eXperimental digipeater</p>
</div>
<div>
<p class="MsoNormal"> </p>
</div>
<div>
<p class="MsoNormal">* Why do we include PacComm P#? I
assume that's left over from pre-TNC ID tocall days?</p>
</div>
<div>
<p class="MsoNormal">* The I# I-gate digi isn't mentioned
anywhere on APRS.org as far as I can tell, but the classic
argument that we don't have Internet access at radio sites
is becoming less true so these I-gate digis are becoming
more of a thing.</p>
</div>
<div>
<p class="MsoNormal">* I would vote for excluding the L#
overlay since many modern digipeaters trap long paths, so
I don't think that should be the defining feature of its
icon. </p>
</div>
<div>
<p class="MsoNormal"> </p>
</div>
<div>
<p class="MsoNormal">My suggestion for a suggested set of
Digipeater overlays for us to promote to users is as
follows:</p>
</div>
<div>
<div>
<p class="MsoNormal"> /# - Generic WIDEn-N digipeater</p>
</div>
<div>
<p class="MsoNormal"> 1# - WIDE1-1/direct-only digipeater</p>
</div>
<div>
<p class="MsoNormal"> A# - Alternate input (i.e.
144.990MHz) digipeater</p>
</div>
<div>
<p class="MsoNormal"> I# - I-gate equipped digipeater</p>
</div>
<div>
<p class="MsoNormal"> S# - SSn-N local net alias
digipeater</p>
</div>
<div>
<p class="MsoNormal"> X# - eXperimental digipeater</p>
</div>
</div>
<div>
<p class="MsoNormal"> </p>
</div>
<div>
<p class="MsoNormal">Thoughts?</p>
</div>
<div>
<div>
<p class="MsoNormal">--<br>
Kenneth Finnegan, W6KWF</p>
</div>
<div>
<p class="MsoNormal">Aprx Maintainer<br>
<a moz-do-not-send="true"
href="http://blog.thelifeofkenneth.com/"
target="_blank">http://blog.thelifeofkenneth.com/</a></p>
</div>
</div>
</div>
</div>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<br>
<pre wrap="">_______________________________________________
aprssig mailing list
<a class="moz-txt-link-abbreviated" href="mailto:aprssig@tapr.org">aprssig@tapr.org</a>
<a class="moz-txt-link-freetext" href="http://www.tapr.org/mailman/listinfo/aprssig">http://www.tapr.org/mailman/listinfo/aprssig</a>
</pre>
</blockquote>
<p><br>
</p>
</body>
</html>