<html>
<body>
<font size=3>At 03:18 PM 2013-09-24, Tony VE6MVP wrote:<br>
<blockquote type=cite class=cite cite="">>So let me see if I can
reword this for clarity (check me on this):<br>
><br>
>The digi should announce a voice repeater that is useful _in_ _the_
<br>
>_coverage_ _area_ _of_ _the_ _digi_.<br>
><br>
>As such, if several short-range digis (out of range of each other)
<br>
>were scattered around the same long-range repeater, could (and
should) <br>
>they all announce the same repeater (using no digipeat aliases in
<br>
>their announcement packets)? Seems like that would ensure the
traveler <br>
>would hear about the repeater from one of the digis he was passing
<br>
>(regardless of which direction he was relative to the repeater)?<br>
><br>
>But then who decides _which_ of the multiple digis should do
it?</blockquote><br>
</font><snip><br><br>
<blockquote type=cite class=cite cite=""><font size=3>In the event that
the digi's can't all see the originating digi I might set a chain of
digi's in the path so the packet "bounces" from one to the next
in the ring. Again Bob and I disagree on
that.</blockquote><br>
Actually when I think about it I'm wrong on that one. At least in
highly utilized areas. You would be best putting the repeater
object with no path in each of those digi's whether they can hear each
other or not. Now what will happen is the repeater object
would undoubtedly be heard outside the voice repeaters range. But
given that my primary APRS object source is the Nuvi 360 list sorted by
distance to me that isn't a problem for me.<br><br>
And the reality is that is what we should be doing out here.
But it's more convenient to update just one digi than multiple digi's
with the repeater object.<br><br>
Tony</font></body>
</html>