I have found several searches in which the result seems to be too long to be logical. For example: 10 hour long routes. I think the problem it is related to the transition between one server and the other, as there is too much time between the arrival to the shared vertex and the departure from the next stop.
An example of this long search result:
Depart: 42.889675,-2.639122
Destination: 43.314125,-2.006378
When:
Depart
11:08am
11/24/2013
Travel by: Transit
Show me the: Quick trip
Maximun walk: 1/2mile
Walk speed: 3mph
In addition, when this problem happens, the longest result is shown first to the user, before other shorter options.
Example of search:
An example of this long search result:
Depart: 43.314125,-2.006378
Destination: 42.889675,-2.639122
I have found several searches in which the result seems to be too long to be logical. For example: 10 hour long routes. I think the problem it is related to the transition between one server and the other, as there is too much time between the arrival to the shared vertex and the departure from the next stop.
An example of this long search result: Depart: 42.889675,-2.639122 Destination: 43.314125,-2.006378
When:
Travel by: Transit Show me the: Quick trip Maximun walk: 1/2mile Walk speed: 3mph
In addition, when this problem happens, the longest result is shown first to the user, before other shorter options.
Example of search:
An example of this long search result: Depart: 43.314125,-2.006378 Destination: 42.889675,-2.639122
When: