<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Geozarr on Lost in Tab</title><link>https://teotl.dev/tags/geozarr/</link><description>Recent content in Geozarr on Lost in Tab</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Tue, 04 Nov 2025 12:00:00 +0000</lastBuildDate><atom:link href="https://teotl.dev/tags/geozarr/index.xml" rel="self" type="application/rss+xml"/><item><title>Metadata makes the data format: metadata storage and representation across array formats</title><link>https://teotl.dev/posts/2025/11/04/metadata-makes-the-data-format-metadata-storage-and-representation-across-array-formats/</link><pubDate>Tue, 04 Nov 2025 12:00:00 +0000</pubDate><guid>https://teotl.dev/posts/2025/11/04/metadata-makes-the-data-format-metadata-storage-and-representation-across-array-formats/</guid><description>When configured equivalently, COG and Zarr store the exact same data bytes.
So what actually distinguishes one raster format from another? Metadata. We
get philosophical about what metadata even is, examine how TIFF and Zarr each
represent it, tour the various ways geospatial coordinate information is
encoded across formats, ask where metadata should live, and make the case that
formal, versioned conventions are what truly enable interoperability.</description></item></channel></rss>