OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.

 


Help: OASIS Mailing Lists Help | MarkMail Help

emergency-comment message

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]


Subject: Re: [emergency-comment] Re: [emergency-cap-profiles] Preliminary thoughts on a few of Jacob's latest comments


> 1)  The area covered by a radio station's signal (or the operational 
> area defined by the state EAS plan, or the area targeted by the 
> program director) often has little to do with where the GPS receiver might be.

Yes of course.  If the transmitter and EAS unit were in the same location, the easy setup might ask the estimated transmit radius along with the GPS coords to produce a very simple circle.  A more advanced setup feature might allow the input of a polygon with the operational area instead.  This advanced feature could certainly help with transmission sites that straddle jurisdictional borders.

> 2)  Unless there is one agreed upon database of FIPS area polygons to 
> use, having each manufacturer compute what FIPS code a CAP alert is 

The US Census Bureau publishes boundary files http://www.census.gov/geo/www/cob/bdy_files.html  Could these be used as the agreed upon standard?  Also just thinking boundary file standards, geospatial allows the NWS to use UGC directly and solve UGC versus FIPS misalignments as well as future storm warning based polygons.

> EAS renderers don't spin off undetectable duplicates.  If the 
> originator supplies the information, as least all downstream devices 
> can still easily generate the identical ZCZC string.

The SAME location codes would be identified as legacy support and as such many originators will still use them to support legacy equipment still in the field, I don't think they'll be disappearing.  However by remaining as legacy, it does allow other IPAWS exchange partners, and new advanced EAS equipment, to move forward with better alert targeting to resolve over-alerting and spillover concerns.  I have some flowcharts and samples that I could donate to the industry group that might help.

-- 
jake@jpw.biz
--


[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]