Is your feature request related to a problem? Please describe.
Terminology inconsistency - Currently the query through core basin3d does not match the returned information in the views metadata (e.g. queries specify monitoring features, observed properties and returns contain sampling features and basin3d/data source variables).
Describe the solution you'd like
Harmonized terminology across basin3d queries/synthesis and basin3d-views, so users can easily understand what is being returned for their queries
Describe alternatives you've considered
A previous version of basin3d used to return the query information as attributes of the metadata field ( in the hdf5 files), but doesn't seem to be there any more. That is helpful to understand what the query exactly was, but it still doesn't fully address the inconsistent terminology issues.
Is your feature request related to a problem? Please describe. Terminology inconsistency - Currently the query through core basin3d does not match the returned information in the views metadata (e.g. queries specify monitoring features, observed properties and returns contain sampling features and basin3d/data source variables).
Describe the solution you'd like Harmonized terminology across basin3d queries/synthesis and basin3d-views, so users can easily understand what is being returned for their queries
Describe alternatives you've considered A previous version of basin3d used to return the query information as attributes of the metadata field ( in the hdf5 files), but doesn't seem to be there any more. That is helpful to understand what the query exactly was, but it still doesn't fully address the inconsistent terminology issues.