More information about statusSeverity

[LeonByford]

No, the line status will not tell you if buses are delayed.

In theory, it may be possible to compare the predicted arrival time to the timetable. However, in practice, this is of limited use because buses in London are usually treated as a frequency-based mode. If, for instance, there is supposed to be a bus every eight minutes, but all the buses are delayed by five minutes, it doesn’t really make much of a difference to customers because they are still receiving the same frequency of service.

[misar]

@LeonByford

If, for instance, there is supposed to be a bus every eight minutes, but all the buses are delayed by five minutes, it doesn’t really make much of a difference to customers because they are still receiving the same frequency of service.

That’s true for the frequent services but there are plenty of TfL routes where the frequency is 15, 20, 30 or even (e.g. on Sunday) 60 minutes. Passengers then tend to go by scheduled times and its annoying when buses deviate, especially a few minutes early. Unlike NR trains, buses rarely wait until their scheduled departure time (apart from “this bus is being held to even out the service”).

[salmanfarisvp]

@LeonByford

the line status will not tell you if buses are delayed.

So, what does the severity level indicate? Only the status of the delay?

@LeonByford

it may be possible to compare the predicted arrival time to the timetable

Do we able to get the predicted arrival time from the API? or can you point the link please.

[salmanfarisvp]

@LeonByford For your information, I’m working on a digital signage app for the Screenly Edge app.

So the idea is it can be installed on the bus top to showcase the bus status and arrival time. For now, I’m using the severity level to showcase the delay. Attaching the UI model, please check and share any feedback if you have. Thank you.

[LeonByford]

Thanks for sharing. Is this a project you’re working with TfL on?

[salmanfarisvp]

@LeonByford Yes. The app will be published soon and will be open source, so you can use a screenly player to run it.

What do you think about the design and information listed? Thanks.

[netstruggler]

Design looks nice and clean.

Since you’ve asked for comments:

• I’d call it a stop rather than a platform
• I don’t think saying ‘On Time’ adds much value when you’re displaying the arrival time. If there’s a bus with an arrival time on the display I wouldn’t show a status unless it suggest the route might be affected.
• What do you show if there are no buses arriving for an expected route? You should probably list the bus number with no time, but a status: important ones being ‘No reported Issues’ or anything that means the service at that stop is suspended or delayed for that bus number.
• The key thing for me would be the ability to set select the stop and route of interest and ‘bookmark’ favourites. TfL’s own arrival app is pretty good but fiddly to navigate.
• Buses in my area now estimate the time to reach selected destinations. If you can get that working it would be cool assuming it’s real world information rather than just a fixed estimate.

Good work and good luck with it.

[misar]

@salmanfarisvp Given users have the arrival times I don’t think the status info in your example adds anything for users. I would be inclined to move that column to the right and only display status (in red?) when it provides meaningful additional information such as Diverted or Not Running. In particular such a status also needs to be shown for routes without an arrival in the next 30 minutes.

[netstruggler]

Great minds think alike

[LeonByford]

@salmanfarisvp

So, what does the severity level indicate? Only the status of the delay?

For buses, the severity level does not indicate much. Honestly, you’re probably best off not using it. It does not tell you anything about delays.

@salmanfarisvp

Do we able to get the predicted arrival time from the API? or can you point the link please.

Yes, please see my earlier post. Do let me know if you require any further information.

[salmanfarisvp]

Hi @netstruggler, Thanks for the feedback and I appreciate it.

@netstruggler

I’d call it a stop rather than a platform

But at the same bus stop, we have different platforms, right? So it’s better to use ID to avoid confusion?

@netstruggler

What do you show if there are no buses arriving for an expected route? You should probably list the bus number with no time, but a status: important ones being ‘No reported Issues’ or anything that means the service at that stop is suspended or delayed for that bus number.

The status screen is based on the severityLevel and description so if there is no bus or status like delayed or Diverted, it will show as the status.

@netstruggler

The key thing for me would be the ability to set select the stop and route of interest and ‘bookmark’ favourites. TfL’s arrival app is pretty good but fiddly to navigate.

Sorry for the confusion; this project is intended to be digital signage. It will display information on the screen; the user has no specific interaction like a webpage.

@netstruggler

The key thing for me would be the ability to set select the stop and route of interest and ‘bookmark’ favourites. TfL’s own arrival app is pretty good but fiddly to navigate.

Understand, but since it’s an digital signae app, I think it’s not applicable here right?

@netstruggler

Buses in my area now estimate the time to reach selected destinations. If you can get that working it would be cool assuming it’s real world information rather than just a fixed estimate.

So mean, compare with bus time chart and TFL API bus arrival information and display the arrival time?

Thank you for the feedback and I really appericte it.

[salmanfarisvp]

@misar

Given users have the arrival times I don’t think the status info in your example adds anything for users. I would be inclined to move that column to the right and only display status (in red?) when it provides meaningful additional information such as Diverted or Not Running. In particular, such a status also needs to be shown for routes that do not arrive within the next 30 minutes.

Yes, we have that, the staus will change depending on the severityLevel and description, it have have all the severityLevel options.