Hi, I scanned through the static gtfs data (which forms the base over which realtime ITMS data comes) a bit and loaded it up on the Transitfeed ScheduleViewer (https://github.com/google/transitfeed/wiki/ScheduleViewer). Sharing some findings.
While the standard route has two shapes/patterns typically : onward direction and return direction, there seem to be many routes that have more than 2 shapes under them. PFA an excel which lists these counts: https://files.nikhilvj.co.in/pudx/route-shape-counts.xlsx
So this might be something some folks may want to watch out for. I’ll suggest to leave out the routes with too many different patterns and focus on the ones which have a solid Onward and Return journey.
Side note: I don’t want to be a complainer here - Compared to other cities of India, Pune is a pioneer and trailblazer. Data improvement is damn difficult and a perennial work in progress. Most govt agencies simply don’t share because of some or the other minor issues (“it is not finalized yet” - how many times have we heard that?) and the data dies in darkness. But Pune is doing things differently and that is highly commendable. Amazing job done so far and I wish all the people involved all the very best. I’ve had a glimpse and known about the issues with this data (both static and realtime) since over an year now, couldn’t do much about it as a lone person on the outside, and it feels so good to see more technical minds concentrating on this stuff and thinking about it. Sharing small findings on a forum like this can be of benefit to all the participants so hoping to do more of that.
Please feel free to reply on this topic with your own findings.