Skip to content
This repository has been archived by the owner on Aug 31, 2023. It is now read-only.

End to End Dataflow

John Kerfoot edited this page May 23, 2023 · 7 revisions

WikiData Flow Pathway

Description of the end to end flow of data through the U.S. IOOS National Glider Data Assembly Center, potential pitfalls for data providers and DAC administration team members and suggestions for fixing issues with real-time and delayed-mode data sets.

Steps

Data Flow Schematic

The image below displays the end-to-end flow of data from the data provider to the DAC and resulting end points.

Data Flow Schematic

User Registration

All data providers must request a user account in order to submit either/both real-time and delayed-mode data sets to the DAC.

This password-protected account allows the user to register deployments, modify and add data set metadata, push NetCDF files and delete data sets. Once you have received your temporary password, please log into the system and create your own secure password. Lost passwords will require the DAC administration team to reset the user account with a new temporary password.

Please consult the FAQ for log in related issues.

WMO ID Acquisition

All data sets released on the Global Telecommunication System must have a valid WMO id. The WMO id is used to identify the platform making the observations. Recent changes to the rules for WMO ids now allow for a single WMO id, regardless of the region for which it was assigned, to be used globally for the same platform. Check the FAQ section for information on requesting a new WMO id.

Deployment Registration

Data providers must register a data set prior to submitting NetCDF files for a real-time or delayed-mode data set. Once the deployment has been registered and one or more NetCDF files have been submitted, the data set status can be tracked via the data set status page.

Data Provider NetCDF Uploads

Data Set Status

ERDDAP Synchronization

Compliance Checks

Modifying Metadata

Data Set Completion

Archiving