<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Spatial-Database on Coyote Time</title>
    <link>https://blog.jonmikeys.com/tags/spatial-database/</link>
    <description>Recent content in Spatial-Database on Coyote Time</description>
    <generator>Hugo -- gohugo.io</generator>
    <language>en-us</language>
    <lastBuildDate>Sun, 21 Jun 2026 00:00:00 +0000</lastBuildDate>
    <atom:link href="https://blog.jonmikeys.com/tags/spatial-database/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Part 4: Spatial Databases for Tactical AI</title>
      <link>https://blog.jonmikeys.com/posts/spatial-databases-for-tactical-ai/</link>
      <pubDate>Sun, 21 Jun 2026 00:00:00 +0000</pubDate>
      <guid>https://blog.jonmikeys.com/posts/spatial-databases-for-tactical-ai/</guid>
      <description>A single tactical score is easy to compute and hard to trust.&#xA;A layered spatial database is easier to debug because each layer answers one question.&#xA;Why layers matter A tactical AI usually needs more than one kind of spatial information.&#xA;One layer can describe visibility. Another can describe cover. Another can describe occupancy or line of fire. Keeping those signals separate makes the system easier to reason about.&#xA;That is the main idea behind the spatial database in the lecture: represent the map as a stack of tactical views.</description>
    </item>
  </channel>
</rss>
