<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>cloud-native raster formats workshop on Lost in Tab</title><link>https://teotl.dev/talks/cloud-native-raster-formats-workshop/</link><description>Recent content in cloud-native raster formats workshop on Lost in Tab</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Sun, 30 Aug 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://teotl.dev/talks/cloud-native-raster-formats-workshop/index.xml" rel="self" type="application/rss+xml"/><item><title>Exploring Cloud Native Geospatial Data Formats: Hands-on with Raster Data</title><link>https://teotl.dev/presentations/foss4g-2026-raster-formats-workshop/</link><pubDate>Sun, 30 Aug 2026 00:00:00 +0000</pubDate><guid>https://teotl.dev/presentations/foss4g-2026-raster-formats-workshop/</guid><description>&lt;p>Ever wonder what GDAL is doing under the hood when you read a GeoTIFF file?
Doubly so when the file is a Cloud-optimized GeoTIFF (COG) on a remote server
somewhere? Have you been wondering what this Zarr thing is all about and
how it works? Then there&amp;rsquo;s the whole Kerchunk/VirtualiZarr indexing to
get cloud-native access for non-cloud-native data formats, what&amp;rsquo;s that about?&lt;/p>
&lt;p>Cloud-native geospatial is all the rage these days, and for good reason. As
data sizes grow, layer counts increase, and analytical methods become more
complex, the traditional download-to-the-desktop approach is quickly becoming
untenable for many applications. It&amp;rsquo;s no surprise then that users are turning
to cloud-based tools to scale out their analyses, or that traditional tooling
is adopting new ways of finding and accessing data from cloud-based sources.
But as we transition away from opening whole files to now grabbing ranges of
bytes off remote servers it seems all the more important to understand exactly
how cloud native data formats actually store data and what tools are doing to
access it.&lt;/p></description></item><item><title>Exploring Cloud Native Geospatial Data Formats: Hands-on with Raster Data</title><link>https://teotl.dev/presentations/foss4g-2025-raster-formats-workshop/</link><pubDate>Mon, 17 Nov 2025 00:00:00 +0000</pubDate><guid>https://teotl.dev/presentations/foss4g-2025-raster-formats-workshop/</guid><description>&lt;p>Ever wonder what GDAL is doing under the hood when you read a GeoTIFF file?
Doubly so when the file is a Cloud-optimized GeoTIFF (COG) on a remote server
somewhere? Have you been wondering what this Zarr thing is all about and
how it works? Then there&amp;rsquo;s the whole Kerchunk/VirtualiZarr indexing to
get cloud-native access for non-cloud-native data formats, what&amp;rsquo;s that about?&lt;/p>
&lt;p>Cloud-native geospatial is all the rage these days, and for good reason. As
data sizes grow, layer counts increase, and analytical methods become more
complex, the traditional download-to-the-desktop approach is quickly becoming
untenable for many applications. It&amp;rsquo;s no surprise then that users are turning
to cloud-based tools to scale out their analyses, or that traditional tooling
is adopting new ways of finding and accessing data from cloud-based sources.
But as we transition away from opening whole files to now grabbing ranges of
bytes off remote servers it seems all the more important to understand exactly
how cloud native data formats actually store data and what tools are doing to
access it.&lt;/p></description></item><item><title>Exploring Cloud Native Geospatial Data Formats: Hands-on with Raster Data</title><link>https://teotl.dev/presentations/foss4g-na-2025-raster-formats-workshop/</link><pubDate>Mon, 03 Nov 2025 00:00:00 +0000</pubDate><guid>https://teotl.dev/presentations/foss4g-na-2025-raster-formats-workshop/</guid><description>&lt;p>Ever wonder what GDAL is doing under the hood when you read a GeoTIFF file?
Doubly so when the file is a Cloud-optimized GeoTIFF (COG) on a remote server
somewhere? Have you been wondering what this Zarr thing is all about and
how it works? Then there&amp;rsquo;s the whole Kerchunk/VirtualiZarr indexing to
get cloud-native access for non-cloud-native data formats, what&amp;rsquo;s that about?&lt;/p>
&lt;p>Cloud-native geospatial is all the rage these days, and for good reason. As
data sizes grow, layer counts increase, and analytical methods become more
complex, the traditional download-to-the-desktop approach is quickly becoming
untenable for many applications. It&amp;rsquo;s no surprise then that users are turning
to cloud-based tools to scale out their analyses, or that traditional tooling
is adopting new ways of finding and accessing data from cloud-based sources.
But as we transition away from opening whole files to now grabbing ranges of
bytes off remote servers it seems all the more important to understand exactly
how cloud native data formats actually store data and what tools are doing to
access it.&lt;/p></description></item><item><title>On-ramp to CNG</title><link>https://teotl.dev/presentations/cng-2025-on-ramp-to-cng/</link><pubDate>Thu, 01 May 2025 00:00:00 +0000</pubDate><guid>https://teotl.dev/presentations/cng-2025-on-ramp-to-cng/</guid><description>A day-long capacity-building workshop for professionals new to working with
cloud-native formats and workflows: an introduction to cloud-native
geospatial for Earth observation, followed by a deep dive into cloud-native
raster formats.</description></item><item><title>Exploring Cloud Native Geospatial Data Formats: Hands-on with Raster Data</title><link>https://teotl.dev/presentations/oceania-2025-raster-formats-workshop/</link><pubDate>Wed, 15 Jan 2025 00:00:00 +0000</pubDate><guid>https://teotl.dev/presentations/oceania-2025-raster-formats-workshop/</guid><description>&lt;p>A virtual delivery of the cloud-native raster formats workshop for an Oceania
geospatial user group: a survey of the cloud-native geospatial landscape
followed by hands-on exploration of how COG and Zarr store data, reading both
by hand from cloud sources using just Python.&lt;/p></description></item><item><title>Deep Dive into Cloud-Native Geospatial Raster Formats</title><link>https://teotl.dev/presentations/foss4g-2024-raster-formats-workshop/</link><pubDate>Tue, 03 Dec 2024 00:00:00 +0000</pubDate><guid>https://teotl.dev/presentations/foss4g-2024-raster-formats-workshop/</guid><description>&lt;p>Ever wonder what GDAL is doing under the hood when you read a GeoTIFF file?
Doubly so when the file is a Cloud-optimized GeoTIFF (COG) on a remote server
somewhere? Have you been wondering what this new GeoZarr thing is all about and
how it actually works? Then there&amp;rsquo;s the whole Kerchunk/VirtualiZarr indexing to
get cloud-native access for non-cloud-native data formats, what&amp;rsquo;s that about?&lt;/p>
&lt;p>Cloud-native geospatial is all the rage these days, and for good reason. As
file sizes grow, layer counts increase, and analytical methods become more
complex, the traditional download-to-the-desktop approach is quickly becoming
untenable for many applications. It&amp;rsquo;s no surprise then that users are turning
to cloud-based tools such as Dask to scale out their analyses, or that
traditional tooling is adopting new ways of finding and accessing data from
cloud-based sources. But as we transition away from opening whole files to now
grabbing ranges of bytes off remote servers it seems all the more important to
understand exactly how cloud native data formats actually store data and what
tools are doing to access it.&lt;/p></description></item></channel></rss>