DEV Community

Cover image for Why PTZ Cameras Shouldn’t Own Your Baseline Coverage
Andrii Slobodskyi
Andrii Slobodskyi

Posted on

Why PTZ Cameras Shouldn’t Own Your Baseline Coverage

A PTZ camera can provide an excellent close view of an incident. However, the moment an operator turns it toward that incident, it stops looking at whatever was previously in frame.

That basic limitation becomes important at the scale of Mercedes-Benz Stadium in Atlanta. On October 20, 2026, Axis Communications published details of a surveillance modernization already operating at the venue, where more than 70,000 visitors and employees may be present on peak event days. The project uses overlapping fixed cameras to cover the seating bowl, with separate PTZ cameras available for investigation.

Axis and stadium personnel also reported two notable outcomes: image detail in the seating bowl increased from roughly 20 to 80 pixels on target, and fan exit time during one soccer match reportedly fell from 16 minutes to eight after personnel used camera views to identify congestion and redirect spectators.

Both numbers need context. The more transferable engineering lesson is the architecture behind them: continuous observation and active investigation are different surveillance functions, and one camera type does not have to perform both.

Separate the coverage layer from the investigation layer

A PTZ offers something a fixed camera cannot: an operator can move the view, follow activity, and use optical zoom to examine a distant event in more detail. That flexibility is valuable in a stadium, but it creates an unavoidable trade-off. Once the camera moves, it no longer observes the previous scene from that viewpoint.

Mercedes-Benz Stadium addresses that problem by giving fixed and PTZ cameras different jobs. Axis says overlapping fixed cameras maintain seating-bowl coverage, while 4K PTZ cameras installed in the bowl and on the scoreboard provide a separate investigation capability. The published material identifies the AXIS Q18 Bullet Camera Series and AXIS Q63 PTZ Camera Series operating with Genetec video management software, although it does not provide a complete camera schedule, exact installed models, or total system camera count.

That distinction matters because an operator investigating a disturbance, medical event, or other developing situation does not have to sacrifice the baseline view of the surrounding seating section. The PTZ can move toward the incident while fixed cameras continue providing context.

From a design perspective, this is more robust than treating a powerful PTZ as the camera responsible for both overview and investigation. Optical zoom can dramatically improve detail, but zoom does not solve continuity. A movable camera cannot preserve its previous field of view while simultaneously looking somewhere else.

Stable coverage also has operational value beyond security incidents. Axis describes staff using the improved seating-bowl views to help locate spectators requiring medical assistance and confirm their seating sections. In those cases, persistent spatial context can be more useful than a camera that is continuously repositioned.

Optical overlap is not the same as system redundancy

Axis says the fixed-camera views were deliberately overlapped so that losing one camera would not leave a seating section unobserved. That is a meaningful resilience objective, but it protects against only one class of failure.

Suppose two cameras provide sufficient overlap over the same seating section. If both cameras depend on the same access switch, PoE source, UPS, or upstream network path, a shared infrastructure failure can remove both views at once. The optical layout may be redundant, but the supporting system may not be.

Public material does not disclose the stadium's switch topology, UPS architecture, camera distribution, or failure-testing methodology, so these sources cannot establish the level of infrastructure redundancy in the actual deployment. That uncertainty should remain separate from Axis's documented claim about overlapping fields of view.

For an integrator, these are two different acceptance questions. The first is whether the remaining camera provides enough useful coverage and image detail after one camera fails. The second is whether the supposedly redundant views survive failures elsewhere in the infrastructure.

A useful conceptual model is:

Coverage resilience
    |
    +--> Optical resilience
    |       +--> overlapping fields of view
    |       +--> usable remaining image detail
    |
    +--> Infrastructure resilience
            +--> switching
            +--> PoE / power
            +--> UPS
            +--> upstream network paths
Enter fullscreen mode Exit fullscreen mode

The first layer is visible on a camera layout drawing. The second requires understanding how those cameras are actually powered and connected.

This is why "we have overlapping cameras" should not automatically become "we have redundant surveillance." You have to trace the failure domain beyond the lens.

Pixel density is more useful than megapixels, but only when the metric is defined

One of the most interesting figures in the case study is the reported increase from roughly 20 to 80 pixels on target in the seating bowl. That is more useful to a surveillance designer than simply saying the replacement cameras have more megapixels because it describes the detail available at the subject.

However, the public material does not define the measurement precisely. Neither Axis source specifies whether the figure means pixels per unit of distance, pixels across a particular target dimension, or another metric. The measurement point, lighting conditions, and test methodology are also not published.

That limitation matters when interpreting a fourfold increase. If a value represents a linear pixel-density measurement, multiplying it by four is not equivalent to saying the target contains four times as many total sampled pixels. Under comparable geometry, quadrupling linear resolution in both dimensions would correspond to roughly sixteen times as many pixels across the same two-dimensional target area. That is a mathematical illustration, not a verified calculation for this stadium installation.

Axis describes the modernization as significantly improving detail and refers to quadrupled image quality in its customer case study. Image quality itself is broader than one resolution metric. Optics, stabilization, lighting, compression, exposure, subject motion, and camera placement can all affect what an operator ultimately sees.

Axis also says the stadium's new cameras exceed an NFL requirement of 50 pixels on target. The source material reviewed for the MASTER did not provide an independently accessible NFL technical specification confirming that requirement, so the figure should remain attributed to Axis and stadium personnel rather than presented as independently established league documentation.

The engineering lesson is not that the 80-pixel figure is unimportant. It is that performance targets need definitions. During design and acceptance, a number is useful only when everyone understands what it measures, where it is measured, under what conditions, and what operational task that level of detail is intended to support.

Better camera coverage still depends on the surrounding infrastructure and operations

The stadium modernization extends beyond the seating bowl. Axis describes long-range rooftop PTZ cameras to monitor surrounding traffic and approaching crowds, as well as an integration with the stadium's drone-detection system.

The two Axis publications differ slightly in how they describe that integration. The press release associates it with rooftop PTZ cameras, while the customer case study refers more generally to Axis PTZ cameras. Neither publication names the drone-detection vendor, describes the interface, or establishes that a camera automatically slews toward a detected drone.

The video system also sits inside a much broader operational environment. GC&E Systems Group served as the project integrator, and Axis identifies Genetec as the VMS, but the public material does not describe the deployment's storage architecture, software topology, or detailed network design.

An independent Security Management article from ASIS International describes a stadium operations center that runs continuously and brings multiple organizations together during events. Representatives from stadium departments, Atlanta Police, Fire Rescue, and Emergency Medical Services can coordinate through that operating environment while surveillance, weather, and other information are monitored.

That context helps explain why the reported improvement in fan exit time cannot reasonably be attributed to cameras alone.

According to stadium personnel, operators used the video system to identify congestion and then communicated with officers, who redirected spectators toward less crowded exits. The stadium reports that exit time during one soccer match fell from 16 minutes to eight.

The exact match, definition of "exit time," and comparison baseline have not been published. The result should therefore be treated as a customer-reported operational outcome rather than a general performance benchmark for the surveillance system.

More importantly, the workflow involved both technology and people:

Camera observation
        ↓
Operator recognizes congestion
        ↓
Information reaches personnel
        ↓
Officers redirect spectators
        ↓
Crowd flow changes
Enter fullscreen mode Exit fullscreen mode

Improved image detail can support the first stages of that process, but it doesn't complete the operational response.

Stable views can also create a better foundation for future analytics

Mercedes-Benz Stadium has discussed computer vision as a possible future step for studying queues and helping personnel direct spectators. Those functions are described as future development rather than capabilities already deployed in the project.

The existing separation between fixed coverage and PTZ investigation is relevant here for another reason. A fixed camera provides a stable scene geometry, while a PTZ changes its field of view whenever an operator moves, zooms, or repositions it. For analytics that depend on consistent spatial relationships, a stable view can provide a more predictable observation surface.

That is an engineering consideration, not a claim about what the stadium's future analytics will do. A camera layout designed for human monitoring does not automatically become a validated measurement system for crowd flow.

Any future analytics would still require appropriate camera positioning, calibration, environmental testing, and performance validation. Lighting variation, occlusion, crowd density, camera perspective, and other site conditions can affect the result even when the underlying video is excellent.

The broader lesson is that camera architecture can either help or complicate whatever comes next. Designing a stable baseline layer today can preserve options for future analytics without requiring PTZ cameras to stop performing their investigation role.

Commissioning should verify coverage and failure behavior separately

The Mercedes-Benz Stadium project points to a useful commissioning principle for other large surveillance systems.

First, test coverage performance. Confirm that the fixed-camera layout provides the required views and image detail across the operational area. Where overlap is intended to survive the loss of one camera, disable or isolate a camera during acceptance and verify that the remaining view still meets the agreed requirement.

Then test infrastructure failure behavior separately. If overlapping cameras share a switch, power source, or network path, understand what happens when that shared component fails. A coverage drawing alone cannot answer that question.

PTZ behavior also deserves its own acceptance criteria. Confirm that operators can use PTZ cameras for investigation without unexpectedly losing baseline coverage elsewhere. Presets, usable zoom ranges, low-light performance, stabilization, latency, and operator workflow may all matter depending on the project's requirements.

Finally, connect the camera system to the actual response procedure. An excellent image has limited operational value if personnel cannot locate the event, retrieve relevant views, communicate the information, or act on it in time.

These are not stadium-specific requirements. They apply anywhere surveillance has to do two jobs at once: maintain awareness of a large area and let an operator investigate something in detail.

The architecture matters more than the individual camera

The most transferable part of the Mercedes-Benz Stadium modernization is not a particular Axis model or a headline resolution figure. It is the decision to keep continuous observation and active investigation as separate surveillance layers.

Fixed cameras maintain the seating-bowl view. PTZ cameras can look elsewhere when the situation requires it. Optical overlap provides one form of resilience, while switches, power, UPS design, and network paths determine another. Image-detail targets provide useful design criteria only when their measurement and operational purpose are understood.

The reported crowd-flow result reinforces the same systems lesson. Better images supported better decisions, but personnel still interpreted those images and changed conditions on the ground.

A PTZ is most valuable when it can investigate freely.

That freedom is much easier to use when the rest of the surveillance architecture does not have to look away with it.

Sources and further reading


AI disclosure: The final prose was generated primarily with AI from a human-reviewed, primary-source-verified technical master.

Top comments (0)