opengisch
Step 7 in QFieldCloud offline editing diagram is misleading — QFieldSync does not synchronize directly with PostGIS
Hello,
In the QFieldCloud offline editing diagram (also used in presentations and documentation), step 7 currently states:
“The manager synchronizes the field data with the local PostGIS database using QFieldSync.”
I think this is misleading, because QFieldSync does not really offer direct synchronization to a PostGIS database.
What actually happens is:
-
QFieldSync downloads a GeoPackage containing the modified data from QFieldCloud.
-
The manager then has to manually import or synchronize these changes into PostGIS using QGIS tools like DB Manager, Processing algorithms, or custom scripts.
This distinction is important for teams implementing PostGIS-based workflows, to avoid false assumptions about automation capabilities.
Suggestion: Update step 7 to something more accurate like:
“The manager imports field data into the local PostGIS database using QGIS tools after downloading with QFieldSync.”
Thanks for the great work on QField
Hello, @CodiceCodax ,
Actually QFieldCloud supports projects with direct PostGIS connection.
See:
- https://docs.qfield.org/get-started/tutorials/advanced-setup-qfc/
- https://docs.qfield.org/how-to/pg-service/?h=
- https://docs.qfield.org/reference/qfieldcloud/secrets/
The key difference is that when you create a project in QFieldSync, you should use the second option:
And you are very right we can do better describing this is in the documentation.
Best, Ivan
Here’s a clarification, as I believe there has been a misunderstanding.
Yes, you're absolutely right that QFieldCloud supports direct PostGIS-connected projects. That’s great, and the documentation about using secrets and pg_service is very clear for that use case.
However, the issue I originally raised was not about online PostGIS access, but specifically about the offline workflow diagram, which shows this 7-step process:
https://docs.qfield.org/get-started/tutorials/advanced-setup-qfc/
In step 7, the diagram currently says:
“The manager synchronizes the field data with the local PostGIS database using QFieldSync.”
This is factually incorrect in the context of the offline workflow, because:
QFieldSync does not perform synchronization with PostGIS.
What it does is download a GeoPackage with field edits, and it’s the user who must manually push those changes into PostGIS, using DB Manager, Processing tools, or scripts.
So the feedback is not about whether QFieldCloud supports PostGIS (which it does!), but that the wording of step 7 in the diagram is misleading, and should be rephrased to avoid confusion for teams working offline.
Thanks again — just want to help make the documentation even more accurate!
Thanks you for the feedback, @CodiceCodax . I do see some misunderstanding, it might also be a bug that you are experiencing. Let me share what is the expectation.
“The manager synchronizes the field data with the local PostGIS database using QFieldSync.”
I do agree that the wording here is not super clear and should be imporved.
QFieldSync does not perform synchronization with PostGIS.
Yes, it is not QFieldSync, it is QFieldCloud that does the synchronization.
What it does is download a GeoPackage with field edits, and it’s the user who must manually push those changes into PostGIS, using DB Manager, Processing tools, or scripts.
This is only valid when you use the first option in QFieldSync (not the one from the screenshot in my previous message).
If you use the second option, then QFieldSync will only upload the .qgz file you have with the PostGIS connection information within the .qgz file. QFieldCloud will prepare a geopackage as a current snapshot from your PostGIS data. That geopackage is downloaded to QField and stores the data for offline editing. Once fieldwork is done, the data (deltas a.k.a. changes) are pushed to QFieldCloud. Then QFieldCloud will apply the changes to your PostGIS directly.
But there is no GeoPackage that is downloaded to QGIS via QFieldSync. If you open your project in QGIS, QGIS will pull the latest changes from the PostGIS, not a geopackage.
I am failing the discover the precise quote from you, if it is on an image, would you mind sending a link to the image?
Thanks you for the discussion, we are always open to improve the documentation and this particular part is definitly on our todo list in the upcoming weeks.
@CodiceCodax did you manage to try the proposed approach to have your PostGIS connection working as expected?
Glad to help you more with solving this issue.
Is this fixed? Ticket is still open. I just read the ticket, and I'm very confused. I have no idea now what 'offline editing' means for a pgsql layer, when doing cable export. I have learned enough to know "don't consider doing that" but that's probably not what's intended :-)
