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
Consistency checks and dummy entries for drives and charges
Why is this needed:
A few times charges or drives aren't logged (for instance API down or no internet connection avail and so on).
Adding data manually is current complicated as it's only possible via SQL-Insert-Statements
So I'm thinking it could be helpful to check consistency.
For instance:
if odometer is "jumping" from the last record without having a drive recorded - it normally was an unlogged drive.
if charge level is higher than last record, but no charge was recorded - it normally was an unlogged charge.
If the "consistency check" fails - it could be added as "dummy" drive / charge.
So it's easier to change it via DB (as it's only an update) or later on via GUI (like "set costs").
Additional context:
I know it's more complicated than that and also it's far from being perfect.
But maybe there're some ideas to make it easier for users.
This discussion was converted from issue #889 on December 08, 2020 18:53.
Heading
Bold
Italic
Quote
Code
Link
Numbered list
Unordered list
Task list
Attach files
Mention
Reference
Menu
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
What would you like to be added:
Consistency checks and dummy entries for drives and charges
Why is this needed:
A few times charges or drives aren't logged (for instance API down or no internet connection avail and so on).
Adding data manually is current complicated as it's only possible via SQL-Insert-Statements
So I'm thinking it could be helpful to check consistency.
For instance:
If the "consistency check" fails - it could be added as "dummy" drive / charge.
So it's easier to change it via DB (as it's only an update) or later on via GUI (like "set costs").
Additional context:
I know it's more complicated than that and also it's far from being perfect.
But maybe there're some ideas to make it easier for users.
Thank you very much in advance.
Beta Was this translation helpful? Give feedback.
All reactions