Metropolis Microservices/RidgeRun Services/Engagement Analytics: Difference between revisions

Metropolis Microservices/RidgeRun Services/Engagement Analytics (view source)

96 bytes added , 26 March

3,072

edits

❯

@@ Line 101: / Line 101: @@
 *'''message_expiration:''' This is the amount of seconds used for engagement messages expiration. If a person is not seen for this configured amount of time, the entry will automatically disappear from redis.
-== Heatmap ==
+== Statistics ==
-The heatmap can be enabled/disabled by using the '''heatmap''' field in the configuration. If enabled, a heatmap will be overlayed on top of the BEV stream. The data for the heatmap is obtained from redis from the Heatmap stream with the following format:
+The service reads detection/direction statistics from redis with the following format:
-<pre>
+<syntaxhighlight lang=JSON>
-"heatmap":[{"position":{"x":int, "y": int}, "intensity":float, "radius": int}, {"position":{"x":int, "y": int}, "intensity":float, "radius": int}, ...]
+{
-</pre>
+    "id": 1,
+    "cameraid": "cam1",
+    "timestamp": "2025-01-01T00:00:00Z",
+    "width": 1920,
+    "height": 1080,
+    "detections": [
+        {
+            "objectid": "object1",
+            "position": {
+                "x": 10,
+                "y": 20
+            },
+            "direction": {
+                "x": 1,
+                "y": 0
+            }
+        }
+    ]
+}
+</syntaxhighlight>
 == Running the Service ==