Skip to content
GeoJibe

Sync QFieldCloud with PostGIS

GeoJibe can keep a QFieldCloud GeoPackage in step with a PostGIS schema.

This is a Sync Job, not a file conversion. GeoJibe checks the remote project for changes. When the GeoPackage changed, it updates PostGIS. When nothing changed, the run succeeds without writing data.

QFieldCloud cannot be used as a Convert Source. Do not add Convert, Transform, or Python to this workflow.

Tip

Sync requires saving as a Job. There is no one-off QFieldCloud download on the Canvas.

Before you start

You'll need:

  • A QFieldCloud account and project that contains a GeoPackage
  • A PostGIS Destination (database already created, with PostGIS enabled)
  • Sign-in, with QFieldCloud sync enabled on the server

Direction is always QFieldCloud → PostGIS. Two-way sync is not available for QFieldCloud.

1. Save a QFieldCloud Source

Open Sources → Add Source → QFieldCloud.

Field What to enter
Server URL Usually https://app.qfield.cloud/api/v1/
Username / Password QFieldCloud login

Click Test, then Save.

This Source is the account. You choose the project when you create the Job.

2. Save a PostGIS Destination

Save a PostGIS connection as in Send data to PostGIS. For Sync you will only set a schema, not a table or write mode.

3. Create a Sync Job

Open Jobs → Add Job → Sync Job, or add QFieldCloud and Sync on the Canvas and click Save as Job.

  1. Select the QFieldCloud Source.
  2. Click List projects, choose the project, then choose the GeoPackage.
  3. Select the PostGIS Destination and the schema GeoJibe should write into.
  4. Set Every N minutes (default 5) and a timezone.
  5. Check Enable schedule if it should run on its own.
  6. Save Job.

4. Run Now

Click Run Now for the first synchronization.

Result Meaning
Succeeded — Initialized First copy into the schema
Succeeded — Synchronized Changes were applied
Succeeded — No changes The GeoPackage has not changed since last time
Failed See Details

How change detection works

GeoJibe checks whether the selected GeoPackage on QFieldCloud changed.

  • Changed → download and update PostGIS
  • Unchanged → Succeeded — No changes, no data update

You do not need to understand the comparison details. The Runs list is enough.

Reset and reinitialize

On the Job Runs page:

Reset synchronization state forgets GeoJibe's local sync files for this Job. It does not drop the PostGIS schema.

Reinitialize destination schema is stronger. You type the schema name to confirm. That replaces destination data in that schema. Use it when the schema should be rebuilt from the project.

Deleting a Job never drops the PostGIS schema.

Having trouble?

See also