QField Feature Requests

For a vector layer with multiple features, I would like to be able to show or hide on the map in QField all features within that layer. I know one can show or hide the whole layer on the map but that is not what I am looking for. The reason for this is that I have a vector layer with lots of features. Sometimes I want to see all the features but other times I want to see only one or a few of the features. In QGIS if I have a vector layer that is categorized, I can click on “hide all items” and then click on each feature I want to see. And if I want to see all the features, I can click on “show all items”. But currently this is does not seem possible in QField. See my post about this https://community.qfield.org/t/show-hide-all-features/1788 .

In the attribute form, when searching in a reference value, we have trouble with accented letters. In our case this is about french letters (especially é, è, ê), but this might be usefull in other languages too. Example with the linked pictures : Qfield doesn't recognize 'Mésange' if one writes 'mesange'. It doesn't seem much but it creates a lot of friction on the field.

We are working with naturalists on the field pointing species. For each observation, they have to select an name through thousands of species. The Reference value widget works perfectly well but it is still time consumming, especially when they often search for the same species. This could be faced with an hybrid of the unique value and the reference value widget. We thought about two options : A dropdown with unique value (P1) The unique values listed before anything is typed (P2) On both cases, once something is typed the widget behaves as the reference relation (P3). This can look like a strange workaround, but that would really save a lot of time for us on the field. The hybrid widget might not be the best solution, if something better is found we'd love it too!

When multiple users edit the same GeoPackage project from QGIS desktop via qfieldsync, there's currently no real protection against one user's sync overwriting another's changes. QField mobile already has a real conflict-resolution mechanism for this class of problem, but qfieldsync doesn't participate in it. Using postgres instance to deal with that problem could be a solution but in some cases it's more inconvinient than it seems to be. I needed a fix quickly for self hosted deployment and prototyped a stopgap: the desktop client remembers the file version it last synced, sends it on upload, and the server does something similar to a three-way merge of the GeoPackage instead of overwriting. It works, but I wonder if building a separate custom system instead of reusing your existing delta/conflict approach is a good final architecture. Is integrating the desktop client into your delta pipeline something you're planning? If you're open to it, I’d be happy to contribute and start off a discussion on how to approach it.

As a QField user and project creator, I want to be able to visualise certain distances either side of a line that I am digitizing. This would allow for more efficient survey planning using QField. For example, I am undertaking a bird survey where I want to approach every point within a given area to within 100 m. I have a line layer that I will use to plan my route. It has been programmed to display the line drawn as well as a 100 m buffer area around it (once committed). The issue with this is that the buffer cannot be viewed while digitizing — the user must save the feature first — which results in a lot of trial and error while trying to ensure the line drawn remains 100 m apart at all times. By adding a toggle and associated settings (buffer distance in meters) underneath the digititizing settings menu on the map canvas, the experience could be improved greatly. Ideally, the symbolisation of the buffer would be ~30-40% opaque and change colour for areas that overlap. Alternatively, implementing a 'barrier' (anti-snapping, where lines must remain apart by 2 x the buffer distance) option as a toggle would be even better.

As a QField user and project creator, I want finer control over the slider functionality in the range widget. In addition to a min, max, and steps value, I would like to be able to set: (1) The slider to act as a percentage of a given maximum, rather than using the steps value. This would allow an odd 'maximum' to be chosen without having to calculate an appropriate 'step' value manually; (2) The slider to operate with a kind of 'ratcheting' mechanism, where the values increase/decrease faster (with a larger 'steps' value) when the slider is moved faster, and much slower (single 'step' value) when moved slowly. Additional haptic feedback would be a welcome addition. This would enable finer control when the slider range is large, e.g. >100.

As a QField user and project creator, I want to be able to use selection tools like in QGIS to select multiple features in a certain area that may not be close to eachother. So, instead of tapping a single feature to open the attributes for that feature, or -- in the case of multiple nearby features -- opening a list of features to choose from, a 'selection' toggle can be turned on while in 'browse' mode, with an associated settings menu. So, when in 'browse' mode, a toggle appears directly below the burger menu (like the editing settings menu that appears when in 'digitise' mode) to turn selection tools on/off. Below this would be a selection tool settings menu that allows to change between selecting by rectangle (default), polygon, freehand and radius. Additional functionality that mirrors QGIS would also be welcome, e.g. Select Feature by Value, Invert Feature Selection, Deselect Features from All Layers, etc.

It would be great if a plugin for data acquisition could create the required layer in the project itself. That's what plugins like Snap would be like! Ready for immediate use without having to configure a suitable layer in QGIS.

Currently, you always have to select the required layer for a plug-in for data acquisition in advance. If plugins could work on any layers in the project using the layer ID or layer name, you could start data collection directly on layer A with button A or layer B with button B.

The form wizard is a really nice feature - for some forms. Especially when you just visit a form and do not want to change any data, the original tab behaviour is better and gives fast access to the desired information. It would be awesome to be able to activate the form wizard layer wise (currently: projectwise) and additionally the option to enable the wizard only when creating features, but show normal tabs when just viewing a feature.