August 31 Drought Telecon

posted Aug 31, 2010, 7:56 AM by Joshua Lieberman   [ updated Sep 1, 2010, 4:50 AM by Will Pozzi ]

Attending:

Ken Korporal (hosting), Stefan Niemeyer, Mike Brewer, Justin Sheffield, Richard Heim, Doug Cripe, Al Howard, Will Pozzi (moderator), Josh Lieberman, and Mattia Santoro

Discussion:

Will: The European Drought Observatory, the Princeton African Drought Monitor, and the North American Drought Monitor (including the National Integrated Drought Information System (NIDIS) demarcate the envelopes of drought zones using Standard Precipitation Index (SPI) or Soil Moisture Anomalies, by using Land Surface Models or hydrological models, such as LISFLOOD, VIC, or NLDAS soil moisture ensemble product.  One can separate the application software from the mapping software which maps the final output of the model, so that a common mapping software has the capability to map the products of each of these systems. The basic idea (and the idea behind AIP) is to have a decision support application client accessible on the GEOSS Water Societal Benefit Area web page that will be accessible that will display the drought mapping.   We have to ask ourselves what is achievable in terms of meeting the very tight deadline of providing a taped video demo in time for the Beijing Earth Observation Summit.

Al: Where will this video be displayed?

Will (with Josh): Through the Architecture and Data Committee (ADC), AIP will be preparing videos for each Societal Benefit Area that has been undertaking work through the AIP process.  IGWCO is also preparing a hand out brochure, and the Sustainable Agriculture Community of Practice will also have a booth or side-event.  I believe the duration of the taping is about 20 or 30 minutes.

Josh: Some of the AIP-3 taped events may only last 3 minutes; others may be much longer

Will: Since we went to a lot of effort to get Stefan, Mike, and Justin together here, let's move our focus back to the question: how do we achieve interoperability among the three systems?  Mike has a global mapping web service running at NIDIS, as does Stefan.

Justin: we don't have a mapping web service up and running.

Will: Not to ask any embarrassing question, but why does the African Drought Monitor not have more products beyond April?

Justin: Ah, we ran out of our funding on the project (UNESCO).

Mike: We can use the NIDIS mapping web service: (  http://www.drought.gov/portal/server.pt/community/drought.gov/map_viewer ). Richard and I have been thinking about global content to display on this map.

Stefan: We should stay focused on a tight achievable end.  Even linking together these three systems will be a major accomplishment. 

Will: Richard, do you have any other drought information--what Mike was referring to?  I know that Australia Bureau of Meteorology has some drought (actually precipitation deficiency mapping) that we have not yet included.

Doug: Given the drought in Russia, including Russia would be a good idea, if it is possible.

Richard: We (NCDC) have some Russian datasets available, but not yet processed into usable form.

Will: I tried to locate a Russia drought monitoring product and was unsuccessful.

Stefan: We looked into this; having the ability to verify drought products is very difficult to do over Russia.  But given the tight timeline we should focus on the three systems.

Will: There are two parallel time tracks: AIP-3 and AIP-4.  What Stefan says of AIP-3 is certainly true.  For AIP-4, Richard, what drought monitoring efforts are you aware of in South America?

Richard: Based upon our April meeting, we decided that a global network should be bottom up, not top down.  Look at continent by continent capability. Countries within each continent have specific problems with providing information. Some countries can contribute, but bringing them all along is a challenge.

Doug: We should stay on a tight, achievable goal.

Immediate need is to pull present dataservices together and see if it makes a reasonable story for a demo.

Josh: There is still the need to consider registration within the GEOSS Common Registry.

Mike: NIDIS is already registered.

Will: Justin, is there any problem about registering the Princeton African Drought Monitor?

Josh: three threads would need to be followed for a feasible demo in the next few weeks:
  1. Content: exchange and examine available data to see whether it makes a reasonable demo story
  2. Access: publish all data as WMS if it isn't yet available.
  3. Discovery: register the data services and sets so that they can be discovered in the Clearinghouse (by a knowledgable user)
  4. (Will) Interoperability can include syntactic interoperability (consistent formatting of data; common ability to ingest data; etc); developing a broker to achieve interoperability; and semantic interoperability to ensure that the GEOSS Common Architecture is current with Web 3.0.  Mediation: Use the EuroGEOSS broker and water (and drought) ontology to support semantic augmented queries within EuroGEOSS broker.
Will: We need to not only use the NIDIS global map as an integrator for these three systems but also the EDO web map server.  That way we can test Stefano and Mattia's system, i.e., the augmented search capability.

Stefan / Mattia: at least some of the various European data sources (Spain, Drought Management Center for Southeast Europe) could be linked to the EuroGEOSS broker, if not all of them.

Al: This sort of demo would of interest to display in both Water Cycle and Sustainable Agriculture booths. Good to keep the focus narrow to produce something usable. Should we hold a side event?  Would Ministerial people be present?

Doug: They are probably on a tight schedule.

Actions:


Exchange of data links and sets by email to see whether there is a critical mass of data, to be followed by discussion of logistics and schedule another call in 2 weeks or so.

Comments