<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
On 3/20/2012 9:56 AM, Stephen H. Smith wrote:
<blockquote cite="mid:4F688CAB.6010601@aol.com" type="cite">
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
<br>
5) This may seem obvious, but many newcomers unwittingly assume
the APRS network has the same kind of ubiquitous coverage as
cellular networks. It DOESN'T! The APRS network has nowhere
near the number of base station igate sites as cellular network
have cell sites. The APRS RF network has large coverage holes in
many parts of the country. If the RF station being addressed
has NOT been heard recently, or is not within range of an igate
station, then messaging attempts Internet-to-RF will fail. <br>
</blockquote>
<br>
For a quick idea of the national coverage and activity of APRS,
check out <a class="moz-txt-link-freetext" href="http://tinyurl.com/APRSAct24">http://tinyurl.com/APRSAct24</a> (24 hours/plot) and
<a class="moz-txt-link-freetext" href="http://tinyurl.com/APRSAct00">http://tinyurl.com/APRSAct00</a> (5-7 day merge). There's various areas
and views in the different plots with the most recent ones normally
at the bottom of the list.<br>
<br>
<blockquote cite="mid:4F688CAB.6010601@aol.com" type="cite"> 6)
The APRS Internet System can function, in a manner similar to
EchoLink or IRLP, as a kind of "wormhole" connecting two radio
users too far apart to communicate directly with each other by
radio-only. In this case, the limitations on what will pass
Internet-to-Rf will apply to BOTH parties involved. I.e. BOTH
parties need to be within the local coverage area of igate
stations. <br>
</blockquote>
<br>
And the IGates at both ends need to be transmit-enabled, not
receive-only, IGates.<br>
<br>
Lynn (D) - KJ4ERJ - Author of APRSISCE for Windows Mobile and Win32<br>
<br>
</body>
</html>