Import from DuckDB¶
Use DuckDB when the data already lives in a DuckDB database file.
DuckDB appears only when GeoJibe's GDAL runtime can open DuckDB files.
This is a spatial table import, not a database migration. GeoJibe copies one table into the workflow.
Before you start¶
You'll need:
- A
.duckdb(or.ddb) file on your computer - At least one spatial table or view in that file
You do not sign in to a server. DuckDB is a file, like GeoPackage.
DuckDB cannot be saved as a reusable Source. There is no file left on the server to fetch next week. For repeatable Jobs, use a URL, S3, or a database Source instead.
1. Add DuckDB on the Canvas¶
Add DuckDB, choose the .duckdb file, then Connect.
GeoJibe lists the spatial tables. Choose the table you want. Click Import.
GeoJibe copies that table into the job workspace and inspects it.
After Import, Transform sees the real field names. Convert offers the same formats as an uploaded file.
Example: DuckDB → Transform → GeoPackage.
2. Process and deliver¶
Add Transform, Convert, or Python if you need them. Then choose a Destination — Download, GeoPackage, PostGIS, DuckDB, and the rest work as usual.
Click Run.
Spatial data¶
GeoJibe imports tables that have geometry. Non-spatial tables are not listed.
Coordinate systems and attributes come through with the table. Convert can reproject afterward.