<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>anatomy of a file on Lost in Tab</title><link>https://teotl.dev/talks/anatomy-of-a-file/</link><description>Recent content in anatomy of a file on Lost in Tab</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Wed, 07 Oct 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://teotl.dev/talks/anatomy-of-a-file/index.xml" rel="self" type="application/rss+xml"/><item><title>Anatomy of a file</title><link>https://teotl.dev/presentations/cng-forum-2026-anatomy-of-a-file/</link><pubDate>Wed, 07 Oct 2026 00:00:00 +0000</pubDate><guid>https://teotl.dev/presentations/cng-forum-2026-anatomy-of-a-file/</guid><description>Raster, vector, point cloud: every geospatial format solves the same core
problems, including linearization, chunking, compression, and metadata. Let&amp;rsquo;s
build a format from scratch to see these concerns in practice.</description></item><item><title>Anatomy of a file</title><link>https://teotl.dev/presentations/foss4g-2026-anatomy-of-a-file/</link><pubDate>Thu, 03 Sep 2026 00:00:00 +0000</pubDate><guid>https://teotl.dev/presentations/foss4g-2026-anatomy-of-a-file/</guid><description>Raster, vector, point cloud: every geospatial format solves the same core
problems, including linearization, chunking, compression, and metadata. Let&amp;rsquo;s
build a format from scratch to see these concerns in practice.</description></item></channel></rss>