Download IVISION Catalog
01Camera input
Capture the counting point with minimal overlap.
Count passages at a clearly defined point
Decide what constitutes one passage, how direction is handled and how queues or re-entry affect totals. Validate the view before using counts for planning.
Catalog workflow. Detector availability, scene suitability and event delivery must be verified for the proposed deployment. Camera observations supplement human review and established safety procedures.
Discuss this workflow
Example
Without IVISIONStandard CCTV feed
With IVISIONIllustrative event overlayThe Process
How It Works
A useful total starts with a clear counting rule Make traffic totals interpretable at the point measured.
01
02Visual criteria
Validate passage recognition through queues and turns.
03Event review
Review totals with available events and exception samples.
04Operator response
Planner compares like-for-like periods and checks anomalies.
Explore Your Options
Explore Related Capabilities
| Dimension |  Vehicle Counting |  Vehicle Entry and Exit Logging |
|---|---|---|
| Observation |  A vehicle crosses an assessed counting line or region. | A vehicle crosses a designated entry or exit boundary. |
| Event criteria | A validated passage meets the counting rule. | A validated directional crossing creates an available event record. |
| Monitoring setup | Confirm direction, duplicate handling and reporting period. | Confirm point names, direction and timestamp handling. |
| What it cannot establish | A passage count is not necessarily unique vehicles or site occupancy. | Missed crossings or uncertain identity can prevent complete visit matching. |
| Practical outcome | Help operations teams understand traffic volume at a specific site point. | Help operators review access activity without assuming every entry has a correctly matched exit. |
Illustrative demonstration
Review The Event.
Understand The Context.
Example footage and simulated events explain the review workflow. They do not measure detector performance.
Sites overview
Example Activity
No matching events.
Related Scenarios
View More
EXPLORE WHAT’S POSSIBLE
What Can You Do With Vehicle Counting?
01 / 04 · VEHICLE COUNTING
Logistics
Arrival volume varies across shifts.
Example event: Vehicles cross the entry line.
Operator response: Manager reviews time-period totals.
Practical value: Better staffing context.
Discuss this capability
02 / 04 · VEHICLE COUNTING
Retail
Repeated entries distort unique-visitor assumptions.
Example event: Passages are counted at the approach.
Operator response: Operator interprets them as movements.
Practical value: More honest traffic reporting.
Discuss this capability
03 / 04 · VEHICLE COUNTING
Manufacturing
Mixed traffic affects access planning.
Example event: Vehicles pass the defined point.
Operator response: Team compares representative periods.
Practical value: Route-planning evidence.
Discuss this capability
04 / 04 · VEHICLE COUNTING
Deployment review
Use a clear lane view near the counting point.
Visibility: Tailgating, queues and occlusion can miss or duplicate passages.
Configuration: Validate direction and duplicate logic with sample counts.
Privacy: Prefer aggregate counts where identity is unnecessary.
Human review: Check anomalies and avoid unsupported occupancy calculations.
Discuss this capability
Frequently asked questions
Vehicle Counting, Explained.
Counts validated vehicle passages across a defined line or through an assessed region.
Are counts unique vehicles?
Not necessarily. A vehicle may cross more than once.
Can entry counts equal occupancy?
Only with a validated entry/exit reconciliation method.
Do queues affect counts?
Yes. Validate slow, stopped and closely spaced traffic.
Is accuracy guaranteed?
No. Measure performance on representative site footage.
Find your fit
What are you trying
to achieve?
Help operations teams understand traffic volume at a specific site point. For Transport planners, Gate operations managers.
Workflow to discuss
Vehicle Counting + Define the unit being counted.
