Download IVISION Catalog
01Prepare the view
Confirm the incident location, approximate time and covering cameras.
Start with the right camera and time window
A reported incident often begins with a place and an approximate time. Camera and date filters help reviewers isolate relevant event records, then open available snapshots or clips. Location filtering depends on camera registration; filters cannot recover events that were never recorded.
Catalog workflow. Confirm detector availability, permitted use and event delivery for the proposed deployment. Website examples are illustrative.
Review your search workflow
Example
Without IVISIONStandard CCTV feed
With IVISIONIllustrative event overlayThe Process
How It Works
Give an investigation a clear scope. Concentrate review on records within the reported scope.
01
02Assess the observation
Apply available criteria, checking the time zone and access scope.
03Review the evidence
Inspect records and evidence; expand the window when initial details are uncertain.
04Choose a response
Document the filters and findings without treating an empty list as proof of absence.
Explore Your Options
Explore Related Capabilities
| Dimension |  Search by location, camera, date or time |  Search for specific activities or incidents |
|---|---|---|
| Observation |  An operator selects available event metadata rather than triggering new detection. | A stored event category or supported query matches the activity being investigated. |
| Event criteria | Apply permitted camera, location and time criteria to an accessible event collection. | Submit an available event type or supported query within a defined scope. |
| Monitoring setup | Use correct time zones, camera labels and permissions; widen uncertain intervals deliberately. | Use detector-specific definitions, known coverage and an agreed interval. |
| What it cannot establish | Metadata filters do not search the visual contents of arbitrary recordings or prove an event did not occur. | General visual activity search is not verified in the reviewed code. Incorrect labels and undetected events limit event-only searches. |
| Practical outcome | Begin an investigation with a manageable, explicitly defined set of records. | Investigate a specific observation before reviewing unrelated event categories. |
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 MoreTracking & MovementSearch for specific activities or incidents
Add an activity criterion when supported event categories exist.
Read More
Tracking & MovementFast retrieval of matching events from large video archives
Check whether retained records still have accessible evidence.
Read MoreTracking & MovementMulti-site and multi-camera management
Maintain the camera and location structure that supports useful filters.
Read MoreEXPLORE WHAT’S POSSIBLE
What Can You Do With Search by location, camera, date or time?
01 / 04 · SEARCH BY LOCATION, CAMERA, DATE OR TIME
Retail
A delivery discrepancy is reported for an afternoon.
Example event: Records match the entrance camera and interval.
Operator response: A reviewer compares clips with the delivery log.
Practical value: The investigation retains a reproducible scope.
Discuss this capability
02 / 04 · SEARCH BY LOCATION, CAMERA, DATE OR TIME
Manufacturing
Several cameras share similar informal names.
Example event: A record identifies its registered camera.
Operator response: The supervisor verifies the location before interpreting it.
Practical value: Viewpoint confusion is addressed during review.
Discuss this capability
03 / 04 · SEARCH BY LOCATION, CAMERA, DATE OR TIME
Property management
A visitor gives an uncertain incident time.
Example event: The initial interval contains few relevant records.
Operator response: The operator broadens and documents the search interval.
Practical value: The investigation accounts for uncertainty in the report.
Discuss this capability
04 / 04 · SEARCH BY LOCATION, CAMERA, DATE OR TIME
Deployment review
Name cameras for the physical areas they cover.
Visibility: Filtering cannot improve a blurred source clip.
Configuration: Require available metadata, correct timestamps and authorized access.
Privacy: Restrict access to the investigation purpose and retention policy.
Human review: A person interprets evidence and records coverage gaps.
Discuss this capability
Frequently asked questions
Search by location, camera, date or time, Explained.
Event filtering narrows accessible records by their camera, location and recorded time before an operator examines the evidence.
Does this search everything visible in a recording?
No. Metadata filtering selects existing records. Visual or semantic archive search requires a separate, confirmed service.
Why might a camera return no results?
It may have no matching records, no event producer, missing data or restricted access.
Can I filter by building or site?
That depends on camera-location structure and enabled filters. Confirm available fields during setup.
Are camera timestamps always comparable?
Check device clocks, event timestamps and interface time zones before reconstructing a sequence.
Find your fit
What are you trying
to achieve?
Begin an investigation with a manageable, explicitly defined set of records. For Security operators, Site administrators, Incident reviewers.
Workflow to discuss
Search by location, camera, date or time + Define a reproducible investigation scope.
