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
|`vehicle_attributes`| Conditionally Required | Array of [vehicle attributes](/modes/#vehicle-attributes)| Vehicle attributes appropriate for the current [mode][modes]|
119
+
|`battery_capacity`| Integer | Required if Available | Capacity of battery expressed as milliamp hours (mAh) |
120
+
|`fuel_capacity`| Integer | Required if Available | Capacity of fuel tank (liquid, solid, gaseous) expressed in liters |
115
121
116
122
201 Success Response:
117
123
@@ -251,7 +257,8 @@ A standard point of vehicle telemetry. References to latitude and longitude impl
251
257
|`gps.accuracy`| Float | Required if Available | Horizontal accuracy, in meters |
252
258
|`gps.hdop`| Float | Required if Available | Horizontal GPS or GNSS accuracy value (see [hdop][hdop]) |
253
259
| `gps.satellites` | Integer | Required if Available | Number of GPS or GNSS satellites
254
-
|`charge`| Float | Required if Applicable | Percent battery charge of vehicle, expressed between 0 and 1 |
260
+
|`battery_percent`| Integer | Required if Applicable | Percent battery charge of vehicle, expressed between 0 and 100 |
261
+
|`fuel_percent`| Integer | Required if Applicable | Percent fuel in vehicle, expressed between 0 and 100 |
255
262
|`stop_id`| UUID | Required if Applicable | Stop that the vehicle is currently located at. Only applicable for _docked_ Micromobility. See [Stops][stops]|
Copy file name to clipboardExpand all lines: geography/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
@@ -128,7 +128,7 @@ Type of geography. These specific types are recommendations based on ones common
128
128
|`municipal_boundary`| Edge of a city |
129
129
|`policy_zone`| Zone where [Policy](/policy) rules could be in effect, like operating area, distribution/equity zones, no/slow ride zone, no parking, etc |
130
130
|`county_boundary`| Edge of a county |
131
-
|`stop`| See [Stops](/general-information.ms#stops)|
131
+
|`stop`| See [Stops](/general-information.md#stops)|
132
132
|`council_district`| City council district |
133
133
|`political_district`| Politically defined voting area |
Copy file name to clipboardExpand all lines: modes/README.md
+4Lines changed: 4 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -58,10 +58,14 @@ The `trip_type` field allows the purpose of each trip segment to be described. S
58
58
59
59
The `trip_attributes` array allows additional mode-specific information about the nature of a trip to be described. It can return a list of JSON-formatted key/value pairs which correspond to the allowed attributes and values for the operative mode. See each [mode definition](#list-of-supported-modes) for details.
60
60
61
+
_See more available trip attributes for any mode in the [trips endpoint](/provider#trips)._
62
+
61
63
### Vehicle Attributes
62
64
63
65
The `vehicle_attributes` array returns a list of JSON-formatted key/value pairs which correspond to the allowed attributes and values for the operative mode. For each mode, the allowed attributes and corresponding values are defined in the [mode definition](#list-of-supported-modes).
64
66
67
+
_See more available vehicle attributes for any mode in the [vehicles endpoint](/provider#vehicles)._
68
+
65
69
### Accessibility Options
66
70
67
71
The `accessibility_options` array returns a list of JSON-formatted key/value pairs which correspond to the allowed accessibility attributes and values for the operative mode. For each mode, the allowed attributes and corresponding values are defined in the [mode definition](#list-of-supported-modes).
0 commit comments