As a final refinement to the automated Measured Parameter population feature for ISO XML products, I would like to see the following:
[x] Refactor the inline schema for the Parameters Description YAML file into its own file. This file should live under src/pge/base/schema since it will be common to all PGEs.
[x] Add code to base_pge.py to load the schema from file before validating the Parameters Description file via Yamale
[x] Enhance the Descriptions schema file with the following additional fields:
An optional "display" (display_name? display_override?) field, that when provided, takes precedence over the default behavior used to "canonicalize" the parameter name. This would replace the current behavior of repeated replace() calls to adjust things like acronyms in parameter names
A required "attribute_type" field which we can use to capture the values used for the EOS_AdditionalAttributeTypeCode tags in the original ISO templates. This field should be an enumeration and the allowable values should match those in the eosCodelists.xml schema used to validate ISO products.
[x] Update the existing Parameters Description config for DSWx-S1 to add the new fields. For the attribute_type field, reference the original values used in the current DSWx-S1 ISO template currently in the main branch.
RKuttruff
commented
1 month ago
As a final refinement to the automated Measured Parameter population feature for ISO XML products, I would like to see the following:
src/pge/base/schemasince it will be common to all PGEs.base_pge.pyto load the schema from file before validating the Parameters Description file via Yamalereplace()calls to adjust things like acronyms in parameter namesEOS_AdditionalAttributeTypeCodetags in the original ISO templates. This field should be an enumeration and the allowable values should match those in theeosCodelists.xmlschema used to validate ISO products.mainbranch.