<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
That sounds more promising, but if you're putting them on RF for
travelers, then I wish you'd consider putting them on APRS for all
travelers. There's more APRS users than just APRS RF radio owners,
and I'm sure some of us would appreciate seeing them beacon on our
mobile APRS-IS clients as well.<br>
<br>
Lynn (D) - KJ4ERJ - Author of APRSISCE for Windows Mobile and Win32<br>
<br>
On 4/26/2012 8:21 PM, Ron Stordahl, AE5E wrote:
<blockquote
cite="mid:1335486092.74237.YahooMailNeo@web125704.mail.ne1.yahoo.com"
type="cite">
<div style="color:#000; background-color:#fff; font-family:times
new roman, new york, times, serif;font-size:12pt">
<div><span>Actually I didn't mean to imply keep ALL of the
object packets off of APRS-IS. What I was trying to
emphasis is that these are primarily local in application.
What I actually do is to send them locally with NOGATE every
10 minutes and then send one every 30 to 60 minutes to
APRS-IS.</span></div>
<div><span><br>
</span></div>
<div><span>The radio object packets are not digipeated,
certainly not out several layers where they would be QRM.
On my recent road trip I heard voice repeater objects from
several hundred miles away. It could be that some sysops
don't realize this is pointless.</span></div>
<div><br>
<span></span></div>
<div><span>Ron, AE5E</span></div>
<div><br>
<blockquote style="border-left: 2px solid rgb(16, 16, 255);
margin-left: 5px; margin-top: 5px; padding-left: 5px;">
<div style="font-family: times new roman, new york, times,
serif; font-size: 12pt;">
<div style="font-family: times new roman, new york, times,
serif; font-size: 12pt;">
<div dir="ltr"> <font face="Arial" size="2">
<hr size="1"> <b><span style="font-weight:bold;">From:</span></b>
Lynn W. Deffenbaugh (Mr)
<a class="moz-txt-link-rfc2396E" href="mailto:ldeffenb@homeside.to"><ldeffenb@homeside.to></a><br>
<b><span style="font-weight: bold;">To:</span></b>
"Ron Stordahl, AE5E"
<a class="moz-txt-link-rfc2396E" href="mailto:ronn5in-aprssig@yahoo.com"><ronn5in-aprssig@yahoo.com></a>; TAPR APRS Mailing
List <a class="moz-txt-link-rfc2396E" href="mailto:aprssig@tapr.org"><aprssig@tapr.org></a> <br>
<b><span style="font-weight: bold;">Sent:</span></b>
Thursday, April 26, 2012 3:43 PM<br>
<b><span style="font-weight: bold;">Subject:</span></b>
Re: [aprssig] APRS Local Info Initative TM-D710A
compatibitility<br>
</font> </div>
<br>
<meta http-equiv="x-dns-prefetch-control" content="off">
<div id="yiv1855685610">
<div> On 4/26/2012 4:10 PM, Ron Stordahl, AE5E wrote:
<blockquote type="cite">
<div
style="color:#000;background-color:#fff;font-family:times
new roman, new york, times,
serif;font-size:12pt;"><span
class="yiv1855685610raw_line">As such it does
have to be sent frequently, perhaps every 10
minutes, but the path should be such that it
does not end up on the APRS-IS network nor
digipeated far far away. You can keep it off
of APRS-IS by terminating the path with the
string ',NOGATE'. IGates which are working
correctly will not send such a packet to the
internet. The path itself should be short,
perhaps only NOGATE so that no area digipeater
will repeat it. </span><br>
</div>
</blockquote>
<br>
Why keep such objects off the APRS-IS? If I'm
planning a trip into an area, I'd like to be able to
scope it out in advance and see what the radio
infrastructure might be there via <a
moz-do-not-send="true" target="_blank"
href="http://aprs.fi">aprs.fi</a> (or your
favorite APRS Internet site).<br>
<br>
Alternatively, if I'm using a contemporary APRS-IS
client to see the surrounding infrastructure and
have a voice-only radio, why hide the repeater
objects from my visibilty?<br>
<br>
You're actually adding path length for NOGATE and
could shorten the packet by 7 over-the-air bytes if
you just let the APRS/APRS-IS work as designed
instead of trying to keep packets "private" for some
reason.<br>
<br>
Lynn (D) - KJ4ERJ - Author of APRSISCE for Windows
Mobile and Win32<br>
<br>
</div>
</div>
<meta http-equiv="x-dns-prefetch-control" content="on">
<br>
<br>
</div>
</div>
</blockquote>
</div>
</div>
</blockquote>
<br>
</body>
</html>