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

Bus stop routes overview: colours distinguishing up/downroute #47

Open
ghost opened this issue Jan 30, 2021 · 2 comments · May be fixed by #64
Open

Bus stop routes overview: colours distinguishing up/downroute #47

ghost opened this issue Jan 30, 2021 · 2 comments · May be fixed by #64
Labels

Comments

@ghost
Copy link

ghost commented Jan 30, 2021

I'm not sure how the current colour scheme is programmed, but would it be possible to, for a bus stop routes overview (for example [https://busrouter.sg/#/stops/59051/routes] ) to colour route segments going towards the bus stop (i.e. uproute) in one colour, and segments going away from the bus stop (i.e. downroute) in another? For stops where the same service serving opposite destinations both ply (e.g. 139 at BS 52109 or 856 at BS 47201), two separate lines can be shown.

This is a good-to-have feature of course and doesn't require priority.

@emer7
Copy link

emer7 commented Jan 21, 2022

Hi I am interested in taking up this issue

I skimmed through assets/app.js and I think adding some simple styling to Mapbox layer should work?

@cheeaun
Copy link
Owner

cheeaun commented Jan 21, 2022

@emer7 hey sure, you can try it out and experiment.

On my side, I generally don't know how to solve this problem yet. Few notes:

  • Colors are tough, especially on a map 😄
  • There are arrow icons but things can get very messy when there are a lot of lines.
  • Some bus routes are very fancy, like can loop back again to the same stop, skip stops even though it's on the same road/track, etc.

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

Successfully merging a pull request may close this issue.

2 participants