Right, there are basically two ways of getting public transport coverage for more regions/operators into Itinerary/KTrip/etc:
-
Dedicated support in KPublicTransport for their public transport routing API. In the easiest case this is just another configuration file if an already supported API/routing engine is used, but in the worst case it can mean reverse engineering and implementing an entirely new thing.
-
Since recently there is also a community-operated free and open public transport routing service (Transitous) that we can use. For regions/operators to be added there we need at least the base schedule data in GTFS format, ideally also realtime schedule data in GTFS-RT format. If that is freely available, it’s a matter of a small configuration file most of the times.
Either of that is helped by API/data/documentation being properly available under free and open licenses. Country-wide unified API/data rather than a highly operator/regionally fragmented system also simplifies this a lot. But first and foremost this depends on input/guidance from somebody familiar with the public transport system in that region, as this is often tricky to research from abroad, let alone judge the quality/usefulness of the results.
Transitous already shows some data for New Zealand, so with 24.05 that should be available in Itinerary/KTrip as well. And I’d obviously love to see India covered too 