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
TBD -- Are there additional fields that should be permitted to update with a PUT?
257
257
258
258
**Endpoint:**`/stops/:stop_id`
259
259
**Method:**`GET`
260
260
**[Beta feature](/general-information.md#beta-features):** Yes (as of 1.0.0)
261
-
**`data` Payload:**`{ "stops": [] }`, an array of [Stops](../general-information.md/#stop)
261
+
**`data` Payload:**`{ "stops": [] }`, an array of [Stops](/general-information.md#stop)
262
262
263
263
In the case that a `stop_id` query parameter is specified, the `stops` array returned will only have one entry. In the case that no `stop_id` query parameter is specified, all stops will be returned.
| stop_id | UUID | Required | Unique ID for stop |
114
-
| stop_name | String | Required | Name of stop |
115
-
| last_reported | Timestamp | Required | Date/Time that the stop was last updated |
116
-
| location | GeoJSON [Point Feature](provider/README.md#geographic-data)| Required | Location of the Stop |
117
-
| status | Enum | Required | Status of the Stop. See [Stop Statuses](#stop-statuses) table. |
118
-
| capacity | {vehicle_type: number} | Required | Number of total spots per vehicle_type |
119
-
| num_vehicles_available | {vehicle_type: number} | Required | How many vehicles are available per vehicle_type at this stop? |
120
-
| num_vehicles_disabled | {vehicle_type: number} | Required | How many vehicles are unavailable/reserved per vehicle_type at this stop? |
121
-
| geography_id | UUID | Optional | Pointer to the Geography that represents the Stop geospatially |
122
-
| region_id | string | Optional | ID of the region where station is located, see [GBFS Station Information](https://github.com/NABSA/gbfs/blob/master/gbfs.md#station_informationjson)|
| stop_id | UUID | Required | Unique ID for stop |
114
+
| stop_name | String | Required | Name of stop |
115
+
| last_reported | Timestamp | Required | Date/Time that the stop was last updated |
116
+
| location | GeoJSON [Point Feature](provider/README.md#geographic-data)| Required | Location of the Stop |
117
+
| status | Enum | Required | Status of the Stop. See [Stop Statuses](#stop-statuses) table. |
118
+
| capacity | {vehicle_type: number} | Required | Number of total spots per vehicle_type |
119
+
| num_vehicles_available | {vehicle_type: number} | Required | How many vehicles are available per vehicle_type at this stop? |
120
+
| num_vehicles_disabled | {vehicle_type: number} | Required | How many vehicles are unavailable/reserved per vehicle_type at this stop? |
121
+
| managed_by | UUID | Optional |`provider_id` for the provider which manages this stop. null/undefined if city managed. |
122
+
| geography_id | UUID | Optional | Pointer to the Geography that represents the Stop geospatially |
123
+
| region_id | string | Optional | ID of the region where station is located, see [GBFS Station Information](https://github.com/NABSA/gbfs/blob/master/gbfs.md#station_informationjson)|
| rental_methods |[Enum](https://github.com/NABSA/gbfs/blob/master/gbfs.md#station_informationjson)| Optional | Payment methods accepted at stop, see [GBFS Rental Methods](https://github.com/NABSA/gbfs/blob/master/gbfs.md#station_informationjson)|
128
+
| cross_street | String | Optional | Cross street of where the station is located. |
129
+
| num_spots_available | {vehicle_type: number} | Optional | How many spots are free to be populated with vehicles at this stop? |
130
+
| num_spots_disabled | {vehicle_type: number} | Optional | How many docks are disabled and unable to accept vehicles at this stop? |
131
+
| parent_stop | UUID | Optional | Describe a basic hierarchy of stops (e.g.a stop inside of a greater stop) |
132
+
| vehicle_ids | UUID[]| Optional | List of device_ids for vehicles which are currently at this stop |
132
133
133
134
### Stop Statuses
134
135
@@ -142,7 +143,7 @@ All String fields, such as `vehicle_id`, are limited to a maximum of 255 charact
142
143
143
144
Some of the fields in the `Stops` definition are using notions which are currently not in MDS, such as `rental_methods`. These fields are included for compatibility with GBFS.
Copy file name to clipboardExpand all lines: provider/README.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -356,7 +356,7 @@ In addition to the standard [Provider payload wrapper](#response-format), respon
356
356
**Endpoint:**`/stops/:stop_id`
357
357
**Method:**`GET`
358
358
**[Beta feature](/general-information.md#beta-features):** Yes (as of 1.0.0)
359
-
**`data` Payload:**`{ "stops": [] }`, an array of [Stops](../general-information.md/#stop)
359
+
**`data` Payload:**`{ "stops": [] }`, an array of [Stops](/general-information.md#stop)
360
360
361
361
In the case that a `stop_id` query parameter is specified, the `stops` array returned will only have one entry. In the case that no `stop_id` query parameter is specified, all stops will be returned.
0 commit comments