Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Moving measurements into sensors' groups #107

Open
castelao opened this issue Sep 12, 2022 · 2 comments
Open

Moving measurements into sensors' groups #107

castelao opened this issue Sep 12, 2022 · 2 comments
Labels
1.X For stuff to postpone and resolve only after the 1.0 release question Further information is requested
Milestone

Comments

@castelao
Copy link
Member

moderator: @castelao

Is your feature request related to a problem? Please describe.
With the approval of sensors as groups would it make sense to move the data within its sensors(groups)? This new structure would be a platform (glider) equipped with multiple sensors, each one with its attributes and measurements.
@emmerbodc , you proposed something like that on the #103 discussions. Could you be interested in leading such a PR? I would be happy to help, including providing the changes on the CDL and netCDF.

Is this related to a specific platform models
Applied to all types of gliders

Describe the solution you'd like
Move the measurements from the root level of the file to within the groups of the respective sensors. Some benefits are on reducing the change of sparse data when operating multiple sensors, and allowing equivalent measurements from multiple sensors, such as temperature from CTD + temperature from DOXY.

Describe alternatives you've considered
Keep it a flat structure as it is now.

Additional context
None at the moment.

@vturpin vturpin added question Further information is requested 1.0 For stuff that must be resolved before we are able to release 1.0 labels Sep 21, 2022
@emmerbodc
Copy link
Collaborator

@castelao Apologies for the delay in replying. Yes I can provide an example like I did in the #103 discussion. Will try to do that today 🤞

@castelao
Copy link
Member Author

@emmerbodc , no need to apologize, take your time.

I'm linking this to #119 since I think that this proposition will be crucial for that discussion and decision.

@castelao castelao added this to the OG-0.1 milestone Sep 24, 2022
@vturpin vturpin added 0.1 For the stuff that we must resolve first. and removed 1.0 For stuff that must be resolved before we are able to release 1.0 labels Sep 30, 2022
@castelao castelao added 1.X For stuff to postpone and resolve only after the 1.0 release and removed 0.1 For the stuff that we must resolve first. labels Apr 24, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
1.X For stuff to postpone and resolve only after the 1.0 release question Further information is requested
Projects
None yet
Development

No branches or pull requests

3 participants