@felixguendling@mastodon.social
Power to the people! 
v2.2 can now post-process timetable data using Lua scripts to improve the user experience.
timetable data is often inconsistent in naming trips, stops and routes, contains wrong coordinates, or needs to be filtered.
Some of these problems can now be solved by writing small scripts to process entities when MOTIS imports the data.
This way, @transitous and @traewelling can have proper train numbers.
More in the documentation: https://github.com/motis-project/motis/blob/master/docs/scripting.md
@felixguendling @transitous @traewelling
We have served as many as 500 GTFS feeds at once. This involved creating a small collection of filters to solve a range of problems with the feeds that weren鈥檛 practical to get fixed upstream.I look forward to this feature to extending to cover more of the GTFS data as time goes on!
@felixguendling @transitous To get an idea of what's useful for filtering in , here are real-world problems that we have written our own filters for in the past:
- Adding Feed IDs
- Adding missing details to "feed_info.txt"
- Dropping fare broken fare rules. We didn't need them for routing.
- Dropping broken feed info (as an alternative to fixing it!)
- Flattening the zip file (we do this universally. The zip file shouldn't have any nested folders but some do).
To be continued! 
