[EAS] Ira's Comments

[Harold Price]

Yes, that would seem to be a better solution, except...  Way back 
when, the FCC allowed States or local areas to invent their own event 
codes - there was language in the rules that permitted it with FCC 
approval.  Sage, at least, allowed for the user to add an event code 
in the EEPROM through the serial port, in the field.  The FCC did not 
allow the creation of new originator codes, so adding a new 
originator code would need a ROM update.  Painful.  Adding an event 
code would require a ROM update for some legacy units, adding an 
originator would require a ROM update for nearly all legacy 
units.  All legacy users would need to update their filters for a new 
event or a new originator.

Another issue with updating legacy EAS to a new originator code is 
the NOAA NWS transmitters, which are used in some areas to relay some 
EAS messages, and would likely also need to be updated to handle the new codes.

FYI, in the Sage EAS/CAP device, we implement the must carry element 
as specified by the IPAWS profile.  By default, so that you don't 
have to change filters, we handle the GMC by looking at your required 
monthly test filter - if the alert is GMC, and the location 
intersects the list in the RMT filter, then it goes on the air by the 
RMT filter's rules.  If you want to handle the GMC in a different 
way, you can build a filter with a name of GOVMUSTCARRY that 
specifies actions to take, and the area to match.  By the IPAWS spec, 
we look only at the GMC flag and the location in deciding whether or 
not to carry the alert.  That also solves the problem where you are 
on the boarder of multiple states, and you want to carry GMC alerts 
for more than one state - if the alert is GMC and is for a county in 
your GOVMUSTCARRY filter's list, you will carry it.  As usual, it 
takes longer to explain than it does to do.

Harold

At 12:48 PM 4/5/2011, Lowell Kiesow wrote:
>How about making GMC an originator code instead of an event code?
>
>At 06:52 AM 4/5/2011, you wrote:
> >There is another difference with EAN - it has no time limit.
> >
> >There are other problems with "overloading" the EAN with other
> >functions, such as the 31 location code problem, that tend to make
> >all EANs national events.
> >
> >Adding a GMC event code will cause legacy devices to say "The Civil
> >Authorities has issued a Governors Must Carry for all of Pennsylvania".
> >
> >Harold
> >
> >At 09:43 PM 4/4/2011, Eric Adler wrote:
> > >I, too, had thought about this but, from what I understand, GMC
> > >can't become EAN as the presidential message must override _all_
> > >messages, including GMC.
> > >Eric
>
>          Lowell Kiesow, Chief Engineer
>          KPLU 88.5, KVIX 89.3, KPLI 90.1
>          www.kplu.org  www.jazz24.org
>
>_______________________________________________
>This is the EAS Forum Discussion List
>
>Please invite your friends to join our Forum!
>http://lists.radiolists.net/mailman/listinfo/eas
>
>And, remember the main page: http://eas.radiolists.net