Update, generalize and rationalize the tool

[datarttu]

TO DO: Update, generalize & rationalize the tool

• [x] Find out if wrangling with dates + times of departures can be avoided. Can we request them from multiple stops such that the result is already ordered neatly by absolute datetime?
• [ ] Parameterize the GraphQL query functions so the user can supply stops by stop id.
• [ ] Create a stop selection pane to the UI, allowing the user to select e.g. 1-5 stops by id, shortcode or name. The departures are then queried from these stops.
  • [ ] Add the stop ids to the URL so it can be bookmarked easily.
  • [ ] Make the selection pane only appear when the edge is touched by the cursor. The pane should disappear after the cursor has been outside it for some seconds.
• [ ] Reorder and add columns in UI as follows: realtime indicator; dep time; route; [wrappable subfield: headsign; stop name & desc]
• [ ] Height dependent row number: set max number of rows by window height, use as query parameter too
• [ ] Width dependent column wrapping: on wide displays, flow rows into two columns

[datarttu]

Digitransit API does not return absolute timestamps. Instead, check the documentation about adding timestamp seconds to serviceDay.