The State and Future of Interoperability for Atmospheric Composition Data
Work by the GEO AQ CoP, http://wiki.esipfed.org/index.php/GEO_AQ_CoP, toward data interoperability has resulted in growing support and demand for data access while at the same time identifying gaps in the supporting technologies and standards. The purpose of this session will be to assess current interoperability efforts, identify gaps and recommend next steps to improve data integration. This first session will contain short presentations by current AQ CoP data providers and users, to be followed by a second session focusing on specific community issues. A full agenda is under development on the wiki.
Introduction to GEO Air Quality Community of Practice GEO AQ CoP - Rudolf Husar
Intro speakers and program
Erin Robinson, ESIP, Internet
· ESIP is providing the network to connect the people in the air quality group. Sometimes using meeting space, and a few side meetings in Europe.
· ESIP supports the technical community to build the infrastructure to other communities such as Gia or other scientific applications
· If no ESIP there would be no AQ work group or group to set in the early phases of GEOSS from the community side
Stefan Falke, Northrop Grumman, VA
· Required 0.25 FTE in activities like ESIP
· AQ was one of 12 possible applications
· Community brought people together with shared challenges and uses, esp. shared model data as a neutral forum where topics could be addressed
· Community was building links and getting the right people together
· On the technical side, not inventing new things, but to reuse and connect these systems
· There was interactions from multiple communities, lots from NASA, EPA, and NOAA
· Goal to improve AQ data and easy the way of disseminating their data
· Q – “were” what is the status of these programs – is there is linkages
o This meeting is a way to reengage
o Not all or most even fall-over
o Can discuss today what is being done and new aspects of list
· Time line divided into brain storming, community building and information, and ‘continuous collaboration, then Connecting with GEOSS
o Wiki started in 2006 – great way to move things forward
o Timeline led to an interoperability cluster
o Last phase – connection to GEOSS – place where workgroup began to contribute tangible outcomes
§ The cataloging, the standardizing metadata… this was all done during this phase
o Became an ESIP “workgroup” which include funds and a broader visibility and representation
· Guiding Principles by Global Observing System of Systems (GEOSS)
o Any single data set can serve many applications, any single problem requires many data sets
o Let the information resource hide the network while pooling the resources
o For those that need data – they just uses data without the difficult paths in the user space
· When approach GEOSS, AQ group was already advanced
o CGI (geoss common infrastructure)
o AQ loaded data via Erin’s work, revised Ufind (metadata browser/catalogue was developed during this time)
· There was other things that GEO was asking AQ to do
· GEOSS defined requirements include use standards and data
· What is the current situation
o Currently 3 region clusters – one is this room (ESIP AQ Workgroup)
o In Europe – begun process of organizing/harmonizing European AQ by Martin Schultz
o Within Indian technological system – they had talent and need for AQ but frustrated by lack of connection (old project had ended activity)
· Outputs
o GEOSS common infrastructure – got the data to flow, register, find, and access data
o Prepared docs
o Organized topical workshops
o Facilitated interoperable AQ data network
· Tour of wiki/ GEO AQ CoP
o CoP = community of practice
o All activities – set up workspace on esip wiki
o Have chronological news list
o Talk page àProblem – find data is saved in different places (data can be changed)
§ Have ecosystem of data
§ Discussion pages always exist
o Paired data of managers and programs (3 from EU and 2 from US)… to compare notes to connect notes
§ Helped with understanding why we have problems
§ Other kind than esip type of communications
Martin Schultz – GEO AQ/CoP and OWS activities at Institute for Energy and Climate Research 8: Proposphere (IEK-8) – Trace Gas and Aerosol Processes in the Troposphere
· 85% are mini gaged measurements – sort of orthagonnal to other activities
· IEK -8 Activities
o Contribution to GEO work plan, different communication and workshops
o Created mailing list
o Confusion as to what stands for and who is responsible for what in GEO AQ
o Demonstrate interoperability – TFHTAP and MACC
§ Demonstrated that data can be access through the web between different institutions
· GEO AQ coP – working groups are growing…propose next workshop in Boulder, CO
· Julich OWS Interface (JOIN
o Have several local data areas (some include near real time data (24h)
o Have external databases
o Have interface and data access model – produce plots of information
· Catalogue list is already outdata
o Highlighted the external local datasets
o Need to go beyond data provisions
o Want to make data usable
o Even with common standards, problems linking external data sets
· Examples
o Able to do analysis without having to download GB of un-used data
o Provide standardize data sets for model interpretation
· Next steps
o MACC wants better user management
o Because hosting MACC data – there needs to be a better link (not through the front page)
o Finish group practices for publishing metadata records
o HTAP will be meeting in Geneva in March
· Q is the JOIN system is ready for users or is it still under development
o Yes – put online yesterday
o Still one issue with apache server, but it is working
o Working on documentation
· Q is the test system still available (580 port)
o Until the end of the month
o Include changes to catalogue names
·
Claire Granier
· ECCAD (Emissions of atmospheric Compounds and Compilation of Ancillary Data)
· Goal is to work with emission data & analyze data and provide to community
· ETHER – connected to international world
· Need to work on user friendly tools
· At request – ECCAD can handle greenhouse gasses
· Eccad.sedoo.fr Introduction to GEO Air Quality Community of Practice GEO AQ CoP - Rudolf Husar
Intro speakers and program
Erin Robinson, ESIP, Internet
· ESIP is providing the network to connect the people in the air quality group. Sometimes using meeting space, and a few side meetings in Europe.
· ESIP supports the technical community to build the infrastructure to other communities such as Gia or other scientific applications
· If no ESIP there would be no AQ work group or group to set in the early phases of GEOSS from the community side
Stefan Falke, Northrop Grumman, VA
· Required 0.25 FTE in activities like ESIP
· AQ was one of 12 possible applications
· Community brought people together with shared challenges and uses, esp. shared model data as a neutral forum where topics could be addressed
· Community was building links and getting the right people together
· On the technical side, not inventing new things, but to reuse and connect these systems
· There was interactions from multiple communities, lots from NASA, EPA, and NOAA
· Goal to improve AQ data and easy the way of disseminating their data
· Q – “were” what is the status of these programs – is there is linkages
o This meeting is a way to reengage
o Not all or most even fall-over
o Can discuss today what is being done and new aspects of list
· Time line divided into brain storming, community building and information, and ‘continuous collaboration, then Connecting with GEOSS
o Wiki started in 2006 – great way to move things forward
o Timeline led to an interoperability cluster
o Last phase – connection to GEOSS – place where workgroup began to contribute tangible outcomes
§ The cataloging, the standardizing metadata… this was all done during this phase
o Became an ESIP “workgroup” which include funds and a broader visibility and representation
· Guiding Principles by Global Observing System of Systems (GEOSS)
o Any single data set can serve many applications, any single problem requires many data sets
o Let the information resource hide the network while pooling the resources
o For those that need data – they just uses data without the difficult paths in the user space
· When approach GEOSS, AQ group was already advanced
o CGI (geoss common infrastructure)
o AQ loaded data via Erin’s work, revised Ufind (metadata browser/catalogue was developed during this time)
· There was other things that GEO was asking AQ to do
· GEOSS defined requirements include use standards and data
· What is the current situation
o Currently 3 region clusters – one is this room (ESIP AQ Workgroup)
o In Europe – begun process of organizing/harmonizing European AQ by Martin Schultz
o Within Indian technological system – they had talent and need for AQ but frustrated by lack of connection (old project had ended activity)
· Outputs
o GEOSS common infrastructure – got the data to flow, register, find, and access data
o Prepared docs
o Organized topical workshops
o Facilitated interoperable AQ data network
· Tour of wiki/ GEO AQ CoP
o CoP = community of practice
o All activities – set up workspace on esip wiki
o Have chronological news list
o Talk page àProblem – find data is saved in different places (data can be changed)
§ Have ecosystem of data
§ Discussion pages always exist
o Paired data of managers and programs (3 from EU and 2 from US)… to compare notes to connect notes
§ Helped with understanding why we have problems
§ Other kind than esip type of communications
Martin Schultz – GEO AQ/CoP and OWS activities at Institute for Energy and Climate Research 8: Proposphere (IEK-8) – Trace Gas and Aerosol Processes in the Troposphere
· 85% are mini gaged measurements – sort of orthagonnal to other activities
· IEK -8 Activities
o Contribution to GEO work plan, different communication and workshops
o Created mailing list
o Confusion as to what stands for and who is responsible for what in GEO AQ
o Demonstrate interoperability – TFHTAP and MACC
§ Demonstrated that data can be access through the web between different institutions
· GEO AQ coP – working groups are growing…propose next workshop in Boulder, CO
· Julich OWS Interface (JOIN
o Have several local data areas (some include near real time data (24h)
o Have external databases
o Have interface and data access model – produce plots of information
· Catalogue list is already outdata
o Highlighted the external local datasets
o Need to go beyond data provisions
o Want to make data usable
o Even with common standards, problems linking external data sets
· Examples
o Able to do analysis without having to download GB of un-used data
o Provide standardize data sets for model interpretation
· Next steps
o MACC wants better user management
o Because hosting MACC data – there needs to be a better link (not through the front page)
o Finish group practices for publishing metadata records
o HTAP will be meeting in Geneva in March
· Q is the JOIN system is ready for users or is it still under development
o Yes – put online yesterday
o Still one issue with apache server, but it is working
o Working on documentation
· Q is the test system still available (580 port)
o Until the end of the month
o Include changes to catalogue names
·
Claire Granier
· ECCAD (Emissions of atmospheric Compounds and Compilation of Ancillary Data)
· Goal is to work with emission data & analyze data and provide to community
· ETHER – connected to international world
· Need to work on user friendly tools
· At request – ECCAD can handle greenhouse gasses
· Eccad.sedoo.fr