QField Feature Requests

Is it possible to add audible alarms for Geofencing breaches? Currently just has a visual indicator some alarms would be nice for noisy machinery.

As a field worker without GIS knowledge, I want configurable one-tap buttons in QField that instantly record a feature at my current position with all attributes prefilled: no forms, no GIS knowledge needed, just one tap. Example: tap "Maple" → new tree object created at current GPS position, all attributes prefilled. Done. The userfriendly buttons are configured in QGIS per feature type and deployed via QFieldCloud, making it fast for experts and accessible for everyone. (Visual created with AI for showcase purposes)

As a developer, I want to maximise the space available to design and customise forms. When using smaller screens and larger font sizes, the intended design can be altered, with detrimental UX. For example, the 'pin'/'calendar'/etc icons can occupy a large proportion of the width of the screen. It would be good to have the ability to scale these and adjust the padding between them. Perhaps even the ability to turn these buttons on and off per field within QGIS. Similarly, I would occasionally prefer an array of radio buttons to appear on the same row, rather than wrap onto the next row. This could be acheived if the height of the buttons could be scaled, but this is not possible. The following abilities would also be most welcome: adjust the padding between rows and columns and add gridlines between them; for checkboxes, show the label (or nothing if label is enabled) instead of 'True' or 'False' (the grey/green toggle switch is sufficient user feedback); per field, a tooltip popup when hovering over a field in a form

It would be very useful to have some basic annotation drawing tools for quickly annotate over map and share markups and notes to others. We currently need to make a screenshot and have to use another application to annotate before sharing to collaborators.

Using the iPad OS “Scribble” function would be very helpful for recording data (filling in attributes). A pencil (stylus) is used to automatically convert handwritten data input into normal text. https://developer.apple.com/fr/videos/play/wwdc2020/10106/

Currently, I can add and delete waypoints in Qfield using the volume buttons on the device. When I add survey points to my point layer, I would like to have the option to close the attribute form using the volume button. This way, I can record the point using the volume up button, check the data in the attribute form if necessary, and immediately confirm the recording and close the attribute form using the volume up button (and, if needed, delete the object again using the volume down button). The advantage is that I can quickly record survey points without having to use the touchscreen. In older versions of Qfield, I could also use the volume down button to jump back to the current location. That was also handy but was unfortunately removed.

Summary QField already includes a useful navigation tool that can guide a field worker to a selected feature. However, the navigation target cannot currently be controlled programmatically from expressions or project logic. For many field workflows, especially ecological surveys, the navigation target needs to be selected dynamically based on spatial context rather than manually choosing a feature. Providing a way to set the navigation target via expressions or a small API would greatly improve QField’s usefulness for guided survey workflows. Example Use Case I am developing a QField system for managing wildlife reserves (UK). We maintain ~160 bird boxes across several reserves. During a work party, volunteers need to: Select a reserve Select a work scope within that reserve Navigate to the nearest unprocessed bird box As each box is inspected and marked processed, the system should automatically guide the worker to the next nearest unprocessed box. Currently this can be implemented partially using expressions (distance, bearing, etc.), but the built-in QField navigation tool cannot be driven by these results. This results in awkward workflows where the worker must repeatedly select features manually. Desired Capability Expose a way for expressions or project logic to control the navigation target. Examples: Expression variable @navigation_target Expression function set_navigation_target(geometry) set_navigation_target(feature) clear_navigation_target() Or project-level setting Allow the navigation target to be defined by an expression such as: navigation_target = nearest_unprocessed_feature() Benefits This would enable QField projects to implement workflows like: ecological surveys (nearest observation target) infrastructure inspection (next asset to inspect) trail or fence inspections agricultural sampling grids forestry plot navigation The navigation UI already exists; exposing the target would simply allow projects to drive it dynamically. Current Workaround The current workaround is to implement custom navigation logic using expressions and symbology: compute nearest feature compute distance and bearing display this in the form render arrows or guidance lines This works but is much less intuitive than using the built-in navigation tool. Why this matters QField is already an excellent field data collection platform. Enabling dynamic navigation targets would allow it to function as a guided survey tool, which is a very common requirement in conservation, agriculture, and infrastructure inspection. Additional Context Our system already uses: QGIS + QField RTK GNSS positioning GeoPackage data store QFieldCloud synchronization Dynamic navigation would integrate naturally with these workflows. I would be happy to help test or prototype this functionality if needed.

Many Qfield projects use photos as field evidence. However, these photos could be very useful for other projects. The Panoramax open field photo sharing platform seems like the ideal place to share these photos. Especially since the Panoramax plugin is now available in Qgis: the photos can therefore be used directly. Several ideas: a Qfield plugin to allow sharing directly add a checkbox “share the photos of this project on Panoramax” when creating a Qfield project mount a Panoramax instance to more easily navigate through all the photos already accessible in open QFieldCloud projects/send future photos sent by contributors

This relates to the already-existing request titled "Ability to create new projects within QField app". As good as QField is, it often feels very restrictive compared to typical professional surveying data collector software. The notion of having to "go back to the office" in order to begin new work or to organize data feels very outdated. Being able to create new projects while in the field would be wonderful, but a large portion of the benefit might be achieved with a perhaps simpler enhancement: the ability to create new layers within an existing project. It is often possible to anticipate the need for a new project and thus be able to create it while in the office. However, it's also often the case that once in the field and performing the work, something is observed that had not been anticipated, but for which data ought to be collected, and that does not properly belong in any of the project's already-existing layers. There might be a logical distinction of these new data from the other categories of data that were planned to be collected. It could be very nice to be able to separately control the visibility of this new category of data, even just for ordinary reduction of clutter on the screen. It could also be that there was a problem with some of the data collection, in any layer, e.g. perhaps a GNSS receiver had been misconfigured, and the problem is discovered while still in the field. So far, I have not found a convenient way in QField to delete a large number of features within a layer (have I missed it?), so a work-around would be to turn off the visibility of the "bad" layer and to create a new layer. Back at the office, the "bad" layer could be deleted. Perhaps the ability to create new layers could be an intermediate step toward the ability to create new projects. It would be very beneficial in the meantime. Maybe an even simpler way to achieve much of the benefit would be to have the ability to duplicate an existing layer, asking the user 1) for a name for the duplicate and 2) whether or not the features in the original layer should be copied into the duplicate. I'm suggesting #2 as a safer alternative to having the ability to delete all the features in a layer (e.g. after duplication, with all the features of the original layer having been automatically copied into the duplicate), so as to avoid accidental deletion of needed data.

As a user I would find it very useful to be able to deactivate the pie menu that opens when clicking on my active location. This would allow easy selection of features underneath without having to do an extra click with the centre button that was added as a fix.