How To Integrate With Hikvision LPR
How To Integrate With Hikvision LPR
ISAPI
Version: 1.1.0
Date: 2016-04-17
2. Overview
Vehicle Detection and Mixed-traffic Detection are available for the road traffic monitoring. In
Vehicle Detection, the passed vehicle can be detected and the picture of its license plate can
be captured; besides, the vehicle color, vehicle logo and other information can be recognized
automatically.
In Mixed-traffic Detection, the pedestrian, motor vehicle and non-motor vehicle can be
detected, and the picture of the object (for pedestrian/non-motor vehicle/motor vehicle
without license plate) or license plate (for motor vehicle with license plate) can be captured.
You can send alarm signal to notify the surveillance center and upload the captured picture
to FTP server.
Note:
Road traffic function varies according to different camera models.
3.1.1 /ISAPI/Traffic/Capabilities
3.1.2 /ISAPI/Traffic/plateList
Query None
PUT
Description Import license plate of black and white black list
Query None
3.1.3 /ISAPI/ITC/capability
3.1.4 /ISAPI/ContentMgmt/search
3.1.5 /ISAPI/Traffic/channels/<ID>/CurVehicleDetectMode
3.1.6 /ISAPI/Traffic/channels/<ID>/vehicleCalibration
3.1.7 /ISAPI/Traffic/channels/<ID>/vehicleDetect/plates
3.1.8 /ISAPI/Traffic/channels/<ID>/vehicleDetect
3.1.10 /ISAPI/Traffic/channels/<ID>/vehicleDetect/capabilities
3.1.11 /ISAPI/Traffic/channels/<ID>/licensePlateAuditData
3.1.12 /ISAPI/Traffic/channels/<ID>/searchLPListAudit
3.1.13 /ISAPI/Traffic/channels/<ID>/picParam
3.1.14 /ISAPI/Traffic/channels/<ID>/picParam/capabilities
3.1.15 /ISAPI/System/Video/inputs/channels/ID/VCAResource
3.1.16 /ISAPI/Traffic/channels/<ID>/vehicleDetect/config
/ISAPI/System/Network/ftp/capabilities
/ISAPI/System/Network/ftp
/ISAPI/System/Network/ftp/<ID>
Depending on the value of <addressingFormatType>, either the <hostName> or the IP address fields
will be used to locate the NTP server.
Note: FTP transfers are always in binary mode.
<pathDepth> the depth of path. For example, / depth is 0, /a depth is 1, /a/b depth is 2
/ISAPI/System/Network/ftp/test
/ISAPI/System/Network/ftp/uploadInfo
3.1.18 Snapshot
/ISAPI/Snapshot
/ISAPI/Snapshot/channels
/ISAPI/Snapshot/channels/<ID>
3.1.19 /ISAPI/Event
The event trigger list defines the set of device behaviors that trigger events.
The event schedule defines when event notifications are active.
/ISAPI/Event/capabilities
/ISAPI/Event/triggersCap
/ISAPI/Event/triggers
Event triggering defines how the device reacts to particular events, such as video loss or motion
detection.
/ISAPI/Event/triggers/<ID>
An event trigger determines how the device reacts when a particular event is detected. The
following types are supported:
IO: trigger when an input IO port changes state.
VMD: trigger on video motion detection.
Video loss: trigger when the input video signal cannot be detected.
Disk failure: trigger when a disk fails.
Recording failure: trigger when recording fails: either there is a problem with the disk, or the
storage volume is full, or the volume is corrupt.
Bad video: trigger when the input video is bad.
POS: trigger when a point-of-sale event is detected.
Analytics: trigger on a general analytics event. Currently analytics events apart from
VMD, which has its own event trigger, are not supported. Fan failure: trigger when a fan fails.
Nicbroken: trigger when net interface is broken.
Resolution mismatch: trigger when video input port resolution is not matched up to compress
resolution.
/ISAPI/Event/triggers/<ID>/notifications
/ISAPI/Event/schedules/inputs
/ISAPI/Event/schedules/inputs/<ID>
/ISAPI/Event/schedules/outputs
/ISAPI/Event/schedules/blackList
/ISAPI/Event/schedules/whiteList
/ISAPI/Event/notification/httpServers/ID