HSLdevcom / HSLdevcom/digitransit-ui
Departure view: grouping rows by route/direction instead of trips?
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 267
- Forks
- 145
- Avg merge
- 1d 15h
- Merged PRs (30d)
- 75
Description
The departure view seems to group departures of identical trips in a row, indicating their next departures:
However, some of our routes have trips which have identical headsigns, nearly identical trip patterns, only their quay differs for a few stops (the parent stop is currently not given in the GTFS but we could deduce it from the stop_id):
Extract from stop_times.txt:
"29.T0.10-2-j20-5.2.H","14:26:00","14:26:00","de:08116:1905:1:1","27","","0","0"
"30.T0.10-2-j20-5.7.H","14:56:00","14:56:00","de:08116:1905:1:2","27","","0","0"
Is there an option to group by route/direction (or headsign) instead of trips? And would the route list be able to handle this?
Or, to just show next departures without grouping (and hence omitting over next departure)?
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by locating the departure view and route-list implementation, then trace how departures are grouped and how the next departure is selected. Compare the possible route/direction or headsign grouping with an ungrouped next-departures view, and define which display behavior handles trips that differ only by quay.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- frontend
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100