|
Post by Pilot on Feb 22, 2021 11:33:36 GMT
That app will also include running numbers soon Doubt.
|
|
|
Post by mateusz180 on Feb 22, 2021 12:25:29 GMT
Well if you click on the link, it has a new feature running numbers
|
|
|
Post by Pilot on Feb 22, 2021 15:49:01 GMT
Well if you click on the link, it has a new feature running numbers Ah user supplied, fair enough.
|
|
|
Post by capitalomnibus on Feb 26, 2021 0:02:58 GMT
Would it be possible to make it so that you could roughly know what headway the buses are actually on just like when you drive a bus on your MDT? To know actual headway from 1 to 7/8 bars. I mean right now you can look at the website and you can see even gaps between buses, you can sort of assume they are on good headway but that's about it, but would be nice to know what actual/roughly headway they are on whether it's 3 or 5 bars and so on...I think it won't be easy to create as there is different sort of PVR/frequency throughout the day. But when you look at the headway on the website at say 11PM at night, you'll see like 2 buses on the tracker long distance apart so it's difficult to know what their actual headway is. Appreciate all your work so far though. I think that this is a great idea and is something I would love to implement. And there are two ways that this could work but neither would be feasible unfortunately. a) Sadly we are not provided the running number of a bus from TfL through their API. If we were, we could use this data to show you how early or late a vehicle is running by comparing it with its scheduled time from the schedules on TfL's website. This would be the ultimate way of making the application just like the real diagrams. b) We could constantly ping the API to get the arrival times of each bus for each stop in London and as you can imagine, that's simply unpractical; from a data storage perspective and server performance perspective (important if you guys want some semi-decent response times when using the system!) Moreover, I don't think TfL would be too pleased if I were making this number of requests . If this were the case though, we could see that LT1 arrived at Liverpool Street at 20:10 and then LT2 arrived at Liverpool Street at 20:22 on a scheduled 10 minute headway. Since LT2 arrived 2 minutes late (on headway-the key to remember here), we could express this as 1 whole headway + 1/5th of a headway. This corresponds to the diagram on a driver's MDT and would hence display as a "bar down from the middle". Conversely, if LT2 arrived at 20:18 this would be expressed as 4/5ths of a headway and displayed as a "bar up from the middle" (80% of the scheduled headway). Open to suggestions if anybody thinks there is another way round this! It can be done, various operators have done this with the APi feeds, this is then used to generate the overall EWT, ewt between buses and the headway of the buses. Although this would only show correctly if every bus is polling. It can still generate a 'ghost bus' to represent the non polling bus, but it would match it to the timetable as though it was on time.
|
|
|
Post by mateusz180 on Apr 1, 2021 22:36:49 GMT
Some routes on that showing run nos today, being 81, 9.
|
|