Saltar a contenido


Projects are the main data containers on QFieldCloud. Users can create any number of projects. Projects must contain a single .qgs/.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.

Crear un proyecto

Se puede crear un proyecto de dos maneras diferentes: utilizando la interfaz web de QFieldCloud o utilizando QFieldSync en 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 .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.


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

La estructura típica de un archivo QGIS podría ser algo así:

├── 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

Versiones de archivo

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 pricing page for further details.

Borrar versiones de archivo antiguas

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. Vaya a la sección "Archivos" de su proyecto.Archivos del proyecto
  2. Localice la capa para la que quiere borrar versiones.Capa seleccionada
  3. Haga clic en los tres puntos próximos al nombre de la capa.Opción clicable
  4. Verá una lista de versiones para esa capa específica.Lista de versiones de archivos
  5. Identifique la versión que quiere borrar y haga clic en el icono de la papelera roja próximo a ella.Icono de papelera
  6. Confirme el borrado cuando se le pregunte. Si quiere borrar todas las versiones anteriores a una versión específica, puede hacerlo activando la opción "Borrar también n versiones más antiguas que la versión seleccionada.".Borrar versiones de archivos
  7. Después de borrar aparecerá un mensaje emergente con el éxito y la lista de versiones solo mostrará las versiones que no se seleccionaron para borrar.Lista de versiones después de borrar las dos versiones anteriores


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 - se ha creado una nueva función.
  • delete - se ha eliminado un objeto espacial existente.
  • patch - se ha modificado un objeto espacial existente.

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.


Los cambios en las capas vectoriales realizados en QGIS no aparecerán aquí.


Saber más de 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.

Hay dos tipos de secretos:

  • Environment variables - Environment variables will be available to QGIS while your project's jobs are running.
  • pgservice connection - Una conexión PostgreSQL/PostGIS como la definida en el archivo de configuración .pg_service.conf. Si utiliza varias definiciones de servicio, deberá añadir varios secretos para cada una de ellas.


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.

  • Cambiar la visibilidad del proyecto a público:
  • Cambiar el propietario del proyecto:
  • Permanentemente eliminar un proyecto:
  • etc


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