| |
ZL3AI > APRDIG 12.05.07 02:16l 41 Lines 1426 Bytes #999 (0) @ WW
BID : 10148-ZL3AI
Read: GUEST
Subj: [APRSSIG] Vol 35 #1, 3/3
Path: DB0FHN<DB0RGB<DB0SL<DB0FSG<HB9EAS<DB0CZ<DB0GV<DB0SIF<DB0EAM<DB0ERF<
DB0FBB<DB0IUZ<DB0OVN<DB0GOS<ON0AR<IK5YZW<VK6HGR<ZL2BAU
Sent: 070511/2330Z @:ZL2BAU.#79.NZL.OC #:47327 [Waimate] $:10148-ZL3AI
From: ZL3AI@ZL2BAU.#79.NZL.OC
To : APRDIG@WW
Message: 16
Date: Tue, 1 May 2007 12:15:23 -0400
From: "Michael J. Wolthuis" <wolthui3_at_msu.edu>
Subject: RE: [aprssig] Weather Alert Network on APRS
In Michigan, we were not quite this in-depth and use it for routing traffic
to the NWS offices not for delivering announcements, but we setup specific
digis in the State as (L) digis instead of (S) digis and put WX inside the
UIDIGI command. Then we have the NWS sponsored weather stations send to
WX2-2 or WX3-3 as needed to get them to the appropriate counties, digis and
Igates. This has worked very well as we leave ID ON for WX and thus can see
the path a weather station takes to get to the IGATE at the NWS and then it
is converted with a script and loaded onto the NWS main forecasting
machines.
It has worked very well, but the problem becomes if you have end-user
weather stations and they send to a standard path and not WX VIA WX2-2 then
the NWS will not pick them up because of the script we use to catch the WX
in the TO call.
There has been pluses and minuses to doing it this way, but overall it has
allowed us to use VERY high beacon rate on specific weather stations for the
good of the 3 regional NWS offices.
Mike
Kb8zgl
------------------------------
aprssig mailing list
aprssig_at_lists.tapr.org
https://lists.tapr.org/cgi-bin/mailman/listinfo/aprssig
End of aprssig Digest, Vol 35, Issue 1
Read previous mail | Read next mail
| |
