Verkada Line Crossing, Loitering, and Crowd Detection Analytics Tested
Verkada has released Alerts for Line Crossing, Loitering, and Crowd Detection, adding these widely available functionalities to its offerings. But how well do they work?
We tested the Line crossing, Crowd and Loitering analytics outdoors and indoors, examining:
- *** **** ** **** ****** ****** and ******** ** *** ********** ******* of ********?
- *** ** *** ********* ******* ** low *****?
- *** **** ** **** **** ** rainy **********?
- *** ********** ** **** ***** ** line ********* *** **** *********?
- *** ******* *** *** ****** ** configure?
Configuration ********
** ********* **** ********, *****, *** loitering ****** ** ******* ******* ******* Verkada *******:
- Line ********: Users can draw up to 4 lines, each set to detect in one or both directions.
- Crowd *********: Users can define up to 3 crowd areas to detect people, vehicles, or both, ranging from 2 to 10 people/vehicles.
- Loitering: Users can draw up to 3 loitering areas, selecting either people or vehicles, with timer options of 10, 15, 30 seconds, or 1, 2, or 5 minutes.
************
********* ** *******, ****** *** **** crossing, *********, *** ***** ********* *** available ** *** ********* **** * valid ****** *******. ***** ******** *** supported ** *** *** *** ********** dome, ******, *** ******* *******, ** well ** *** ********.
Executive *******
***** *******'* ****** *** **** ********, crowd, *** ********* ********* ********* ********** in *******, ** *********** ****** ** a *** ******** **********.
******* ****** **** ** ********* ****** and ******** ** *** ********** ******* of ********, ********* ** **** *** low ***** **********, **** ******* *** outdoors, *** *** *** ******** ***** alerts *** ** ****.
*******, ******* *** ******** ** *** following ***** *********:
- *** ********* ******* **** ** ****, the ****** ********** ****** ********* **** crossings ** ****** ****** ** ********.
- *** ****** ***** ****** ** ****** line ********* **** *** ***** **** partially ********** ** ******* ** **** droplets ** *** ******'* ****.
- ** ************ ********* ***** ****** *** loitering **** ****** ******** ** ****** quickly ****** ******* ** **** ** when ****** ****** ** *** **** of ***** *****.
Catch ** ******** ** ***********
**** *** ********** ****** ********* *********, including **-***** ******* **** ****** ****** *********. ******* ***** *********** ************ *** available ** *** ******, **** ********** ******,**** ***,****** ******* **, *** ******. *******'* *** ****** for **** ********, *********, *** ***** detection *** *****-** *************** ** **** competitive *********.
Limited ** **** *****
****** *** *******, ** ***** **** alerts *** **** ********, ********* *** crowd ********* ******* * ******* ** 35 *** *** ********** ***********. ***** features **** **** ** ****-***** ********* such ** *****-** ********* *** **********. However, **** *** *** ******** *** long-range *********, **** ** ********** ****** or ***** ******* ****.
Line ******** *********
** ****-***** ********** (~*** ***), *** system ************ ******** **** *********, **** at ****** ** ** ** ******* (perpendicular ** *** ******), *********** ******** clear ************ ****** *** ***** **** multiple ****** ******** **************.
** *** ***** ********** (~** ***), the ********* ******** ********** *** **** humans *** ********.
*** ****** ********* ***-*** ******** ********* at *** **** ** ** ****, such ** ********, ******** ******** *********** leaving *** *** ***** ********, ***** highlights * ********** ** **-*********** ********* at *****.
************, ***** ****** **** ********* *** individuals ******** **** *** **** ******* actually ******** **.
*** ****** ********** ****** **** ******** when ********* ******* *** ********* ***** in ***** **********. **** ***** * red **** ** *** ******** ** indicate ***** *** **** ******** *** originally *****.
**** ******** ********* ***** ****** ********* at ********* ** ************* ** **** for **** *********** *** ********.
Loitering *********
*******'* ********* ********* ********** ******** ********* in ***-***** ********** (~** ***) **** different **** *********.
********** ***** ********* ****** **** ********* when ******** ***** ******* **** *** detection *****, ********** ********** ** ********* objects. ***** *** ******** ** ***** false ******:
******* ** * ***** ***** ** a *-****** ********* **** ****:
******* ** * ***** ***** ** a **-****** ********* ****:
Crowd *********
*** ***** ********* ********* ********** ******** humans *** ******** ** ********** ******* of ********, **** ** *** ***** (~20 ***).
************, ***** ***** ********* ****** **** triggered **** ** ********** ****** **** the **** ** *** ********** **** of ********.
Strong **** **********:
*** ********* ************ ****** ********** ** false ****** ** ***** **********, **** no ***** ****** ******** **** ********* in ***** *** ********* *****.
Verkada's ********
******* **** **** **** ****** ******* better ** ****-***** ***** ******* ********** and **** ****** ********* ** ***** of ******** ** ********* *** ******* performance. **** ***** **** ***** ********* are ********* ** *** ****, *** performance **** *** ******* **** **** alerts.
***** *** *******'* *******, **** ****'* questions *********** ** ****:
Are ***** ********* ********* ** *** ******* ** ** *** *****? Our line crossing, crowd, and loitering analytics are processed on the edge.
Is ** ******** *** *** *********** ** ******* **** *** ****** ** ****** ******** *********? No, our camera performance remains the same regardless of the number of alerts deployed. We also have cooldowns for alerts and limits on the number of presets that might be setup.
Is ***** * ***** ** *** ****** ** ****** **** *** ** *** *** ******? There is a limit on the number of presets that can be setup for cameras, but not on the number of alerts.
What ** *** ******* *** (** ******* ********) ******** *** ********** ****** *** ******* ******? ** ***** ************ ****** ** *** *****? We published *** *************** *** ********* ******** *** *********************** ****** *** ********* ******. ** **** ******** ****** **** on *** **** **********, ** ********* customers ******* *** ******* ** * similar ******. ** **** ******* * similar ***** *** *** ****** ** the ****** ******.
The ****** ******* **** * ***** ** * ******* ** ** ******* ** ******** *** ***** ******. **** *** ****** ****** **** ******* ****** **** ********* ** **** ** ****** **** ******** *** ********? Is it possible to include more objects of interest? Based on current customer needs, we felt 10 was an optimal number for crowd alerts.
Cameras *** ******** ******
******* **-** *** **-***: "** ** date"
******* **-**: "** ** ****"