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
enum OccupancyStatus {
// The vehicle is considered empty by most measures, and has few or no
// passengers onboard, but is still accepting passengers.
EMPTY = 0;
// The vehicle has a relatively large percentage of seats available.
// What percentage of free seats out of the total seats available is to be
// considered large enough to fall into this category is determined at the
// discretion of the producer.
MANY_SEATS_AVAILABLE = 1;
// The vehicle has a relatively small percentage of seats available.
// What percentage of free seats out of the total seats available is to be
// considered small enough to fall into this category is determined at the
// discretion of the feed producer.
FEW_SEATS_AVAILABLE = 2;
// The vehicle can currently accommodate only standing passengers.
STANDING_ROOM_ONLY = 3;
// The vehicle can currently accommodate only standing passengers
// and has limited space for them.
CRUSHED_STANDING_ROOM_ONLY = 4;
// The vehicle is considered full by most measures, but may still be
// allowing passengers to board.
FULL = 5;
// The vehicle is not accepting additional passengers.
NOT_ACCEPTING_PASSENGERS = 6;
}
We should consume this data from the OBA REST API (when it is implemented) and expose it in the app. See OneBusAway/onebusaway-application-modules#121 for progress in providing this data via the OBA REST API.
Please note that not all agencies have the hardware to support real-time occupancy.
We can also support historical occupancy using a very similar format if an agency isn't able to supply real-time occupancy data, but is able to supply historical data via GTFS (exact design TBD).
The text was updated successfully, but these errors were encountered:
OccupancyStatus
is now an "experimental/proposed" GTFS-realtime field, as discussed on the gtfs-realtime list.Here’s an explanation of the enumeration values:
https://groups.google.com/forum/#!msg/gtfs-realtime/_HtNTGp5LxM/0mvvEW1WuMMJ
...and the same text inline, for convenience:
We should consume this data from the OBA REST API (when it is implemented) and expose it in the app. See OneBusAway/onebusaway-application-modules#121 for progress in providing this data via the OBA REST API.
Companion issue on iOS:
OneBusAway/onebusaway-iphone#361
Please note that not all agencies have the hardware to support real-time occupancy.
We can also support historical occupancy using a very similar format if an agency isn't able to supply real-time occupancy data, but is able to supply historical data via GTFS (exact design TBD).
The text was updated successfully, but these errors were encountered: