Documento
Projetos

Projetos

Projects is are are the main data container on QField andQFieldCloud . Users is create can create any number of project . Projects is contain m

Related articles

Análise VPN Super Unlimited Proxy; Download Grátis 2024 Proxy x VPN Xbox Cloud Gaming permitirá streaming de jogos que você comprou How to use a VPN QuTScloud

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

QFieldCloud projects have a name andan owner.
The owner of a project is a QFieldCloud user oran organization.
No two projects can use the same pair owner_name andproject_name.

Projects can be marked as either public orprivate.
Private projects are accessible only to users added to a project as project collaborators.
Public projects are visible to, andcan be downloaded by,any QFieldCloud user.

Criar um projeto

A project can be created in multiple ways:

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

Ficheiros

Files 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 orraster 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).

Uma estrutura de ficheiro típico de um ficheiro QGIS pode ser algo como isto:

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
├── project_attachments.zip
└── project.qml

The files in a QGIS project can be in one of the following groups by their purpose:

  • QGIS project file – a .qgs or.qgz project file.
  • QGIS sidecar files – the utility files to the QGIS project file,such as * _ attachments.zip orother sidecar files.
  • Data source files – all your vector andraster data,such as .gpkg,.tif,.mbtiles orother data source files.
  • Attachments – all your additional project data,such as .jpg,.pdf orother 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. Files andfile 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, andto 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 ” Files ” section of your project .Projetos
  2. Locate the layer for which you want to delete versions.Projetos
  3. click on the three dot next to the layer name .Projetos
  4. You will see a list of versions for that specific layer.Projetos
  5. Identify the version you want to delete andclick on the red trash bin icon next to it.Projetos
  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.”.Projetos
  7. After deleting a pop up message will appear with the success andthe list of versions will show just the versions that was not selected for deletion.Projetos

colaboradore

A project collaborator is QFieldCloud user invited to contribute to a project. A single project may have multiple collaborators. Collaborators with roles owner oradmin can add more users as collaborators. Projects owned by an organization allow adding teams as collaborators. Read more about collaborator roles.

alterações

Changes made on vector layers anduploaded to QFieldCloud from a QField device will appear here. A change stores the difference between attributes orgeometries before andafter the upload.

change register which method was used for upload ; it is be can be one of :

  • create – um novo elemento foi criado.
  • delete – um elemento existente foi eliminado.
  • patch – um elemento existente foi modificado.

Features that have been created andlater 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.

Nota

As alterações nas camadas vetoriais feitas no QGIS não aparecerão aqui.

Trabalhos

Leia mais sobre trabalhos is projeto do projeto .

secret

secret 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.

Existem dois tipos de secrets:

  • Environment variables – Environment variables will be available to QGIS while your project’s jobs are running.
  • pgservice connection – Uma ligação PostgreSQL / PostGIS is conforme conforme definido no ficheiro de configuração.pg_service.conf. Se usar várias definições de serviço,deverá adicionar vários secrets para cada um deles.

Configurações

Project settings are available only to project owners andcollaborators with “admin” roles. Settings should be handled carefully as users can modify sensitive project settings andperform unrecoverable actions.

  • Altere a visibilidade do projeto para público.
  • Altere o proprietário do projeto.
  • Excluir permanentemente um projeto.
  • etc

Warning

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