Sources¶

Sources are simply where GeoJibe gets your data.

Source Processing Destination

Source	Best for
Upload	Files on your computer
URL	Public files available by URL
HTTP/API	Authenticated or configurable HTTP/REST datasets
S3	Object storage
ArcGIS	ArcGIS FeatureServer layers
PostGIS	A spatial table or view
SQL Server	A spatial table or view
MySQL / MariaDB	A spatial table or view
Oracle Spatial	A spatial table or view
DuckDB	A spatial table in a `.duckdb` file
Google BigQuery	A spatial table or view
GeoServer	A published vector layer
GeoNode	A published vector dataset
Hub	A file stored in Hub
QFieldCloud	Syncing a field project into PostGIS
Mergin Maps	Syncing a Mergin Maps project into PostGIS

Upload¶

Drop a file on the Canvas or use Choose a file.

Common inputs include GeoPackage, GeoJSON, Shapefile (as a ZIP of companion files), GeoTIFF, and CSV with geometry. See Supported formats.

Upload cannot be saved as a reusable Source. There is no file left on the server to fetch next week. For repeatable Jobs, use URL, HTTP/API, S3, FeatureServer, PostGIS, SQL Server, MySQL / MariaDB, Oracle Spatial, Google BigQuery, GeoServer, GeoNode, or Hub.

A ZIP must contain one spatial dataset. A Shapefile needs .shp, .shx, and .dbf together. GeoPackage may contain several layers — you choose layers at Convert time.

URL¶

Paste an http/https link and click Import. No login fields. Private or local addresses are blocked.

Import data from a URL

HTTP/API¶

Use this when the web service needs a token, API key, Basic login, headers, query parameters, or POST. URL stays the simple public-file option.

Import from HTTP/API

S3¶

Saved account + bucket, then an object Key per import.

Import data from S3

ArcGIS (FeatureServer)¶

Connect to a public FeatureServer, pick a layer, Import. The Canvas label is ArcGIS.

Import a FeatureServer layer

PostGIS¶

Saved database connection, then a schema and table per import.

Import from PostGIS

SQL Server¶

Saved database connection, then a schema and table per import.

Import from SQL Server

MySQL / MariaDB¶

Saved database connection, then a table per import. MySQL and MariaDB use the same connector.

Import from MySQL / MariaDB

Oracle Spatial¶

Saved database connection, then a schema and table per import. Vector tables only.

Import from Oracle Spatial

DuckDB¶

Upload a .duckdb file, then choose a spatial table. Vector tables only. DuckDB cannot be saved as a reusable Source.

Import from DuckDB

Google BigQuery¶

Saved Google Cloud project and service-account JSON key, then a dataset and table per import. Vector tables only. GEOGRAPHY columns become feature geometry.

Import from Google BigQuery

GeoServer¶

Saved GeoServer connection, then a published vector layer per import.

Import from GeoServer

GeoNode¶

Saved GeoNode connection, then a vector dataset per import. GeoNode 4 and 5 are both supported.

Import from GeoNode

QFieldCloud and Mergin Maps¶

These are Sync Sources. They cannot be used with Convert.

Saved Sources¶

URL, HTTP/API, FeatureServer, S3, PostGIS, SQL Server, MySQL / MariaDB, Oracle Spatial, Google BigQuery, GeoServer, GeoNode, Hub, QFieldCloud, and Mergin Maps can be saved. Upload and DuckDB cannot.

See Saved connections.