{ "api_version": "1", "kind": "dse_post", "self": "https://update.dsesecurity.com/api/v1/posts/read-back-axis-view-geometry-after-a-crop-change/", "item": { "id": "https://update.dsesecurity.com/updates/read-back-axis-view-geometry-after-a-crop-change/", "slug": "read-back-axis-view-geometry-after-a-crop-change", "url": "https://update.dsesecurity.com/updates/read-back-axis-view-geometry-after-a-crop-change/", "alternate_urls": { "markdown": "https://update.dsesecurity.com/updates/read-back-axis-view-geometry-after-a-crop-change.md", "json": "https://update.dsesecurity.com/api/v1/posts/read-back-axis-view-geometry-after-a-crop-change/" }, "title": "Read back Axis view geometry after a crop change", "summary": "Accept the Axis view-area geometry returned by the device after a crop request. Grid alignment can make it differ from the submitted rectangle, so reconcile client state and the resulting view.", "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": "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-29T19:49:59+00:00", "modified_at": "2026-10-29T19:50:08+00:00", "reviewed_on": "2026-10-29", "reading_minutes": 3, "word_count": 537, "potentially_affected": "Axis products exposing the documented View Area API interface; confirm actual device, hardware and software applicability before applying the proposed checks.", "dse_recommendation": "DSE recommends reconciling submitted, returned and observed view geometry as three separate parts of a crop change.", "primary_source": { "name": "Axis Communications — View Area API", "url": "https://developer.axis.com/vapix/network-video/view-area-api/", "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: Read back and retain the returned view rectangle after a geometry change. Compare it with the intended scene instead of letting the client continue to display or calculate from the requested coordinates alone.

\n

Source fact: documented behavior

\n

Axis’s View Area API defines view subsections as virtual channels and expects their pixel coordinates to match the overview stream’s rotation and mirroring.

\n

The documentation requires crop geometry to align with the canvas grid, usually 8 by 8 pixels, and describes seeking an optimal fit when the request cannot align on every side.

\n

The geometry-change example advises updating local geometry from the response because the returned rectangle can differ from the submitted one.

\n

What the source does not establish

\n

Do not assume the usual grid size applies identically to every product or that an accepted crop preserves the operational image requirement. Confirm the intended canvas, orientation and supported view area. Keep crop geometry separate from channel enablement, privacy-region acceptance and measured recorded detail.

\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 reconciling submitted, returned and observed view geometry as three separate parts of a crop change.

\n
    \n
  1. Read the current view-area information and identify the exact channel, canvas and orientation. Record the approved scene boundary with a permitted reference image or marked task location. Prepare the requested rectangle in the documented coordinate system. Avoid using a rectangle from a different stream size as if it were already expressed on this canvas.
    2. \n
  2. Apply an approved test geometry through the supported interface and preserve the full sanitized response. Compare the returned rectangle with the submitted values before updating the client’s local state. If they differ, retain both rather than rounding the returned values back to the request. Make the returned supported geometry the basis for the client’s subsequent display and review.
    3. \n
  3. Inspect the resulting live view and the relevant recorded workflow with the operator. Check the required edges and targets, not just the center of the crop. For a proposed client exercise, include a supported request near a grid or aspect-ratio boundary and observe the actual returned fit. If the result misses the task, revise the approved geometry or design rather than concealing the difference in the client.
    4. \n
\n

Verification and evidence

\n

Retain the original, requested and returned rectangles with their canvas, channel and orientation. Keep a permitted resulting-view observation linked to the same change. Ask another reviewer to explain which coordinates the client now stores and why they may differ from the submitted request.

\n

Repeat the reconciliation after an approved orientation or view configuration change. Record image-quality and privacy checks separately where required. The proposed exercise does not assert a universal rounding rule, an exact installed grid size or a successful crop on any customer camera.

\n

Official references

\n\n

Source review completed October 29, 2026. Recheck the official documentation and the deployed device’s capabilities before changing production settings.

\n", "content_text": "Bottom line: Read back and retain the returned view rectangle after a geometry change. Compare it with the intended scene instead of letting the client continue to display or calculate from the requested coordinates alone.\nSource fact: documented behavior\nAxis’s View Area API defines view subsections as virtual channels and expects their pixel coordinates to match the overview stream’s rotation and mirroring.\nThe documentation requires crop geometry to align with the canvas grid, usually 8 by 8 pixels, and describes seeking an optimal fit when the request cannot align on every side.\nThe geometry-change example advises updating local geometry from the response because the returned rectangle can differ from the submitted one.\nWhat the source does not establish\nDo not assume the usual grid size applies identically to every product or that an accepted crop preserves the operational image requirement. Confirm the intended canvas, orientation and supported view area. Keep crop geometry separate from channel enablement, privacy-region acceptance and measured recorded detail.\nApplicability questions\n\nWhich virtual channel and overview canvas define the requested rectangle?\nDo the client’s coordinates match the actual rotation and mirroring?\nHow does the client update its saved geometry from the response?\nWhich edge or target must remain visible in the accepted scene?\n\nDSE recommendation: controlled next steps\nThe following steps are DSE recommendations based on the cited source.\nDSE recommends reconciling submitted, returned and observed view geometry as three separate parts of a crop change.\n\nRead the current view-area information and identify the exact channel, canvas and orientation. Record the approved scene boundary with a permitted reference image or marked task location. Prepare the requested rectangle in the documented coordinate system. Avoid using a rectangle from a different stream size as if it were already expressed on this canvas.\nApply an approved test geometry through the supported interface and preserve the full sanitized response. Compare the returned rectangle with the submitted values before updating the client’s local state. If they differ, retain both rather than rounding the returned values back to the request. Make the returned supported geometry the basis for the client’s subsequent display and review.\nInspect the resulting live view and the relevant recorded workflow with the operator. Check the required edges and targets, not just the center of the crop. For a proposed client exercise, include a supported request near a grid or aspect-ratio boundary and observe the actual returned fit. If the result misses the task, revise the approved geometry or design rather than concealing the difference in the client.\n\nVerification and evidence\nRetain the original, requested and returned rectangles with their canvas, channel and orientation. Keep a permitted resulting-view observation linked to the same change. Ask another reviewer to explain which coordinates the client now stores and why they may differ from the submitted request.\nRepeat the reconciliation after an approved orientation or view configuration change. Record image-quality and privacy checks separately where required. The proposed exercise does not assert a universal rounding rule, an exact installed grid size or a successful crop on any customer camera.\nOfficial references\n\nView Area API — Axis Communications; official VAPIX documentation.\n\nSource review completed October 29, 2026. Recheck the official documentation and the deployed device’s capabilities before changing production settings.", "content_markdown": "Bottom line: Read back and retain the returned view rectangle after a geometry change. Compare it with the intended scene instead of letting the client continue to display or calculate from the requested coordinates alone.\n\n## Source fact: documented behavior\n\nAxis’s [View Area API](https://developer.axis.com/vapix/network-video/view-area-api/) defines view subsections as virtual channels and expects their pixel coordinates to match the overview stream’s rotation and mirroring.\n\nThe documentation requires crop geometry to align with the canvas grid, usually 8 by 8 pixels, and describes seeking an optimal fit when the request cannot align on every side.\n\nThe geometry-change example advises updating local geometry from the response because the returned rectangle can differ from the submitted one.\n\n## What the source does not establish\n\nDo not assume the usual grid size applies identically to every product or that an accepted crop preserves the operational image requirement. Confirm the intended canvas, orientation and supported view area. Keep crop geometry separate from channel enablement, privacy-region acceptance and measured recorded detail.\n\n## Applicability questions\n\n- Which virtual channel and overview canvas define the requested rectangle?\n\n- Do the client’s coordinates match the actual rotation and mirroring?\n\n- How does the client update its saved geometry from the response?\n\n- Which edge or target must remain visible in the accepted scene?\n\n## DSE recommendation: controlled next steps\n\nThe following steps are DSE recommendations based on the cited source.\n\nDSE recommends reconciling submitted, returned and observed view geometry as three separate parts of a crop change.\n\n- Read the current view-area information and identify the exact channel, canvas and orientation. Record the approved scene boundary with a permitted reference image or marked task location. Prepare the requested rectangle in the documented coordinate system. Avoid using a rectangle from a different stream size as if it were already expressed on this canvas.\n\n- Apply an approved test geometry through the supported interface and preserve the full sanitized response. Compare the returned rectangle with the submitted values before updating the client’s local state. If they differ, retain both rather than rounding the returned values back to the request. Make the returned supported geometry the basis for the client’s subsequent display and review.\n\n- Inspect the resulting live view and the relevant recorded workflow with the operator. Check the required edges and targets, not just the center of the crop. For a proposed client exercise, include a supported request near a grid or aspect-ratio boundary and observe the actual returned fit. If the result misses the task, revise the approved geometry or design rather than concealing the difference in the client.\n\n## Verification and evidence\n\nRetain the original, requested and returned rectangles with their canvas, channel and orientation. Keep a permitted resulting-view observation linked to the same change. Ask another reviewer to explain which coordinates the client now stores and why they may differ from the submitted request.\n\nRepeat the reconciliation after an approved orientation or view configuration change. Record image-quality and privacy checks separately where required. The proposed exercise does not assert a universal rounding rule, an exact installed grid size or a successful crop on any customer camera.\n\n## Official references\n\n- [View Area API](https://developer.axis.com/vapix/network-video/view-area-api/) — Axis Communications; official VAPIX documentation.\n\nSource review completed October 29, 2026. Recheck the official documentation and the deployed device’s capabilities 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/read-back-axis-view-geometry-after-a-crop-change/", "url": "https://update.dsesecurity.com/updates/read-back-axis-view-geometry-after-a-crop-change/", "isPartOf": { "@id": "https://update.dsesecurity.com/#website" }, "lastReviewed": "2026-10-29" }, { "@type": "BreadcrumbList", "@id": "https://update.dsesecurity.com/updates/read-back-axis-view-geometry-after-a-crop-change/#breadcrumbs", "itemListElement": [ { "@type": "ListItem", "position": 1, "name": "DSE Updates", "item": "https://update.dsesecurity.com/" }, { "@type": "ListItem", "position": 2, "name": "Video Surveillance", "item": "https://update.dsesecurity.com/topic/video-surveillance/" }, { "@type": "ListItem", "position": 3, "name": "Read back Axis view geometry after a crop change", "item": "https://update.dsesecurity.com/updates/read-back-axis-view-geometry-after-a-crop-change/" } ] }, { "@type": [ "Article", "TechArticle" ], "@id": "https://update.dsesecurity.com/updates/read-back-axis-view-geometry-after-a-crop-change/#article", "identifier": "https://update.dsesecurity.com/updates/read-back-axis-view-geometry-after-a-crop-change/", "url": "https://update.dsesecurity.com/updates/read-back-axis-view-geometry-after-a-crop-change/", "headline": "Read back Axis view geometry after a crop change", "description": "Accept the Axis view-area geometry returned by the device after a crop request.", "abstract": "Accept the Axis view-area geometry returned by the device after a crop request. Grid alignment can make it differ from the submitted rectangle, so reconcile client state and the resulting view.", "articleBody": "Bottom line: Read back and retain the returned view rectangle after a geometry change. Compare it with the intended scene instead of letting the client continue to display or calculate from the requested coordinates alone.\nSource fact: documented behavior\nAxis’s View Area API defines view subsections as virtual channels and expects their pixel coordinates to match the overview stream’s rotation and mirroring.\nThe documentation requires crop geometry to align with the canvas grid, usually 8 by 8 pixels, and describes seeking an optimal fit when the request cannot align on every side.\nThe geometry-change example advises updating local geometry from the response because the returned rectangle can differ from the submitted one.\nWhat the source does not establish\nDo not assume the usual grid size applies identically to every product or that an accepted crop preserves the operational image requirement. Confirm the intended canvas, orientation and supported view area. Keep crop geometry separate from channel enablement, privacy-region acceptance and measured recorded detail.\nApplicability questions\n\nWhich virtual channel and overview canvas define the requested rectangle?\nDo the client’s coordinates match the actual rotation and mirroring?\nHow does the client update its saved geometry from the response?\nWhich edge or target must remain visible in the accepted scene?\n\nDSE recommendation: controlled next steps\nThe following steps are DSE recommendations based on the cited source.\nDSE recommends reconciling submitted, returned and observed view geometry as three separate parts of a crop change.\n\nRead the current view-area information and identify the exact channel, canvas and orientation. Record the approved scene boundary with a permitted reference image or marked task location. Prepare the requested rectangle in the documented coordinate system. Avoid using a rectangle from a different stream size as if it were already expressed on this canvas.\nApply an approved test geometry through the supported interface and preserve the full sanitized response. Compare the returned rectangle with the submitted values before updating the client’s local state. If they differ, retain both rather than rounding the returned values back to the request. Make the returned supported geometry the basis for the client’s subsequent display and review.\nInspect the resulting live view and the relevant recorded workflow with the operator. Check the required edges and targets, not just the center of the crop. For a proposed client exercise, include a supported request near a grid or aspect-ratio boundary and observe the actual returned fit. If the result misses the task, revise the approved geometry or design rather than concealing the difference in the client.\n\nVerification and evidence\nRetain the original, requested and returned rectangles with their canvas, channel and orientation. Keep a permitted resulting-view observation linked to the same change. Ask another reviewer to explain which coordinates the client now stores and why they may differ from the submitted request.\nRepeat the reconciliation after an approved orientation or view configuration change. Record image-quality and privacy checks separately where required. The proposed exercise does not assert a universal rounding rule, an exact installed grid size or a successful crop on any customer camera.\nOfficial references\n\nView Area API — Axis Communications; official VAPIX documentation.\n\nSource review completed October 29, 2026. Recheck the official documentation and the deployed device’s capabilities before changing production settings.", "datePublished": "2026-10-29T19:49:59+00:00", "dateModified": "2026-10-29T19:50:08+00:00", "mainEntityOfPage": { "@id": "https://update.dsesecurity.com/updates/read-back-axis-view-geometry-after-a-crop-change/" }, "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/read-back-axis-view-geometry-after-a-crop-change/#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": "Read back Axis view geometry after a crop change" }, "articleSection": [ "Video Surveillance" ], "keywords": [ "Video Surveillance", "Guide", "Advisory priority" ], "genre": "Guide", "about": [ { "@type": "Thing", "name": "Video Surveillance", "url": "https://update.dsesecurity.com/topic/video-surveillance/" } ], "wordCount": 537, "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 — View Area API", "url": "https://developer.axis.com/vapix/network-video/view-area-api/" } } ] } }