Send data to DuckDB¶
GeoJibe can write the result of a workflow into a DuckDB database file you download.
DuckDB appears only when GeoJibe's GDAL runtime can write DuckDB files.
This writes one spatial table into a .duckdb file. It is not a schema or database migration.
DuckDB is a file Destination, like Download. You do not save a DuckDB connection.
Before you start¶
You'll need a vector dataset in the workflow and a table name for this delivery.
1. Add your data and any changes¶
Upload or import a vector dataset. Add Transform or Convert if you need them.
DuckDB is for vector data.
If you used Convert to reproject, DuckDB receives that CRS. GeoJibe does not reproject again at the Destination.
2. Choose DuckDB¶
Add DuckDB on the Canvas, or choose DuckDB in Classic.
Then set:
| Field | Typical value |
|---|---|
| Table | neighborhoods |
| Write mode | See below |
3. Choose a write mode¶
| Mode | What it does |
|---|---|
| Create | Creates a new DuckDB file for this job. Fails if that file already exists. |
| Replace | Overwrites the DuckDB file if it already exists in this job. |
Append is not offered. There is no existing DuckDB file sitting on the server to append into.
Warning
Replace mode overwrites the DuckDB file produced earlier in the same job.
4. Run¶
Click Run, or Send to DuckDB in Classic.
You should see a successful delivery. Download then gives you the .duckdb file.
Example: PostGIS → Transform → DuckDB.
What happens next?¶
Open the file in QGIS, DuckDB, or another tool that reads spatial DuckDB tables.
This is a one-off unless you deliver somewhere that can be saved as a Job.