Reference documentation and code samples for the Google Maps FleetEngine V1 Client class VehicleAttribute.
Describes a vehicle attribute as a key-value pair. The "key:value" string
length cannot exceed 256 characters.
Generated from protobuf messagemaps.fleetengine.v1.VehicleAttribute
Namespace
Google \ Maps \ FleetEngine \ V1
Methods
__construct
Constructor.
Parameters
Name
Description
data
array
Optional. Data for populating the Message object.
↳ key
string
The attribute's key. Keys may not contain the colon character (:).
↳ value
string
The attribute's value.
↳ string_value
string
String typed attribute value. Note: This is identical to thevaluefield which will eventually be deprecated. For create or update methods, either field can be used, but it's strongly recommended to usestring_value. If bothstring_valueandvalueare set, they must be identical or an error will be thrown. Both fields are populated in responses.
↳ bool_value
bool
Boolean typed attribute value.
↳ number_value
float
Double typed attribute value.
getKey
The attribute's key. Keys may not contain the colon character (:).
Returns
Type
Description
string
setKey
The attribute's key. Keys may not contain the colon character (:).
Parameter
Name
Description
var
string
Returns
Type
Description
$this
getValue
The attribute's value.
Returns
Type
Description
string
setValue
The attribute's value.
Parameter
Name
Description
var
string
Returns
Type
Description
$this
getStringValue
String typed attribute value.
Note: This is identical to thevaluefield which will eventually be
deprecated. For create or update methods, either field can be used, but
it's strongly recommended to usestring_value. If bothstring_valueandvalueare set, they must be identical or an error will be thrown.
Both fields are populated in responses.
Returns
Type
Description
string
hasStringValue
setStringValue
String typed attribute value.
Note: This is identical to thevaluefield which will eventually be
deprecated. For create or update methods, either field can be used, but
it's strongly recommended to usestring_value. If bothstring_valueandvalueare set, they must be identical or an error will be thrown.
Both fields are populated in responses.
[[["Easy to understand","easyToUnderstand","thumb-up"],["Solved my problem","solvedMyProblem","thumb-up"],["Other","otherUp","thumb-up"]],[["Hard to understand","hardToUnderstand","thumb-down"],["Incorrect information or sample code","incorrectInformationOrSampleCode","thumb-down"],["Missing the information/samples I need","missingTheInformationSamplesINeed","thumb-down"],["Other","otherDown","thumb-down"]],["Last updated 2025-09-04 UTC."],[],[],null,["# Google Maps FleetEngine V1 Client - Class VehicleAttribute (0.4.1)\n\nVersion latestkeyboard_arrow_down\n\n- [0.4.1 (latest)](/php/docs/reference/maps-fleetengine/latest/V1.VehicleAttribute)\n- [0.4.0](/php/docs/reference/maps-fleetengine/0.4.0/V1.VehicleAttribute)\n- [0.3.1](/php/docs/reference/maps-fleetengine/0.3.1/V1.VehicleAttribute)\n- [0.2.0](/php/docs/reference/maps-fleetengine/0.2.0/V1.VehicleAttribute)\n- [0.1.6](/php/docs/reference/maps-fleetengine/0.1.6/V1.VehicleAttribute) \nReference documentation and code samples for the Google Maps FleetEngine V1 Client class VehicleAttribute.\n\nDescribes a vehicle attribute as a key-value pair. The \"key:value\" string\nlength cannot exceed 256 characters.\n\nGenerated from protobuf message `maps.fleetengine.v1.VehicleAttribute`\n\nNamespace\n---------\n\nGoogle \\\\ Maps \\\\ FleetEngine \\\\ V1\n\nMethods\n-------\n\n### __construct\n\nConstructor.\n\n### getKey\n\nThe attribute's key. Keys may not contain the colon character (:).\n\n### setKey\n\nThe attribute's key. Keys may not contain the colon character (:).\n\n### getValue\n\nThe attribute's value.\n\n### setValue\n\nThe attribute's value.\n\n### getStringValue\n\nString typed attribute value.\n\nNote: This is identical to the `value` field which will eventually be\ndeprecated. For create or update methods, either field can be used, but\nit's strongly recommended to use `string_value`. If both `string_value`\nand `value` are set, they must be identical or an error will be thrown.\nBoth fields are populated in responses.\n\n### hasStringValue\n\n### setStringValue\n\nString typed attribute value.\n\nNote: This is identical to the `value` field which will eventually be\ndeprecated. For create or update methods, either field can be used, but\nit's strongly recommended to use `string_value`. If both `string_value`\nand `value` are set, they must be identical or an error will be thrown.\nBoth fields are populated in responses.\n\n### getBoolValue\n\nBoolean typed attribute value.\n\n### hasBoolValue\n\n### setBoolValue\n\nBoolean typed attribute value.\n\n### getNumberValue\n\nDouble typed attribute value.\n\n### hasNumberValue\n\n### setNumberValue\n\nDouble typed attribute value.\n\n### getVehicleAttributeValue"]]
