I’m now developing a country-wide journey planner using OpenTripPlanner and I’m using the GTFS downloaded from BODS as a prototype for everything apart from National Rail, unfortunately I am not finding it adequate for production use. In particular, I can’t see any route colours as shown in Google Maps or other apps (in particular Google Maps’ native format is GTFS), also the agency ID is not something standard that I recognise (it is not the National Operator Code) that it is impossible for me to match the SIRI-SX disruption feeds.
I’m now testing the prototype implementation but I can’t even find the bus route X50 in Manchester, and it also tells me to take the tube even when it is closed for planned engineering works in London.
Can anyone share your thoughts of using the GTFS? Thanks.
One reason we do not recommend or default to the GTFS version for our end users is the lack of a direction_id value.
In the converted GTFS data, all trips are set as direction_id=0. However, the TXC data often contains enough information to understand whether a VehicleJourney is an inbound or outbound trip.
Are you aware of any tools which can convert the TXC into NeTEx (Nordic profile) such that they can be fed into OpenTripPlanner?
I’m trying to tidy up some of the data but our app currently shows the following on the route 757 from Finchley Road (note the distinction between the bus and coach icons, also the colours have been added manually).
Why do the 757 shows up like this with massively different timetable and a bus terminating at Brent Cross?! Where do these data come from?
Another issue at Finchley Road:
I see that all patterns for both directions for the tube stop at 9400ZZLUFYR1. It makes correct wheelchair routing impossible because they represent two physical platform islands, where it is possible to change between lines on the same island but not between the two islands.
