Localization
How to send localization data to twinzo REST API
ConfigurationPlease see the sectors configuration course to learn how the twinzo coordination system works and how to import your layouts to the digital twin. Localization works for registered devices only.
Devices: https://twinzo.eu/slides/slide/devices-84
Sectors: https://twinzo.eu/slides/slide/sectors-50
Localization data
Localization data can be sent to twinzo API per device or in a batch of devices at once. Each data record must include information about the position, timestamp, sector and device identifier in the case of a batch scenario.

The only difference in data payload is, that batch localization is wrapping the location contract into the parent object with the device login identifier. Bellow are described data contracts available for 3rd party integration. Other fields that visible in the swagger are only used for twinzo’s RTLS BLE solution and can be ignored. Coordinates must respect the settings of the sector coordinate system described in the sector edit section in the previous chapters.
{
Timestamp (integer),
SectorId (integer, optional),
X (number, optional),
Y (number, optional),
Z (number, optional),
Interval (integer, optional),
Battery (integer, optional),
IsMoving (boolean, optional),
LocalizationAreas(array integer, optional),
NoGoAreas(array integer, optional)
LocalizationAreas(array integer, optional),
NoGoAreas(array integer, optional)
}
- Login: Sensor login field(used as a unique identifier in the batch data POST).
- Timestamp: A Unix timestamp in milliseconds that represents the time when the data was collected.
- Timestamp: A Unix timestamp in milliseconds that represents the time when the data was collected.
- SectorId: An integer that represents the sector ID where the location data was collected.
- X: A number that represents the X coordinate of the location data.
- Y: A number that represents the Y coordinate of the location data.
- Z: A number that represents the Z coordinate of the location data.
- Interval: An integer that represents the interval at which the location data was collected. This interval means, what is the expected time gap between localization records. If the time gap between the records is more than 10*interval, this means there are missing positions and the next position will be highlighted as "respawn".
- Battery: An integer that represents the battery level at which the location data was collected.
- IsMoving: A boolean value that indicates whether or not the device was moving when the location data was collected. True value is required by default if the source system does not possess this information. Otherwise, devices won't move correctly in the 3D application.
- LocalizationAreas: List of IDs of areas in which the device is currently present in.
- NoGoAreas: List of IDs of no-go areas in which the device is currently present in.
- LocalizationAreas: List of IDs of areas in which the device is currently present in.
- NoGoAreas: List of IDs of no-go areas in which the device is currently present in.
Views | |
---|---|
1 | Total Views |
1 | Members Views |
0 | Public Views |
Actions | |
---|---|
0 | Likes |
0 | Dislikes |
0 | Comments |
Share by mail
Please login to share this webpage by email.