{ "api_version": "1", "kind": "dse_post", "self": "https://update.dsesecurity.com/api/v1/posts/check-axis-directional-labels-across-their-ptz-zone-bounds/", "item": { "id": "https://update.dsesecurity.com/updates/check-axis-directional-labels-across-their-ptz-zone-bounds/", "slug": "check-axis-directional-labels-across-their-ptz-zone-bounds", "url": "https://update.dsesecurity.com/updates/check-axis-directional-labels-across-their-ptz-zone-bounds/", "alternate_urls": { "markdown": "https://update.dsesecurity.com/updates/check-axis-directional-labels-across-their-ptz-zone-bounds.md", "json": "https://update.dsesecurity.com/api/v1/posts/check-axis-directional-labels-across-their-ptz-zone-bounds/" }, "title": "Check Axis directional labels across their PTZ zone bounds", "summary": "Check an OSDI name against its pan, tilt and optional zoom bounds. Treat label configuration and the actual displayed scene as separate acceptance evidence.", "format": { "slug": "guide", "name": "Guide" }, "priority": { "slug": "advisory", "name": "Advisory" }, "featured": false, "image": { "theme": "physical-security", "label": "Physical security", "alt": "Integrated video surveillance and controlled entry at a modern commercial facility.", "card_url": "https://update.dsesecurity.com/assets/editorial/physical-security-card.webp?v=1.8.20", "hero_url": "https://update.dsesecurity.com/assets/editorial/physical-security-hero.webp?v=1.8.20", "social_url": "https://update.dsesecurity.com/assets/editorial/physical-security-social-v2.jpg?v=1.8.20", "width": 2400, "height": 1350 }, "topics": [ { "slug": "it", "name": "IT", "url": "https://update.dsesecurity.com/topic/it/" }, { "slug": "video-surveillance", "name": "Video Surveillance", "url": "https://update.dsesecurity.com/topic/video-surveillance/" } ], "author": { "name": "DSE Security Editorial Team", "url": "https://update.dsesecurity.com/#editorial-team", "type": "Organization" }, "publisher": { "name": "Detection Systems & Engineering", "url": "https://dsesecurity.com/" }, "published_at": "2026-10-30T06:05:04+00:00", "modified_at": "2026-10-30T06:05:13+00:00", "reviewed_on": "2026-10-30", "reading_minutes": 3, "word_count": 528, "potentially_affected": "Axis PTZ devices supporting the documented On-screen directional indicator parameters; actual image source and zone capacity must be confirmed.", "dse_recommendation": "DSE recommends an attended boundary review of the named zone before the label is used in operational decisions.", "primary_source": { "name": "Axis Communications — On-screen directional indicator", "url": "https://developer.axis.com/vapix/network-video/on-screen-directional-indicator/", "published_on": null, "authority": "Axis Communications" }, "publishing_principles": "https://update.dsesecurity.com/updates/dse-updates-editorial-methodology/", "usage_info": "https://update.dsesecurity.com/usage/", "copyright_notice": "Copyright © 2026 Detection Systems & Engineering. All rights reserved.", "content_html": "

Bottom line: Accept the label only after its configured zone and the actual view agree. Review zoom handling deliberately so a familiar name is not treated as an unconditional description of every camera view.

\n

Source fact: documented behavior

\n

The On-screen directional indicator defines a named zone through pan, tilt and zoom coordinates and describes displaying that zone name in the text overlay.

\n

Its optional Zoom range limits when the zone is active; if that parameter is unset, zoom is not considered for the zone.

\n

Zones are represented by parameter groups, and deleting a group also removes its corresponding zone.

\n

What the source does not establish

\n

This article reviews an operator label and its configured activation bounds. It does not establish geographic accuracy, full scene coverage, a dispatch location or support for a particular PTZ model. Keep the meaning of the label and any operational response dependent on it subject to separate owner approval.

\n

Applicability questions

\n\n

DSE recommendation: controlled next steps

\n

The following steps are DSE recommendations based on the cited source.

\n

DSE recommends an attended boundary review of the named zone before the label is used in operational decisions.

\n
    \n
  1. Read the actual image-source zone configuration through the supported interface. Match the zone identifier to its name and angular bounds, then record whether the zoom range is present. Ask the operator owner to describe the view that the name should represent. Keep names borrowed from old drawings or adjacent cameras provisional until that view is checked.
    2. \n
  2. Prepare a proposed observation sequence with approved positions inside and outside each intended boundary. Include a zoom change if the configuration should distinguish views by zoom. Keep the camera’s movement area clear and assign an operator with a supported stop method. Do not rely on a parameter example’s coordinates as the site’s surveyed or approved values.
    3. \n
  3. Apply only an expressly approved label or boundary edit and retrieve the resulting configuration again. Observe the actual overlay and scene together at the planned positions. If the label creates an ambiguous interpretation, stop acceptance and revise the naming or bounds with the owner. Avoid deleting and recreating a parameter group merely to correct its displayed name.
    4. \n
\n

Verification and evidence

\n

Proposed verification: preserve the returned zone values and a minimal set of sanitized observations showing the expected inside and outside cases. Record the camera position and zoom context beside each observation. Ask a second operator to explain the label from that evidence without relying on unstated knowledge of the original setup.

\n

Review a desk case in which a wide and a tight view should have different approved descriptions. Identify whether the actual optional zoom constraint expresses that requirement before any edit. Keep unresolved boundary behavior visible in the handoff. No coordinate calibration, camera movement or overlay test was performed for this article.

\n

Official references

\n\n

Source review completed October 30, 2026. Recheck the official source and deployment-specific applicability before changing production settings.

\n", "content_text": "Bottom line: Accept the label only after its configured zone and the actual view agree. Review zoom handling deliberately so a familiar name is not treated as an unconditional description of every camera view.\nSource fact: documented behavior\nThe On-screen directional indicator defines a named zone through pan, tilt and zoom coordinates and describes displaying that zone name in the text overlay.\nIts optional Zoom range limits when the zone is active; if that parameter is unset, zoom is not considered for the zone.\nZones are represented by parameter groups, and deleting a group also removes its corresponding zone.\nWhat the source does not establish\nThis article reviews an operator label and its configured activation bounds. It does not establish geographic accuracy, full scene coverage, a dispatch location or support for a particular PTZ model. Keep the meaning of the label and any operational response dependent on it subject to separate owner approval.\nApplicability questions\n\nWhich image source and exact zone should carry the label?\nWhat pan and tilt bounds represent its intended view?\nShould zoom participate, or is its omission deliberate?\nDoes another operator workflow depend on this same zone group?\n\nDSE recommendation: controlled next steps\nThe following steps are DSE recommendations based on the cited source.\nDSE recommends an attended boundary review of the named zone before the label is used in operational decisions.\n\nRead the actual image-source zone configuration through the supported interface. Match the zone identifier to its name and angular bounds, then record whether the zoom range is present. Ask the operator owner to describe the view that the name should represent. Keep names borrowed from old drawings or adjacent cameras provisional until that view is checked.\nPrepare a proposed observation sequence with approved positions inside and outside each intended boundary. Include a zoom change if the configuration should distinguish views by zoom. Keep the camera’s movement area clear and assign an operator with a supported stop method. Do not rely on a parameter example’s coordinates as the site’s surveyed or approved values.\nApply only an expressly approved label or boundary edit and retrieve the resulting configuration again. Observe the actual overlay and scene together at the planned positions. If the label creates an ambiguous interpretation, stop acceptance and revise the naming or bounds with the owner. Avoid deleting and recreating a parameter group merely to correct its displayed name.\n\nVerification and evidence\nProposed verification: preserve the returned zone values and a minimal set of sanitized observations showing the expected inside and outside cases. Record the camera position and zoom context beside each observation. Ask a second operator to explain the label from that evidence without relying on unstated knowledge of the original setup.\nReview a desk case in which a wide and a tight view should have different approved descriptions. Identify whether the actual optional zoom constraint expresses that requirement before any edit. Keep unresolved boundary behavior visible in the handoff. No coordinate calibration, camera movement or overlay test was performed for this article.\nOfficial references\n\nOn-screen directional indicator — Axis Communications; official VAPIX documentation.\n\nSource review completed October 30, 2026. Recheck the official source and deployment-specific applicability before changing production settings.", "content_markdown": "Bottom line: Accept the label only after its configured zone and the actual view agree. Review zoom handling deliberately so a familiar name is not treated as an unconditional description of every camera view.\n\n## Source fact: documented behavior\n\nThe [On-screen directional indicator](https://developer.axis.com/vapix/network-video/on-screen-directional-indicator/) defines a named zone through pan, tilt and zoom coordinates and describes displaying that zone name in the text overlay.\n\nIts optional Zoom range limits when the zone is active; if that parameter is unset, zoom is not considered for the zone.\n\nZones are represented by parameter groups, and deleting a group also removes its corresponding zone.\n\n## What the source does not establish\n\nThis article reviews an operator label and its configured activation bounds. It does not establish geographic accuracy, full scene coverage, a dispatch location or support for a particular PTZ model. Keep the meaning of the label and any operational response dependent on it subject to separate owner approval.\n\n## Applicability questions\n\n- Which image source and exact zone should carry the label?\n\n- What pan and tilt bounds represent its intended view?\n\n- Should zoom participate, or is its omission deliberate?\n\n- Does another operator workflow depend on this same zone group?\n\n## DSE recommendation: controlled next steps\n\nThe following steps are DSE recommendations based on the cited source.\n\nDSE recommends an attended boundary review of the named zone before the label is used in operational decisions.\n\n- Read the actual image-source zone configuration through the supported interface. Match the zone identifier to its name and angular bounds, then record whether the zoom range is present. Ask the operator owner to describe the view that the name should represent. Keep names borrowed from old drawings or adjacent cameras provisional until that view is checked.\n\n- Prepare a proposed observation sequence with approved positions inside and outside each intended boundary. Include a zoom change if the configuration should distinguish views by zoom. Keep the camera’s movement area clear and assign an operator with a supported stop method. Do not rely on a parameter example’s coordinates as the site’s surveyed or approved values.\n\n- Apply only an expressly approved label or boundary edit and retrieve the resulting configuration again. Observe the actual overlay and scene together at the planned positions. If the label creates an ambiguous interpretation, stop acceptance and revise the naming or bounds with the owner. Avoid deleting and recreating a parameter group merely to correct its displayed name.\n\n## Verification and evidence\n\nProposed verification: preserve the returned zone values and a minimal set of sanitized observations showing the expected inside and outside cases. Record the camera position and zoom context beside each observation. Ask a second operator to explain the label from that evidence without relying on unstated knowledge of the original setup.\n\nReview a desk case in which a wide and a tight view should have different approved descriptions. Identify whether the actual optional zoom constraint expresses that requirement before any edit. Keep unresolved boundary behavior visible in the handoff. No coordinate calibration, camera movement or overlay test was performed for this article.\n\n## Official references\n\n- [On-screen directional indicator](https://developer.axis.com/vapix/network-video/on-screen-directional-indicator/) — Axis Communications; official VAPIX documentation.\n\nSource review completed October 30, 2026. Recheck the official source and deployment-specific applicability before changing production settings." }, "json_ld": { "@context": "https://schema.org", "@graph": [ { "@type": "Organization", "@id": "https://dsesecurity.com/#organization", "name": "Detection Systems & Engineering", "alternateName": "DSE Security", "url": "https://dsesecurity.com/", "logo": { "@type": "ImageObject", "url": "https://update.dsesecurity.com/assets/dse-logo-20260812.png?v=1.8.20" } }, { "@type": "Organization", "@id": "https://update.dsesecurity.com/#editorial-team", "name": "DSE Security Editorial Team", "url": "https://update.dsesecurity.com/", "parentOrganization": { "@id": "https://dsesecurity.com/#organization" } }, { "@type": "WebSite", "@id": "https://update.dsesecurity.com/#website", "name": "DSE Updates", "alternateName": "DSE Security Knowledge Hub", "url": "https://update.dsesecurity.com/", "inLanguage": "en-US", "publisher": { "@id": "https://dsesecurity.com/#organization" }, "potentialAction": { "@type": "SearchAction", "target": { "@type": "EntryPoint", "urlTemplate": "https://update.dsesecurity.com/?q={search_term_string}" }, "query-input": "required name=search_term_string" } }, { "@type": "WebPage", "@id": "https://update.dsesecurity.com/updates/check-axis-directional-labels-across-their-ptz-zone-bounds/", "url": "https://update.dsesecurity.com/updates/check-axis-directional-labels-across-their-ptz-zone-bounds/", "isPartOf": { "@id": "https://update.dsesecurity.com/#website" }, "lastReviewed": "2026-10-30" }, { "@type": "BreadcrumbList", "@id": "https://update.dsesecurity.com/updates/check-axis-directional-labels-across-their-ptz-zone-bounds/#breadcrumbs", "itemListElement": [ { "@type": "ListItem", "position": 1, "name": "DSE Updates", "item": "https://update.dsesecurity.com/" }, { "@type": "ListItem", "position": 2, "name": "IT", "item": "https://update.dsesecurity.com/topic/it/" }, { "@type": "ListItem", "position": 3, "name": "Check Axis directional labels across their PTZ zone bounds", "item": "https://update.dsesecurity.com/updates/check-axis-directional-labels-across-their-ptz-zone-bounds/" } ] }, { "@type": [ "Article", "TechArticle" ], "@id": "https://update.dsesecurity.com/updates/check-axis-directional-labels-across-their-ptz-zone-bounds/#article", "identifier": "https://update.dsesecurity.com/updates/check-axis-directional-labels-across-their-ptz-zone-bounds/", "url": "https://update.dsesecurity.com/updates/check-axis-directional-labels-across-their-ptz-zone-bounds/", "headline": "Check Axis directional labels across their PTZ zone bounds", "description": "Check an OSDI name against its pan, tilt and optional zoom bounds. Treat label configuration and the actual displayed scene as separate acceptance evidence.", "abstract": "Check an OSDI name against its pan, tilt and optional zoom bounds. Treat label configuration and the actual displayed scene as separate acceptance evidence.", "articleBody": "Bottom line: Accept the label only after its configured zone and the actual view agree. Review zoom handling deliberately so a familiar name is not treated as an unconditional description of every camera view.\nSource fact: documented behavior\nThe On-screen directional indicator defines a named zone through pan, tilt and zoom coordinates and describes displaying that zone name in the text overlay.\nIts optional Zoom range limits when the zone is active; if that parameter is unset, zoom is not considered for the zone.\nZones are represented by parameter groups, and deleting a group also removes its corresponding zone.\nWhat the source does not establish\nThis article reviews an operator label and its configured activation bounds. It does not establish geographic accuracy, full scene coverage, a dispatch location or support for a particular PTZ model. Keep the meaning of the label and any operational response dependent on it subject to separate owner approval.\nApplicability questions\n\nWhich image source and exact zone should carry the label?\nWhat pan and tilt bounds represent its intended view?\nShould zoom participate, or is its omission deliberate?\nDoes another operator workflow depend on this same zone group?\n\nDSE recommendation: controlled next steps\nThe following steps are DSE recommendations based on the cited source.\nDSE recommends an attended boundary review of the named zone before the label is used in operational decisions.\n\nRead the actual image-source zone configuration through the supported interface. Match the zone identifier to its name and angular bounds, then record whether the zoom range is present. Ask the operator owner to describe the view that the name should represent. Keep names borrowed from old drawings or adjacent cameras provisional until that view is checked.\nPrepare a proposed observation sequence with approved positions inside and outside each intended boundary. Include a zoom change if the configuration should distinguish views by zoom. Keep the camera’s movement area clear and assign an operator with a supported stop method. Do not rely on a parameter example’s coordinates as the site’s surveyed or approved values.\nApply only an expressly approved label or boundary edit and retrieve the resulting configuration again. Observe the actual overlay and scene together at the planned positions. If the label creates an ambiguous interpretation, stop acceptance and revise the naming or bounds with the owner. Avoid deleting and recreating a parameter group merely to correct its displayed name.\n\nVerification and evidence\nProposed verification: preserve the returned zone values and a minimal set of sanitized observations showing the expected inside and outside cases. Record the camera position and zoom context beside each observation. Ask a second operator to explain the label from that evidence without relying on unstated knowledge of the original setup.\nReview a desk case in which a wide and a tight view should have different approved descriptions. Identify whether the actual optional zoom constraint expresses that requirement before any edit. Keep unresolved boundary behavior visible in the handoff. No coordinate calibration, camera movement or overlay test was performed for this article.\nOfficial references\n\nOn-screen directional indicator — Axis Communications; official VAPIX documentation.\n\nSource review completed October 30, 2026. Recheck the official source and deployment-specific applicability before changing production settings.", "datePublished": "2026-10-30T06:05:04+00:00", "dateModified": "2026-10-30T06:05:13+00:00", "mainEntityOfPage": { "@id": "https://update.dsesecurity.com/updates/check-axis-directional-labels-across-their-ptz-zone-bounds/" }, "inLanguage": "en-US", "isAccessibleForFree": true, "author": { "@type": "Organization", "name": "DSE Security Editorial Team", "url": "https://update.dsesecurity.com/#editorial-team" }, "publisher": { "@id": "https://dsesecurity.com/#organization" }, "image": { "@type": "ImageObject", "@id": "https://update.dsesecurity.com/updates/check-axis-directional-labels-across-their-ptz-zone-bounds/#primaryimage", "url": "https://update.dsesecurity.com/assets/editorial/physical-security-social-v2.jpg?v=1.8.20", "contentUrl": "https://update.dsesecurity.com/assets/editorial/physical-security-social-v2.jpg?v=1.8.20", "width": 1200, "height": 630, "caption": "Check Axis directional labels across their PTZ zone bounds" }, "articleSection": [ "IT", "Video Surveillance" ], "keywords": [ "IT", "Video Surveillance", "Guide", "Advisory priority" ], "genre": "Guide", "about": [ { "@type": "Thing", "name": "IT", "url": "https://update.dsesecurity.com/topic/it/" }, { "@type": "Thing", "name": "Video Surveillance", "url": "https://update.dsesecurity.com/topic/video-surveillance/" } ], "wordCount": 528, "timeRequired": "PT3M", "publishingPrinciples": "https://update.dsesecurity.com/updates/dse-updates-editorial-methodology/", "usageInfo": "https://update.dsesecurity.com/usage/", "copyrightHolder": { "@id": "https://dsesecurity.com/#organization" }, "copyrightNotice": "Copyright © 2026 Detection Systems & Engineering. All rights reserved.", "citation": { "@type": "CreativeWork", "name": "Axis Communications — On-screen directional indicator", "url": "https://developer.axis.com/vapix/network-video/on-screen-directional-indicator/" } } ] } }