Bluetooth GATT Characteristic Reference
Location and Speed Characteristic (0x2A67)
The Location and Speed characteristic is a variable length structure containing a Flags field and, based on the contents of the Flags field, may contain a combination of data fields listed below. Note that it is possible for this characteristic to exceed the default LE MTU size.
Quick Summary
Payload length is profile-defined or variable based on field formats. This page is generated from official GATT XML and presented as implementation-ready guidance.
At a Glance
Key reference details for BLE implementation, interoperability testing, and AI-assisted troubleshooting.
| Property | Value |
|---|---|
| Name | Location and Speed Characteristic |
| UUID | 0x2A67 |
| Type | org.bluetooth.characteristic.location_and_speed |
| XML Root | Characteristic |
| Source File | org.bluetooth.characteristic.location_and_speed.xml |
| Field Count | 9 |
Field Specification
Parsed field definitions from the source XML value structure.
| Field | Requirement | Format | Unit | Exponent | Notes |
|---|---|---|---|---|---|
| Flags | Mandatory | 16bit | - | - | - |
| Instantaneous Speed | Optional | uint16 | org.bluetooth.unit.velocity.metres_per_second | -2 | Unit is in meters per second with a resolution of 1/100 |
| Total Distance | Optional | uint24 | org.bluetooth.unit.length.meter | -1 | Unit is in meters with a resolution of 1/10 |
| Location - Latitude | C1 | sint32 | org.bluetooth.unit.plane_angle.degree | -7 | Unit is in degrees with a resolution of 1/(10^7) |
| Location - Longitude | C1 | sint32 | org.bluetooth.unit.plane_angle.degree | -7 | Unit is in degrees with a resolution of 1/(10^7) |
| Elevation | Optional | sint24 | org.bluetooth.unit.length.meter | -2 | Unit is in meters with a resolution of 1/100 |
| Heading | Optional | uint16 | org.bluetooth.unit.plane_angle.degree | -2 | Unit is in degrees with a resolution of 1/100 |
| Rolling Time | Optional | uint8 | org.bluetooth.unit.time.second | 0 | Unit is in seconds with a resolution of 1 second |
| UTC Time | Optional | N/A | - | - | Smallest units in seconds |
Bit Map
Bit-level enumerations extracted from the XML BitField definition.
| Field | Bit | Size | Name | 0 Means | 1 Means |
|---|---|---|---|---|---|
| Flags | 0 | 1 | Instantaneous Speed Present | False | True |
| Flags | 1 | 1 | Total Distance Present | False | True |
| Flags | 2 | 1 | Location Present | False | True |
| Flags | 3 | 1 | Elevation Present | False | True |
| Flags | 4 | 1 | Heading Present | False | True |
| Flags | 5 | 1 | Rolling Time Present | False | True |
| Flags | 6 | 1 | UTC Time Present | False | True |
| Flags | 7 | 2 | Position Status | No Position | Position Ok |
| Flags | 9 | 1 | Speed and Distance format | 2D | 3D |
| Flags | 10 | 2 | Elevation Source | Positioning System | Barometric Air Pressure |
| Flags | 12 | 1 | Heading Source | Heading based on movement | Heading based on magnetic compass |
Byte Layout and Decode
Payload length is profile-defined or variable based on field formats.
function decodePayload(dataView, offset = 0) {
// Parse flags (16bit) according to Bluetooth format rules.
const instantaneous_speed = dataView.getUint16(offset + 0, true);
// Parse total_distance (uint24) according to Bluetooth format rules.
const location_latitude = dataView.getInt32(offset + 2, true);
const location_longitude = dataView.getInt32(offset + 6, true);
// Parse elevation (sint24) according to Bluetooth format rules.
const heading = dataView.getUint16(offset + 10, true);
const rolling_time = dataView.getUint8(offset + 12);
// Parse utc_time (N/A) according to Bluetooth format rules.
return { flags, instantaneous_speed, total_distance, location_latitude, location_longitude, elevation };
}Use Cases and Integration Notes
BLE Telemetry
Map characteristic values into dashboards and alerts for device observability.
Firmware Regression
Compare decoded fields across builds to detect protocol or scaling changes.
App Integration
Build stable parsing paths that convert raw payloads into typed app models.
Implementation Checklist
- Validate payload length and mandatory fields before decode.
- Decode with Bluetooth-specified signedness, unit, and exponent handling.
- Convert units at presentation boundaries to avoid drift in business logic.
- Persist raw packets and decoded values for reproducible troubleshooting.
FAQ
What is Location and Speed Characteristic in Bluetooth GATT?
Location and Speed Characteristic is defined as a Bluetooth GATT characteristic entry with type org.bluetooth.characteristic.location_and_speed and UUID 0x2A67.
What UUID identifies Location and Speed Characteristic?
The UUID for Location and Speed Characteristic is 0x2A67.
How should I parse Location and Speed Characteristic?
Payload length is profile-defined or variable based on field formats.
Where does this definition come from?
This page is generated from the Bluetooth SIG mirror XML in the oesmith/gatt-xml repository.
How does this page support BLE implementation?
The page combines structured tables, practical Q&A, and JSON-LD metadata to help teams validate integrations and troubleshoot consistently.