[EAS] IPAWS and NOAA

[Harold Price]

Dave,

Yes, this is one of the issues that need to be addressed before NWS 
CAP messages can be enabled for EAS via IPAWS.

One issue is that there is no way to uniquely identify the original 
CAP message from an EAS message, especially if the location list 
differs.  Depending on the number of messages flowing through the 
system you could often make a good guess, but on a busy day with fast 
moving storms, you might have a false duplicate detection.

EAS vendors, FEMA, FCC, and NOAA, are continuing to look into the 
issue, even so far as considering changes to the basic EAS protocol.

There are some other issues, including the intelligibility of lengthy 
messages when converted to TTS and a crawl, boilerplate info (turn 
around, don't drown), and web sites, Twitter IDs, facebook pages, 
etc.  These are suitable for other NWS uses but sometimes less so for 
a broadcast interrupt message.

This is a common problem for messages meant for various delivery 
methods.  Work is continuing, and suggestions are always welcome.

Harold

At 04:30 PM 7/6/2018, Dave Turnmire wrote:

>So... IF my assumptions above are correct... wouldn't it be 
>relatively simple to modify the decoder software to favor the CAP vs 
>NWR alerts from NOAA... and IF it sees two such alerts that are 
>identical in every way EXCEPT the county list... to check to verify 
>the NWR version is indeed a subset of the CAP version.  And if so...