Are you a data provider interested in exposing your geophysical data to the IOOS community? If so, the information below will provide you with everything you need to know about requirements for participation in DMAC.
IOOS partners must implement a DMAC Subsystem component that follows these guiding principles:
IOOS, being a part of the Global Earth Observing System of Systems (GEOSS), ascribes to the GEOSS data sharing principles. The basic intent of these principles is for full and open exchange of data and metadata with minimum possible cost, delay and restriction. In particular, observations gathered with IOOS funding are to be freely available. In some instances, IOOS® data providers may act as a “clearinghouse” for other lower capacity or smaller scale providers.
(top)
The World Meteorological Organization Global Telecommunications System (WMO GTS), and an emerging next generation system - the WMO Information System (WIS), - disseminates data in near-real-time to operational weather and ocean forecasting centers. NOAA IOOS is committed to ensuring that all relevant U.S. coastal ocean observations will be contributed in near real time to the global GTS network. IOOS partners can fulfill this requirement by entering into an agreement with NOAA’s National Data Buoy Center (NDBC) to post data onto the GTS in near real time. NOAA IOOS® will provide specific guidance to partners on data priorities.
(top)
DMAC employs a service-oriented architecture (SOA). IOOS® partners must participate in a highly distributed system of compatible components that includes:
(top)
The basic data access services currently used by IOOS® DMAC are described below. IOOS® data partners are expected to establish, register, and maintain services which correspond to their data types (legacy services may also be maintained, if desired).
(top)
IOOS DMAC has selected several preferred data formats, and is researching others in an effort to maximize usefulness. IOOS® partners are expected to offer data in one or more approved IOOS® formats (legacy formats may also be maintained, if desired). Approved formats include:
For gridded data:
For in situ data:
FORMATS UNDER CONSIDERATION: In an effort to maximize usefulness, other formats under consideration are listed below
OGC KML (formerly Google Keyhole Markup Language)
(top)
IOOS is presently developing and adopting shared vocabularies for terminology such as names of observed properties, units of measure, coordinate reference systems, animal species, etc.
IOOS data partners are encouraged to implement, and to help expand, such vocabularies and identifiers, as well as develop cross-walks (i.e., semantic mediation) between IOOS® and existing local or community-of-interest vocabularies and identifiers.
(top)
Descriptive information about datasets, sensors, platforms, models, analysis methods, quality-control procedures is essential for the long-term usability and reuse of information.
IOOS is developing conventions for use of metadata formats such as:
All IOOS partners are encouraged to follow the IOOS guidance; they are expected to ensure relevant metadata is produced, accessible and compliant with IOOS conventions, and to participate as appropriate in the development of such conventions.
(top)
IOOS partners must describe how they will:
NOAA’s National Oceanographic Data Center (NODC) is the nominal archive center for IOOS data. Data providers are expected to provide for storage of data, metadata and other supporting documentation and algorithm descriptions, to establish data recovery mechanisms, and to perform off-site storage of backups until the data and metadata are submitted to NODC for archiving. NOAA IOOS will facilitate execution of NODC partnerships with IOOS partners.
(top)
IOOS partners should maintain the capacity to and demonstrate how they will:
(top)
IOOS is presently developing capability maturity levels for particular areas in data management such as use of standardized data access services, provision of metadata, system reliability, and others. IOOS will assess and display maturity levels for IOOS data and service providers. IOOS partners shall permit and assist with such assessment, and will be encouraged to achieve as high a level as practical in each category and to describe requirements or obstacles to moving to higher maturity levels if applicable.
The IOOS observing, data management, and modeling capacities being developed will, ideally, persist as the overall enterprise matures. IOOS partners should include a discussion of potential plans for maintaining such persistence as part of normal IOOS operations (e.g., by automating as many activities as possible, implementing operational procedures).
(top)
For general inquiries about DMAC projects contact: data.ioos@noaa.gov
If you would like to participate in discussions related to data management of ocean observations sign up for the ioostech mailing list.
Notifications of changes to registered IOOS data access services, such as the NDBC and CO-OPS SOS servers, are sent to the [ioos.system.status@noaa.gov] list.
If you would like to receive these notifications, please send a request to data.ioos@noaa.gov.