<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Django on Pi Stack</title>
    <link>https://www.pistack.xyz/tags/django/</link>
    <description>Recent content in Django on Pi Stack</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Fri, 12 Jun 2026 00:00:00 +0000</lastBuildDate>
    <atom:link href="https://www.pistack.xyz/tags/django/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Self-Hosted Hydrologic Data Platforms: Tethys Platform vs HydroShare vs CUAHSI HydroClient</title>
      <link>https://www.pistack.xyz/posts/2026-06-12-self-hosted-hydrologic-data-platforms-tethys-hydroshare-cuahsi/</link>
      <pubDate>Fri, 12 Jun 2026 00:00:00 +0000</pubDate>
      <guid>https://www.pistack.xyz/posts/2026-06-12-self-hosted-hydrologic-data-platforms-tethys-hydroshare-cuahsi/</guid>
      <description>&lt;h2 id=&#34;why-self-host-hydrologic-data-management&#34;&gt;Why Self-Host Hydrologic Data Management?&lt;/h2&gt;&#xA;&lt;p&gt;Water resource management depends on integrating diverse datasets — stream gauge readings, groundwater well logs, satellite precipitation estimates, climate model outputs, and water quality samples — into coherent analysis workflows. Historically, hydrologists spent more time locating and formatting data than actually analyzing it. Purpose-built hydrologic data platforms address this fragmentation by providing centralized catalogs, standardized metadata, and web-based visualization tools.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
