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

Add "num_usable_bikes" and "num_usable_spaces" to station_status.json #95

Closed
wants to merge 1 commit into from
Closed
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 2 additions & 0 deletions gbfs.md
Original file line number Diff line number Diff line change
Expand Up @@ -198,6 +198,8 @@ Field Name | Required | Defines
--------------------- | ----------| ----------
stations | Yes | Array that contains one object per station in the system as defined below
\- station_id | Yes | Unique identifier of a station (see station_information.json)
\- num_usable_bikes | Yes | Number of usable bikes at the station. A bike is usable if it's not broken and could be rented if `is_renting` was true.
\- num_usable_spaces | Yes | Number of usable docks at the station. A dock is usable if it's not broken and could receive bikes if `is_returning` was true.
\- num_bikes_available | Yes | Number of bikes available for rental
\- num_bikes_disabled | Optional | Number of disabled bikes at the station. Vendors who do not want to publicize the number of disabled bikes or docks in their system can opt to omit station capacity (in station_information), num_bikes_disabled and num_docks_disabled. If station capacity is published then broken docks/bikes can be inferred (though not specifically whether the decreased capacity is a broken bike or dock)
\- num_docks_available | Yes | Number of docks accepting bike returns
Expand Down