search

PCMDI / obs4MIPs-cmor-tables

JSON Tables for CMOR3 to create obs4MIPs datasets
Other
6 stars 3 forks source link

RC for NOAA NCEI SeaWinds #104

Closed scott-stevens closed 7 years ago

scott-stevens commented 7 years ago

source_name = 'NOAA NCEI SeaWinds' release_year = '2008' source_description = 'Blended Sea Surface Winds' source_version_number = '1.2' institution_id = 'NOAA-NCEI' region = 'global_ocean' source_type = 'satellite_blended'

If StdDev ends up being included, then we'd like Nobs and StdDev, otherwise no.

gleckler1 commented 7 years ago

@scott-stevens Is this entry for zonal (ua) and meridional (va) winds or will it be used for a magnitude only?

scott-stevens commented 7 years ago

@gleckler1 @JimBiardCICS We were just discussing that earlier and what would be the best way to handle it. Within the same source files, we have all three (u, v, and magnitude). Should that be three separate source_ids, or just the one?

JimBiardCics commented 7 years ago

@durack1 @gleckler1 @scott-stevens It will be uas, vas, and sfcWind. We have all three. It seems to me that we would have one source_id for all three, as they live in the same input file and are closely related.

gleckler1 commented 7 years ago

@scott-stevens @JimBiardCics @taylor13 @durack1 Your current source_description is informative but not too prescriptive - it is relevant for all 3 fields. Right now I'd say it is ok as is, but will continue soul searching. Related: we are discussing adding an attribute to each key in the obs4MIPs_source_id.json which identifies which variable_ids the source_id info is valid for, e.g., in this case, something like: source_variables = ['ua','va','sfcWind']

JimBiardCics commented 7 years ago

It's uas, vas, and sfcWind. They are all single-level quantities.

gleckler1 commented 7 years ago

@scott-stevens @JimBiardCics source_id updated to include this