Query-farm

Query-farm / geosilo

Public

DuckDB extension for compact geometry encoding using delta-encoded coordinates. 3-4x smaller than WKB.

compression duckdb duckdb-extension geoarrow geometry
19
0
100% credibility
Found Apr 12, 2026 at 19 stars -- GitGems finds repos before they trend. Get early access to the next one.
Sign Up Free
AI Analysis
C++
AI Summary

GeoSilo is a DuckDB extension that provides efficient compression for geometry data, enabling smaller storage and direct spatial queries without decompression.

How It Works

1
🔍 Discover GeoSilo

You hear about a handy tool that shrinks map and location data to save space while keeping it easy to use in your database.

2
📥 Add to your database

You simply include this map compressor into your existing database setup with a quick command.

3
🗺️ Prepare your map data

You take your shapes, lines, and points from maps and ready them for compression.

4
✨ Compress your maps

With one easy function, you turn bulky map data into a super-compact form that still works perfectly.

5
📊 Run queries instantly

You ask questions about areas, lengths, or bounding boxes directly on the compact data without waiting to unpack it.

🎉 Handle huge datasets effortlessly

Your maps load faster, files stay tiny, and you explore location data smoothly every time.

Sign up to see the full architecture

4 more

Sign Up Free

Star Growth

See how this repo grew from 19 to 19 stars Sign Up Free
Repurpose This Repo

Repurpose is a Pro feature

Generate ready-to-use prompts for X threads, LinkedIn posts, blog posts, YouTube scripts, and more -- with full repo context baked in.

Unlock Repurpose
AI-Generated Review

What is geosilo?

DuckDB extension in C++ that compresses GEOMETRY data (WKB) into GEOSILO blobs, 3-4x smaller via delta-encoded coordinates. Pairs with the spatial extension for geosilo_encode/geosilo_decode functions, a castable GEOSILO type, and direct ST_Area/ST_Length queries without decoding. Supports CRS scaling (EPSG:4326 at 1e7, UTM at 100) and Arrow for Parquet/httpfs.duckdb extension workflows.

Why is it gaining traction?

Crushes WKB bloat on disk and wire—benchmarks hit 3-4x savings on TIGER counties/states, plus ZSTD stacks to 10x. No-decode spatial ops (bbox, area) and metadata extraction keep queries fast; Arrow integration shines for duckdb extensions download from the duckdb extension repository. Stands out versus raw spatial in duckdb github repo for geometry-heavy ETL.

Who should use this?

GIS engineers ingesting massive GeoParquet/OSM into DuckDB via httpfs.duckdb extension. Analysts benchmarking TIGER data in duckdb github python/R scripts needing compact storage. Spatial devs bridging duckdb extension postgres dumps or exporting via duckdb github action/releases.

Verdict

Promising for geometry compression (proven 3-4x wins) but early-stage: 19 stars, 1.0% credibility, thin docs/tests. Prototype in non-prod DuckDB setups via duckdb extensions or pip duckdb extensions—watch duckdb github issues for polish.

(178 words)

Sign up to read the full AI review Sign Up Free

Similar repos coming soon.