I am currently looking into the extent to which Travelynx could replace this manual table. It is able to track all the basic data I need, except of the tariff and the ticket price. It would be possible to write it into the comment-field, although this isn't really a clean solution, especially when exporting it later.
So I was thinking about having the possibility to set uniform custom data fields in the settings, to add extra information to each connection. Those could be exported via CSV with specific columns.
I did a quick sketch of that it could look like in the Settings:
In the individual connection, it could look like that:
In the year 2023 I tracked all my trains with this table: https://docs.google.com/spreadsheets/d/e/2PACX-1vT_rtEjqwK4KhnY-LSQewP6OYogPUQioyecTpDQOu5Ydh0gItceQuAXgwwLlApPS8L6FiqeaYfb7m3j/pubhtml (see Tab "Daten" for data structure).
I am currently looking into the extent to which Travelynx could replace this manual table. It is able to track all the basic data I need, except of the tariff and the ticket price. It would be possible to write it into the comment-field, although this isn't really a clean solution, especially when exporting it later.
So I was thinking about having the possibility to set uniform custom data fields in the settings, to add extra information to each connection. Those could be exported via CSV with specific columns.
I did a quick sketch of that it could look like in the Settings:![image](https://github.com/derf/travelynx/assets/43503899/45dcb586-c766-4755-8f76-81d0f515184c)
In the individual connection, it could look like that:![image](https://github.com/derf/travelynx/assets/43503899/1bedd605-2797-4e9e-a923-6d3008828106)