(Not sure if this is the right place to report this) A few observations about the following bit of TfL Bus Open Data data:
<VehicleActivity>
<RecordedAtTime>2021-11-27T04:16:04+00:00</RecordedAtTime>
<ItemIdentifier>b27232b9-e7d8-47f6-a128-7676009847a3</ItemIdentifier>
<ValidUntilTime>2021-11-27T04:21:58.915210</ValidUntilTime>
<MonitoredVehicleJourney>
<LineRef>443</LineRef>
<DirectionRef>2</DirectionRef>
<PublishedLineName>36</PublishedLineName>
<OperatorRef>TFLO</OperatorRef>
<OriginRef>490010204K</OriginRef>
<OriginName>New Cross Bus Garage</OriginName>
<DestinationRef>490012248W</DestinationRef>
<DestinationName>Peckham Road / Southampton Way</DestinationName>
<OriginAimedDepartureTime>2021-11-28T03:41:00+00:00</OriginAimedDepartureTime>
<VehicleLocation>
<Longitude>-0.165228</Longitude>
<Latitude>51.516563</Latitude>
</VehicleLocation>
<Bearing>315.0</Bearing>
<VehicleJourneyRef>81405</VehicleJourneyRef>
<VehicleRef>9085</VehicleRef>
</MonitoredVehicleJourney>
<Extensions/>
</VehicleActivity>
- The OriginAimedDepartureTime is one day in the future – seems to happen in the early hours of the morning
- The VehicleRefs are different to the different to the vehicleIds used by the TfL API. It’s possible to convert between the two – 9085 above I think corresponds to YY67URO – but would be nicer if they were consistent
- The DestinationRef and DestinationName aren’t quite right in the example above – the journey confinutes to Queen’s Park (490013353E)