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

Random feature ideas #8

Open
elad661 opened this issue Jun 3, 2018 · 2 comments
Open

Random feature ideas #8

elad661 opened this issue Jun 3, 2018 · 2 comments

Comments

@elad661
Copy link
Owner

elad661 commented Jun 3, 2018

  • Fuzzy stop name search, curlbus.app/~<something> to find stop codes matching a specific name
  • Direct routing (no transfers!), curlbus.app/<stop_code>/to/<other_stop_code> will show only lines that will take you from the first stop to the other stop.
  • Static schedule for stop? Frequencies? this needs some thought.
  • Filtering using the URL, to only see lines you care about for a specific stop. This needs thought about syntax (perhaps curlbus.app/<stop_code>|dan1|dan51 or something similar)
    • Alternatively, curlbus.app/<operator>/<route>/<alternative>/<stop_code>, but that doesn't allow chaining. Would be nice to support both as the latter is more discoverable, but the first is more useful.
  • Show status for trains? (delayed/on-time)
  • Show distance on-route (using shapes.txt) of the nearest bus from the current stop. Calculating this is expensive in terms of CPU time, is it worth it?
@danyshaanan
Copy link
Contributor

  • Location based stop identification in web interface. Allow browser access of location services to guess my current stop / show a short list of the closest stops.
  • Show time to future stops for the bus I'm on. (chosen through location services, or from bus stop list).

I'd be happy to help out with anything.

@elad661
Copy link
Owner Author

elad661 commented Dec 23, 2018

when I first designed curlbus I thought I don't want to get location info from users, because I didn't want to deal with the privacy implications. However, since #17 curlbus has a nearby stops endpoint, so there's no reason to not implement this.

I would accept a pull request that adds this kind of functionality with some interface that keeps the spirit of the esthetics of curlbus's web UI (which tries to imitate an actual console as much as possible)

Regarding "how time to future stops for the bus you're on" that sounds very complicated, because you'd need to know exactly which bus (specific bus, not just line number) you're on, and your location, and update in real time... I don't think curlbus fits this usecase. Google Maps and Moovit already provide this functionality in a very easy to use way.

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

2 participants