Projects are the main data containers on QFieldCloud. Users can create any number of projects. Projects must contain a single
.qgz QGIS file, and may in addition contain any combination of geospatial files -- GeoPackages, Shapefiles, TIFs -- or data files such as photos, PDFs etc. Files cannot be shared between projects.
QFieldCloud projects have a name and an owner. The owner of a project is a QFieldCloud user or an organization. No two projects can use the same pair
Projects can be marked as either public or private. Private projects are accessible only to users added to a project as project collaborators. Public projects are visible to, and can be downloaded by, any QFieldCloud user.
Creating a project¶
A project can be created in two different ways: either using the QFieldCloud web interface or using QFieldSync in QGIS.
Files are the skeleton on which QFieldCloud project works. To make a QFieldCloud project alive users need to upload at least a single QGIS project file in the
.qgz file formats. All geospatial files must be uploaded using the same relative paths as on one's computer. If external SVG or raster symbology is used, users must upload the corresponding files too.
QFieldCloud does not support projects stored in a GeoPackage (
.gpkg) files (but users can still use GeoPackage files to store datasets for their projects).
A typical file structure of a QGIS file might look something like this:
project ├── data │ ├── basemap.tif │ ├── bees.gpkg │ └── fields.gpkg ├── symbology │ ├── icon.svg │ └── line-pattern.png ├── DCIM │ ├── bees-20220404121212.jpg │ ├── bees-20220405040506.jpg │ └── fields-20220405040607.jpg └── project.qgs
QFieldCloud uses file versioning. This allows users to restore to a previous version of any modified file. Files and file versions can be found under the Files section of one's projects. Subscriptions plans allow a different number of versions per file. See the qfield.cloud pricing page for further details.
Deleting old file versions¶
To ensure that only relevant file versions are kept, and to reduce the amount of storage needed by accounts, users can delete obsolete file versions. One can manually delete file versions from the project's File section.
To delete file versions in QFieldCloud, follow these steps:
- Go to the "Files" section of your project.
- Locate the layer for which you want to delete versions.
- Click on the three dots next to the layer name.
- You will see a list of versions for that specific layer.
- Identify the version you want to delete and click on the red trash bin icon next to it.
- Confirm the deletion when prompted, if you want to delete all versions before a specific version, you can do it activating the option "Also delete
nversion(s) older than the selected version.".
- After deleting a pop up message will appear with the success and the list of versions will show just the versions that was not selected for deletion.
A project collaborator is QFieldCloud user invited to contribute to a project. A single project may have multiple collaborators. Collaborators with roles owner or admin can add more users as collaborators. Projects owned by an organization allow adding teams as collaborators. Read more about collaborator roles.
Changes made on vector layers and uploaded to QFieldCloud from a QField device will appear here. A change stores the difference between attributes or geometries before and after the upload.
Changes register which method was used for uploading; it can be one of:
create- a new feature has been created.
delete- an existing feature has been deleted.
patch- an existing feature has been modified.
Features that have been created and later deleted without being pushed to QFieldCloud do not appear in project changes.
Changes to online vector layers (PostGIS, WFS) that do not have "Offline editing" cloud layer action do not generate a change, but instead modify the original data source directly.
Changes to vector layers done in QGIS will not appear here.
Read more about project jobs.
Secrets are settings that are securely stored in encrypted way. Project jobs automatically have access to their secrets. Once added, a secret may be removed, but not edited.
There are two types of secrets:
- Environment variables - Environment variables will be available to QGIS while your project's jobs are running.
- pgservice connection - A PostgreSQL/PostGIS connection as defined in the
.pg_service.confconfiguration file. If you use multiple service definitions, you should add multiple secrets for each of them.
Project settings are available only to project owners and collaborators with "admin" roles. Settings should be handled carefully as users can modify sensitive project settings and perform unrecoverable actions.
- Change the project visibility to public.
- Change the project owner.
- Permanently delete a project.
Actions issued from a project' settings page can lead to data loss!