As a skier continues to partake in activities throughout the season, they tend to visit different trials from different resorts. A particular need that spawns from this aspect as a consequence would be that a user would like to know about some historical data regarding resorts.
Currently, OpenTracks only offers users the ability to see where they were at on a map when viewing the recorded track. The aggregated stats page does not showcase some key metrics about resort locations such as most used lifts, the total amount of resorts visited or the most common resort visited. There needs to an extension made to the all-time stats component of the app to showcase these components to the user visually.
Proposed Solution
Utilize OverallStatistics's methods to dynamically integrate the calculated resort stats onto the view page element of the all-time stats components. These should be used when the page is rendered as a form of lazy loading as it may not be guaranteed that the user will immediately need to see this information, if at all.
Alternatives
Get the results of the calculations to be stored into a cashed variable to be invoked later. While it does make the results available on demand, it may be wasteful for reasons mentioned in the proposed solution.
Completeness Requirements
The dynamic generation of the stats is rendered onto the all-time ski stats page
Provided that the full implementation of runs, days and seasons and resort information is done, the generated values are accurate
Description
Proposed Solution
OverallStatistics
's methods to dynamically integrate the calculated resort stats onto the view page element of the all-time stats components. These should be used when the page is rendered as a form of lazy loading as it may not be guaranteed that the user will immediately need to see this information, if at all.Alternatives
Completeness Requirements
Additional Context
7
141