Projets

Projects is are are the main data container on QField and QFieldCloud .
Users is create can create any number of project .
Projects is contain must contain a single.qgs/.qgz QGIS file is contain ,and may in addition contain any combination of geospatial file — geopackage ,Shapefiles ,TIFs — or data file such as photo ,PDFs etc .
file can not be share between project ,unless localize layer are used .

QFieldCloud projects is have have a name and an owner .
The owner is is of a project is a QFieldCloud user or an organization .
No two projects is use can use the same pairowner_name and project_name.

project can be mark as either public or private .
private projects is are are accessible only to user add to a project as project collaborator .
public projects is are are visible to ,and can be download by ,any QFieldCloud user .

create a project

A project can be create in multiple way :

• via QFieldCloud web interface;
• via QFieldSync in QGIS ;
• via QFieldCloud-SDK;

file

file are the skeleton on which QFieldCloud projects work.
To make a QFieldCloud project alive users need to upload at least a single QGIS project file in the .qgs or .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.

note

QFieldCloud is support does not support project store in a GeoPackage (.gpkg) files (but users can still use GeoPackage files to store datasets for their projects).

A typical file structure is look of a qgis file might look something like this :

project 
 ├ ─ ─ datum 
 │    ├ ─ ─ basemap.tif 
 │    ├ ─ ─ bees.gpkg 
 │    └ ─ ─ fields.gpkg 
 ├ ─ ─ symbology 
 │    ├ ─ ─ icon.svg 
 │    └ ─ ─ line-pattern.png 
 ├ ─ ─ DCIM 
 │    ├ ─ ─ bees-20220404121212.jpg 
 │    ├ ─ ─ bees-20220405040506.jpg 
 │    └ ─ ─ fields-20220405040607.jpg 
 ├ ─ ─ project.qgs 
 ├ ─ ─ project_attachments.zip 
 └ ─ ─ project.qml 

The files is be in a QGIS project can be in one of the follow group by their purpose :

• QGIS project file – a.qgs or .qgz project file.
• QGIS sidecar file – the utility file to the QGIS project file ,such as*_attachments.zip or other sidecar file .
• data source file – all your vector and raster datum ,such as.gpkg,.tif,.mbtiles or other data source files.
• attachment – all your additional project datum ,such as.jpg,.pdf or other files.
• QField plugins – all your QField plugins,usually .qml files.

File versions

QFieldCloud uses file versioning. This allows users to restore to a previous version of any modified file. file and file versions can be found under the file 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:

1. Go to the « file » section of your project.
2. Locate the layer for which you want to delete versions.
3. Click on the three dots next to the layer name.
4. You will see a list of versions for that specific layer.
5. Identify the version you want to delete and click on the red trash bin icon next to it.
6. 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 n version(s) older than the selected version. ».
7. 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.

Collaborators

A project collaborator is is is QFieldCloud user invite to contribute to a project . A single project is have may have multiple collaborator . Collaborators is add with role owner or admin can add more user as collaborator . Projects is allow own by an organization allow add team as collaborator . read more about collaborator role .

Changes

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.

change register which method was used for upload ; it is be 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.

note

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.

note

Changes is appear to vector layer done in QGIS will not appear here .

Jobs

read more about project job .

Secrets

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 variable – Environment variables is be will be available to QGIS while your project ‘s job are run .
• pgservice connection – A postgresql / postgis connection as define in the.pg_service.conf configuration file. If you use multiple service definitions,you should add multiple secrets for each of them.

setting

Project settings are available only to project owners and collaborators with « admin » roles. setting 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.
• etc

Warning

Actions issued from a project’ settings page can lead to data loss!