AQ Cluster Meeting Notes

From Earth Science Information Partners (ESIP)
The printable version is no longer supported and may have rendering errors. Please update your browser bookmarks and please use the default browser print function instead.

Back to: Air_Quality_Session:_17th_Federation_meeting_highlights
These notes are a partial recording, please add to/edit this. Help editing the wiki

July 20, 2006 10:30 -12

  • Introduction: R.Husar
  • Unidata: Mohan
    • Created to provide data to community (30 streams) - 200 universities in subscription service worldwide (U.S., Latin America)
      • Universities primary audience, but not the sole audience. System is open.
      • Also redistribution of data once reaches the university - other applications like public health.
    • Important aspect to this cluster netCDF - HDF IO in 6-9 months
    • Started as meteorological data, but become increasingly more interdisciplinary e.g. hydrology, AQ data, etc
    • Brokers agreements between data providers and use
    • AQ Community also has need for atmospheric datasets so the flow is two ways
    • Unidata is a community of communities (oceanography, GIS, AQ)
  • Husar: Thrilled to have Unidata offer to distribute AQ data. Portal idea: move data from provider to user - centralized approach. Distributed approach, move data as close to user as you can get - surface area approach, putting it in as many places as you can - multiple paths to the same place. RSS - provider publishes whoever subscribes can have it in their home setting, Unidata is an RSS system. Bring individual projects into the cluster?
    • Function of ESIP - at first required to be there and it took a while to set own direction and should be self-motivated.
    • ex. DataFed - We keep pushing certain activities harder than others, will that help or choke cluster activities?
    • Clusters microcosom of federation - group finds internal dynamic that works.
    • frank lindsay:" Could have a "my air quality" portal that is custom configured (alal Google personal page). We need a framework for bringing portlets together. Plenty of users have been identified by agencies. Cluster should focus on identifying users but on getting content to them in right way.
    • other: Need to engage users and incorporate their feedback rather than one-way selling job of data and services. Should not simply collect content - need to provide better ways to use it.
  • Public Health Cluster - Bill Teng
    • January meeting covered the scope of community looking for potential partnerships, (int. society of disease survelliance, pan-american health org, CDC) (January Meeting Highlights)
      • Determine needs of user community - fostering relationship between providers and users and how do we grow the community.
      • What other clusters could we coordinate with? (AQ and Water quality)
      • At end of meeting had an e-mail list, but cluster is still not stable.
    • This meeting - identify specific projects, collaboration with AQ very natural
    • Discussion about data products fitting with user needs
  • Wrap-up Session - Husar
    • Portals - resources galore. Coherent presentation and portals seem ideal medium, helping users lay out
    • Use Case connecting/networking to illustrate and test system
    • Public Health - No reason use case shouldn't include public health with impact in near-realtime.