Five weeks in and #Transitous' coverage in Europe is filling up nicely. There are big ČD- and MÁV-shaped holes still though, pointers to #GTFS feeds very welcome :)
Five weeks in and #Transitous' coverage in Europe is filling up nicely. There are big ČD- and MÁV-shaped holes still though, pointers to #GTFS feeds very welcome :)
And here is Hungary a few hours later :)
(screenshot from a local test, deployment to the #Transitous instance still in review)
@VolkerKrause Oh I love the project, we desperately need cross-border public transport planning! I already managed to get it to 504 though, seems it has a bit of trouble doing longer trips across borders 😅
Is this going to be integrated into KTrip?
@bart Please add the affected routes/scenarios to https://github.com/motis-project/motis/issues/471, this is being worked on :)
Integration with KPublicTransport (and thus KTrip/Itinerary) should be ready in time for 24.05. It's already fully implemented, just not enabled by default yet.
@VolkerKrause Awesome!
How is Motis related to Transitous though? I got the error on https://routing.spline.de which is linked on the Transitous repo, but seems to be running Motis?
It also needs some translation fixes though, lots of texts are German only 😅
@bart Transitous is the service and MOTIS is the software.
Just like what Wikipedia is to Mediawiki.
@VolkerKrause, far from my expertise, but seems like it yes.
@anze , ideas?
@taketwo The regulations in this area seem to be rather weak on the enforcement side unfortunately.
We do have realtime data in some areas, but it is indeed not as widely available yet as static schedules. GBFS data (bikes, scooters, etc) is a bit more common, but we don't have that enabled yet, that needs OSM routing integration set up first.
And yes, just filling the white holes isn't enough obviously. It does help us with an immediate problem of hitting some edge cases in the router though.