QField Feature Requests

As a long-time power user of QField who regularly trains water utility companies in its use, I find the app fantastic for field data collection. However, a critical feature is missing that would dramatically expand its adoption: the ability to type precise distances when drawing lines or polygons, mirroring QGIS Desktop’s "Advanced Digitizing" tool. Currently, water companies (and similar industries) rely on CAD or QGIS for designing water networks due to the need for millimeter-accurate digitization (e.g., pipe lengths, valve placements). While QField excels in mobility, the lack of distance input forces field crews to approximate measurements or resort to post-processing, reducing efficiency and accuracy. Proposed Solution: Integrate a "Distance Input" toggle during vertex placement when drawing lines/polygons. Allow users to manually enter: Distance (e.g., 5.25 m) and angle (e.g., 45°) for the next segment. Mimic the workflow of QGIS’s "Advanced Digitizing" panel for intuitive use. Impact: This addition would make QField indispensable for infrastructure management. Water utilities (currently hesitant to switch from CAD/QGIS Desktop) could: Digitize water/sewer networks with precision directly in the field. Eliminate post-processing errors and save significant time. Fully replace traditional tools with QField’s mobile-first approach. Closing: This feature would elevate QField from a "great" app to a game-changer for engineering-grade fieldwork. Industries managing linear networks (water, energy, telecom) would adopt it en masse, knowing they can trust on-site precision. Thank you for considering this transformative enhancement!

Add the possibility to deactivate the new pie menu in the settings, or add a button in the pie menu to edit features at the current location.

It would be really useful to display WMS layers legend obtained by the GetLegendGraphic request. The request returns an image with the legend graphic. Currently, no legend at all is displayed for WMS layers in QField. Example of a GetLegendGraphic request : https://geoegl.msp.gouv.qc.ca/ws/mffpecofor.fcgi?version=1.3.0&service=WMS&request=GetLegendGraphic&sld_version=1.1.0&layer=ori_pee_close_scale&format=image/png&STYLE=Couleur_avec_etiquette&

As a GIS specialist, I want to be able to create a new project in the QField app. (source: https://github.com/opengisch/QField/issues/5823 )

As a QField user, I want the ability to modify the sorting order of child features, so that I have the flexibility to switch from the default ascending order to descending order.

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.

We would like to store Photos from a QField project directly to a server using WebDAV. This works fine in QGIS, but we need the same functionality in Qfield. If there would be an option in future to do this in QField the same way, that would be a big help for us.

After intensive use of the printing options, for example, the Layouts folder is filled with PDF files that are no longer required. Due to security settings, not all mobile device project directories can be reached via the PC in order to clean up from there. It would be great to get an option to delete selected files from QField

While exploring ways to develop QField extensions, I noticed there are no direct functions exposed to QML for reading and writing file content. This makes certain common operations difficult to implement, such as: Reading file content to send via POST requests to APIs Storing local data when offline Implementing custom file-based caching mechanisms Processing local files directly in QML extensions I've looked through the codebase, particularly FileUtils, PlatformUtilities, and QFieldCloudConnection, but couldn't find any functions that directly expose file content reading/writing to QML. Proposed Solution Add three utility functions to FileUtils that would allow QML extensions to read, write, and get information about file content: https://gist.github.com/t-book/83488fcf3ff8a97d5cba70846d36e799 The getFileInfo function is useful as it provides a comprehensive way to get file metadata along with content in a single call, saving multiple file accesses when both content and metadata are needed. Additionally test cases to ensure the functions work correctly could be added: https://gist.github.com/t-book/5b7fdad8198c182c95a8e054b4e58a9b If I've missed existing implementations, I apologize and would appreciate being pointed to them. Further I've prepared these functions based on studying the codebase, but since I've had issues with my local build environment, they remain untested in a running QField instance - I would appreciate any feedback if there are better approaches within the QField architecture. Would a PR adding these utility functions be welcome? I believe they would significantly enhance the capabilities of QField extensions without adding much complexity to the codebase.

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