Real-time, updating public transport info display that aggregates OpenTripPlanner schedules for multiple stops. Previously known as virtual monitor
Stop monitor provides both the configuration and displaying of public transit stop data. Configurations are saved to Azure CosmosDB database and a static url is created for the monitor. Currently no real login system is implemented, though there is poc version of that too.
A display can show either a single view, or multiple different views that are rotated after a specified time period. To create a new display, navigate to the link http://localhost:3000/createView. Or you can click a button from front page.
The link created in create view is a link to the Stop monitor view of current configuration. Please remember that after the link is copied, it will always show the same configuration, even if changes are made in the editor. Thus remember to always create a new link after each modification. You can also go back from the monitor view when you move mouse over the monitor, then go back button appears.
Monitor aggregates stop times for multiple stops from current time on. To add stops to the view, search for stops by the search field. You can add more stops and edit the view multiple ways in configuration page.
It's possible to give names to the stops and displays. Some stops have a pier or stop number provided by the OTP back-end, but self-assigned names might be clearer.
Monitor also shows alerts for stops when available. There is also hidden functionality for viewing only alerts from selected stops. It can be accessed by hiding all the departures from all selected stops in the stop settings.
npm install && cd server/ && npm install
Use node version 16.7.0
To run the front end of the app: npm start To run backend server cd server/ && npm start
To access the stop monitor: http://localhost:3000/
Steps for customization for different organizations is detailed separately in Customisation.md.