<html><head><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:#0563C1;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:#954F72;
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></head><body lang="EN-US" link="#0563C1" vlink="#954F72"><div class="WordSection1"><p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1f497d">APRS by design will be digipeated by EVERY digipeater that hears it. So if the one farther south hears it, it is already going to digipeat it anyway. Nothing you need to do to make that happen… </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">And in SoCal, there are so many digis, that your path should be just one hop and it will still hit every digi that hears it that first hop.</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">Bob</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 href="mailto:aprssig-bounces@tapr.org">aprssig-bounces@tapr.org</a>] <b>On Behalf Of </b>Jess Haas<br><b>Sent:</b> Monday, March 06, 2017 1:08 PM<br><b>To:</b> TAPR APRS Mailing List<br><b>Subject:</b> [aprssig] Smart TX igate message routing?</span></p><p class="MsoNormal"> </p><div><p class="MsoNormal">Where I am located in Southern California I can hit many digipeaters. For home station beaconing setting a single one of them as my route seems to be the way to go but for tx message igating I was thinking it may make more sense if the outgoing path was the one that the station was last heard on. Has anyone implemented anything like this?</p><div><p class="MsoNormal"> </p></div><div><p class="MsoNormal">For example the digipeater I have the strongest path to may not be able to get a message to a station farther south but I can hear and hit a digipeater rather far south that the station can hear easily. Also if I have heard a station directly recently than I should have no problem getting a message to them directly even if they have moved some with my basestation antenna and possibly higher power so digipeating to the whole area may be unnecessary.</p></div><div><p class="MsoNormal"> </p></div><div><p class="MsoNormal">Another advantage of this would be that a station that is in an RF hole such as a valley that can't hear or hit a digipeater but has a path to another station that can could set that station as a path and messages would automatically be routed back to them.</p></div><div><p class="MsoNormal"> </p></div><div><p class="MsoNormal">Thoughts?</p></div><div><p class="MsoNormal"> Jess</p></div></div></div></body></html>