-
Notifications
You must be signed in to change notification settings - Fork 0
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
Change in workflow #279
Labels
enhancement
New feature or request
Comments
elma13
pushed a commit
that referenced
this issue
Feb 20, 2024
elma13
pushed a commit
that referenced
this issue
Feb 20, 2024
… from the table; add module to get input from the user about data capture minimum value
Comments: |
elma13
pushed a commit
that referenced
this issue
Feb 20, 2024
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
continuing from #270, maybe a different approach is more useful:
first see all the data and set a maximum value to exclude 'outliers', get a first feeling of the measurements and there min and max
select data on the map and creates groups. This is an useful approach if you have many sensors and use their combined power. Probably you are interested in a specific area of the municipality/project or wants to make onw clusters/groups.
Approval of individual sensors if you wants them in your selection. Approval based upon data capture, so show also that part of the metadata table. Important if you don't have many sensors and want to focus on the sensors which measured long time. Add input field so the user can choose the minimum level of data capture. Be careful, low data capture doesn't have to be a bad sensor. Additional the plausibility or other can be added later for that.
visualisation, part of comparing the data with reference and each other, doing interpretation of patterns and measurements
The text was updated successfully, but these errors were encountered: