Distinguish on-request stops

[Gerzer]

Some shuttle stops are on-request-only—i.e., buses don’t stop at them unless either someone is waiting at the stop or someone on the bus indicates to the driver that they want to get off. We should implement a Boolean flag that indicates whether a particular stop is on-request-only, returning this flag in response to /stops HTTP GET requests so that clients can display these stops differently to users. This will also involve devising some standard way to store this flag in our GPX files since those files are the ground-truth for all routes and stops data.

[a-winikoff]

On the North shuttle, the Barton Hall bus stop (while it does have a sign) is so underutilized that drivers never stop there (and in some cases don't even know the stop exists) unless explicitly asked for. This may be true with other stops on the North route (I don't really know, I don't use it regularly).

[Gerzer]

On the North shuttle, the Barton Hall bus stop (while it does have a sign) is so underutilized that drivers never stop there (and in some cases don't even know the stop exists) unless explicitly asked for. This may be true with other stops on the North route (I don't really know, I don't use it regularly).

I’m honestly considering removing the Barton Hall stop entirely after seeing buses use Sherry Road instead of Sage Avenue, which means that they aren’t even driving by the stop.

What do you think?

[Gerzer]

The Georgian Court and E-Lot stops on the North Route seem to lack signs, so maybe we should remove those, too.

The only on-request stops that that leaves are Academy Hall and Tibbits Avenue on the West Route.

[Aeonoi]

The web, android, and IOS team should implement a way to read the new stop.json file that added the isByRequest stops.