<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Linear Infrastructure on Counter UAV Radar — Low-Altitude Surveillance Radar</title>
    <link>https://www.counteruavradar.com/tags/linear-infrastructure/</link>
    <description>Recent content in Linear Infrastructure on Counter UAV Radar — Low-Altitude Surveillance Radar</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Fri, 27 Mar 2026 21:15:00 +0800</lastBuildDate>
    <atom:link href="https://www.counteruavradar.com/tags/linear-infrastructure/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Pipeline Monitoring Systems</title>
      <link>https://www.counteruavradar.com/knowledge-base/pipeline-monitoring-systems/</link>
      <pubDate>Fri, 05 Sep 2025 00:00:00 +0000</pubDate>
      <guid>https://www.counteruavradar.com/knowledge-base/pipeline-monitoring-systems/</guid>
      <description>&lt;p&gt;Pipeline monitoring systems have to protect a fundamentally different asset geometry from most physical security programs. A pipeline right-of-way is long, distributed, and exposed to varied terrain, changing access conditions, and many kinds of third-party activity. That means monitoring design should focus on risk-based corridor awareness, not on copying a fixed-site perimeter model.&lt;/p&gt;&#xA;&lt;p&gt;PHMSA guidance is helpful because it treats patrol frequency, leak recognition, and safety management as ongoing operational disciplines. In other words, pipeline monitoring is not only about spotting one bad event. It is about combining observations, condition indicators, and operating context across a long asset.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
