<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Detection Geometry on Counter UAV Radar — Low-Altitude Surveillance Radar</title>
    <link>https://www.counteruavradar.com/tags/detection-geometry/</link>
    <description>Recent content in Detection Geometry on Counter UAV Radar — Low-Altitude Surveillance Radar</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Fri, 27 Mar 2026 20:10:00 +0800</lastBuildDate>
    <atom:link href="https://www.counteruavradar.com/tags/detection-geometry/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>What is Radar Resolution?</title>
      <link>https://www.counteruavradar.com/knowledge-base/what-is-radar-resolution/</link>
      <pubDate>Mon, 29 Sep 2025 09:00:00 +0800</pubDate>
      <guid>https://www.counteruavradar.com/knowledge-base/what-is-radar-resolution/</guid>
      <description>&lt;p&gt;What is radar resolution? In simple terms, radar resolution is the radar&amp;rsquo;s ability to tell that two nearby things are not actually one thing. If two targets are too close together for the radar to separate them, the radar may display them as one blob, one return, or one measurement cell. If the radar can distinguish them as separate, then its resolution is good enough for that situation.&lt;/p&gt;&#xA;&lt;p&gt;This idea matters because beginners often focus on detection range first. Range is important, but it answers a different question. Range asks how far away the radar may detect something. Resolution asks how clearly the radar can separate details within what it detects. A radar may see far and still have trouble telling whether a return comes from one object or two. That is why high range does not automatically mean high resolution.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
