Event response \ Event response data example
Response contains XML document, data fields are as follows:
Field | Description |
TS |
Event timestamp, Unix timestamp, UTC, milliseconds
|
MOD_TS | Event timestamp, human readable
|
CAR_ID | Vehicle ID, per database id |
LPR | Number plate as text |
RTIME | License plate recognition duration, ms |
ACTION | Barrier action taken : 0= "no action", 1 = "opened" |
ACT_PARAM | deprecated |
THRESHOLD | Recognition confidence value, float |
ROI_X | ROI coordinates and dimensions |
ROI_Y |
ROI_W |
ROI_H |
LP_X | Number plate crop coordinates and dimensions |
LP_Y |
LP_W |
LP_H |
LP_BMP | URL of a plate image stored on a camera |
ROI_BMP | URL of a ROI image stored on a camera, if enabled |
COUNTRY | Alpha3 ISO3166 country code |
ROI_ID | ROI number, ACAP is supporting 2 ROI inthe frame |
ROI_IDU | reserved |
FRAMES | reserved |
DISTANCE | reserved |
SPEED | reserved |
DIRECTION | 2 IN 3 OUT 0,1- UNKNOWN
|
Event response data example
<event>
<TS>1528371395804689</TS>
<MOD_TS>2023-05-17 14:36:36 TRT</MOD_TS>
<CAR_ID>66948</CAR_ID>
<LPR>2AN2563</LPR>
<RTIME>150.0</RTIME>
<ACTION>0</ACTION>
<ACT_PARAM></ACT_PARAM>
<THRESHOLD>0.717648804187775</THRESHOLD>
<ROI_X>53</ROI_X>
<ROI_Y>54</ROI_Y>
<ROI_W>1728</ROI_W>
<ROI_H>972</ROI_H>
<LP_X>1501</LP_X>
<LP_Y>288</LP_Y>
<LP_W>168</LP_W>
<LP_H>28</LP_H>
<ROI_ID>1</ROI_ID>
<ROI_IDU>0</ROI_IDU>
<FRAMES>0</FRAMES>
<DISTANCE>0</DISTANCE>
<SPEED>0</SPEED>
<DIRECTION>1</DIRECTION>
<LP_BMP>tools.cgi?action=getImage&name=45/20230517143636_205385lp_2AN2563_2176954.png</LP_BMP>
<ROI_BMP>tools.cgi?action=getImage&name=44/20230517143635_805012lp_2AN2563_2176951.png</ROI_BMP>
<COUNTRY>CZE</COUNTRY>
</event>
Related Articles
JSON Fields (Protocol 1.6) \ JSON example
Token Type Format / Value Description packetCounter Unsigned int Counter of packets. Starts from “1”. Counter starts after successful connection or after start of device. It does not matter. datetime string YYYYMMDD HHMMSSFFF YYYY - year 4 digits MM ...
Package Description for License Plate Recognition (LPR)
Real-time recognition events are received from a camera using either the VAPIX or ONVIF protocol. These events provide relevant information related to license plate recognition, without including the actual image data. To learn more about the usage ...
HTML response
HTTP GET request target: http://<camera-IP-address>/local/fflprapp/events.cgi?<paramName1>=<value1>&<paramName2>=<value2> Request and response parameters are as above, while response data is wrapped into HTML instead of XML.
Managing License Plate Blacklist and Whitelist
CAMMRA offers the functionality to add license plates to both the blacklist and whitelist. You can conveniently add license plates directly through the web interface or import them from a CSV file. Here's how to manage the lists: Web Interface ...
Confidence level (recognition issue)
If you are experiencing frequent missed license plates, consider lowering the recognition confidence setting by 0.1 or 0.05. After adjusting the confidence level, monitor the system and review the results after 100-150 license plate events to gather ...