How GeoJibe works

Every GeoJibe workflow is the same idea:

Source → Optional processing → Destination

You pick where data comes from, change it only if you need to, then choose where it should go.

Source — where the data comes from

Examples:

• A file on your computer (Upload)
• A file on the web (URL)
• An authenticated or configurable HTTP/REST dataset (HTTP/API)
• An object in S3 or Azure Blob Storage
• A file in Google Drive
• A layer from an ArcGIS FeatureServer
• A table in PostGIS, SQL Server, MySQL / MariaDB, Oracle Spatial, DuckDB, Google BigQuery, or Snowflake
• A vector layer published by GeoServer or GeoNode
• A collection from OGC API Features or WFS
• A file discovered from STAC, CKAN, or Hub

Field-data projects use a different path. QFieldCloud and Mergin Maps are for Sync, not for ordinary file conversion.

Processing — what you want to change

Processing is optional. You can upload a file and download it as-is when that is what you need.

When you do want changes, add only the steps you need:

Component	Use it to
Convert	Change format or coordinate system
Transform	Rename fields, keep or drop columns, filter rows, clip / simplify / buffer geometry, or write DuckDB SQL
Python	Custom changes Transform cannot do

You do not have to use all three.

Examples:

Upload → Download

URL → Transform → PostGIS

S3 → Python → GeoServer

Destination — where the finished data goes

• Download — get a file back
• 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
• Snowflake — write a table
• S3 — store the file
• Azure Blob — store the file
• Google Drive — store the file
• SFTP — send the file to a server
• Hub — store a dataset version
• GeoServer — publish a layer
• GeoNode — publish a catalog resource
• Webhook — POST or PUT the converted file to an HTTP endpoint

All Destinations need a signed-in account. Download does not need a saved connection. The others usually do; see saved connections.

One-off vs Job vs Sync

One-off — build, Run, done. No saved Job.

Job — save the workflow so you can run it again or schedule it.

Sync — a special Job for QFieldCloud or Mergin Maps. GeoJibe checks the remote project and updates PostGIS when the data has changed.

The public API and CLI call one-off interactive processing a Workspace. It is not a saved Job. See Jobs vs Workspaces.

Tip

You don't need to save a Job for a one-time conversion.

Canvas

Create opens the Canvas. Drag a Source, add any processing you need, choose a Destination, then Run.

See Using the Canvas.