public-transport-enabler
public-transport-enabler copied to clipboard
AbstractNavitiaProvider: Remove all providers based on Navitia.
I propose to remove all providers based on Navitia. They have been causing many runtime errors since years, without anyone working on them. If we don't find a responsible maintainer for the Navitia API (mainly AbstractNavitiaProvider), we I think we'd rather remove these classes.
Pinging @aelkhour and @grote as you're listed as authors.
Also pinging @ialokim and @prhod about the removal of Navitia from PTE.
I think it's less the PTE's implementation of AbstractNavitiaProvider
that leads to problems, but instead the data on the Navitia server which is not always up-to-date or gets some updates changing IDs or such. I think we can not do much on PTE's side on this, apart from perhaps implementing a slightly better error handling.
It would be really a shame if all those providers were removed from PTE. I would be okay maintaining them to the extend that is possible without having access to the data source (Navitia API) itself.
@schildbach I don't have the bandwidth to maintain this provider. Although I am the instigator of this and had a lot of fun adding it, I understand your decision if there are no maintainers.
The removal of all providers based on Navitia would be a big loss :( What specific errors/problems are encountered with Navitia? I would be happy to help working those out :)
Thanks @grote for poking me, seems i've missed a few messages, sorry about that. I've relayed the message to the Navitia dev team, I hope a solution can be found on this.
Hi all, Here is some reflexions i had this evening
- Maybe we could post a message to get some help from the navitia forum. But i can't understand what kind of errors we are talking about, and what kind of contributions we need on PTE
- If errors occurs mostly on few providers (seems to be "coverages" in Navitia API), maybe could you delete only these providers ?
- @grote told us about some id change problems. As it comes from GTFS providers, you may known some good practise : how do you manage this kind of change with the other providers ? Maybe we could do some improvement in Navitia API on that point ?
The removal of all providers based on Navitia would be a big loss :( What specific errors/problems are encountered with Navitia? I would be happy to help working those out :)
Sorry for getting back to your question only now.
I tagged most of the open issues with the tag "navitia".
There is one more problem with Navitia: their API limit for free accounts seems to be exceeded by Öffi now and then. Not sure how other apps like Transportr do, but for Öffi this is quite discouraging.