Unidata 2020: Geoscience at the Speed of Thought Draft Action Plan
Unidata 2020: Geoscience at the Speed of Thought Draft Action Plan
Unidata 2020: Geoscience at the Speed of Thought Draft Action Plan
Create successful ePaper yourself
Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.
<strong>Unid<strong>at</strong>a</strong> <strong>2020</strong>:<br />
<strong>Geoscience</strong> <strong>at</strong> <strong>the</strong><br />
<strong>Speed</strong> <strong>of</strong> <strong>Thought</strong><br />
<strong>Draft</strong> <strong>Action</strong> <strong>Plan</strong><br />
April 2012<br />
<strong>Unid<strong>at</strong>a</strong> Program Center<br />
UCAR Office <strong>of</strong> Programs<br />
P.O. Box 3000<br />
Boulder, CO 80307-3000<br />
www.unid<strong>at</strong>a.ucar.edu<br />
Mohan Ramamurthy, Director<br />
Page 1
Introduction<br />
This document defines specific actions envisioned by <strong>Unid<strong>at</strong>a</strong>’s development, community<br />
services, administr<strong>at</strong>ion, and inform<strong>at</strong>ion technology groups to work toward <strong>the</strong> goals<br />
outlined in <strong>the</strong> 2012 str<strong>at</strong>egic plan.<br />
Goal:<br />
Enable widespread, efficient access to geoscience d<strong>at</strong>a<br />
Seamless access to d<strong>at</strong>a is essential for advancing educ<strong>at</strong>ion and research. To ensure th<strong>at</strong> <strong>the</strong><br />
geoscience research and educ<strong>at</strong>ion community gains access to <strong>the</strong> d<strong>at</strong>a it needs, we will:<br />
• Distribute <strong>at</strong>mospheric and o<strong>the</strong>r geoscience d<strong>at</strong>a in real time<br />
• Develop innov<strong>at</strong>ive cyberinfrastructure solutions to facilit<strong>at</strong>e dissemin<strong>at</strong>ion <strong>of</strong> scientific<br />
d<strong>at</strong>a<br />
• Work with d<strong>at</strong>a providers to make geoscience d<strong>at</strong>a freely available for advancing research<br />
and educ<strong>at</strong>ion<br />
• Develop and maintain <strong>the</strong> computing and networking infrastructure necessary to keep<br />
<strong>the</strong> growing volume <strong>of</strong> d<strong>at</strong>a flowing reliably and in a timely manner<br />
Development group actions supporting <strong>the</strong>se goals<br />
1. Maintain, coordin<strong>at</strong>e, and support LDM/IDD infrastructure and community.<br />
Timetable<br />
Staff<br />
Resources<br />
Progress<br />
Indic<strong>at</strong>ors<br />
2. Maintain, coordin<strong>at</strong>e, and support d<strong>at</strong>a ingest (NOAAPort, McIDAS GOES, etc.)<br />
Timetable<br />
Staff<br />
Resources<br />
Progress<br />
Indic<strong>at</strong>ors<br />
3. Improve document<strong>at</strong>ion <strong>of</strong> d<strong>at</strong>asets available over IDD and how to access <strong>the</strong> d<strong>at</strong>a.<br />
Timetable<br />
Staff<br />
Resources<br />
Progress<br />
Indic<strong>at</strong>ors<br />
4. Investig<strong>at</strong>e mo<strong>the</strong>rlode server redundancy. For instance:<br />
- Cloud-like capabilities and how <strong>the</strong>y might impact <strong>the</strong> IDD, TDS, RAMADDA.<br />
- Unique, resolvable IDs (e.g., <strong>the</strong> Handle System and DOI) th<strong>at</strong> support resolution to<br />
multiple resolution points.<br />
Page 2
Timetable<br />
Staff<br />
Resources<br />
Progress<br />
Indic<strong>at</strong>ors<br />
5. Improve usability <strong>of</strong> <strong>the</strong> LDM:<br />
Timetable<br />
Staff<br />
Resources<br />
Progress<br />
Indic<strong>at</strong>ors<br />
- Add an LDM Config GUI<br />
- Convert LDM queue to use virtual buffer<br />
6. <strong>Unid<strong>at</strong>a</strong>-in-a-Box: VMware app with LDM, TDS, RAMADDA, already installed<br />
Timetable<br />
Staff<br />
Resources<br />
Progress<br />
Indic<strong>at</strong>ors<br />
7. Investig<strong>at</strong>e closer ties between IDD/LDM and TDS<br />
Timetable<br />
Staff<br />
Resources<br />
Progress<br />
Indic<strong>at</strong>ors<br />
8. Investig<strong>at</strong>e PubSub, P2P, Messaging (AMQP/ZeroQP), etc. Work with o<strong>the</strong>r groups, e.g.,<br />
OGC PubSub SWG, iRODS.<br />
Timetable<br />
Staff<br />
Resources<br />
Progress<br />
Indic<strong>at</strong>ors<br />
9. Standing query/filter on d<strong>at</strong>a streams (PubSub with query/filter)<br />
Timetable<br />
Staff<br />
Resources<br />
Progress<br />
Indic<strong>at</strong>ors<br />
Community Services group actions supporting <strong>the</strong>se goals<br />
1. Work with governing committees and d<strong>at</strong>a providers to negoti<strong>at</strong>e for d<strong>at</strong>a, model output<br />
and observ<strong>at</strong>ional d<strong>at</strong>a deemed important for teaching and research.<br />
Page 3
Timetable<br />
Staff<br />
Resources<br />
Progress<br />
Indic<strong>at</strong>ors<br />
This is an ongoing project<br />
2. Foster collabor<strong>at</strong>ions with providers <strong>of</strong> d<strong>at</strong>a, i.e., MADIS, NCEP, NCDC, NOAA/NWS,<br />
Lightning, Radar, and follow new developments leading to future opportunities.<br />
Timetable This is an ongoing project<br />
Staff<br />
Resources<br />
Progress<br />
Indic<strong>at</strong>ors<br />
3. Coordin<strong>at</strong>e with <strong>Unid<strong>at</strong>a</strong> technical staff to ensure <strong>Unid<strong>at</strong>a</strong> technologies are comp<strong>at</strong>ible<br />
with each o<strong>the</strong>r.<br />
Timetable This is an ongoing project<br />
Staff<br />
Resources<br />
Progress<br />
Indic<strong>at</strong>ors<br />
4. Augment <strong>the</strong> <strong>Unid<strong>at</strong>a</strong> web site d<strong>at</strong>a pages with clear, easy to follow instructions<br />
describing how to retrieve each type <strong>of</strong> d<strong>at</strong>a.<br />
Timetable This is an ongoing project<br />
Staff<br />
Resources<br />
Progress<br />
Indic<strong>at</strong>ors<br />
Answer <strong>the</strong>se questions, as a start:<br />
- wh<strong>at</strong> s<strong>of</strong>tware do I need?<br />
- How do I get <strong>the</strong> d<strong>at</strong>a?<br />
- Should I access <strong>the</strong> d<strong>at</strong>a remotely or copy it to a local server?<br />
5. Regularize <strong>Unid<strong>at</strong>a</strong> web site s<strong>of</strong>tware pages so community members can easily find<br />
inform<strong>at</strong>ion relevant to each piece <strong>of</strong> technology, so as to be able to understand how it fits<br />
in <strong>Unid<strong>at</strong>a</strong>’s overall <strong>of</strong>ferings, how it compares to o<strong>the</strong>r solutions, and how to install or<br />
implement it.<br />
Timetable This is an ongoing project<br />
Staff<br />
Resources<br />
Progress<br />
Indic<strong>at</strong>ors<br />
6. Use <strong>Unid<strong>at</strong>a</strong>’s various media streams (web site, e-mail lists, blogs, social media, etc.) to<br />
communic<strong>at</strong>e d<strong>at</strong>a <strong>of</strong>ferings to community members.<br />
Timetable This is an ongoing project<br />
Staff<br />
Resources<br />
Progress<br />
Indic<strong>at</strong>ors<br />
Page 4
Administr<strong>at</strong>ive group actions supporting <strong>the</strong>se goals<br />
1. Work with <strong>Unid<strong>at</strong>a</strong> staff to ensure th<strong>at</strong> each staff member has <strong>the</strong> administr<strong>at</strong>ive support<br />
necessary to facilit<strong>at</strong>e <strong>the</strong>ir work such as travel support, contract and purchasing support,<br />
proposal development support and human resource support<br />
Timetable<br />
Staff<br />
Resources<br />
Progress<br />
Indic<strong>at</strong>ors<br />
2. Collabor<strong>at</strong>e on <strong>the</strong> <strong>Unid<strong>at</strong>a</strong> website pages providing maintenance and upkeep on relevant<br />
administr<strong>at</strong>ive areas such as proposal tracker, personnel inform<strong>at</strong>ion and links to various<br />
funding opportunities.<br />
Timetable<br />
Staff<br />
Resources<br />
Progress<br />
Indic<strong>at</strong>ors<br />
3. Provide administr<strong>at</strong>ive support to <strong>Unid<strong>at</strong>a</strong>’s governing committees through travel<br />
support and meeting facilit<strong>at</strong>ion<br />
Timetable<br />
Staff<br />
Resources<br />
Progress<br />
Indic<strong>at</strong>ors<br />
4. Provide budget and financial upd<strong>at</strong>es to <strong>the</strong> Director and program managers to help form<br />
str<strong>at</strong>egic plans supporting <strong>the</strong> goals set forth here<br />
Timetable<br />
Staff<br />
Resources<br />
Progress<br />
Indic<strong>at</strong>ors<br />
Inform<strong>at</strong>ion Technology group actions supporting <strong>the</strong>se goals<br />
1. To be added…<br />
Timetable<br />
Staff<br />
Resources<br />
Progress<br />
Indic<strong>at</strong>ors<br />
Page 5
2. To be added…<br />
Timetable<br />
Staff<br />
Resources<br />
Progress<br />
Indic<strong>at</strong>ors<br />
Page 6
Goal:<br />
Develop and provide open-source tools for effective use<br />
<strong>of</strong> geoscience d<strong>at</strong>a<br />
Faced with an abundance <strong>of</strong> scientific d<strong>at</strong>a, researchers and educ<strong>at</strong>ors need well-integr<strong>at</strong>ed,<br />
st<strong>at</strong>e-<strong>of</strong>-<strong>the</strong>-art tools to access, analyze, manage, and visualize <strong>the</strong> d<strong>at</strong>a. Because our<br />
experience shows us th<strong>at</strong> robust solutions arise from community and collabor<strong>at</strong>ive efforts, we<br />
will foster an open-source environment th<strong>at</strong> encourages collabor<strong>at</strong>ive s<strong>of</strong>tware development.<br />
In this context, and in cooper<strong>at</strong>ion with community members and o<strong>the</strong>r partners, we will<br />
develop and support open-source development approaches and s<strong>of</strong>tware solutions to:<br />
• Analyze, integr<strong>at</strong>e, and visualize heterogeneous geoscience d<strong>at</strong>a in two, three, and four<br />
dimensions<br />
• Enable visualiz<strong>at</strong>ion and effective use <strong>of</strong> very large d<strong>at</strong>a sets<br />
• Access, manage, and share collections <strong>of</strong> d<strong>at</strong>a from diverse sources<br />
Development group actions supporting <strong>the</strong>se goals<br />
1. Improve document<strong>at</strong>ion, standardize across s<strong>of</strong>tware packages<br />
Timetable<br />
Staff<br />
Resources<br />
Progress<br />
Indic<strong>at</strong>ors<br />
Advance <strong>the</strong> communities capabilities to analyze and visualize scientific d<strong>at</strong>a.<br />
2. Add and improve AWIPS2 document<strong>at</strong>ion and training m<strong>at</strong>erials.<br />
Timetable<br />
Staff<br />
Resources<br />
Progress<br />
Indic<strong>at</strong>ors<br />
3. Assist NCEP in <strong>the</strong> development and testing <strong>of</strong> AWIPS II d<strong>at</strong>abase access by GEMPAK<br />
programs<br />
Timetable<br />
Staff<br />
Resources<br />
Progress<br />
Indic<strong>at</strong>ors<br />
4. Add IDV scientific fe<strong>at</strong>ure type capabilities as CDM/netCDF-Java and TDS add new<br />
fe<strong>at</strong>ure types.<br />
Timetable<br />
Staff<br />
Resources<br />
Page 7
Progress<br />
Indic<strong>at</strong>ors<br />
5. Improve IDVs d<strong>at</strong>a access and export capabilities<br />
Timetable<br />
Staff<br />
Resources<br />
Progress<br />
Indic<strong>at</strong>ors<br />
- Support ability to select and subset a region from global<br />
d<strong>at</strong>asets th<strong>at</strong> crosses <strong>the</strong> seam in <strong>the</strong> underlying d<strong>at</strong>aset. (See<br />
netCDF item below, also JIRA issue TDS-143.)<br />
- Autom<strong>at</strong>ic subsetting <strong>of</strong> d<strong>at</strong>a based on current projection<br />
(and screen size/resolution?)<br />
- Support progressive resolution<br />
- Improve and extend d<strong>at</strong>a export capabilities<br />
6. Ensure AWIPS2 evolves to include any currently missing GEMPAK functionality<br />
Timetable<br />
Staff<br />
Resources<br />
Progress<br />
Indic<strong>at</strong>ors<br />
7. Work on (with collabor<strong>at</strong>ors) <strong>the</strong> development <strong>of</strong> AWIPS2 plug-ins to enable AWIPS2<br />
access to CDM d<strong>at</strong>a.<br />
Timetable<br />
Staff<br />
Resources<br />
Progress<br />
Indic<strong>at</strong>ors<br />
8. Improve <strong>the</strong> IDV's extensability and non-GUI utility<br />
Timetable<br />
Staff<br />
Resources<br />
Progress<br />
Indic<strong>at</strong>ors<br />
- Solidify, publish, and support an IDV API.<br />
- Improve server side functionality (with IDV web API?).<br />
9. IDV/THREDDS collabor<strong>at</strong>ion on server-side processing capabilities.<br />
Timetable<br />
Staff<br />
Resources<br />
Progress<br />
Indic<strong>at</strong>ors<br />
10. Work with GEMPAK community to transition support to <strong>the</strong> community.<br />
Timetable<br />
Staff<br />
Page 8
Resources<br />
Progress<br />
Indic<strong>at</strong>ors<br />
Advance <strong>the</strong> netCDF ecosystem<br />
Advance <strong>the</strong> netCDF ecosystem by advancing <strong>the</strong> capabilities <strong>of</strong> <strong>the</strong> netCDF file form<strong>at</strong>s and<br />
netCDF-based tools and utilities. As well as by advancing and developing CDM-like APIs<br />
(coordin<strong>at</strong>e-space, scientific fe<strong>at</strong>ure types) and rel<strong>at</strong>ed services (e.g., Web APIs).<br />
11. Improve <strong>the</strong> portability <strong>of</strong> <strong>the</strong> netCDF-C library<br />
Timetable<br />
Staff<br />
Resources<br />
Progress<br />
Indic<strong>at</strong>ors<br />
- Support Fortran 2003, 2008 (C interoperability)<br />
- Fully support Windows (for Visual Studio, 32- and 64-bit,<br />
DAP,Fortrans)<br />
- Perform on HPC pl<strong>at</strong>forms as well as HDF5<br />
12. Improve remote access (DAP4, server-side processing, streaming)<br />
Timetable<br />
Staff<br />
Resources<br />
Progress<br />
Indic<strong>at</strong>ors<br />
13. Provide compression as good as GRIB2 (working with NCAR/RAL and The HDF Group)<br />
Timetable<br />
Staff<br />
Resources<br />
Progress<br />
Indic<strong>at</strong>ors<br />
14. Support NetCDF as exchange form<strong>at</strong> (netCDF-4 file examples, CF conventions, etc.)<br />
Timetable<br />
Staff<br />
Resources<br />
Progress<br />
Indic<strong>at</strong>ors<br />
15. Develop ASCII to netCDF-CF converter for d<strong>at</strong>a logger d<strong>at</strong>a.<br />
Timetable<br />
Staff<br />
Resources<br />
Progress<br />
Indic<strong>at</strong>ors<br />
Page 9
16. Focus <strong>Unid<strong>at</strong>a</strong>'s decoder efforts on CDM/netCDF-Java<br />
Timetable<br />
Staff<br />
Resources<br />
Progress<br />
Indic<strong>at</strong>ors<br />
17. Make developing generic netCDF tools easier (higher-level APIs, test d<strong>at</strong>a, single-purpose<br />
utilities)<br />
Timetable<br />
Staff<br />
Resources<br />
Progress<br />
Indic<strong>at</strong>ors<br />
18. Increase <strong>the</strong> number <strong>of</strong> scientific d<strong>at</strong>a form<strong>at</strong>s and conventions from which<br />
georeferencing and fe<strong>at</strong>ure inform<strong>at</strong>ion can be extracted.<br />
Timetable<br />
Staff<br />
Resources<br />
Progress<br />
Indic<strong>at</strong>ors<br />
- File form<strong>at</strong>s:<br />
- netCDF-C: GRIB, radar, etc.<br />
- netCDF-Java: GeoTIFF, Shapefiles, FITS, etc.<br />
- Conventions and fe<strong>at</strong>ure types:<br />
- netCDF-C: Developer higher-level (CDM-like) APIs<br />
- netCDF-Java: UGRID, NPP, JPSS, sw<strong>at</strong>hs, s<strong>at</strong>ellite,<br />
polygonal regions<br />
19. Support netCDF access and CDM capabilities in o<strong>the</strong>r lanuage APIs (Python, C#/.NET,<br />
Javascript/DART)<br />
Timetable<br />
Staff<br />
Resources<br />
Progress<br />
Indic<strong>at</strong>ors<br />
- CDM Remote server (TDS-lite)<br />
- Python support: investig<strong>at</strong>e py4j<br />
20. Implement additional netCDF form<strong>at</strong> variants, e.g., CDF5 (aka "Big netCDF"), appendonly<br />
form<strong>at</strong> for fast writes, streaming; n<strong>at</strong>ive, for independence from HDF5<br />
Timetable<br />
Staff<br />
Resources<br />
Progress<br />
Indic<strong>at</strong>ors<br />
Advance server-side d<strong>at</strong>a services (discovery, access, processing)<br />
Page 10
21. Expand <strong>the</strong> variety <strong>of</strong> d<strong>at</strong>a sources th<strong>at</strong> can be supported<br />
Timetable<br />
Staff<br />
Resources<br />
Progress<br />
Indic<strong>at</strong>ors<br />
- Develop new ADDE servers as new d<strong>at</strong>a sources (typically<br />
s<strong>at</strong>ellite) become available.<br />
- Use TDS as driver on netCDF-Java support <strong>of</strong> new file form<strong>at</strong>s<br />
and conventions.<br />
- Support UGRID d<strong>at</strong>asets via OPeNDAP and o<strong>the</strong>r d<strong>at</strong>a access<br />
methods<br />
22. Continue improving TDS support for very large collections <strong>of</strong> files (e.g., NCDC's large<br />
d<strong>at</strong>a collections).<br />
Timetable<br />
Staff<br />
Resources<br />
Progress<br />
Indic<strong>at</strong>ors<br />
23. Support subsetting <strong>of</strong> global d<strong>at</strong>asets across seam (see IDV)<br />
Timetable<br />
Staff<br />
Resources<br />
Progress<br />
Indic<strong>at</strong>ors<br />
24. Expand and improve web services for point d<strong>at</strong>a collections.<br />
Timetable<br />
Staff<br />
Resources<br />
Progress<br />
Indic<strong>at</strong>ors<br />
25. Refactor TDS for performance and extensibility<br />
Timetable<br />
Staff<br />
Resources<br />
Progress<br />
Indic<strong>at</strong>ors<br />
- Simplify and expand user extensibility (plug-in capabilities)<br />
- Refactor THREDDS c<strong>at</strong>alog API<br />
- Refactor configur<strong>at</strong>ion st<strong>at</strong>e, including dynamic config.<br />
- Develop Web UI for TDS configur<strong>at</strong>ion<br />
26. Conduct regular security audits <strong>of</strong> all web applic<strong>at</strong>ions (TDS, RAMADDA):<br />
Timetable<br />
Staff<br />
Page 11
Resources<br />
Progress<br />
Indic<strong>at</strong>ors<br />
- Work with RAMADDA developers<br />
- Look for ways to autom<strong>at</strong>e this in regular build cycle.<br />
Community Services group actions supporting <strong>the</strong>se goals<br />
1. Coordin<strong>at</strong>e with <strong>Unid<strong>at</strong>a</strong> technical staff on open source tools, communic<strong>at</strong>e with <strong>the</strong><br />
community and provide desired document<strong>at</strong>ion and inform<strong>at</strong>ion for smooth transitions<br />
as changes evolve.<br />
Timetable This is an ongoing project<br />
Staff<br />
Resources<br />
Progress<br />
Indic<strong>at</strong>ors<br />
2. Develop document<strong>at</strong>ion, descriptions, inform<strong>at</strong>ion, and conduct community surveys via<br />
email, blog, web articles.<br />
Timetable This is an ongoing project<br />
Staff<br />
Resources<br />
Progress<br />
Indic<strong>at</strong>ors<br />
3. Provide present<strong>at</strong>ions as general outreach opportunities arise.<br />
Timetable This is an ongoing project<br />
Staff<br />
Resources<br />
Progress<br />
Indic<strong>at</strong>ors<br />
4. Provide a single, <strong>Unid<strong>at</strong>a</strong>-branded Open Source community experience, common to all<br />
<strong>Unid<strong>at</strong>a</strong> s<strong>of</strong>tware efforts. A community “hub” <strong>of</strong> this sort would provide a common<br />
interface for community use <strong>of</strong> and particip<strong>at</strong>ion in all <strong>of</strong> <strong>Unid<strong>at</strong>a</strong>’s s<strong>of</strong>tware products.<br />
We feel th<strong>at</strong> this is a very high priority project for <strong>Unid<strong>at</strong>a</strong> as a whole, and will require<br />
buy-in and actions by individuals across <strong>the</strong> organiz<strong>at</strong>ion.<br />
At least one branded, functioning Open Source community effort should be running by<br />
<strong>the</strong> end <strong>of</strong> 2012, with o<strong>the</strong>rs to follow as quickly as is feasible.<br />
Timetable<br />
Staff<br />
Resources<br />
Progress<br />
Indic<strong>at</strong>ors<br />
5. Move towards a standardized, web-based system for providing effective and up-to-d<strong>at</strong>e<br />
user document<strong>at</strong>ion for each s<strong>of</strong>tware package. This project may be influenced by<br />
decisions made in setting up Open Source communities.<br />
Timetable This project can be completed by ????<br />
Page 12
Staff<br />
Resources<br />
Progress<br />
Indic<strong>at</strong>ors<br />
6. Cre<strong>at</strong>e a series <strong>of</strong> product- and service-focused webcasts, demonstr<strong>at</strong>ing new, interesting,<br />
or difficult to explain fe<strong>at</strong>ures <strong>of</strong> <strong>Unid<strong>at</strong>a</strong> products. Webcasts would be short (1-3<br />
minutes) and would be cre<strong>at</strong>ed on an ongoing basis by developers and <strong>the</strong> Community<br />
Services group.<br />
Web infrastructure and an initial three to six webcasts can be<br />
Timetable<br />
finished by Fall 2012.<br />
Staff<br />
Resources<br />
Progress<br />
Indic<strong>at</strong>ors<br />
Administr<strong>at</strong>ive group actions supporting <strong>the</strong>se goals<br />
See previous goal section. No specific actions are rel<strong>at</strong>ed to development <strong>of</strong> Open Source<br />
tools.<br />
Inform<strong>at</strong>ion Technology group actions supporting <strong>the</strong>se goals<br />
1. To be added…<br />
Timetable<br />
Staff<br />
Resources<br />
Progress<br />
Indic<strong>at</strong>ors<br />
2. To be added…<br />
Timetable<br />
Staff<br />
Resources<br />
Progress<br />
Indic<strong>at</strong>ors<br />
Page 13
Goal:<br />
Provide cyberinfrastructure leadership in d<strong>at</strong>a<br />
discovery, access, and use<br />
The tools and techniques <strong>of</strong> distributed scientific computing are continually evolving.<br />
<strong>Unid<strong>at</strong>a</strong> provides inform<strong>at</strong>ion and leadership th<strong>at</strong> allow community members to better<br />
anticip<strong>at</strong>e, react to, or influence new developments. In order for <strong>the</strong> <strong>Unid<strong>at</strong>a</strong> community to<br />
benefit from changes in <strong>the</strong> scientific cyberinfrastructure landscape, we will:<br />
• Develop useful d<strong>at</strong>a models, frameworks, and protocols for geoscience d<strong>at</strong>a<br />
• Advance geoscience d<strong>at</strong>a and metad<strong>at</strong>a standards and conventions<br />
• Facilit<strong>at</strong>e d<strong>at</strong>a discovery mechanisms for quickly finding and accessing geoscience d<strong>at</strong>a<br />
• Evalu<strong>at</strong>e emerging cyberinfrastructure trends and technologies, providing inform<strong>at</strong>ion<br />
and guidance to community members<br />
Development group actions supporting <strong>the</strong>se goals<br />
1. Evalu<strong>at</strong>e emerging cyberinfrastructure trends and technologies, provide inform<strong>at</strong>ion and<br />
guidance to community members (use blogs, whitepapers, workshops, etc.)<br />
Timetable<br />
Staff<br />
Resources<br />
Progress<br />
Indic<strong>at</strong>ors<br />
2. Work with <strong>the</strong> OPeNDAP group to develop <strong>the</strong> DAP4 specific<strong>at</strong>ion, implement it in <strong>the</strong><br />
netCDF-C and -Java libraries as well as in <strong>the</strong> TDS, and to develop DAP4 conformance<br />
test suites for client and server.<br />
Timetable<br />
Staff<br />
Resources<br />
Progress<br />
Indic<strong>at</strong>ors<br />
3. Work with standards groups and various communities (e.g, CF, OGC, and NASA) on <strong>the</strong><br />
development <strong>of</strong> standards rel<strong>at</strong>ed to <strong>the</strong> earth sciences, including metad<strong>at</strong>a, d<strong>at</strong>a models,<br />
d<strong>at</strong>a access protocols, and real-time d<strong>at</strong>a distribution (e.g., OGC PubSub) standards.<br />
Timetable<br />
Staff<br />
Resources<br />
Progress<br />
Indic<strong>at</strong>ors<br />
4. Work with various groups to expand <strong>Unid<strong>at</strong>a</strong>'s server-side d<strong>at</strong>a access and processing<br />
capabilities. For instance, by adding OGC WFS, SOS, and WPS implement<strong>at</strong>ions and by<br />
working on asynchronous remote d<strong>at</strong>a access.<br />
Page 14
Timetable<br />
Staff<br />
Resources<br />
Progress<br />
Indic<strong>at</strong>ors<br />
5. Work with oper<strong>at</strong>ional we<strong>at</strong>her services (WMO, NCEP, ECMWF e.g.) to develop and<br />
standardize a registr<strong>at</strong>ion service for GRIB and BUFR tables.<br />
Timetable<br />
Staff<br />
Resources<br />
Progress<br />
Indic<strong>at</strong>ors<br />
Community Services group actions supporting <strong>the</strong>se goals<br />
1. Networking and learning wh<strong>at</strong> <strong>the</strong> community needs are.<br />
Timetable This is an ongoing project<br />
Staff<br />
Resources<br />
Progress<br />
Indic<strong>at</strong>ors<br />
2. Providing inform<strong>at</strong>ion about <strong>Unid<strong>at</strong>a</strong> <strong>of</strong>ferings and trends in our field.<br />
Timetable This is an ongoing project<br />
Staff<br />
Resources<br />
Progress<br />
Indic<strong>at</strong>ors<br />
3. Facilit<strong>at</strong>e collabor<strong>at</strong>ion among groups th<strong>at</strong> could be mutually beneficial<br />
Timetable This is an ongoing project<br />
Staff<br />
Resources<br />
Progress<br />
Indic<strong>at</strong>ors<br />
4. Use <strong>Unid<strong>at</strong>a</strong>’s various media streams (web site, e-mail lists, blogs, social media, etc.) to<br />
provide inform<strong>at</strong>ion about <strong>Unid<strong>at</strong>a</strong>’s d<strong>at</strong>a technology solutions to community members.<br />
Timetable This is an ongoing project<br />
Staff<br />
Resources<br />
Progress<br />
Indic<strong>at</strong>ors<br />
Administr<strong>at</strong>ive group actions supporting <strong>the</strong>se goals<br />
Page 15
See previous goal section. No specific actions are rel<strong>at</strong>ed to cyberinfrastructure<br />
leadership.<br />
Inform<strong>at</strong>ion Technology group actions supporting <strong>the</strong>se goals<br />
1. To be added…<br />
Timetable<br />
Staff<br />
Resources<br />
Progress<br />
Indic<strong>at</strong>ors<br />
2. To be added…<br />
Timetable<br />
Staff<br />
Resources<br />
Progress<br />
Indic<strong>at</strong>ors<br />
Page 16
Goal:<br />
Build, support, and advoc<strong>at</strong>e for <strong>the</strong> diverse geoscience<br />
community<br />
<strong>Unid<strong>at</strong>a</strong> works to help community members learn from each o<strong>the</strong>r by providing opportunities<br />
for collabor<strong>at</strong>ion, discussion, and knowledge sharing. To monitor <strong>the</strong> pulse <strong>of</strong> <strong>the</strong><br />
community, track user needs, and build community rel<strong>at</strong>ionships, we will:<br />
• Provide expertise and resources to researchers in designing and implementing effective<br />
d<strong>at</strong>a management plans<br />
• Represent <strong>the</strong> academic community in partnerships with agencies and o<strong>the</strong>r stakeholders<br />
• Conduct workshops rel<strong>at</strong>ed to current community interests and needs.<br />
• Offer training and support for <strong>Unid<strong>at</strong>a</strong> products and services<br />
• Provide reference implement<strong>at</strong>ions and demonstr<strong>at</strong>ion systems to allow evalu<strong>at</strong>ion <strong>of</strong><br />
<strong>Unid<strong>at</strong>a</strong> tools and technologies, and assist with deployment <strong>of</strong> those tools and<br />
technologies in <strong>the</strong> field<br />
• Foster interactions between community members through meetings and o<strong>the</strong>r<br />
opportunities for collabor<strong>at</strong>ion and communic<strong>at</strong>ion<br />
• Present <strong>Unid<strong>at</strong>a</strong> community perspectives and experiences <strong>at</strong> scientific meetings,<br />
conferences, and o<strong>the</strong>r venues<br />
• Use our community-based governance mechanisms to ensure th<strong>at</strong> <strong>Unid<strong>at</strong>a</strong> program<br />
efforts continue to align with <strong>the</strong> needs <strong>of</strong> community members<br />
Development group actions supporting <strong>the</strong>se goals<br />
1. Support, training, and maintenance for all s<strong>of</strong>tware products.<br />
Timetable<br />
Staff<br />
Resources<br />
Progress<br />
Indic<strong>at</strong>ors<br />
2. Look for opportunities to use user communic<strong>at</strong>ions to build connections between<br />
community members.<br />
Timetable<br />
Staff<br />
Resources<br />
Progress<br />
Indic<strong>at</strong>ors<br />
3. Improve consistency and cohesiveness <strong>of</strong> document<strong>at</strong>ion for s<strong>of</strong>tware and systems.<br />
Timetable<br />
Staff<br />
Resources<br />
Progress<br />
Indic<strong>at</strong>ors<br />
Page 17
4. Improve OSS collabor<strong>at</strong>ive environment:<br />
Timetable<br />
Staff<br />
Resources<br />
Progress<br />
Indic<strong>at</strong>ors<br />
Make it easier for collabor<strong>at</strong>ors to contribute:<br />
- Source code repositories: git/gitHub (CDM/TDS, LDM, IDV)<br />
- Build and dependency management: Maven (CDM/TDS,<br />
IDV?)<br />
- Continuous Integr<strong>at</strong>ion: Jenkins (CDM/TDS, netCDF-C)<br />
- Issue tracking: JIRA (netCDF-C, CDM/TDS); Redmine (IDV)<br />
- netCDF, CDM, TDS, IDV, AWIPS2<br />
5. Work with <strong>the</strong> community on various s<strong>of</strong>tware development collabor<strong>at</strong>ions:<br />
Timetable<br />
Staff<br />
Resources<br />
Some current collabor<strong>at</strong>ions include:<br />
- CDM/TDS: NOAA (NCDC, NGDC, PMEL, etc.), USGS CIDA,<br />
Progress etc.<br />
Indic<strong>at</strong>ors - IDV: SSEC McIDAS-V, NOAA (GSD, etc.), CMA, etc.<br />
- AWIPS2: NCEP, Ray<strong>the</strong>on, NOAA/ESRL/GSD, etc.<br />
6. Continue developing close ties with <strong>the</strong> WRF community (IDV, netCDF, and CDM/TDS).<br />
Timetable<br />
Staff<br />
Resources<br />
Progress<br />
Indic<strong>at</strong>ors<br />
7. Actively particip<strong>at</strong>e in standards development: CF, OGC, OD<strong>at</strong>a , etc.<br />
Timetable<br />
Staff<br />
Resources<br />
Progress<br />
Indic<strong>at</strong>ors<br />
8. Build community around netCDF-4/CDM as d<strong>at</strong>a exchange form<strong>at</strong>. Use this goal to drive<br />
development. Communic<strong>at</strong>e this message in support, training, and o<strong>the</strong>r communic<strong>at</strong>ions<br />
with <strong>the</strong> community.<br />
Timetable<br />
Staff<br />
Resources<br />
Progress<br />
Indic<strong>at</strong>ors<br />
Page 18
9. Annual and regional training workshops<br />
Timetable<br />
Staff<br />
Resources<br />
Progress<br />
Indic<strong>at</strong>ors<br />
10. Present<strong>at</strong>ions and demonstr<strong>at</strong>ions <strong>at</strong> conference<br />
Timetable<br />
Staff<br />
Resources<br />
Progress<br />
Indic<strong>at</strong>ors<br />
11. Work with collabor<strong>at</strong>ors<br />
Timetable<br />
Staff<br />
Resources<br />
Progress<br />
Indic<strong>at</strong>ors<br />
Community Services group actions supporting <strong>the</strong>se goals<br />
1. Work with technical staff regarding d<strong>at</strong>a set comp<strong>at</strong>ibility with visualiz<strong>at</strong>ion and analysis<br />
tools.<br />
Timetable<br />
Staff<br />
Resources<br />
Progress<br />
Indic<strong>at</strong>ors<br />
This is an ongoing project<br />
2. Communic<strong>at</strong>e with <strong>the</strong> community to ensure we are meeting <strong>the</strong>ir needs to reach <strong>the</strong>ir<br />
educ<strong>at</strong>ion and research goals rel<strong>at</strong>ed to d<strong>at</strong>a access/distribution, visualiz<strong>at</strong>ion and<br />
analysis and o<strong>the</strong>r tools.<br />
Timetable<br />
Staff<br />
Resources<br />
Progress<br />
Indic<strong>at</strong>ors<br />
This is an ongoing project<br />
3. Educ<strong>at</strong>e <strong>the</strong> community on new d<strong>at</strong>a and tools available from <strong>Unid<strong>at</strong>a</strong>.<br />
Timetable<br />
Staff<br />
Resources<br />
Progress<br />
Indic<strong>at</strong>ors<br />
This is an ongoing project<br />
Page 19
4. Work with governing committees to organize workshops, community surveys and o<strong>the</strong>r<br />
perceived community needs.<br />
Timetable<br />
Staff<br />
Resources<br />
Progress<br />
Indic<strong>at</strong>ors<br />
This is an ongoing project<br />
5. Coordin<strong>at</strong>e and provide demonstr<strong>at</strong>ions and early testers to allow evalu<strong>at</strong>ion <strong>of</strong><br />
technologies in <strong>the</strong> field, i.e. AWIPS II.<br />
This is an ongoing project, although AWIPS II activities will be<br />
Timetable<br />
especially heavy 2012-2014.<br />
Staff<br />
Resources<br />
Progress<br />
Indic<strong>at</strong>ors<br />
6. Coordin<strong>at</strong>e with staff for provision <strong>of</strong> training and support for <strong>Unid<strong>at</strong>a</strong> products and<br />
services.<br />
Timetable This is an ongoing project<br />
Staff<br />
Resources<br />
Progress<br />
Indic<strong>at</strong>ors<br />
7. Collabor<strong>at</strong>e with Director, technical staff and governing committees on metrics and<br />
assessments collection.<br />
Timetable This is an ongoing project<br />
Staff<br />
Resources<br />
Progress<br />
Indic<strong>at</strong>ors<br />
8. Foster collabor<strong>at</strong>ion between <strong>Unid<strong>at</strong>a</strong> community members, government agencies, and<br />
priv<strong>at</strong>e industry through particip<strong>at</strong>ion <strong>at</strong> scientific meetings, conferences, and o<strong>the</strong>r<br />
venues.<br />
Timetable This is an ongoing project<br />
Staff<br />
Resources<br />
Progress<br />
Indic<strong>at</strong>ors<br />
9. Spread <strong>the</strong> word about <strong>Unid<strong>at</strong>a</strong> and wh<strong>at</strong> it can do to advance educ<strong>at</strong>ion and research.<br />
Timetable This is an ongoing project<br />
Staff<br />
Resources<br />
Progress<br />
Page 20
Indic<strong>at</strong>ors<br />
10. Continue to rely and enhance <strong>Unid<strong>at</strong>a</strong>'s governance mechanism to ensure <strong>the</strong> diverse<br />
represent<strong>at</strong>ion from <strong>the</strong> <strong>Unid<strong>at</strong>a</strong> community.<br />
Timetable This is an ongoing project<br />
Staff<br />
Resources<br />
Progress<br />
Indic<strong>at</strong>ors<br />
11. Cre<strong>at</strong>e a templ<strong>at</strong>e d<strong>at</strong>a management plan th<strong>at</strong> shows researchers wh<strong>at</strong> <strong>the</strong>y must submit,<br />
providing a clear explan<strong>at</strong>ion <strong>of</strong> how various <strong>Unid<strong>at</strong>a</strong> tools and technologies could be<br />
used as part <strong>of</strong> <strong>the</strong> plan. Provide guidance on how to choose appropri<strong>at</strong>e solutions for<br />
several classes <strong>of</strong> research project, along with inform<strong>at</strong>ion on third-party providers <strong>of</strong><br />
tools and services th<strong>at</strong> may be useful (e.g. d<strong>at</strong>a archives, hosting, etc.).<br />
This is a high-value project th<strong>at</strong> should be completed, in its<br />
Timetable<br />
initial form, in 2012.<br />
Staff<br />
Resources<br />
Progress<br />
Indic<strong>at</strong>ors<br />
12. Ensure th<strong>at</strong> training and support m<strong>at</strong>erials are clear and effective learning tools.<br />
Timetable This is an ongoing project<br />
Staff<br />
Resources<br />
Progress<br />
Indic<strong>at</strong>ors<br />
13. Ensure th<strong>at</strong> demonstr<strong>at</strong>ion systems are well-explained and easy for users to evalu<strong>at</strong>e.<br />
Timetable This is an ongoing project<br />
Staff<br />
Resources<br />
Progress<br />
Indic<strong>at</strong>ors<br />
Administr<strong>at</strong>ive group actions supporting <strong>the</strong>se goals<br />
1. Work with technical staff in preparing, developing and coordin<strong>at</strong>ing proposals defined by<br />
<strong>the</strong> goals set forth and approved by <strong>the</strong> governing committees<br />
Timetable<br />
Staff<br />
Resources<br />
Progress<br />
Indic<strong>at</strong>ors<br />
Page 21
2. Educ<strong>at</strong>e and communic<strong>at</strong>e with <strong>the</strong> community in developing and managing <strong>the</strong> <strong>Unid<strong>at</strong>a</strong><br />
Equipment Awards<br />
Timetable<br />
Staff<br />
Resources<br />
Progress<br />
Indic<strong>at</strong>ors<br />
3. Work with governing committees and staff to organize and coordin<strong>at</strong>e users and training<br />
workshops<br />
Timetable<br />
Staff<br />
Resources<br />
Progress<br />
Indic<strong>at</strong>ors<br />
4. Provide e-support to <strong>the</strong> community for workshops and Equipment Awards processes<br />
and functions<br />
Timetable<br />
Staff<br />
Resources<br />
Progress<br />
Indic<strong>at</strong>ors<br />
5. Provide input to <strong>the</strong> Director, technical staff and governing committees on various UCAR<br />
processes, policies and projects<br />
Timetable<br />
Staff<br />
Resources<br />
Progress<br />
Indic<strong>at</strong>ors<br />
6. Foster collabor<strong>at</strong>ion between <strong>Unid<strong>at</strong>a</strong> community members, government agencies, and<br />
priv<strong>at</strong>e industry through booth particip<strong>at</strong>ion <strong>at</strong> <strong>the</strong> AMS conference<br />
Timetable<br />
Staff<br />
Resources<br />
Progress<br />
Indic<strong>at</strong>ors<br />
7. Spread <strong>the</strong> word about <strong>Unid<strong>at</strong>a</strong> and wh<strong>at</strong> it can do to advance educ<strong>at</strong>ion and research<br />
through conference particip<strong>at</strong>ion, and UCAR and UCP involvement<br />
Timetable<br />
Staff<br />
Resources<br />
Progress<br />
Indic<strong>at</strong>ors<br />
Page 22
8. Continue to enhance <strong>Unid<strong>at</strong>a</strong>'s governance mechanism by providing financial upd<strong>at</strong>es to<br />
<strong>the</strong> Policy Committee and to <strong>the</strong> Users Committee as appropri<strong>at</strong>e<br />
Timetable<br />
Staff<br />
Resources<br />
Progress<br />
Indic<strong>at</strong>ors<br />
Inform<strong>at</strong>ion Technology group actions supporting <strong>the</strong>se goals<br />
1. To be added…<br />
Timetable<br />
Staff<br />
Resources<br />
Progress<br />
Indic<strong>at</strong>ors<br />
2. To be added…<br />
Timetable<br />
Staff<br />
Resources<br />
Progress<br />
Indic<strong>at</strong>ors<br />
Page 23
SAVE THIS ONE<br />
Timetable<br />
Staff<br />
Resources<br />
Progress<br />
Indic<strong>at</strong>ors<br />
Page 24
Change language