Major changes:
-
Now supports to show congestion level and occupancy status if the realtime feed provides it.
-
The gtfsschedule tool will not show services which end at the monitored stop (#17)
Bugfixes:
-
$scheduledDepartureTime$ falsely returned the delay in minutes instead of the actual time. The delay is now mapped to$readableDelay$ and the field returns the right time.
Major changes:
-
New subcommand
search. This allows to lookup stop id locally from the imported dataset (#23) -
Now supports templating the formatting of the schedule item (#21)
Major changes:
-
URLs from which gtfsschedule reads the static dataset (schedule) and realtime feed from now need to be explicitly given as command line options
-
The -r or --realtime option has been deprecated. It is given by providing the --realtime-url option
-
Now supports a configuration file which supports setting URLs
-
Provides a man page
-
Allows to adjust how many schedule items are shown using the -l or --limit options
Bugfixes:
-
Changed prefix for delay indicator. Now a delay of is indicated by a + prefix and running ahead by -. Reason being that it is easier to understand, since the delay is because the service is running additional seconds or minutes from the scheduled time.
Major changes:
-
Support for automatic updates (issue 18). This removes any form of "offline" mode only relying on the static data as every execution tries to determine if the static data is up to date. If the lookup fails the application will print an error to stderr and continues relying on information of the static schedule.
-
Consistently formatted if service is delayed or running ahead
-
Easier to read service delays (issue #6)
-
Supports to specify multiple stops via positional args. (Contributed by Fraser Tweedale)
Bugfixes:
-
Shows message if no services are leaving a stop for the next couple of minutes.
Major changes:
-
Tool uses subcommands. Options of the former tool can now be found under
gtfsschedule monitor --help. -
Addition of an automatic setup command. Running
gtfsschedule setupdownloads static dataset, unpacks and import all CSV data into an sqlite database. The setup is finished by overwriting the existing database.