Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Default Sequence: choose another trip #133

Open
answerquest opened this issue Dec 19, 2018 · 2 comments
Open

Default Sequence: choose another trip #133

answerquest opened this issue Dec 19, 2018 · 2 comments

Comments

@answerquest
Copy link
Collaborator

Problem description

Tool > "Default Route Sequence" page.

  • On choosing a route, the first trip on that route is loaded by default.
  • But in many cases, first trips are non-standard trips. There might be extra stops or some stops left out.
  • The last trip of the day is even more suspect :)

Suggested Flow

Two possible options :

  • Take the middle / median trip in the trips list for that route+direction.
  • Load first trip by default, but show a second dropdown and allow user to load a different trip instead.
@answerquest
Copy link
Collaborator Author

Obvious drawback of first option of taking middle/median trip : what if it's not the middle trip of the day, but another margin case? We have no control on how people sort their data before they import it into the tool.

@answerquest
Copy link
Collaborator Author

Another approach : Do it like transitfeed ScheduleViewer does it : Identify the unique trip patterns in the route and list them all. Let user pick the one they want. Then they can edit that pattern, give it a shape.

Or, let them create a new pattern.

If multiple patterns, then a default pattern will have to be set.

It would be nice to enable display of all the varying patterns on the map at the same time.

Man, this rabbit hole just keeps getting deeper.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant