QFieldCloud Feature Requests

We would find it useful to access storage used by an organization through API. Our self-hosted QFC allows one storage plan across all organizations so we need a way of monitoring storage used by each organization. It would also be useful to get individual project storage usage.

Problems: QFieldCloud is currently only accessible via ipv4 QFieldCloud tries to connect to PostgreSQL Databases only via ipv4 It would be great to have ipv6-enabled QFieldCloud to access ipv6-only PostgreSQL Server. Since many hosting and internet provides only supply a public ipv6 and no public ipv4 address.

Hi, are there any plans to publish images for QFieldCloud on Docker Hub? This would simplify deployment for users. Best regards Toni

Currently 'public' projects allow public viewing, but not public editing. In certain cases it would be really useful to edit a project from a team of mappers, without requiring any sort of login. The ideal workflow would be: One user downloads the project from QField cloud web via QRCode --> the user shares the QRCode with the mapping team / colleagues --> all users can load the project and edit geometries / attributes freely. If it's a truly public mapping campaign, such as mapping geometries for OpenStreetMap, I don't see this as an issue. The geoms will be validated prior to any upload to OpenStreetMap. See https://github.com/opengisch/QFieldCloud/issues/1222

Current functionality is to assign postgres logins to either organisations or individual users. It would be good to have an intermediate option of assigning the logon to a team.

There appears to be no means of easily removing and/or updating a shared dataset. Removing a shared dataset from the layers of the shared_datasets project does not result in its removal from cloud storage. In my case, basemaps are still likely to be updated with some frequency until my projects mature. Removing the old basemap and adding the new to the shared_datasets project does not result in update of cloud storage.

As an organization administrator, I would like to receive invoices by email and be able to pay in Swiss francs instead of euros.

Variable created to reflect the Team membership of a user in QField Cloud. This would likely need to be an array/csv attribute to store all teams they were part of? If this variable can be processed when a user logs in or is refreshed when reopening a project, more granular permissions through expression filtering could be applied to each layer. (e.g. if @cloud_team LIKE Asset_Team then make visible) At the moment if there are sensitive layers that some teams should not have access to, a separate project must be created with that layer removed. This then means: Additional administrative overhead in managing multiple similar projects Back-end data workflows are required to reconcile identical layers between different projects (and then sync back!)

A web map viewer capable of a minimal web map rendering of the uploaded .qgs/qgz files a fit that would require qgis-server ofcource something similar to QWC2 at https://qwc2.sourcepole.ch/?t=qwc_demo&l=edit_points%2Cedit_lines%2Cedit_polygons%2Cgeographic_lines%2Ccountry_names%2Cstates_provinces%2Ccountries&bl=mapnik&c=1740775%2C3057935&s=25000000 Repo at https://github.com/qgis/qwc2

It'd be useful to allow input of an email to send monthly invoices to (i.e. to accounts dept)