You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
As of now a number of different parsers are generating and or mapping the original variable store within a source file to a variable vocabulary.
Some of those variables map to multiple vocabulary terms, as example for the GF3 term TEMP_01 will map to the following BODC terms based on the organization (IML vs BIO), the variable label, its units and the instrument associated:
By default the tool outputs all the original variables as well as the mapped variables from BODC.
This has for goal to make it easier to present all the potential mapping within ERDDAP. However this can significantly increase the size of the generated files with extra variables which are not mandatory.
Suggestion
In some cases, only the original variables are desired and within the others only the most precise BODC term would be needed.
It would good to add a optional flag within the dfo.odf parser to handle the different cases:
original: Keep original variable names (still populate the variables attributes to the most accurate BODC term)
rename: Map ODF variables to BODC's most accurate term
multi: Generate all BODC associated variables (present stage)
The text was updated successfully, but these errors were encountered:
Issue
As of now a number of different parsers are generating and or mapping the original variable store within a source file to a variable vocabulary.
Some of those variables map to multiple vocabulary terms, as example for the GF3 term TEMP_01 will map to the following BODC terms based on the organization (IML vs BIO), the variable label, its units and the instrument associated:
By default the tool outputs all the original variables as well as the mapped variables from BODC.
This has for goal to make it easier to present all the potential mapping within ERDDAP.
However this can significantly increase the size of the generated files with extra variables which are not mandatory.
Suggestion
In some cases, only the original variables are desired and within the others only the most precise BODC term would be needed.
It would good to add a optional flag within the dfo.odf parser to handle the different cases:
The text was updated successfully, but these errors were encountered: