SedonaDB: Why Yet Another Geospatial Database Engine?
2026-09-01 , Conference Management Room4

SedonaDB is an open-source single-node analytical database engine for GIS. But, with established options like PostGIS and DuckDB, why do we need yet another engine? This talk will provide an overview of the current FOSS4G database landscape and explain why SedonaDB is a name you need to know.


SedonaDB is a powerful open-source, single-node analytical database engine specifically designed for modern GIS workloads. However, with industry titans like PostGIS and the rising popularity of DuckDB-Spatial, you might find yourself asking—or being told by your boss—"Don't we already have a geospatial database at home?" Why would we need yet another tool in an already crowded ecosystem?

As of this writing, one of the most convincing answers is probably that SedonaDB can handle both raster and vector data without requiring a complex setup like PostGIS. But, honestly, it's hard to give a definitive answer because the technology is advancing so rapidly that today's advantage might disappear tomorrow. For example, SedonaDB was previously the only database among PostGIS and DuckDB to have a native GEOMETRY type. However, since DuckDB v1.5.0, the GEOMETRY type is now native.

So, in this talk, rather than focusing on advertising SedonaDB based on current status alone, I will explore the recent progress of open-source databases with geospatial support, such as DuckDB, PostGIS, LanceDB, and SedonaDB.


Level of technical complexity: 2 - intermediate Indicate what is (are) the open source project(s) essential in your talk:

Apache SedonaDB, DuckDB, PostGIS

I make my conference contribution available under the CC BY 4.0 license. The conference contribution comprises the abstract, the text contribution for the conference proceedings, the presentation materials as well as the video recording and live transmission of the presentation: