You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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?
The text was updated successfully, but these errors were encountered:
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).
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.
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.The text was updated successfully, but these errors were encountered: