<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
</head>
<body>
Ok, so 1 mile ambiguity around average of all station pos reports first-repeated by that digi. I'm assuming I shouldn't count the same originating station twice because I have a history of multiple pos reports from that station unless the station is significantly
moving (ie., use multiple digipeats from different positions to improve point sampling). Also, should I weight the averaging by the inverse of each pos report's ambiguity? I'm assuming that the first time I hear about a stealth digi, I can only do standard
vicinity plotting because I only have one reference position. Updates won't change the vicinity plot or the algorithm until I get a different reference position to combine with the first one.
<div><br>
</div>
<div>Of course, the answer would be seriously skewed if the stealth digi had a directional antenna, which would offset its coverage area. How many digis out there have other than an omnidirectional antenna?</div>
<div><br>
</div>
<div>Hmmm... this could also be useful forwards to improve vicinity plotting and locate stations with bogus position data (like the station with a U.S. callsign I saw displayed in Afghanistan, presumably with an incorrect sign in its longitude). Of course,
such analysis could only occur on an RF listening station because of the duplicate stripping of the APRS-IS backbone.</div>
<div><br>
</div>
<div>Andrew, KA2DDO </div>
<br>
<br>
-------- Original message --------<br>
From: Robert Bruninga <bruninga@usna.edu> <br>
Date:12/11/2014 11:49 (GMT-05:00) <br>
To: TAPR APRS Mailing List <aprssig@tapr.org> <br>
Subject: Re: [aprssig] Vicinity plotting of stealth digipeaters <br>
<br>
<style>
<!--
p.x_MsoNormal, li.x_MsoNormal, div.x_MsoNormal
{margin:0in;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Times New Roman","serif"}
span.x_MsoHyperlink
{color:blue;
text-decoration:underline}
span.x_MsoHyperlinkFollowed
{color:purple;
text-decoration:underline}
p.x_MsoAcetate, li.x_MsoAcetate, div.x_MsoAcetate
{margin:0in;
margin-bottom:.0001pt;
font-size:8.0pt;
font-family:"Tahoma","sans-serif"}
span.x_EmailStyle17
{font-family:"Calibri","sans-serif";
color:#1F497D}
span.x_BalloonTextChar
{font-family:"Tahoma","sans-serif"}
.x_MsoChpDefault
{font-family:"Calibri","sans-serif"}
div.x_WordSection1
{}
-->
</style>
<div lang="EN-US" link="blue" vlink="purple">
<div class="x_WordSection1">
<p class="x_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="x_MsoNormal"><span style="font-size:11.0pt; font-family:"Calibri","sans-serif"; color:#1f497d"> </span></p>
<p class="x_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="x_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="x_MsoNormal"><span style="font-size:11.0pt; font-family:"Calibri","sans-serif"; color:#1f497d"> </span></p>
<p class="x_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="x_MsoNormal"><span style="font-size:11.0pt; font-family:"Calibri","sans-serif"; color:#1f497d"> </span></p>
<p class="x_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="x_MsoNormal"><span style="font-size:11.0pt; font-family:"Calibri","sans-serif"; color:#1f497d"> </span></p>
<p class="x_MsoNormal"><span style="font-size:11.0pt; font-family:"Calibri","sans-serif"; color:#1f497d">Bob</span></p>
<p class="x_MsoNormal"><span style="font-size:11.0pt; font-family:"Calibri","sans-serif"; color:#1f497d"> </span></p>
<p class="x_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="x_MsoNormal"> </p>
<div>
<p class="x_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="x_MsoNormal"> </p>
</div>
<div>
<p class="x_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="x_MsoNormal"> </p>
</div>
<div>
<p class="x_MsoNormal">There are exceptions to this thought, of course, but better than nothing at all!</p>
</div>
<div>
<p class="x_MsoNormal"> </p>
</div>
<div>
<p class="x_MsoNormal">Randy</p>
</div>
<div>
<p class="x_MsoNormal">WF5X</p>
</div>
<div>
<p class="x_MsoNormal"> </p>
</div>
</div>
<div>
<p class="x_MsoNormal"> </p>
<div>
<p class="x_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="x_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="x_MsoNormal"> </p>
</div>
<div>
<p class="x_MsoNormal">Andrew, KA2DDO </p>
</div>
<div>
<div>
<p class="x_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="x_MsoNormal">Greetings, all. </p>
<div>
<p class="x_MsoNormal"> </p>
</div>
<div>
<p class="x_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="x_MsoNormal"> </p>
</div>
<div>
<p class="x_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="x_MsoNormal"> </p>
</div>
<div>
<p class="x_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="x_MsoNormal"> </p>
</div>
<div>
<p class="x_MsoNormal">But should I be doing this kind of approximation at all?</p>
</div>
<div>
<p class="x_MsoNormal"> </p>
</div>
<div>
<p class="x_MsoNormal">Just curious.</p>
</div>
<div>
<p class="x_MsoNormal"> </p>
</div>
<div>
<p class="x_MsoNormal">Andrew, KA2DDO </p>
</div>
<div>
<p class="x_MsoNormal">(putting my asbestos shorts on now :-)</p>
</div>
</div>
</div>
</div>
</div>
<p class="x_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="x_MsoNormal"> </p>
</div>
</div>
</div>
</body>
</html>