Skip to content

Check & Replace marine obs in glopara to post ioda format #1976

@apchoiCMD

Description

@apchoiCMD

Description

To support the ongoing G-W implementation and ensure consistency across the unified obs workflow, we need to update the marine observation datasets stored in glopara.
Currently, marine obs in glopara rely on pre-IODA formats (legacy BUFR/NetCDF structures). Going forward, all marine datasets must be replaced by the newly generated IODA-formatted outputs to ensure compatibility with recent obsForge updates, retrospective experiments, and planned operational tests.

This task involves identifying all marine observation types inside glopara, replacing them with the corresponding IODA versions, and ensuring the directory structure matches the post-IODA workflow conventions.

Requirements

  • Replace all marine observation files in glopara with their IODA-formatted equivalents.
  • Confirm that all relevant marine products are included, such as:
    • SST, SSS, ADT, sea-ice, in situ (ARGO, Drifters, NDBC Buoys etc.)
  • Ensure completeness of the dataset for:
    • as same as what glopara has (Maybe including ongoing real-time)
  • Ensure IODA files follow the expected naming conventions and directory layout used by the unified obs workflow.
  • Validate that all IODA files are compatible with downstream G-W processing and retrospective tests.
  • Maintain backward consistency with the retrospective testing window currently being used.

Expected Changes

  • The glopara marine observation directories will transition from mixed-format legacy files to a fully IODA-based structure.
  • Any redundant or outdated pre-IODA files will be removed or archived as appropriate.
  • The updated structure will align with the unified post-IODA layout, for example:
    glopara_location/gdas.YYYYMMDD/CC/ocean
        status.log
        sst/
        sss/
        adt/
        icec/
        insitu/status.log
    

Metadata

Metadata

Assignees

Labels

No labels
No labels

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions