I just wanted to suggest that (for example) for Slope/Distance implementing a CSV Import feature would be very useful. Format proposal
- # Slope(%),Distance(m)
3.5%,500.0
5.0,1000
7.5,200.0
...
I.e.:
- The first row is the header (which may be foregone if the first character in the row happens to be a digit, in which case it is already data).
The second and posterior rows: 1st item is the distance (float or int) and the second one is the slope in % (also a float or an int)
That would allow to use (for example) a spreadsheet to quickly create an entire ramp broken down in 100m segments if desired and then import it into my e-training. And also create several variations of the same track.
If CSV is too old school, don't drop the feature ... use json or yaml or whatever feels trendy these days.
P.S.
The same concept can be applied to things like "Slope/Time", "Power/Distance" and all other categories with just a simple 2 column CSV file.
