Compatible data

Simulation output

OceanVal validates ocean model output in NetCDF format. Files should be CF-compliant as far as possible — most ocean model output already is, so there should be no compatibility issues.

Unstructured grids

Not compatible out-of-the-box. If unstructured output can be regridded to a regular grid and saved as CF-compliant NetCDF, OceanVal can use it. FVCOM output is supported via oceanval.fvcom_preprocess.

Vertical grids

Both z-level files and files with a varying vertical grid are supported, provided cell thickness is stored in the simulation output.

Folder structure

Files need a consistent, logical naming convention, e.g. YYYY/MM/model_output_YYYYMMDD.nc. OceanVal automatically identifies the naming convention and matches the right files.

Time requirements

At least a single year of model output is required. Time resolution can be daily or monthly.

Gridded observational data

Gridded observations (e.g. satellite data) should also be in NetCDF format — in a single file or multiple files, which OceanVal will merge. Files must be CF-compliant, which gridded observational products almost always are.

Vertically-resolved files are supported, with depth as a dimension and a consistent vertical grid — the norm for gridded data products.

Key OceanVal assumption

If you supply a gridded file with only one timestep, OceanVal assumes it represents a climatological annual average.

Time requirements: ideally observational files contain time information — its absence can make it impossible to figure out how to handle the data, and may raise an error.

In-situ observational data

In-situ observations (e.g. from research cruises or moorings) should be in CSV format. Supplying anything other than the columns below will raise an error, and OceanVal checks that required columns are present.

Required columns
  • lon — longitude, decimal degrees
  • lat — latitude, decimal degrees
  • observation — the observed value, ideally in the same units as the model output
Optional columns
  • depth — depth in metres. Required for subsurface validation; if supplied for surface-only validation, only the top 5 m is used
  • year, month, day — as much or as little time information as you have
  • source — a label for the data's provenance, e.g. a cruise or platform ID