[aprssig] digi and igate coverage in the plains
Stephen H. Smith
wa8lmf2 at aol.com
Thu Sep 29 19:48:07 CDT 2005
tyler at allisonhouse.com wrote:
> One major concern is none of us hams in the group have run an APRS tracker
> in the plains so we are leary of the coverage.
> Is there a way for me to put together a "likely" coverage map for APRS to
> see if running a tracker would prove useful or an excercise in futility as
> we blink in and out every couple hours?
> The main states would probably be:
> Eastern Colorado
> Northern Texas
> OK, KS, NE, SD, MN, IA, MO, WI, IL
> If you think it's worth it what path should we use for maximum chance of
Based on my last trip from L.A. to Michigan via I-70. I-76 and I-80 last
January, and numerous previous trips across the heartland:
Eastern Colorado, once out of range of digipeaters above Denver in the
front range, has no coverage at all.
All of NB until you get to Lincoln-Omaha area is a black hole of
non-coverage except for a small island around Kearny.
KS - Activity in KC-Topeka -Wichita corridor; very little west of there
until you get to Denver.
SD - Almost nothing except an island around Sioux Falls
IA - Excellent modern WIDEn-N network covers nearly 100% of the
Interstates and most other areas as well.
MO - Coverage along most interstates but very spotty in the hilly Ozark
area in the west, and on secondary roads.
WI and MN good almost continuous coverage in the southern (i.e. more
urbanized) part of both states. Rather spotty in the northern parts
(i.e. activity in Duluth, then very little until you get to Minneapolis
metro area for example.)
Stephen H. Smith wa8lmf (at) aol.com
EchoLink Node: 14400 [Think bottom of the 2M band]
Home Page: http://wa8lmf.com
"APRS 101" Explanation of APRS Path Selection & Digipeating
Updated Rev H APRS Symbol Chart
New/Updated "Rev H" APRS http://webs.lanset.com/wa8lmf/aprs
Symbols Set for UI-View,
UIpoint and APRSplus:
More information about the aprssig