You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Right now gtfs static we have is pretty old, in the last two years RTEC and PUA added new routes and did some other changes, so we need to add the updates to our gtfs static repo.
I assume that tranzy.ai is operating on the most up to date data and they are offering an API to access the data -> https://tranzy.dev/
So this is the plan of actions:
Check if https://tranzy.dev/ is offering the latest information about the public transport in Chisinau, RTEC and PUA
I would have nothing against it, but before embarking on this journey we should ask whether this is necessary. Who would use the data? And for what purpose?
Roataway is currently frozen, and even if it weren't - we didn't use GTFS (though there was work in progress to use this for ETA calculation).
If Tranzy gives out GTFS data that are polished and usable "as is", then it is a low-hanging fruit. If not, then I think we should start by having a discussion with Roataway contributors to see if there is interest in putting energy into the project.
@iamandrewluca , @PlugaruT - what do you think? Perhaps we can set up a short video call to discuss it?
@ralienpp@iamandrewluca Updated gtfs
data -> updated google maps data. The current data which is displayed on the gmaps is from 2020, meanwhile new routes and trips have been added.
I posted in the Developer Community Moldova group from Facebook, maybe someone could pick this and start working on.
Right now gtfs static we have is pretty old, in the last two years RTEC and PUA added new routes and did some other changes, so we need to add the updates to our gtfs static repo.
I assume that tranzy.ai is operating on the most up to date data and they are offering an API to access the data -> https://tranzy.dev/
So this is the plan of actions:
The text was updated successfully, but these errors were encountered: