QField Feature Requests

Unlike QGIS, the QField measure tool does not allow the choice of ellipsoidal or cartesian distances. Apparently, it calculates ellipsoidal distances. For projects that are based on a cartesian grid (e.g. UTM), this can be a source of error or confusion, or at least cause the user to have to do extra calculations involving a scale factor. There should be a setting to choose whether ellipsoidal or cartesian calculations are performed. Along with affecting the calculation of distances, the setting should also affect the calculations of the measure tool's other results as well (azimuth, perimeter, and area).

QField offers settings for "Enforce accuracy requirement" and, when averaging GNSS positions, for "Minimum number of positions collected". Additional settings are needed. Along with the linear accuracy thresholds, there also needs to be a position quality threshold for the value of the Quality field of the NMEA GGA messages from the GNSS device. The threshold would range from "Autonomous" or "Single Point" as the least restrictive, to DGNSS, to RTK Float, and to RTK Fix as the most restrictive. If the current quality value does not equal or exceed the position quality threshold, then collection of new measurements should be prevented, similarly to the effect of the existing "Enforce accuracy requirement" setting. This will ensure that measurements are not collected that do not meet the user's quality needs. If the position quality drops below the position quality threshold, the accuracy indicator badge attached to the location button should turn red, again, similarly to the effect of the existing "Enforce accuracy requirement setting. During averaging of GNSS positions, if the position quality drops below the position quality threshold, the low-quality positions should not be incorporated into the average, nor cause the displayed count of positions to increment, i.e. averaging should pause. When the position quality rises to equal or exceed the position quality threshold, the averaging and incrementing should resume. This too will ensure that measurements are not collected that do not meet the user's quality needs. If the position quality threshold is implemented, an additional enhancement that would be helpful is another GNSS averaging setting for a time limit (with a resolution of 1 second and a maximum of at least 10 minutes — but really, the setting should allow specifying arbitrary hours, minutes, and seconds). When either the number of averaged positions (with quality values that equal or exceed the position quality threshold) reaches the existing "Minimum number of positions collected" setting, or the time limit setting is reached, the averaging should terminate. If the termination is because of reaching the time limit, the user should be presented with the option to either accept or reject the averaged measurement. The number of positions that were incorporated into the average should be easily visible while that option is presented. Note: These recommended features are typical of other GNSS data collection software.

Hi all, Could it be possible to agrement QFIELD with filter like in Qgis via searchbar or a plugin? Like select all entities that response to filter argument ( and not use symbology fonctions like in this post https://georezo.net/forum/viewtopic.php?id=135403 ) Second point is, it would be very nice if users could export attributs layer as .ODS file directly from QFIELD Thanks in advance

As an iOS user, I would like an option to connect to external GPS receivers via Bluetooth the way you can with Android devices. There is currently only an option to connect via TCP or UDP.

I create a trigger (SQL) in the QGIS data GPKG and when packaging for QField, it generates the data.gpkg. This contains the layers that I have configured as offline editing and other log tables. However, it doesn't contain the trigger that I configured in QGIS. In my case, what the trigger does is: when you cut a geometry, it assigns 1 to the partition value of the original geom and to the rest it adds 1. I manually insert the trigger in data.gpkg and when I cut a geometry from the project, the changes in attributes modified by the trigger are not recorded in the log table (although they can be seen in QField) and are therefore lost when synchronizing the project. It would be nice if the export to QField supported the packaging of triggers.

For the monitoring of plant life we would like in QField to access a dropdown list of all species. This dropdown should be searchable and allow multiple selection (as possible in QGIS).

As a Qfield user, I want an option within the settings to toggle the coordinate curser following the location because... 3.6.0 Gondwana introduced (in Changelog under 'Improvements') "Greatly improved canvas lock to position, with constant panning insuring the location stays in the center of the screen." Now, when the canvas is moved so that the coordinate curser moves away from the current position, the message 'Follow location paused [Unlock]' appears below, requiring an additional screen tap to unlock. If you are using the volume up and down keys to enter data, this feature gets in the way. It would be better if this feature could be disabled within the settings, as there is already a button to toggle locking the coordinate curser to the position.

Actualy, only form view is available, for somme use cases tabular view could be nice. For exemple we would be interested in using Qfield for flow speed measures and need to see all data recorded at a time with conditionnal formating. It will give to operator immediate infromation on data quality and perform more measures if needed.

As Qfield user, I would like to suggest a new feature to improve the workflow when editing layers with value-relation fields. Currently, when filling out linked forms (e.g., parent-child relationships), we have to manually save and close each individual form one after the other. I really appreciate that the forms stay open during editing—this is useful—but it would be much more efficient to have an additional button that allows us to "Save and Close All" related forms in one click. Attached is an example of how it could look like. Thank you for your attention. Bye

The feature will allow users to manually type in new values in a field, the most recently entered value will be recalled on the next entry, and a lookup function will auto-fill suggestions of prior values that match characters as users type. Optionally, suggestions will be tied to values in another field. Steps which explain the enhancement User manually enters a value, which is stored with that record User creates a new record, the last value is already entered using the Recall last entered value function User taps in the field and the full text is highlighted to be efficiently overwritten As the user types, other previously entered values are suggested that match initial characters Optionally, value suggestions could be tied to value map entries in another field. Current and suggested behavior Currently in a manual text entry, the last value can be recalled, but previously entered values before the last record cannot be recalled as the user types. An example of workflow for suggested behavior: --In a value map field called "Material", 'andesite' is chosen from the dropdown --In a "Color" field, 'red' is manually typed, and after some other fields are entered the record is saved --In the next record, "Material" is 'chert' and in "Color," 'blue' is manually typed --In the next record, "Material" is 'andesite' again and "Color" auto-fills with 'red', but when the user taps in the color field, 'red' is highlighted and as the user begins typing bl... 'blue' is automatically suggested. Why would the enhancement be useful to most users For data entry in forms, where field technicians must enter a lot of data and a prefilled dropdown value list is not feasible due to the potential uniqueness of observations, the current workflow of manually retyping previously entered values is cumbersome. This suggestion will allow rapid data entry where unique values are needed, and it will also reduce replication error. QField Version: 3.5.5 Fangorn OS and Version: 3.40.6 Bratislava LTR