Aerosol optical properties/MACv2-SP data upload

[znichollscr]

Issue for tracking the progress and any issues related to the aerosol optical properties/MACv2-SP data upload.

cc @durack1 @vnaik60

[znichollscr]

Comments on the first received file:

There are a number of global attributes that should be added to the file (format: - <attribute_name> = "<suggested_value>"). These are important for tracking the file and providing users with required metadata (as well as ensuring that data providers get appropriate credit!).

• Conventions = "CF-1.8"
• activity_id = "input4MIPs"
• contact = "" # not posting email address in public without checking first
• creation_date = "YYYY-mm-ddThh:MM:SSZ" # the date the file was created, should ideally be UTC time
• dataset_category = "aerosolProperties"
• frequency = "mon"
• further_info_url = "" # can also be set to "http://www.tbd.invalid" if you don't have a website, like us at the moment :)
• grid_label = "gn" # although even this is a bit weird because the data isn't really gridded
• institution_id = "G-UHD" x-ref Aerosol optical properties/MACv2-SP metadata #125
• license = "The input4MIPs data linked to this entry is licensed under a Creative Commons Attribution 4.0 International (https://creativecommons.org/licenses/by/4.0/). Consult https://pcmdi.llnl.gov/CMIP6/TermsOfUse for terms of use governing CMIP6Plus output, including citation requirements and proper acknowledgment. The data producers and data providers make no warranty, either express or implied, including, but not limited to, warranties of merchantability and fitness for a particular purpose. All liabilities arising from the supply of the information (including any liability arising in negligence) are excluded to the fullest extent permitted by law."
• license_id = "CC BY 4.0"
• mip_era = "CMIP6Plus"
• nominal_resolution = "100 km" # just guessing, change to whatever value makes sense
• product = "reanalysis" # see options here https://github.com/PCMDI/input4MIPs_CVs/blob/main/CVs/input4MIPs_product.json
• realm = "atmos"
• source_id = "G-UHD-SPv2-1-0"
• source_version = "1.0"
• target_mip = "CMIP"
• tracking_id = "" # needs to be a unique tracking ID for each file. (Python code to generate it "hdl:21.14100/" + str(uuid.uuid4()), I assume ncl has something similar or you can use python)
• variable_id = "multiple"

In terms of the data itself:

• the plume_number variable should have units of "1" I guess?
• the plume_feature variable seems to just be [1, 1]. Is this intended? I would have thought the features would have different values? In terms of units, "1" I guess?
• does your data have a time axis? If yes, can we format it as a more standard time axis rather than years and year_fr? (There may well be a good reason that you don't have a time axis, similar to why we don't have a 'standard' time axis for some of the volcanic eruptions. It would be good to understand though, to help make sure we apply the format conventions appropriately. If I look at the data and https://gmd.copernicus.org/articles/10/433/2017/gmd-10-433-2017.pdf, it seems like you are basically giving locations and function parameters, which I assume groups then turn back intro aerosol properties on a grid custom to their model, for the years of interest to their model (using the scale factors); and for the wavelength of interest to their model?)
  • speaking of, how does your data's year axis extend to 2100? We don't have future emissions yet (as far as I'm aware)
• units of is_biomass should just be "1" I guess? (Doesn't really have units, but to match CF-Conventions, we have to put something valid)
• units of plume_lat, sig_lat_W and sig_lat_E should be "degrees_north"
• units of plume_lon, sig_lon_W, sig_lon_E should be "degrees_east"
• the year_weight variable should have units of "1" I guess?

[durack1]

@znichollscr just catching up, this data is now live at ../StephanieFiedler-MACv2SP/20240930/