Home

Notes for presentation

General Suggestions

• There should be no such thing as a multisegment search.. Look at the Deutsche Bahn Webinterface. You first select one trip, then the trip back or to somewhere else. Step by Step. When gathering ALL possible connections and travel routes to take with 3 or more segments we easily get into a combinatorial explosion that we just can’t handle anymore. Even if all combinations could be found in like 6 Seconds we still need to display something like 2825761 (e.g. try 3 segments each from FRA to TXL) different routes you could take.
  And for a webservice this approach would also just not work. Maybe limit the maximum amount of results?
  My approach would be: Display the five cheapest trips, the five shortest trips and the five most accurate trips to your search. That would also clean up our result page a lot i think.