LVF - The London Vehicle Finder

The London Vehicle Finder

The London Vehicle Finder (LVF) was created not too long ago by Brian and Thomas Cheyney and uses the TFL Live bus arrivals API (instant) Which is Avalible for Request Here: http://goo.gl/FrALv 

Since its creation it has proven very popular with bus enthusiasts as you can track a bus down while sitting at home or when you are about to leave so you have a rough idea of where the bus is, effectively cheating in other words, You can also check it on your smartphone!

It can show data like this, where you can see what buses are/have been out on a route

Here is the Link but Please read the information below and if any help is needed just let us know in the comments 

http://goo.gl/nFKVm

 Data can be requested in a number of ways by :-- registration- operator/fleetnumber- route- stop A history facility is available for all except by stop (see below) The entered value will attempt to match in the order:- registration, operator/fleetnumber, route, stop and as a countdown registration. Wildcards In most cases any individual character can be replaced by an underscore '_' to create a wildcard search. The '*' character can be used to replace multiple characters.. Ranges In some cases ranges can be specified. A range is signified by the "-" character. A wildcard cannot be used in a request where a range is specified. In all cases of multiple output, a maximum of 100 entries will be displayed. Each of the requests is explained in detail below By Registration: Enter the registration of the vehicle you wish to lookup. Spaces entered are ignored so YX 58 DXA and YX58DXA will be treated the same. Wildcards are allowed as are ranges. Example of valid ranges are YX58DXA-D, returns details of 4 vehicles or GAL E1-100, returns details of 100 vehicles. YX*DXA-D is not valid as it is potentially many ranges. By Route: Any character string less than 5 character long is deemed to be a route number. Wildcards are not allowed as part of the route number. Information will be displayed by direction of travel and then by vehicle fleetnumber order. If a vehicle is not working a journey to the normal destination, the entry will be in blue with the stop name replaced by the actual destination of the vehicle. There are some cases of very common different destinations and in these cases the entry will still be in blue but a code will be displayed to indicate the reason By Stop: Stop ids can be indentified by the 5 character stop codes often displayed in the output from other enquires. If a stop code is entered numerically then spaces and wildcards are not allowed. One or more stop code can be entered by putting a comma between the codes. However no check is made that stop codes are geographically close to each other.Alternatively a stop or stops can be entered by name. Wildcards can be used as part of the name. The system will check that what is entered is unique. Because special characters, eg '&', cannot be entered to be able to lookup somewhere like "Elephant & Castle" the "&" must be entered as a wildcard character.Vehicles will be displayed in the order they are expected to arrive although this cannot be guaranteed. By Operator/Fleetnumber: Operator codes cannot be wildcarded and must be included in any fleetnumber request. When requesting data on First London vehicles class codes are optional. To lookup more than one vehicle in a request the fleet nummber may include wildcards or a range may be specified Valid Operator codes are :- AL =Arriva LondonFLN =First LondonML =MetrolineASC =Arriva Southern Counties  GAL =GoAhead London  SB =Sullivans BusesASE =Arriva The ShiresLS =London SovereignSLN =Stagecoach LondonCTP =CT PlusLU =London UnitedTLN =Abellio LondonEP =Epsom BusesMB =Metrobus History: The facility exists to request the history of a vehicle, ie what routes it has worked on within the last 2 weeks, or the history of a route - what vehicles have been used on the route within the last 2 weeks and when they were last recorded. To obtain history data enter the keyword history followed by a registration, operator/fleetnumber or Route number. This request does not allow wildcards. 

Information Provided by Brian and Thomas Cheyney who created the LVF