Historical user data

[michih]

When I'm back from a road trip and have submitted my list file, I usually wanna know how many new miles I've clinched. For that reason, I'm used to download the log file when my updated list file is online. This way I can compare how many miles I've clinched on the last trip, during the last season or last year. I could even compare the log file entries to evaluate the change for each region, system or even route. Like I've reported about my last trip.

Dunno if I'm the only one interested in mileage progress monitoring like that but if other's are also interested we could enter a feature issue on GitHub.

If the log file data would be stored in the data base (well, not in log file format but maybe the data of the file in a csv file), we could implement a front-end displaying historical user data one day. However, we would need data first. We could already start collecting data albeit a missing front-end.

I think it's too complex (and too less benefit) to store route data but region and system data would be fine.

That means, data had to be stored

• with every site update
• with list file update or
• once per month?

Code: [Select]

Log file created at: 2016-10-13 22:12:56.167225
Processed 1300 good lines marking 22862 segments traveled.
Clinched Highway Statistics
Overall in active systems: 29838.52 of 627254.13 mi (4.8%)
Overall in active+preview systems: 36834.34 of 829800.60 mi (4.4%)
Overall by region: (each line reports active only then active+preview)
LUX: 317.69 of 603.71 mi (52.6%), 317.69 of 603.71 mi (52.6%)
BEL: 1033.66 of 1489.07 mi (69.4%), 1033.66 of 1489.07 mi (69.4%)
BC: 283.91 of 1462.97 mi (19.4%), 547.89 of 7708.64 mi (7.1%)
AUT: 1303.10 of 1708.14 mi (76.3%), 1640.74 of 7164.50 mi (22.9%)
NLD: 1304.65 of 1582.11 mi (82.5%), 1540.74 of 2044.87 mi (75.3%)
POL: 920.38 of 12006.89 mi (7.7%), 920.38 of 12006.89 mi (7.7%)
HUN: 769.09 of 1621.96 mi (47.4%), 879.27 of 5261.08 mi (16.7%)
ESP: 1782.56 of 9825.71 mi (18.1%), 1782.56 of 9825.71 mi (18.1%)
MI: 92.91 of 9550.65 mi (1.0%), 92.91 of 9550.65 mi (1.0%)
AB: 116.44 of 734.82 mi (15.8%), 142.94 of 9211.39 mi (1.6%)
DEU: 8731.49 of 8882.80 mi (98.3%), 13315.66 of 31103.19 mi (42.8%)
QC: 224.63 of 1807.16 mi (12.4%), 224.63 of 1807.16 mi (12.4%)
ON: 381.58 of 7503.47 mi (5.1%), 381.58 of 7503.47 mi (5.1%)
NOR: 581.20 of 5839.22 mi (10.0%), 581.20 of 5839.22 mi (10.0%)
FRA: 5733.09 of 13117.01 mi (43.7%), 5733.09 of 13117.01 mi (43.7%)
SWE: 1335.65 of 4339.01 mi (30.8%), 2137.94 of 9686.57 mi (22.1%)
CZE: 354.33 of 1809.33 mi (19.6%), 642.49 of 4207.74 mi (15.3%)
IL: 61.36 of 13694.10 mi (0.4%), 61.36 of 13694.10 mi (0.4%)
DNK: 1266.48 of 2570.94 mi (49.3%), 1266.48 of 2570.94 mi (49.3%)
ROU: 1159.71 of 10148.50 mi (11.4%), 1159.71 of 10148.50 mi (11.4%)
ITA: 1143.14 of 6313.07 mi (18.1%), 1143.14 of 6313.07 mi (18.1%)
CHE: 941.49 of 1209.16 mi (77.9%), 1288.30 of 3569.32 mi (36.1%)

[Jim]

Something like this is very interesting to me.  But let's discuss here rather than in GitHub.

Without having thought through the details, something I'd like to see TM support is the ability to show a series of snapshots of a user's travels, both in stats and map form.  Maybe there would be the chance to "play" a map view, showing how travels expand over time.

Many questions need to be answered about what we'd really want and how that historical data would come into the system, among others.  And of course I or someone else would have to find time to implement it all.  But no harm in getting some of the ideas out there.

[michih]

Something like this is very interesting to me.

But let's discuss here rather than in GitHub.

I just wanna add an issue* that the idea does not get lost... Of course, we should discuss it here!

*Is it "DataProcessing", "Web" or both?

both in stats and map form.  Maybe there would be the chance to "play" a map view, showing how travels expand over time.

It's much more than I've expected but it sounds great (Have I told that I made screen shots of regions before planning a travel and marked them with different colors for each day? Opening it in a standard pic viewer, I can jump from day to day by clicking cursor keys...)

[oscar]

One easy, though incomplete, fix could be for interested users to keep local copies of their old list files, with dates added to the file names, then pull them in to GitHub as needed.

I have kept, more or less accidentally, some such "back issues", which I have found useful to help me reconstruct my travels on new/in-dev route systems. CHM, for those of us on that system when it went dormant, also provides a single snapshot of our past travels, though without systems later added to TM.