Satellite imagery vs roadside cameras for border crossing queues

A planner at a land port asked us last month why anyone would bother with a satellite pass when the crossing already has CCTV on the approach lanes. Fair question, and the answer comes down to what each one can physically see. Fixed cameras and VHR imagery solve different parts of the queue problem, and mixing them up is how queue estimates go wrong during exactly the surge you needed to catch.

What a fixed camera actually sees

A roadside camera on a pole at the gate does one thing well: it watches the first few hundred meters of approach, usually the stretch covered by the pole height and lens angle someone chose years ago when the lot layout was different. That's useful for counting booths in operation or spotting a stalled vehicle at the primary inspection line. It doesn't answer the question most queue tracking needs answered, which is: where does the back of the line sit right now?

Queues at a busy terminal or crossing don't stay inside camera range. They spill past the last pole, bend around a frontage road, or back up onto a highway shoulder that was never wired for surveillance. Once the tailback crosses that boundary, the camera feed stops telling you anything useful, and you're left guessing from driver reports, a radio call from the gate, or whatever the last truck in frame looked like twenty minutes ago. Camera coverage limits are a physical limit of where the pole sits and how far the lens reaches. At most crossings nobody budgeted for a camera every 200 meters along every possible overflow route.

There's also the maintenance side, which planners who've run a camera network know well: a cut cable, a fogged lens, a camera that's been pointed at the wrong lane since the last storm. Fixed infrastructure needs someone local to keep it working, and at a lot of crossings and terminals, especially newer ones or smaller satellite ports, that infrastructure was never installed at all.

Where a VHR pass fits instead

A very-high-resolution satellite or aerial pass isn't trying to replace the camera's close-in view of the booths. It answers a different question: how far back this line stretches, end to end, right now. At sub-0.5 m resolution, individual vehicles show up clearly enough to count the line from the gate back past wherever the cameras quit, whether that's a frontage road, a rest stop, or a highway lane.

Cadence is where the two diverge in practice. CCTV writes a new frame continuously, all day, which is why it's suited to catching a stall in real time. A VHR pass gives you one image, captured when it's tasked, daily or on demand when a surge looks likely. That single image is built to answer how far back the line runs at the moment the shutter opens. It won't tell you what's happening at booth 4 a minute later. A planner tracking queue extent for a crossing with no ground sensor at all, or with cameras that only cover the first stretch, gets a measurement a camera network can't produce: one image showing the whole line, gate to tail.

Picking between them

The two aren't competing for the same job. CCTV earns its keep on anything close to the gate: booth counts, incident spotting, dwell time at primary inspection. A VHR pass earns its keep on the question cameras weren't built to answer: total queue length when the back of the line has moved past whatever's wired for video. If your crossing already has reliable coverage end to end, you may not need the satellite pass. If the tailback regularly outruns your camera range, or the crossing has no fixed camera to begin with, that's the gap a single tasked image is built for.

Queue Length Monitor was built around exactly that gap: a tasked VHR pass delivered as a numbered briefing note with a queue length estimate and the marked-up image it came from, for crossings and terminals where the cameras run out before the line does.

If your queue regularly stretches past where your cameras can see, it might be worth a look.