Skip to content

Destinations

Destinations are where GeoJibe sends the finished data.

Destination Best for
Download Get a file back once
PostGIS Write a table
SQL Server Write a table
MySQL / MariaDB Write a table
Oracle Spatial Write a table
DuckDB Download a .duckdb file
Google BigQuery Write a table
S3 Store the converted file
SFTP Drop the file on a server
GeoServer Publish a vector layer
GeoNode Publish a catalog resource
Webhook POST or PUT the converted file to an HTTP endpoint

Download

Use Download for one-off conversions. You do not create a saved Download connection.

After Run, click Download. Without signing in, Download and DuckDB are available without a saved connection.

Download cannot be used as a scheduled Job Destination — there is no file waiting for you next week unless you fetch it at run time.

PostGIS

Saved database connection, then schema, table, and write mode (Create, Replace, Append) per run.

Sync Jobs are different: they use a schema only. See Send data to PostGIS.

SQL Server

Saved database connection, then schema, table, and write mode (Create, Replace, Append) per run.

Send data to SQL Server

MySQL / MariaDB

Saved database connection, then table and write mode (Create, Replace, Append) per run.

Send data to MySQL / MariaDB

Oracle Spatial

Saved database connection, then schema, table, and write mode (Create, Replace, Append) per run. Vector tables only.

Send data to Oracle Spatial

DuckDB

Writes one spatial table into a .duckdb file you download. Create or Replace only. DuckDB cannot be saved as a reusable Destination.

Send data to DuckDB

Google BigQuery

Saved Google Cloud project and service-account JSON key, then dataset, table, and write mode (Create, Replace, Append) per run. Geometry is written as native GEOGRAPHY. The dataset must already exist. Vector tables only. Requires EPSG:4326.

Send data to Google BigQuery

S3

Saved bucket and credentials, then an object key per run. AWS or S3-compatible storage.

Send data to S3

SFTP

Saved host and login, then a remote path. Parent directories must already exist.

Send data by SFTP

GeoServer

Saved GeoServer login. Each publish creates a new store and layer in an existing workspace. Vector data is published as GeoPackage.

Publish data to GeoServer

GeoNode

Saved GeoNode login (token or username/password). Each publish creates a new catalog resource. Vector data is uploaded as GeoPackage.

Publish data to GeoNode

Webhook

Saved HTTP endpoint and authentication. Each delivery sends the converted file (POST or PUT, multipart or raw body). This is not a Job-success notice.

Send data to a Webhook

Job outcome emails and JSON notices are configured on the Job, not as a Destination. See Job Notifications.

Who can use which

Destination Without signing in Saved connection
Download Yes Not used
PostGIS, S3, SFTP No Optional (can fill in once)
GeoServer, GeoNode No Required
Webhook No Optional (can fill in once)

See Saved connections.