<html><head><meta http-equiv="Content-Type" content="text/html; charset=utf-8"><meta name="Generator" content="Microsoft Word 14 (filtered medium)"><style><!--
/* Font Definitions */
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
{font-family:Tahoma;
panose-1:2 11 6 4 3 5 4 4 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;}
p.MsoAcetate, li.MsoAcetate, div.MsoAcetate
{mso-style-priority:99;
mso-style-link:"Balloon Text Char";
margin:0in;
margin-bottom:.0001pt;
font-size:8.0pt;
font-family:"Tahoma","sans-serif";}
span.EmailStyle17
{mso-style-type:personal-reply;
font-family:"Calibri","sans-serif";
color:#1F497D;}
span.BalloonTextChar
{mso-style-name:"Balloon Text Char";
mso-style-priority:99;
mso-style-link:"Balloon Text";
font-family:"Tahoma","sans-serif";}
.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="blue" vlink="purple"><div class="WordSection1"><p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1f497d">Good idea. But if you are going to average the positions to try to figure out the position of a BLIND digi, then better not to plot it with 10 mile ambiguity, but more like 1 mile so that you actually get to see the solution of the average. Plotting it with 10m ambiguity would place the actual symbol somewere randomly within a 400 square mile box.</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">But again, that is only plotting the “solution”. In that case, it should be a definite different symbol and name from the actual digi and name which might be misleading.</span></p><p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1f497d">If one is going to plot the actual digi and name, then 10 mile ambiguity might be OK.</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">Kinda depends on how it will be used.</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">P.S. PSAT nearing launch will be reporting its position in 60 mile ambiguity (1 degree) so I hope most softare is OK with that.</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:10.0pt;font-family:"Tahoma","sans-serif"">From:</span></b><span style="font-size:10.0pt;font-family:"Tahoma","sans-serif""> <a href="mailto:aprssig-bounces@tapr.org">aprssig-bounces@tapr.org</a> [mailto:<a href="mailto:aprssig-bounces@tapr.org">aprssig-bounces@tapr.org</a>] <b>On Behalf Of </b>Randy Love<br><b>Sent:</b> Thursday, December 11, 2014 11:09 AM<br><b>To:</b> TAPR APRS Mailing List<br><b>Subject:</b> Re: [aprssig] Vicinity plotting of stealth digipeaters</span></p><p class="MsoNormal"> </p><div><p class="MsoNormal">In a feeble, off the cuff, maybe-it-would-work first suggestion, how about averaging the lat and lon of the stations digipeated by the stealth digi, and have position ambiguity of 10 miles?</p><div><p class="MsoNormal"> </p></div><div><p class="MsoNormal">Theoretically, the digi would be somewhat central to those stations that were digipeated by it, thus averaging the lat and long would place the digi somewhere in the area outlined by the locations of the stations digi'd by it. </p></div><div><p class="MsoNormal"> </p></div><div><p class="MsoNormal">There are exceptions to this thought, of course, but better than nothing at all!</p></div><div><p class="MsoNormal"> </p></div><div><p class="MsoNormal">Randy</p></div><div><p class="MsoNormal">WF5X</p></div><div><p class="MsoNormal"> </p></div></div><div><p class="MsoNormal"> </p><div><p class="MsoNormal">On Thu, Dec 11, 2014 at 10:05 AM, Andrew P. <<a href="mailto:andrewemt@hotmail.com" target="_blank">andrewemt@hotmail.com</a>> wrote:</p><div><p class="MsoNormal">Does anyone have any advice or opinion on vicinity plotting of stealth digipeaters? Or have I stepped into a brave new world here? </p><div><p class="MsoNormal"> </p></div><div><p class="MsoNormal">Andrew, KA2DDO </p></div><div><div><p class="MsoNormal" style="margin-bottom:12.0pt"><br><br>-------- Original message --------<br>From: "Andrew P." <<a href="mailto:andrewemt@hotmail.com" target="_blank">andrewemt@hotmail.com</a>> <br>Date:12/05/2014 13:20 (GMT-05:00) <br>To: TAPR APRS Mailing List <<a href="mailto:aprssig@tapr.org" target="_blank">aprssig@tapr.org</a>> <br>Subject: [aprssig] Vicinity plotting of stealth digipeaters </p><div><p class="MsoNormal">Greetings, all. </p><div><p class="MsoNormal"> </p></div><div><p class="MsoNormal">I've got a question about vicinity plotting (i.e., guessing where a station is based on its first digipeater's position when the station hasn't reported its position yet).</p></div><div><p class="MsoNormal"> </p></div><div><p class="MsoNormal">Is it reasonable to do this in reverse, i.e., guessing where a first digipeater is, based on the position report of the digipeated station? Because stealth (non-beaconing) digipeaters are common in my area, I have implemented a first draft of this in my YAAC program.</p></div><div><p class="MsoNormal"> </p></div><div><p class="MsoNormal">I assume this needs to be improved, perhaps using direction-finding tricks such as guessing the digipeater has to be within the PHG range circles of all stations it has first-digipeated.</p></div><div><p class="MsoNormal"> </p></div><div><p class="MsoNormal">But should I be doing this kind of approximation at all?</p></div><div><p class="MsoNormal"> </p></div><div><p class="MsoNormal">Just curious.</p></div><div><p class="MsoNormal"> </p></div><div><p class="MsoNormal">Andrew, KA2DDO </p></div><div><p class="MsoNormal">(putting my asbestos shorts on now :-)</p></div></div></div></div></div><p class="MsoNormal" style="margin-bottom:12.0pt"><br>_______________________________________________<br>aprssig mailing list<br><a href="mailto:aprssig@tapr.org">aprssig@tapr.org</a><br><a href="http://www.tapr.org/mailman/listinfo/aprssig" target="_blank">http://www.tapr.org/mailman/listinfo/aprssig</a></p></div><p class="MsoNormal"> </p></div></div></body></html>