<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Geometry on Pi Stack</title>
    <link>https://www.pistack.xyz/tags/geometry/</link>
    <description>Recent content in Geometry on Pi Stack</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Sat, 20 Jun 2026 00:00:00 +0000</lastBuildDate>
    <atom:link href="https://www.pistack.xyz/tags/geometry/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Self-Hosted Spatial Index and Computational Geometry Libraries: libspatialindex vs GEOS vs S2 Geometry vs Boost.Geometry vs rbush</title>
      <link>https://www.pistack.xyz/posts/2026-06-20-spatial-index-computational-geometry-libraries-libspatialindex-geos-s2-boost-rbush/</link>
      <pubDate>Sat, 20 Jun 2026 00:00:00 +0000</pubDate>
      <guid>https://www.pistack.xyz/posts/2026-06-20-spatial-index-computational-geometry-libraries-libspatialindex-geos-s2-boost-rbush/</guid>
      <description>&lt;h2 id=&#34;introduction&#34;&gt;Introduction&lt;/h2&gt;&#xA;&lt;p&gt;Spatial data is everywhere — from GPS coordinates in mobile apps to geometric shapes in CAD software and polygons in GIS systems. Efficiently querying &amp;ldquo;what is near this point?&amp;rdquo; or &amp;ldquo;do these polygons intersect?&amp;rdquo; requires specialized data structures and algorithms that standard databases cannot provide out of the box. Spatial index libraries bridge this gap, offering R-trees, quadtrees, and computational geometry primitives optimized for 2D and 3D spatial queries.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
