Open elad661 opened 6 years ago
I'd be happy to help out with anything.
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 https://github.com/elad661/curlbus/issues/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.
curlbus.app/~<something>
to find stop codes matching a specific namecurlbus.app/<stop_code>/to/<other_stop_code>
will show only lines that will take you from the first stop to the other stop.curlbus.app/<stop_code>|dan1|dan51
or something similar)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.