<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Line of Sight on Counter UAV Radar — Low-Altitude Surveillance Radar</title>
    <link>https://www.counteruavradar.com/tags/line-of-sight/</link>
    <description>Recent content in Line of Sight on Counter UAV Radar — Low-Altitude Surveillance Radar</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Fri, 27 Mar 2026 18:45:00 +0800</lastBuildDate>
    <atom:link href="https://www.counteruavradar.com/tags/line-of-sight/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>How to Select Detection Range</title>
      <link>https://www.counteruavradar.com/knowledge-base/how-to-select-detection-range/</link>
      <pubDate>Tue, 21 Apr 2026 00:00:00 +0000</pubDate>
      <guid>https://www.counteruavradar.com/knowledge-base/how-to-select-detection-range/</guid>
      <description>&lt;p&gt;Selecting detection range sounds simple until the planning questions become specific. How much range is enough? Enough for what target, from what direction, at what altitude, and with how much time left for a human or automated response?&lt;/p&gt;&#xA;&lt;p&gt;That is why useful range selection starts with time and action, not with a single specification sheet number.&lt;/p&gt;&#xA;&lt;h2 id=&#34;convert-range-into-warning-time&#34;&gt;Convert Range Into Warning Time&lt;/h2&gt;&#xA;&lt;p&gt;The first design question is not &amp;ldquo;What range can I buy?&amp;rdquo; It is &amp;ldquo;How much warning time do I need?&amp;rdquo;&lt;/p&gt;</description>
    </item>
    <item>
      <title>What is Line of Sight in Surveillance?</title>
      <link>https://www.counteruavradar.com/knowledge-base/what-is-line-of-sight-in-surveillance/</link>
      <pubDate>Mon, 08 Sep 2025 09:00:00 +0800</pubDate>
      <guid>https://www.counteruavradar.com/knowledge-base/what-is-line-of-sight-in-surveillance/</guid>
      <description>&lt;p&gt;What is line of sight in surveillance? In plain language, &lt;code&gt;line of sight&lt;/code&gt;, usually shortened to &lt;code&gt;LOS&lt;/code&gt;, means the sensor has a usable direct path to the part of the scene it needs to observe. If a hill, building, wall, tree line, container stack, or even the Earth&amp;rsquo;s curvature blocks that path, then the target may be inside the system&amp;rsquo;s theoretical range and still not be seen in practice.&lt;/p&gt;&#xA;&lt;p&gt;That is why line of sight is one of the most important ideas for beginners to understand. People often focus on advertised sensor range, optical zoom, or camera resolution and assume those numbers tell the whole story. They do not. A camera with excellent zoom still cannot see through a warehouse corner. A radar with strong detection range still has blind sectors created by terrain masking or low-altitude geometry. A thermal camera can improve contrast at night, but it still needs a path to the target area. In real deployments, line of sight often determines whether the sensor is useful more than the headline specification does.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
