Order Tray | Contact Us | Home | SIG Lists

[aprssig] Identifying TX Igates

Bob Bruninga bruninga at usna.edu
Mon Sep 19 15:39:22 UTC 2011

All IGate operators please read and consider action on this proposal.

RX-only IGates kill the functionality of the APRS-IS as a universal system!
And they give casual observers the impression that APRS has global
connectivity, when in fact, that view has lots of invisible holes because of
RX-only IGates.

Compounding this problem is that we have no way of knowing if people are
using the right symbol for their IGate.  Are they using "I" because it is
really  a TX Igate, or just because it seems logical?

Using http://www.findu.com/cgi-bin/symbol.cgi?icon=Iamp&limit=2000 I see 960
"I&" Igates
Using http://www.findu.com/cgi-bin/symbol.cgi?icon=Ramp&limit=2000 I see 130
"R&" Igates

Maybe we need to have a 3rd symbol, a "T" Overlay so that operators of
serious two-way IGates and indicate their dedicated intent to provide good
APRS-IS local service.  These guys will take the trouble to indicate a TX
Igate.  When we see one of those, we have proof-positive that the IGate
includes a two-way TX capability.

We could even go one step farther.  We could indicate the NUMBER OF HOPS
that the IGate uses by default for IS-to-RF packets.  This could help us
better manage overlapping IGate coverage...  So how about this plan:

I& - is an IGate, but is ambiguous with respect to transmitting
R& - means it is definitely an RX only IGate
T& - Means it is definitely a TX IGate with one hop path only
2& - means it is a TX igate clobbering two hops in all directions
3& - means it is a TX SPAM GENERATOR , (or a legitimate special case)

Should we do this???


An easy way to check an IGate is to find a mobile Kenwood, Yeasu or other
two-way APRS messaging device on http://map.findu.com/callsign and then from
the internet send him a message.  If he gets it, then the nearby IGate is

More information about the aprssig mailing list