QField Feature Requests

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.

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.

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 GIS specialist, I want to be able to create a new project in the QField app to streamline project management. (source: https://github.com/opengisch/QField/issues/5823 )

Basically, this idea explains exactly what I'm looking for, but is only works for Value Map: https://ideas.qfield.org/app-feature-requests/p/radiobutton-instead-of-dropdown-list I would like it to apply to Value Relations. We use hundreds of those and they provide a more robust way to create standardized forms, and this would help accelerate field work!

When using a custom sorting by a specific column by the "key column" in QGIS desktop this sorting is not transferred to QField. Value relation seems to always be sorted by default value. We would like it to follow the settings as added in QGIS Desktop.

The feature I believe is called COGO calculation. Essentially, this entails computing or calculating from a baseline using distance and offset parameters. The baseline itself can be established through previously collected points or temporary points. A Laser Rangefinder would be paired via Bluetooth, then, a baseline or reference point is defined using either internal or external GPS. Subsequently, points and polygons relative to this reference point can be measured. This offers the advantage of measuring points and objects beyond physical reach, and would be, in my opinion, a great feature to have in QField.