Add button to enable/disable flights in the web interface

[jbruechert]

Flights can be very disruptive and replace all other routes due to being faster on paper. MOTIS currently cant't handle the transfer between eg. a train and an airport which takes long in practise.

Currently we have very little data for flights but it looks like that could change.

They should then be off by default.

[Altonss]

They should then be off by default.

I'm not sure this is a good idea. A lot of remote areas might only (or at least mainly) be accessible by flights. Turning flights off by default would result in no/not practical routing options for those areas.

We should rather fix the transfer problems, but I don't know how hard it is 🤔 What's the main issue there? Pedestrian routing or adding buffer transfer times for things like security checks?

[felixguendling]

At the moment, the default setting is to not route transfers with pedestrian routing. So that's not an issue (for now).

The problem is time for boarding start (+-30min before takeoff), security checks, luggage, etc. Usually, the recommendation is to arrive 2h before (maybe a bit less if you don't have checkin luggage). So the footpath length between the bus stop and airport stop should probably be at least 1,5 hours.

• In many cases, this can't be modelled in one dataset because flights and public transport come from different data sources which are only connected inside MOTIS. I guess one option would be to add 1,5h to every footpath going to or coming from stops with only flight routes.
• If there's one dataset that contains both, the transfer has to be modelled in the transfers.txt file. Then we only have to make sure that MOTIS doesn't create any additional edges that are faster.

[Altonss]

• I guess one option would be to add 1,5h to every footpath going to or coming from stops with only flight routes.

Wouldn't this look strange to the user, as it would display a very long walk time?

[felixguendling]

I think that's more a matter of how to deal with this in the user interface. Maybe the API could annotate those footpaths with an additional flag that tells the UI to not display it as a pure footpath but rather a buffer for security checks, luggage checkin, boarding, etc. But overall this is probably what the user wants in terms of feasibility (is it realistic to take this trip).