Motion Tracking System
The Motion Tracking System (a.k.a., Device Tracking System) is a collection of location-data-driven services that allow a user to query and extract location data from the system in multiple formats granting various insights, alerts, and notifications based on different events and rules. These triggers are offered by the system or configured by the user.
Devices send real-time tracking data to MTS in a predefined format and MTS is responsible to store it and make it available for various data consumers(dashboard/UI/other platform applications). Appropriate APIs are exposed to insert as well as extract data from MTS.
MTS Service provides APIs and Pub-Sub mechanisms for continuous tracking of device location or geofence entry/exit events.
📘 What is GPS Tracking Device?
A GPS tracking device is a navigation device normally on a vehicle, asset, or person that uses the Global Positioning System(GPS) to determine its movement and also determine its geographic position to determine its location.
App developers can leverage MTS for storing and managing real-time tracking data for their use, reducing their development effort and time. Developers can use data from MTS and write their business logic using the APIs exposed by MTS.
- Fleet Management: Monitor vehicle locations and optimize routes for better efficiency.
- Asset Tracking: Maintain real-time visibility of valuable assets to prevent loss or theft.
- Safety Solutions: Implement applications that ensure personal safety through location tracking.
- Logistics: Improve tracking of deliveries and enhance operational efficiency.
- Sports and Fitness: Analyze performance metrics using real-time location data.
MTS Geofence
MTS Tiles
MTS ETA
Speed Profiling
MTS Nearby Search
- Onboard a new device onto MTS so that it can start sending trace data via MQTT broker or via API. This POST API can be used by any source that needs to send data to MTS via the MQTT broker. The API accepts a device. This hardware ID needs to be unique for every device. In the case of FE mobile apps.
- The UpdateTraceData API is used to insert trace data to MTS. You can insert trace data using either trackName or trackId.
- The GetTraceData API fetches trace data for a specific device within a specified time range using the trackName or trackId.
- The GetMissingSequenceNumbers API fetches missing sequence numbers for a specific deviceId and app and in between the provided time.
- The DeregisterDevice API is used to deregister devices in MTS by passing the isActive parameter in the body. The GetAllDevices API returns all devices pertaining to a specific tenant_id.
MTS also has the functionality of sending a notification once the location of a GPS device is close to a mentioned geographic location. You can create a new geofence entry in the database for which the notification is to be sent when the GPS device approaches the location.
The CreateSubscription API can be used to add a new subscription configuration to the Cassandra table. The following parameters will be passed in the body:
Member | Description | Data type |
|---|---|---|
interval | Time interval in seconds between two trace packets while streaming. | integer |
expiry | Topic expiry time. | string |
With the GetSnappedDistance API, you can easily obtain the distance covered by a device during specific time intervals. This feature enables you to precisely calculate the distance traveled, which can be useful for determining driver payouts or more accurately measuring fuel usage.
Parameter | Description |
|---|---|
deviceId | The ID of the device to retrieve distance for. |
app | Your appId provided after registration. |
startTime | The start time of the period to calculate distance over (ISO 8601 format). Limits: This timestamp cannot be older than 2 days from current time. |
endTime | The end time of the period to calculate distance over (ISO 8601 format). |
Field | Description |
|---|---|
totalTraces | The total number of trace points for the device in the specified time period. |
rsOutput | Output from the RouteStats snapped distance algorithm. |
confidence | The confidence level of the calculated distance. Possible values are high, medium, medium_1, medium_2, medium_3, or low. |
distance | The snapped distance traveled by the device in meters, calculated by RouteStats. |
Example Response
The response shows a snapped distance of 37.4 km calculated with high confidence. The totalTraces indicates there were 250 location traces analyzed to calculate the distance.