Go to file
2024-10-30 13:30:33 +00:00
app cabal init and some Haskell nixy stuff 2024-10-27 20:19:38 +00:00
frontend WIP before change of direction 2024-10-27 18:16:02 +00:00
lib use real gpx namespace 2024-10-30 13:30:33 +00:00
tests use real gpx namespace 2024-10-30 13:30:33 +00:00
CHANGELOG.md cabal init and some Haskell nixy stuff 2024-10-27 20:19:38 +00:00
default.nix make "cabal test" work 2024-10-27 20:19:58 +00:00
elm.json WIP before change of direction 2024-10-27 18:16:02 +00:00
LICENSE cabal init and some Haskell nixy stuff 2024-10-27 20:19:38 +00:00
README.md slight README 2024-10-29 21:49:06 +00:00
souplesse.cabal use real gpx namespace 2024-10-30 13:30:33 +00:00

Souplesse

This readme describes what may someday be, not what is today

Reads a GPX file which you generated by cycling around, and tells you interesting(sic) things about it.

The principle we aspire to is that the measurement is subsidary to the ride, not the purpose of the ride. The purpose of the ride is to enjoy cycling, or to see new places, or to get from A to B, and the purpose of Souplesse is to see if we can get any useful numbers out of the riding you were doing anyway without making you do more of it.

So, the general idea is that given some ride data it can tell you how long/how often you spent at a given level of effort (e.g. heart rate), or output (power, speed, cadence, rate of ascent).

Canned views

ride view

graph of (selected variables) / time, with buttons to select variables slider for threshold level all points above threshold are highlighted and interval times above threshold shown zoom in/out on time range show the selected points on a map

calendar view

note this will need some kind of server-side storage so that the system remembers all your gpx files

shows dates that you rode for each ride, show time at effort some kind of slider for effort level

Query view

Not yet decided if this is useful, something that allows graphs of arbitrary functions of properties (e.g. to look at power/cadence ratio, or ... some other weirdness)


Do not look below this line

WIP, Puzzles and TODO

  • [done] Pos can't include elevation if it's sometimes unknown
  • do we even need Track? will it ever be anything more than a collection of Points?
  • need a real gpx file with namespace decls before we can parse power and stuff