You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It would be great to add the information prognosisType and occupancy that are both provided from the v6.bvg api on which the hafas-client is deployed on.
prognosisType has different states, depending on whether real-time information is given or not. Most of the time trips that are cancelled are not officially cancelled in the systems, but you could still point them out because there is obviously no real-time data available, so prognosisType would be null. If we could get that information, we could mark those departures as different from those that are fitted with real-time data.
It would be great to make that an option in the configuration.
E.g., the well-known navigator app for iOS makes use of that information and displays departures with prognosisType: "calculated" (real-time information given) in italic and those without real-time information given (prognosisType: "null") in normal font.
occupancy is of course self-explanatory and it would be great to have the possibility to get another column with the information for each departure, including how full the train is expected to be.
Hi there,
It would be great to add the information
prognosisType
andoccupancy
that are both provided from thev6.bvg api
on which the hafas-client is deployed on.prognosisType
has different states, depending on whether real-time information is given or not. Most of the time trips that are cancelled are not officially cancelled in the systems, but you could still point them out because there is obviously no real-time data available, so prognosisType would benull
. If we could get that information, we could mark those departures as different from those that are fitted with real-time data.It would be great to make that an option in the configuration.
E.g., the well-known navigator app for iOS makes use of that information and displays departures with
prognosisType: "calculated"
(real-time information given) in italic and those without real-time information given (prognosisType: "null"
) in normal font.occupancy
is of course self-explanatory and it would be great to have the possibility to get another column with the information for each departure, including how full the train is expected to be.e.g. output from https://v6.bvg.transport.rest/stops/900140518/departures?duration=120:
The text was updated successfully, but these errors were encountered: