Drivers Log

[IzzySoft]

Could you include a drivers log functionality with the app? That would be a real good complement for the fuel log. Even better if it would contain all the fields required for tax. Here's an example from a German paper variant:

km at start could be pre-filled from the previous entry's end. Targets (col 3) and purpose (col 4) could allow for pre-defined values to be picked (recurring trips). Well, if there were an OBDII connection, other values could be auto-filled, too :wink:

Thanks for considering!

Columns translated:

• date
• time (from/to)
• route/target, purpose
• purpose / visited companies, driver / occupants / cargo
• mileage at start
• mileage at end
• driven kilometers (business, private, home/work)
• fuel (litres, cost) – this is already covered by your app but could e.g. be linked
• Oil (litres, cost)
• others (cost, purpose)

[juanro49]

It will be one of the functions I will try to implement in the early 2024 😋

[IzzySoft]

Cool, thanks! Just collecting ideas here: as most car manufacturers have their cars "connected" (to collect as much data as they can it's said), some of them even offer exports for trip data. Here's an example for Škoda's format:

"Bis","Entfernung (km)","Zeit (min)","Ø Geschw. (km/h)","Ø Verbrauch (l/100km)"
"2023-12-13 19:35:19","165","196","50","6.5"

You could consider import functionality for such things, allowing to map the columns from the CSV to those of your drivers log. Comparing to the details in the initial post, date would be the start of col#1, time to the second part of col#1, time (from) could be calculated subtracting col#3, and so on. The import could ask for (and remember) the mapping plus the field delimiter (here a comma). Škoda actually ships an *.xls with 3 sheets of the same format, the 3rd has the "all-time summary" and thus would provide the "mileage at end".

Should you consider this, I can provide you with an example *.xls – but I'd prefer to not make it public here :wink: