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
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.
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 ...
Real-time Events API (VAPIX or ONVIF)
To receive real-time recognition events from the camera, you can utilize either the VAPIX or ONVIF protocol. These protocols allow you to access event data packets containing relevant information without the actual image. The packet structure for ...
API FF Integration Events \ HTTP Multipart POST
New Event: This event occurs when a vehicle is detected for the first time. The direction of the vehicle is undefined. Update Event: This event occurs when there is a change in the data package. It can include updates to the recognized license plate, ...
Simple Web form for testing receiver
ff_post_form.html <html> <head> <meta http-equiv="content-type" content="text/html; charset=UTF-8"> </head> <form method="post" enctype="multipart/form-data" action="ff_post.php"> Enter event file: <input type="file" name="event" size="40"> Enter ...