finds.dev← search

// the find

opengeos/qgis-gee-data-catalogs-plugin

★ 353 · Python · MIT · updated May 2026

A QGIS Plugin for searching data from the official Earth Engine Data Catalog and Awesome GEE Community Catalog

A QGIS plugin that surfaces Google Earth Engine's 5000+ datasets (official + community) directly in the QGIS GUI, letting you browse, filter, load, and inspect satellite imagery without touching the GEE Code Editor. Aimed at GIS professionals who prefer desktop workflows over browser-based Earth Engine but still want access to the full catalog.

The dual-catalog approach (780 official + 4360 community datasets, fetched live with disk cache fallback) is genuinely useful — most tools only expose the official catalog. The pixel time series inspector is a real feature: point-click extraction with chartable output and CSV/JSON export matches what people usually have to write custom GEE scripts to do. Installing via Pixi rather than fighting QGIS's bundled Python is the right call and saves most users a painful dependency mess. The QGIS Processing Provider integration means you can drop catalog searches into Model Builder, which is not something plugin authors usually bother with.

Google Earth Engine requires a Google Cloud project and increasingly enforces paid quota tiers — this plugin does nothing to surface that cost exposure to the user, so someone loading large ImageCollections may hit quota walls with no warning. The README's project structure section is already out of date: the actual tree has files (chat_dock.py, dependency_dialog.py, deps_manager.py, oauth.py, python_manager.py, uv_manager.py, venv_manager.py) that aren't mentioned, suggesting the docs aren't maintained in sync with the code. Installing the plugin itself requires Pixi, QGIS through Pixi, and a separate EE authentication step — that's a non-trivial onboarding burden for non-developer GIS users who are a natural audience here. The AI assistant (OpenGeoAgent) is underdocumented and ships as a chat panel with no explanation of what model powers it, what data it sends, or what it actually does beyond 'assistance'.

View on GitHub →

// want more like this?

We dig through GitHub every week and send a few repos picked for what you actually care about — each with an honest take like this one.

Get finds in your inbox → Search again →