<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Eccodes on Pi Stack</title>
    <link>https://www.pistack.xyz/tags/eccodes/</link>
    <description>Recent content in Eccodes on Pi Stack</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Fri, 23 Oct 2026 00:00:00 +0000</lastBuildDate>
    <atom:link href="https://www.pistack.xyz/tags/eccodes/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>ecCodes vs cfgrib vs MetPy in 2026: The Right Way to Decode GRIB2 Weather Data in Python</title>
      <link>https://www.pistack.xyz/posts/2026-10-23-grib2-weather-data-python-eccodes-cfgrib-metpy-guide/</link>
      <pubDate>Fri, 23 Oct 2026 00:00:00 +0000</pubDate>
      <guid>https://www.pistack.xyz/posts/2026-10-23-grib2-weather-data-python-eccodes-cfgrib-metpy-guide/</guid>
      <description>&lt;p&gt;A single ERA5 pressure-level file is 400 MB. A GFS 0.25° forecast cycle is several gigabytes spread over dozens of files. And when you open the first one, Python hands you back a wall of undocumented integer codes, a longitude axis running from 0 to 360, and a &lt;code&gt;KeyError&lt;/code&gt; for a parameter you were sure existed.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
