23 Apr 2016, 7:30 pm
#602
(23 Apr 2016, 7:14 pm)BusLoverMum One that we caught the other week did that in Birtley. The audio just jumped ahead of itself then didn't recover. Visuals stayed fine.
Not sure about anything that's happened in the past, but most of the Angels had their media updated last Sunday. That should have cured any issues... Will try and get myself on an Angel next week to replicate the issue Ambassador has observed.
(23 Apr 2016, 7:18 pm)NK53 TKT That is not true in the case of some buses including the Q3
Think the guy who manages the company's Next Stop Announcements knows the process..!
It is true - I receive a stop list from the commercial department, which uses the information from the NAPTAN database (where amendments have not been made). This stop list feeds the company's real time information system, and in turn the mobile app, as well as a number of other things 'behind the scenes' that customers don't get to see. This stop list doesn't just have a list of names, but the bus stop code as well as GPS co-ordinates of that stop.
I make amendments to the names of the stops, based on street names and well-known places in that area, using Google Maps. These are then recorded. I didn't do the Quaylink, but I'm guessing that the person responsible for the Next Stop Announcements prior to me would have had a similar process.
