How to access the speed, distance and other fileds from RTSP radar-video fusion Metadata Stream using Axis Q1656 DLE Radar-Video Fusion Camera #902
Replies: 2 comments
-
This automatically generated reply acts as a friendly reminder. Answers to your questions will most often come from the community, from developers like yourself. You will, from time to time, find that Axis employees answers some of the questions, but this is not a guarantee. Think of the discussion forum as a complement to other support channels, not a replacement to any of them. If your question remains unanswered for a period of time, please revisit it to see whether it can be improved by following the guidelines listed in Axis support guidelines. |
Beta Was this translation helpful? Give feedback.
-
Hi @gahangandi11 ,
|
Beta Was this translation helpful? Give feedback.
-
Hi, I found some information on this page how to access the rtsp radar video fusion metadata stream from the axis Q1656 camera.
https://developer.axis.com/analytics/radar-video-fusion
I want to access the speed and distance values from the rtsp radar-video fusion meta data stream and integrate with a third party python application. But I am facing issues on how to decode this stream and access those fields in the meta data stream.
I am using this link for the rtsp metadata stream given in the page.
/axis-media/media.amp?camera=2&video=0&audio=0&analytics=polygon
when i try to see the stream using simple gstreamer pipeline, it is encoded with a lot of binary and other data that i do not understand how to decode and parse it to successfully access the speed and distance values in each metadata frame. I would really appreciate any support here.
This is the gstreamer pipeline that i built to dump the metadata from the stream.
gst-launch-1.0 rtspsrc location="rtsp://:@128.206.18.61/axis-media/media.amp?camera=2&video=0&audio=0&analytics=polygon" ! fakesink dump=true
I can see something like this in my terminal ,
00000340 (0x7396b001cde0): 6e 3e 3c 61 78 72 74 3a 52 61 64 61 72 4f 62 6a n><axrt:RadarObj
00000350 (0x7396b001cdf0): 65 63 74 49 6e 66 6f 20 78 6d 6c 6e 73 3a 61 78 ectInfo xmlns:ax
00000360 (0x7396b001ce00): 72 74 3d 22 68 74 74 70 3a 2f 2f 77 77 77 2e 61 rt="http://www.a
00000370 (0x7396b001ce10): 78 69 73 2e 63 6f 6d 2f 32 30 31 37 2f 72 61 64 xis.com/2017/rad
00000380 (0x7396b001ce20): 61 72 2f 61 78 72 74 22 3e 3c 61 78 72 74 3a 50 ar/axrt"><axrt:P
00000390 (0x7396b001ce30): 6f 6c 61 72 43 6f 6f 72 64 69 6e 61 74 65 20 61 olarCoordinate a
000003a0 (0x7396b001ce40): 6e 67 6c 65 3d 22 31 35 2e 37 30 35 31 22 20 72 ngle="15.7051" r
000003b0 (0x7396b001ce50): 61 6e 67 65 3d 22 32 2e 30 33 37 30 39 22 20 65 ange="2.03709" e
000003c0 (0x7396b001ce60): 6c 65 76 61 74 69 6f 6e 2d 61 6e 67 6c 65 3d 22 levation-angle="
000003d0 (0x7396b001ce70): 30 22 2f 3e 3c 61 78 72 74 3a 56 65 6c 6f 63 69 0"/><axrt:Veloci
000003e0 (0x7396b001ce80): 74 79 20 6d 2d 73 3d 22 31 2e 34 30 38 36 32 22 ty m-s="1.40862"
000003f0 (0x7396b001ce90): 20 61 6e 67 6c 65 3d 22 31 36 38 2e 37 37 22 20 angle="168.77"
00000400 (0x7396b001cea0): 65 6c 65 76 61 74 69 6f 6e 2d 61 6e 67 6c 65 3d elevation-angle=
00000410 (0x7396b001ceb0): 22 30 22 2f 3e 3c 61 78 72 74 3a 53 69 7a 65 20 "0"/><axrt:Size
00000420 (0x7396b001cec0): 6d 3d 22 32 2e 33 22 20 2f 3e 3c 2f 61 78 72 74 m="2.3" /></axrt
00000430 (0x7396b001ced0): 3a 52 61 64 61 72 4f 62 6a 65 63 74 49 6e 66 6f :RadarObjectInfo
00000440 (0x7396b001cee0): 3e 3c 2f 74 74 3a 45 78 74 65 6e 73 69 6f 6e 3e ></tt:Extension>
00000450 (0x7396b001cef0): 3c 2f 74 74 3a 41 70 70 65 61 72 61 6e 63 65 3e </tt:Appearance>
00000460 (0x7396b001cf00): 3c 74 74 3a 42 65 68 61 76 69 6f 75 72 3e 3c 74 tt:Behaviour<t
00000470 (0x7396b001cf10): 74 3a 53 70 65 65 64 3e 31 2e 34 30 38 36 32 3c t:Speed>1.40862<
00000480 (0x7396b001cf20): 2f 74 74 3a 53 70 65 65 64 3e 3c 74 74 3a 44 69 /tt:Speed><tt:Di
00000490 (0x7396b001cf30): 72 65 63 74 69 6f 6e 20 79 61 77 3d 22 2d 37 38 rection yaw="-78
000004a0 (0x7396b001cf40): 2e 37 37 30 35 22 20 70 69 74 63 68 3d 22 30 22 .7705" pitch="0"
000004b0 (0x7396b001cf50): 20 2f 3e 3c 2f 74 74 3a 42 65 68 61 76 69 6f 75 /></tt:Behaviou
000004c0 (0x7396b001cf60): 72 3e 3c 2f 74 74 3a 4f 62 6a 65 63 74 3e 3c 2f r></tt:Object></
000004d0 (0x7396b001cf70): 74 74 3a 46 72 61 6d 65 3e 3c 2f 74 74 3a 56 69 tt:Frame></tt:Vi
000004e0 (0x7396b001cf80): 64 65 6f 41 6e 61 6c 79 74 69 63 73 3e 3c 2f 74 deoAnalytics></t
000004f0 (0x7396b001cf90): 74 3a 4d 65 74 61 64 61 74 61 53 74 72 65 61 6d t:MetadataStream
00000500 (0x7396b001cfa0): 3e 0a >.
I can see some fields like speed and distance in the output , I want to know if there is a simpler way to decode this stream and access those fields easily from a third party application like simple C or python program..
Thanks
Beta Was this translation helpful? Give feedback.
All reactions