[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: Re: CAP Exchange
Count me in, Jeff! Eliot At 06:23 AM 7/13/2005, Jeff Harrison wrote: >All: > >The Sensor Alert Service IE is a good idea. However, I am wondering >whether or not something more immediate might be called for given that >USGS, NOAA, CDC, and all other Federal agencies to some extent, are >required to implement CAP for all public alerts and notifications this year. > >What I have in mind is a "virtual" CAP exchange that challenges >participants to - > >1) exchange a GML file containing CAP alert messages between systems >2) access GML content from a WFS service that can deliver the CAP alerts >as map features on request >3) Provide feedback on the structure of GML and features needed to support >information exchange > >We could use the information contained in - > >http://www.usgs.gov/hazard_alert/alerts/capgml.xml > >and get started in a "come as you are fashion" and see what can be done >with the "test CAP" above. Goals would be to exchange the CAP messages >above among software components and participants providing immediate >feedback on the structure of GML and features needed to function within >RSS feeds like the one at http://www.usgs.gov/hazard_alert/alerts/rss.xml >(and other message formats). Results of the CAP exchange would be >documented rapidly and provided as feedback to interested parties. > >Thoughts welcome and we'd be happy to get started right away. > >Regards, >Jeff > >Jeff Harrison | The Carbon Project | www.TheCarbonProject.com >Phone (703) 491 9543 | Mobile (703) 628 8655 > > >----- Original Message ----- From: "George Percivall" ><percivall@opengeospatial.org> >To: "Eliot Christian" <echristi@usgs.gov> >Cc: "Jeff Harrison" <jharrison@thecarbonproject.com>; "Doug Nebert" ><ddnebert@usgs.gov>; "Bill Miller" <bmiller@usgs.gov>; "Bob Bunge" ><robert.bunge@noaa.gov>; "Chris Tucker" <"tucker"@ionicenterprise.com>; >"Jeff Yutzler" <jeff@ionicenterprise.com>; "Peter Vretanos" ><pvretano@cubewerx.com>; "Ron Lake" <rlake@galdosinc.com>; ><ddanko@esri.com>; <rob@socialchange.net.au>; "Martin Daly" ><Martin.Daly@cadcorp.com>; "Markus Mueller" <mueller@lat-lon.de>; "Greg >Yetman" <gyetman@ciesin.org>; "Art Botterell" <acb@incident.com>; ><ngoldstein@thecarbonproject.com>; "Bob Wyman" <bob@wyman.us>; "Neil >Bourgeois" <bourgenc@battelle.org>; "Travis Hubbard" ><HubbardT-c@battelle.org>; "Gary Ham" <hamg@battelle.org>; "David >Oppenheimer" <oppen@usgs.gov>; "Jeff Sloan" <jlsloan@usgs.gov>; "Jill >Cress" <jjcress@usgs.gov>; "Ed Zimmermann" <edz@bsn.com>; "Ivan B >DeLoatch" <ideloatch@usgs.gov>; "Johnny Tolliver" <tolliverjs@ornl.gov>; >"EM GIS SC" <emergency-gis@lists.oasis-open.org> >Sent: Sunday, July 10, 2005 3:02 PM >Subject: Re: Web Feature Service for CAP alerts > > >>Eliot, >> >>OGC recently began a Sensor Alert Service (SAS) Interoperability Experiment >>(IE). The SAS IE announcement includes a reference to CAP: >>http://www.opengeospatial.org/press/?page=pressrelease&year=0&prid=225 >> >>The IE participants will decide if CAP is used in the IE. You are encouraged >>to bring the FDGC point of view as a participant in the IE. Contact me and >>we will get you involved. >> >>Regards, >>George >> >> >>On 7/7/05 5:47 PM, "Eliot Christian" <echristi@usgs.gov> wrote: >> >>>This year, USGS, NOAA, CDC, and all other Federal agencies >>>to some extent, are required to implement CAP for all public >>>alerts and notifications. Such CAP alerts will be available >>>typically as an RSS feed, e.g., http://www.weather.gov/alerts >>>or http://www.usgs.gov/hazard_alert/alerts/rss.xml >>> >>>A CAP alert is designed to describe a hazardous event, and >>>a given CAP message can designate more than one area. For >>>instance, a CAP message about a tornado might designate >>>one area as "evacuate" and a larger surrounding area as >>>"shelter in place". (I suppose the larger one ought to >>>have a hole corresponding to the smaller one, but that >>>may be an aside point for now.) >>> >>>In any case, each feature offered by a Web Feature Service >>>(WFS) should be associated with one particular area. So, we >>>need to "flatten" the CAP alert structure and make a set of >>>place-specific copies. In the tornado example, we should >>>have one WFS feature for the "evacuate" area and another >>>WFS feature for the "shelter in place" area. >>> >>>I posted a CAP Implementors Note about this two years ago >>>and I am now drafting an update of that Note (my draft is >>>at http://www.usgs.gov/hazard_alert/ImplementorsNote.doc ). >>> >>>So, we can have a GML file containing CAP alert messages >>>that have been converted into featureMember elements within >>>a WFS featureCollection. My example of such a file is at >>>http://wwww.usgs.gov/hazard_alert/alerts/capgml.xml . >>> >>>As I understand the overall OGC architecture for displaying >>>maps, we need to serve this GML content from a WFS service >>>that can deliver the CAP alerts as map features on request. >>> >>>I'd appreciate help on this from anyone who uses the OGC >>>open standards for getting CAP alerts displayed on maps. >>> >>>Of course, corrections or comments on any of my text or >>>example stuff would be greatly appreciated! >>> >>>Eliot >>> >>> >>>Eliot Christian, USGS, 590 National Center, Reston VA 20192 >>>cell: 571-212-8294 office: 703-648-7245 fax: 703-648-7112 >> >>George Percivall >>Executive Director, Interoperability Architecture >>Open Geospatial Consortium >>E-mail: percivall@opengeospatial.org >>Voice: 1+301-560-6439 >> >> >> >>**************************************************************************** >>This communication, including attachments, is for the exclusive use of >>addressee and may contain proprietary, confidential or privileged >>information. If you are not the intended recipient, any use, copying, >>disclosure, dissemination or distribution is strictly prohibited. If you are >>not the intended recipient, please notify the sender immediately by return >>email and delete this communication and destroy all copies. >>**************************************************************************** >> >> >>
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]