duckdb-map

Analyze tabular and spatial data with DuckDB SQL into map-ready GeoJSON outputs.

1|Updated Feb 15, 2026
One-click install
npx skills add https://github.com/yuiseki/NEREID --skill duckdb-map
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: duckdb-map
Source: https://github.com/yuiseki/NEREID/tree/main/agents/gemini-workspace/.gemini/skills/duckdb-map
Command: npx skills add https://github.com/yuiseki/NEREID --skill duckdb-map

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

DuckDB enables local analytical SQL for tabular and geospatial data, making it easy to prepare map-ready results without heavy external dependencies.

Core Features & Use Cases

  • Local analytical SQL with DuckDB for tabular and geospatial data.
  • Convert SQL results into map-ready formats (GeoJSON, coordinate columns) for visualization.
  • Use cases include ad-hoc geospatial analysis, rapid map prototype workflows, and reproducible query-to-map pipelines.

Quick Start

Load your input data, write a SQL query with DuckDB, and export the results as map-ready data.

Frequently Asked Questions about duckdb-map

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I prepare geospatial data for map visualization using SQL?

You can prepare geospatial data for map visualization by running local analytical SQL queries with DuckDB to summarize tabular data and export map-ready outputs like GeoJSON or coordinate columns.

Can I use DuckDB for local geospatial analysis without external dependencies?

Yes, DuckDB enables local analytical SQL for tabular and geospatial data, allowing you to prepare map-ready results without heavy external dependencies or complex server setups.

What is the best way to convert SQL query results into map-ready formats?

The best way to convert SQL results into map-ready formats is to load your input data into DuckDB, write a SQL query for spatial summarization, and export the deterministic results as GeoJSON.

Does DuckDB work for reproducible query-to-map pipelines?

DuckDB works well for reproducible query-to-map pipelines by providing a deterministic local workflow to execute SQL queries and generate mapping-ready outputs for rapid map prototyping.

When should I use DuckDB for map workflows instead of other analytics tools?

Use DuckDB for map workflows when you need ad-hoc geospatial analysis or rapid map prototype workflows locally, and want to avoid heavy external dependencies while using SQL for data summarization.