[Xastir] Weather Polygons

[Lynn W. Deffenbaugh (Mr)]

Pete's alerts DO make it from APRS-IS through firenet.us to clients.  
APRSISCE/32 generates the following filter pieces to ensure proper 
reception of all of the weather alerts (Pete's, Curt's, and Australia):

  t/n e/AE5PL-WX/WE7U-WX/WXSVR-AU

Alternatively, if you only want the alerts for selected CWAs (), you can 
put them into a prefix (p/) filter like:

p/CTP/JAX/KEY/MFL/MLB/MOB/OUN/PBZ/TAE/TBW/TSA

That one gets stuff around Oklahoma City, Pittsburgh, and Florida and 
covers both feeds because they share the CWA as the prefix for the alert 
packets.

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

PS.  As a matter of convenience, there's actually an active coordinate 
alert right now in RNK (Roanoke, VA).  Here's how APRSISCE/32 displays 
it along with the popup information:



Here's what it looks like with the shapefile alert around the lat/lon alert:



On 6/21/2011 4:51 AM, Curt, WE7U wrote:
> On Mon, 20 Jun 2011, Christian Reynolds wrote:
>
>> Thank you for the note.  I added the Firenet.us as mentioned, and 
>> have ran it for a few hours now.  It did not catch / display the 
>> recently issued PDS Tor Watch for Kansas (Tor 523).
>
> I believe that's one of the types of messages that gets turned into 
> the severe weather polygons.  By Pete.  I'd have to look at the 
> particular message to be sure, but if it doesn't have a certain set of 
> machine-parsable info inside it, my script ignores it.  Some of the 
> messages have only the polygons in them, and I seem to remember the 
> tornado messages were in that category.
>
> So...  If you want both types of weather alerts right now you'd have 
> to connect to both firenet.us (to get mine) and aprs-is (to get 
> Pete's).  Sorry about that, but at least there's a work-around.  Lynn 
> probably knows off the top of his head, but Pete's alerts must not get 
> propagated across from APRS-IS to Firenet?  I seem to remember that 
> some of my initial alerts bled over to APRS-IS, but I think that was 
> someone gating from local RF here to APRS-IS, not an actual gating 
> from Firenet to APRS-IS.
>