[Xastir] WXSVR-WE7U Go-live

[Lynn W. Deffenbaugh (Mr)]

You might also want to include e/WE7U-WX (Curt's new entry call as 
WXSVR-WE7U was truncating to WXSVR-WE) as there seems to be a bug in 
javAPRSSrvr's filter implementation of t/n.  It will not give you any 
NWS object (defined as a 6 alpha source call and a 5 alpha-numeric 
"sequence" after the }, but their definition of alpha-numeric does not 
include lower-case letters.  This means that any alert originated (start 
time?) in minute 37 of the hour through 59 will not come through the t/n.

When I brought this up to Pete (AE5PL), I was told that a Prefix filter 
for the CWA (County Warning Area or NWS office) of interest was a more 
reliable way of getting the alerts you're interested in.  You can find 
your CWA at http://www.aprs-is.net/WX/NWSCodes.aspx

Lynn (D) - KJ4ERJ - Author of APRSISCE for Windows Mobile and Win32

PS.  If anyone wants to run parallel feeds from Firenet, one with 
e/WE7U-WX and the other with t/n I'd love to have my observations above 
confirmed or debunked.  Note that the t/n will give you more packets 
than the e/WE7U-WX as you'll be getting those from WXSVR-AU and AE5PL-WX 
(as few as those are), but none of those (in my experience) will have 
lower case letters in their sequence.

On 2/25/2011 2:35 PM, Curt, WE7U wrote:
>
> WXSVR-WE7U went live today, injecting into "Firenet.us".
>
> Make sure you've run the xastir/scripts/get-NWSdata script as root, 
> connect to "firenet.us" with at least "t/n" for a filter, and you 
> should see a bunch of zones start to light up w/Xastir.
>
> It does NOT have the finger server or the multi-line severe weather 
> polygons implemented.
>