Vehicle Database

[E400]

RE: Vehicle Database

(21/06/2015 15:49)B10B6514 Wrote:  I feel your idea is excellent but I would not include sightings unless they were from a different depot or operator as you could end up being inundated with eg. 7653 on route 10,43,437 or whatever 20 times a day. But say 7653 working out of Preston instead of Birkenhead would be of use.

I was thinking more along the lines of if you wanted to list a bus as being on a particular route then you select that route and it gets logged along with the time you saw it and the bus stop. Routes could be imported from an online service called TransportAPI and so the database could forecast where that vehicle would be at particular times, incase somebody wanted to flag it down for photos if it were an unusual allocation, or for whatever reason.

The sightings would only be displayed on the bus' own page under a 'recent sightings' section - if it were sighted at another depot then that could be listed as a depot realocation either on a temporary or permanent basis.

In theory, using this TransportAPI software, you could show the locations of buses at any given time. So, say I saw 1234 on the 464 at Town Lane at around 14:30 on Saturday, I put in route 464 14:30 on Saturday and it shows me a route map with the supposed locations of each vehicle allocation for that time and day.

If the 464 has 3 vehicles, with one in Liverpool, one near Town Lane and one in Shorefields at 14:30, then the one near Town Lane is undoubtedly the one you sighted, so you'd select it.

If the bus has not been 'sighted', it could show as a 'ghost' - ie: unknown vehicle - but when you click on the ghost and enter 1234 (for arguments sake, a Gemini Hybrid) it then maps out for the rest of that day that particular vehicle as a Gemini Hybrid, unless somebody lists otherwise, in which case they may include details of a vehicle swap due to breakdown. That's more what I envisaged the sightings to be.