# Container Visibility

![Container Visibility](https://docs.sitetrax.io/uploads/images/gallery/2026-09/st-intel-container-visibility-feature.png)

Checking when and where a container was observed, and reviewing recorded arrivals and departures, without first walking the yard or calling the gate. Current presence depends on the available observations and capture coverage.

## In the application

1. Open **Assets** and set the project and date range.
2. The gallery lists stored readings with their project and time, plus direction information and captured images where available.
3. Open a record to see the asset type, status code, heading, coordinates and full payload.

![The assets gallery showing container readings with direction and capture type](https://docs.sitetrax.io/uploads/images/gallery/2026-09/st-intel-ui-assets-gallery.png)

The dashboard gives the same period at a summary level: total assets, containers and chassis for the selected project and range.

## From an assistant

> Using SiteTrax.io, show today's detections at the Utah site by asset type. State the timezone and resolved time window.

> Using SiteTrax.io, where was container TCLU8472070 last observed?

## Watch out for

- **Define the count.** Repeated observations and combined processing can create multiple stored rows for one passage. Ask for distinct usable container identifiers when that is the relevant measure, and retain the type/status filters. Distinct stored text is not a guarantee of distinct physical equipment.
- **A unit with no recent reading is not proven absent.** It may be parked outside camera coverage. Check your coverage before concluding a unit has left.
- **Direction depends on configuration.** It may be derived from a record's heading or assigned from a dedicated project or camera. Ask which interpretation was used; a missing heading does not establish entry or exit.