Expand functionality#338
Conversation
…led in yaml_to_adoc such that the mmd element is None in the output .adoc table. Convetions has been added to mmd yaml and is currently in both cf and acdd tables. Passing all unit tests
… Added acdd_ext elements operational_status and activity_type.
…ternal_variables may me missing.
mortenwh
left a comment
There was a problem hiding this comment.
Thanks - it looks promising. See inline comments. In addition, flake errors should be resolved, and the coverage should be brought back to 100%.
There was a problem hiding this comment.
This is ACDD elements, right? Or are there additional ones from/for ADC? Maybe better to call it "ACDD_elements.yaml"?
There was a problem hiding this comment.
According to https://adc.met.no/node/4 there are five attributes that are "Global attributes not being part of ACDD, but that are parsed" by ADC. This would be:
- iso_topic_category
- activity_type
- operational_status
- featureType
- wigos_id (as you mentioned this can be removed anyway)
But I could call it ACDD_elements.yaml and maybe add a disclaimer in the comments for these atrributes?
There was a problem hiding this comment.
The task is focused on making a yaml for ACDD isn't it? I suggest taking out those elements that are not ACDD, and as you suggest, call it ACDD_elements.yaml. Not sure about the others but featureType at least is CF and is already in cf_elements.yaml. mmd_elements.yaml should cover the ADC needs as far as I know (also the wigos_id).
There was a problem hiding this comment.
Originally I thought we were making a yaml for Arctic Data Centre requirements like this adc_required_global_attributes.yaml
I have now made a acdd_elements.yaml as suggested.
Previously we discussed possibly removing the cf_elements.yaml since ACDD 1.3 adopts all CF 1.6 (and presumably later versions) global attributes. All cf elements except external_variables (I couldn't find it in ACDD) has already been added to mmd_elements.yaml.
So the wigos_id needs of ADC are covered by the platform/instrument attribute in mmd_elements.yaml?
There was a problem hiding this comment.
yes, the data producer should add the station url as platform_resource, e.g., https://oscar.wmo.int/surface/#/search/station/stationReportDetails/0-20000-0-01447, and use the name provided there.
similarly, the instrument should be added with name and resource from the oscar database.
There was a problem hiding this comment.
if this cannot be used, we should in principle create another yaml file adc_elements.adoc containing the wigos_id field but I can't understand that this is necessary.
… any newly genrated adc_elements.yaml
_elements.yaml that only contains ACDD elements. None of the extrtra ADC elements.
|
I have 3 tests failing: but these are also failing on the master branch. |
The master branch seems good. Maybe it's just a local problem? |
No - I get the same. Quite surprising, as this should not happen. I'll look into it |
|
I have solved it: #341 We can update this branch when that is merged |
|
@Alessimc - the tests are passing now, except coverage. Can you add tests for the new code? |
Absolutely! I will try to look into this later today. Sorry for some late responses. My work hours are reduced now that university courses have started again. |
No problem, I see some tests are still failing but you can pick up this when it suits you. |
…py_mmd_tools/script/mmd2acdd.py
Summary:
Related issue:
Suggested reviewer(s):
Reviewer checklist:
The checklist is based on the S-ENDA conventions and definition of done (see https://s-enda-documentation.readthedocs.io/en/latest/general_conventions.html). The above points are not necessarily relevant to all contributions. In that case, please add a short explanation to help the reviewer.