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
Background: One of the first steps undertaken by our users is data wrangling. It primarily involves, ordering the datasets, naming the datasets according to CF conventions etc. Given the ever increasing size of datasets, expecting users to re-save the data specifically for using VAPOR could become a major hurdle. Suggestion: Are there any options that allows users to specify the "mapping" of variables between their format and what VAPOR expects (through a script- for instance), which VAPOR could use to read the data?
Of course we would still keep the "one-click import" options that VAPOR offers and encourage users to use that approach. This is for all other cases.
The text was updated successfully, but these errors were encountered:
Background: One of the first steps undertaken by our users is data wrangling. It primarily involves, ordering the datasets, naming the datasets according to CF conventions etc. Given the ever increasing size of datasets, expecting users to re-save the data specifically for using VAPOR could become a major hurdle.
Suggestion: Are there any options that allows users to specify the "mapping" of variables between their format and what VAPOR expects (through a script- for instance), which VAPOR could use to read the data?
Of course we would still keep the "one-click import" options that VAPOR offers and encourage users to use that approach. This is for all other cases.
The text was updated successfully, but these errors were encountered: