# Handle empty and multiple Axis coordinate conversion results > Preserve the result grouping for every Axis coordinate-conversion input. An individual point can produce no result or several results, so a flat one-to-one mapping is unsafe to assume. - Canonical URL: https://update.dsesecurity.com/updates/handle-empty-and-multiple-axis-coordinate-conversion-results/ - Publisher: Detection Systems & Engineering (DSE Security) - Author: DSE Security Editorial Team - Published: 2026-10-29T19:50:01+00:00 - Modified: 2026-10-29T19:50:08+00:00 - Last reviewed by DSE: 2026-10-29 - Resource type: Guide - DSE priority: Advisory - Topics: IT, Video Surveillance - Reading time: 3 minutes ## What you need to know Preserve the result grouping for every Axis coordinate-conversion input. An individual point can produce no result or several results, so a flat one-to-one mapping is unsafe to assume. ## Potentially affected Axis products exposing the documented Coordinate conversion API interface; confirm actual device, hardware and software applicability before applying the proposed checks. ## DSE recommendation DSE recommends accepting the consumer’s zero-result and multiple-result handling before enabling coordinate-driven behavior. ## Article Bottom line: Keep each input point linked to its complete conversion result. Design the consumer to handle an empty result or multiple candidate points before using converted coordinates to draw an overlay or direct another function. ## Source fact: documented behavior Axis’s [Coordinate conversion API](https://developer.axis.com/vapix/device-configuration/coordinate-conversion-api/) provides discovery of coordinate spaces known by the product and conversion of points between those spaces. For a conversion request, an individual point can fail; the corresponding output is then an empty list, while another input can yield more than one output point. The documented multi-camera example lacks device-centric and geographic coordinate knowledge, unlike the separate camera-and-radar example. ## What the source does not establish Do not assume that every product exposes geographic coordinates or the same channel spaces. Do not invent a replacement point when conversion returns no result. Keep coordinate conversion separate from calibration accuracy, physical location acceptance and authorization to move a camera or trigger an operational response. ## Applicability questions - Which source and destination spaces does the actual device report? - How will the client preserve the identity of every input point? - What should the application do with zero or several returned points? - Which independent observation will validate any operational use of a converted location? ## DSE recommendation: controlled next steps The following steps are DSE recommendations based on the cited source. DSE recommends accepting the consumer’s zero-result and multiple-result handling before enabling coordinate-driven behavior. - Discover the actual coordinate-space names and record the intended conversion pair. Identify the originating channel or sensor rather than assigning a universal meaning to a familiar coordinate name. Establish an approved test dataset with input identities and expected handling categories. Obtain any device-specific coordinate or calibration requirements from the relevant official documentation before selecting numerical points. - Submit a bounded proposed test through the supported conversion workflow and keep each returned group beside its original input. Inspect the result structure before flattening or exporting it. For an empty group, follow the application’s approved unresolved-location behavior. For several candidates, use an explicitly reviewed selection or presentation policy instead of silently choosing the first result. - Test the consumer’s decision logic with clearly labeled harmless fixtures for zero, one and several outputs. Keep those fixtures separate from observations actually returned by a device. Require the integration owner to explain how ambiguous results are displayed or escalated. Withhold automated movement or other consequential use until its own independent location and response checks have been accepted. ## Verification and evidence Retain the discovered spaces, sanitized request, grouped response, input identifiers and the consumer’s disposition for every point. Ask another reviewer to reconstruct that association without relying on list lengths alone. Record a missing location as missing evidence rather than assigning a plausible coordinate. For a later channel or calibration change, repeat the relevant real-device conversion check and the consumer’s ambiguity cases. Keep the numerical observation separate from the application policy that chooses what to do with it. This article reports no converted site position, measured accuracy or completed coordinate-driven operation. ## Official references - [Coordinate conversion API](https://developer.axis.com/vapix/device-configuration/coordinate-conversion-api/) — Axis Communications; official VAPIX documentation. Source review completed October 29, 2026. Recheck the official documentation and the deployed device’s capabilities before changing production settings. ## Primary reference - Name: Axis Communications — Coordinate conversion API - Authority: Axis Communications - URL: https://developer.axis.com/vapix/device-configuration/coordinate-conversion-api/ - Source publication date: Not stated by the source ## Citation and use Preferred citation: “Handle empty and multiple Axis coordinate conversion results,” DSE Security, https://update.dsesecurity.com/updates/handle-empty-and-multiple-axis-coordinate-conversion-results/ Publishing principles: https://update.dsesecurity.com/updates/dse-updates-editorial-methodology/ Usage and citation policy: https://update.dsesecurity.com/usage/ Copyright © 2026 Detection Systems & Engineering. All rights reserved.