<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Presentations on Lost in Tab</title><link>https://teotl.dev/presentations/</link><description>Recent content in Presentations on Lost in Tab</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Tue, 03 Nov 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://teotl.dev/presentations/index.xml" rel="self" type="application/rss+xml"/><item><title>Do formats exist? Towards a unified foundation for data tooling</title><link>https://teotl.dev/presentations/foss4g-na-2026-do-formats-exist/</link><pubDate>Tue, 03 Nov 2026 00:00:00 +0000</pubDate><guid>https://teotl.dev/presentations/foss4g-na-2026-do-formats-exist/</guid><description>What if data formats didn&amp;rsquo;t need their own libraries? The cylf ecosystem
leverages WebAssembly to make codecs, format drivers, and storage drivers
modular, sandboxed, and fetchable on-demand. Each can be developed
independently and on its own lifecycle. We&amp;rsquo;ll demo a working proof of
concept.</description></item><item><title>Exploring Cloud Native Geospatial Data Formats: Hands-on with Vector Data</title><link>https://teotl.dev/presentations/foss4g-na-2026-vector-formats-workshop/</link><pubDate>Mon, 02 Nov 2026 00:00:00 +0000</pubDate><guid>https://teotl.dev/presentations/foss4g-na-2026-vector-formats-workshop/</guid><description>Dig into geospatial vector formats—including GeoJSON, WKT/WKB, and
cloud-native GeoParquet—using Python to see in detail how vector features are
stored in each format and to understand what cloud-native means for vector
data.</description></item><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><item><title>Do formats exist? Towards a unified foundation for data tooling</title><link>https://teotl.dev/presentations/foss4g-2026-do-formats-exist/</link><pubDate>Thu, 03 Sep 2026 00:00:00 +0000</pubDate><guid>https://teotl.dev/presentations/foss4g-2026-do-formats-exist/</guid><description>What if data formats didn&amp;rsquo;t need their own libraries? The cylf ecosystem
leverages WebAssembly to make codecs, format drivers, and storage drivers
modular, sandboxed, and fetchable on-demand. Each can be developed
independently and on its own lifecycle. We&amp;rsquo;ll demo a working proof of
concept.</description></item><item><title>Exploring Cloud Native Geospatial Data Formats: Hands-on with Vector Data</title><link>https://teotl.dev/presentations/foss4g-2026-vector-formats-workshop/</link><pubDate>Mon, 31 Aug 2026 00:00:00 +0000</pubDate><guid>https://teotl.dev/presentations/foss4g-2026-vector-formats-workshop/</guid><description>Dig into geospatial vector formats—including GeoJSON, WKT/WKB, and
cloud-native GeoParquet—using Python to see in detail how vector features are
stored in each format and to understand what cloud-native means for vector
data.</description></item><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>Redefining cloud native with the Coalesced Chunk Retrieval Protocol</title><link>https://teotl.dev/presentations/esip-january-2026-ccrp/</link><pubDate>Wed, 21 Jan 2026 00:00:00 +0000</pubDate><guid>https://teotl.dev/presentations/esip-january-2026-ccrp/</guid><description>&lt;p>A presentation of the Coalesced Chunk Retrieval Protocol (CCRP) as part of the
ESIP winter meeting session &amp;ldquo;Bridging the Cloud Divide - Part 1&amp;rdquo;, which
highlighted new advancements in supporting cloud adoption, from guides and
standards to new formats and services.&lt;/p>
&lt;p>For the full story behind CCRP, see the blog post
&lt;a href="https://teotl.dev/posts/2025/09/23/redefining-cloud-native-with-the-coalesced-chunk-retrieval-protocol/">Redefining cloud native with the Coalesced Chunk Retrieval Protocol&lt;/a>.&lt;/p></description></item><item><title>The importance of community in geospatial</title><link>https://teotl.dev/presentations/pgrsc-2025-community-in-geospatial/</link><pubDate>Tue, 25 Nov 2025 00:00:00 +0000</pubDate><guid>https://teotl.dev/presentations/pgrsc-2025-community-in-geospatial/</guid><description>&lt;p>Transcript of the talk as delivered:&lt;/p>
&lt;blockquote>
&lt;p>Hello everyone &amp;ndash; or I suppose I should say bula! Kia ora! Namaste! As-salamu alaykum!&lt;/p>
&lt;p>I know from the introduction yesterday I&amp;rsquo;ve missed many greetings. So find me
and tell me your greetings and tell me about where you are from, I know I have
a lot to learn about all your cultures here in the pacific. This is my first
time here, and it is a long way from where I live in Oregon in the United
States. I thank you all for your welcomeness and hospitality.&lt;/p></description></item><item><title>State of STAPI: A community tasking standard</title><link>https://teotl.dev/presentations/foss4g-2025-state-of-stapi/</link><pubDate>Thu, 20 Nov 2025 00:00:00 +0000</pubDate><guid>https://teotl.dev/presentations/foss4g-2025-state-of-stapi/</guid><description>Explore STAPI, a specification for a Sensor Tasking API. We’ll highlight
recent developments, showcase the open-source projects being developed in the
ecosystem, and share the community&amp;rsquo;s vision of increased interoperability
driving the next generation of geospatial workflows.</description></item><item><title>Is Zarr the new COG?</title><link>https://teotl.dev/presentations/foss4g-2025-is-zarr-the-new-cog/</link><pubDate>Wed, 19 Nov 2025 00:00:00 +0000</pubDate><guid>https://teotl.dev/presentations/foss4g-2025-is-zarr-the-new-cog/</guid><description>Zarr is gaining traction in geospatial workflows—but is it replacing COG,
complementing it, or something else entirely? We’ll unpack the formats’
shared foundations, explore their tradeoffs, and offer a path toward better
community guidance, tooling, and support.</description></item><item><title>Exploring Cloud Native Geospatial Data Formats: Hands-on with Vector Data</title><link>https://teotl.dev/presentations/foss4g-2025-vector-formats-workshop/</link><pubDate>Tue, 18 Nov 2025 00:00:00 +0000</pubDate><guid>https://teotl.dev/presentations/foss4g-2025-vector-formats-workshop/</guid><description>Dig into geospatial vector formats—including GeoJSON, WKT/WKB, and
cloud-native GeoParquet—using Python to see in detail how vector features are
stored in each format and to understand what cloud-native means for vector
data.</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>Is Zarr the new COG?</title><link>https://teotl.dev/presentations/foss4g-na-2025-is-zarr-the-new-cog/</link><pubDate>Tue, 04 Nov 2025 00:00:00 +0000</pubDate><guid>https://teotl.dev/presentations/foss4g-na-2025-is-zarr-the-new-cog/</guid><description>Zarr is gaining traction in geospatial workflows—but is it replacing COG,
complementing it, or something else entirely? We’ll unpack the formats’
shared foundations, explore their tradeoffs, and offer a path toward better
community guidance, tooling, and support.</description></item><item><title>State of STAPI: A community tasking standard</title><link>https://teotl.dev/presentations/foss4g-na-2025-state-of-stapi/</link><pubDate>Tue, 04 Nov 2025 00:00:00 +0000</pubDate><guid>https://teotl.dev/presentations/foss4g-na-2025-state-of-stapi/</guid><description>Explore STAPI, a specification for a Sensor Tasking API. We’ll highlight
recent developments, showcase the open-source projects being developed in the
ecosystem, and share the community&amp;rsquo;s vision of increased interoperability
driving the next generation of geospatial workflows.</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>Let's solve the problem of object storage</title><link>https://teotl.dev/presentations/pangeo-showcase-2025-object-storage/</link><pubDate>Wed, 01 Oct 2025 00:00:00 +0000</pubDate><guid>https://teotl.dev/presentations/pangeo-showcase-2025-object-storage/</guid><description>&lt;p>Object storage transformed data at planetary scale, giving us cheap, durable,
elastic storage. But in geospatial, it also turned chunking into everyone&amp;rsquo;s
problem. Misaligned queries waste time, compute, and money, while producers
struggle to optimize datasets for all users. This talk reframes our problems
with chunking as a limitation of the object model itself. We&amp;rsquo;ll look at why
object storage makes chunking visible, what that means for usability and
efficiency, and how the Coalesced Chunk Retrieval Protocol (CCRP) could
restore transparent, efficient access — this time at cloud scale.&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>Earth-Search: A STAC API of Open datasets on AWS</title><link>https://teotl.dev/presentations/foss4g-2024-earth-search-stac-api/</link><pubDate>Thu, 05 Dec 2024 00:00:00 +0000</pubDate><guid>https://teotl.dev/presentations/foss4g-2024-earth-search-stac-api/</guid><description>&lt;p>Earth-Search is a publicly-accessible SpatioTemporal Asset Catalog (STAC)
index and API providing data discovery and access for several major
geospatial data collections as part of the AWS Registry of Open Data (RODA),
including Sentinel-1, Sentinel-2, Landsat Collection 2, and NAIP imagery.
Items are backed by data assets accessible in cloud-native formats such as
Cloud-Optimized GeoTIFF (COG).&lt;/p>
&lt;p>This talk will provide an overview of the Earth-Search STAC catalog, how to
search it to discover items, and how best to access the backing data assets.
We&amp;rsquo;ll look at recent changes to catalog and discuss the progress and
challenges of the Sentinel-2 reprocessing/reindexing effort. We&amp;rsquo;ll also
briefly discuss the architecture of the data orchestration pipeline and what
open source tooling underlies its operation.&lt;/p></description></item><item><title>Community Standards and Satellite Tasking</title><link>https://teotl.dev/presentations/foss4g-2024-community-standards-and-satellite-tasking/</link><pubDate>Wed, 04 Dec 2024 00:00:00 +0000</pubDate><guid>https://teotl.dev/presentations/foss4g-2024-community-standards-and-satellite-tasking/</guid><description>&lt;p>Community standards are specifications that are created through informal
organization and are then widely adopted by a larger group. The STAC
specification and Cloud-Optimized GeoTIFFs are examples of community
specifications that have become de facto standards for geospatial
interoperability. This talk will examine how the process of developing
community standards differs from traditional standards development and how to
drive adoption. Numerous examples of successful community standards will be
presented.&lt;/p>
&lt;p>In addition, we will provide a case study of a current effort - that of
STAPI - a specification for satellite tasking, or more specifically, an API for
how users can order data from the future from satellite platforms. We have been
spearheading an effort to develop such a specification and after two sprints we
presented at the last FOSS4G in Kosovo. This prompted a third sprint in Europe,
bringing together an even larger community. Working with government groups,
commercial satellite operators, and data integrators, these sprints have worked
toward developing a specification as well as implementations for several
commercial providers, as well as ordering APIs for public datasets.&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><item><title>Planet-scale raster catalogs with STAC</title><link>https://teotl.dev/presentations/gis-in-action-2023-planet-scale-raster-catalogs/</link><pubDate>Tue, 18 Apr 2023 00:00:00 +0000</pubDate><guid>https://teotl.dev/presentations/gis-in-action-2023-planet-scale-raster-catalogs/</guid><description>&lt;p>SpatioTemporal Asset Catalogs (STAC) is a set of standards defining geospatial
metadata, catalog organization, and search APIs. With a growing set of tooling
and support from the open-source community, STAC is making it easier and more
efficient to discover, search, and analyze geospatial data. Element 84 operates
EarthSearch, a STAC catalog of the complete Sentinel-2 archive in
Cloud-Optimized GeoTIFF (COG) format, as part of the Registry of Open Data on
AWS.&lt;/p></description></item><item><title>Interfacing ArcGIS Desktop and GIS Server for Web-Based Basin Analysis GIS</title><link>https://teotl.dev/presentations/gis-in-action-2019-ebagis/</link><pubDate>Mon, 22 Apr 2019 00:00:00 +0000</pubDate><guid>https://teotl.dev/presentations/gis-in-action-2019-ebagis/</guid><description>&lt;p>The Center for Spatial Analysis and Research (CSAR) at PSU is currently
engaged in a multi-year agreement with the USDA-NRCS, National Water and
Climate Center (NWCC) to develop a spatial decision support system (SDSS) for
improving water forecast accuracy. One of the goals of the SDSS is to make the
GIS data used in the analysis available to government and public users. We
designed and developed a data repository framework (eBAGIS) that integrates
the geoprocessing capabilities of an existing desktop basin analysis GIS
(BAGIS) and an internet-based GIS server to share the basin analysis GIS data.
This presentation introduces the PostgreSQL-based GIS repository developed in
Django, a high-level Python web framework, and the REST APIs developed for
interfacing with ArcGIS Desktop addins implemented with VB .NET framework. The
internet GIS repository allows NWCC water supply forecasters and hydrologists
to upload their basin analysis GIS data created on their desktop ArcMap and
share these data with water managers and the public over the internet.&lt;/p></description></item><item><title>Crop classification using multi-temporal MODIS vegetation indices</title><link>https://teotl.dev/presentations/gis-in-action-2014-modis-crop-classification/</link><pubDate>Thu, 17 Apr 2014 00:00:00 +0000</pubDate><guid>https://teotl.dev/presentations/gis-in-action-2014-modis-crop-classification/</guid><description>&lt;p>The ability to map agricultural lands by crop type is crucial to understanding
the geography and dynamics of land use/land cover change and global production.
Existing remote sensing methods that can differentiate crops by type require
high spatial resolution data, high spectral resolution data, or extensive
ground truth information to develop training sites, none of which are freely
available for much of the world. As an alternative, I propose a new method of
crop classification using multi-temporal MODIS vegetation indices as a base
image from which to extract crops using their phenologies. I test and refine
this method in Kansas, USA using the USDA Cropland Data Layer as reference. I
discuss the numerous factors that effect the application and accuracy of the
method, the method&amp;rsquo;s current limitations, and how the method might be further
tested and refined.&lt;/p></description></item><item><title>HydrantTools: An ArcGIS Python Toolbox</title><link>https://teotl.dev/presentations/gis-in-action-2014-hydranttools/</link><pubDate>Wed, 16 Apr 2014 00:00:00 +0000</pubDate><guid>https://teotl.dev/presentations/gis-in-action-2014-hydranttools/</guid><description/></item></channel></rss>