cuappdev / cuappdev/ithaca-transit-backend
Analytics: Use selected routes to improve ordering
Open
Priority: Low
Type: Enhancement
- Dominant language
- JavaScript
- Stars
- 18
- Forks
- 2
- PR merge metrics
- No merged PRs in 30d
Description
Currently we only order routes by arrival time, but we know that the fastest route isn't always the most selected. We have found that users prefer not to transfer, walk less, etc and will select slower routes because of this. Once we have a solid amount of data logged, we should leverage this to automatically re-order the route suggestions generated by graphhopper.
Contributor guide
Assessment
This issue has not been assessed yet.