QField Feature Requests

Add the option to draw freehand without a pen or mouse
As a QField user, it would be very convenient, especially for field work, to be able, when digitizing layers, to enable freehand drawing without specific devices (active pencils and mice), but also allowing capacitive pencils and the same finger. It is at the discretion of the rest of the community and the developers to determine the most convenient way. I personally think that the best thing would be to make the most of the existing infrastructure and merely modify the Freehand Draw button in the Digitization mode, adding a small gear to its icon, so that, when you hold it down, it presents your options: a box that unlocks the drawing by hand and a slider that allows you to choose the sensitivity for tracing lines and polygons when tracing across the screen (fewer milliseconds = more vertices, smoother strokes). The latter is somewhat similar to what was requested at https://ideas.qfield.org/app-feature-requests/p/add-option-to-smooth-lines-digitised-using-the-freehand-option . It may not be a bad option to express sensitivity in the selected measurement unit or in pixels either, but saying that is easier than doing it. Dragging one finger adds vertices due to sensitivity (except in points, leaving only the last position), dragging with two fingers moves the map, pinching with two fingers adjusts the zoom. As with the rest of the scans, it would not be confirmed until the green tick button was activated, the option to undo the last vertex and the rest of the options is maintained.
1
·
looking for funding
Linux ARM64 AppImage release
For more versatile usage of the QField during field works it would be greate, if we could use it on arm64 devices with GNU linux distros - as Raspberry Pi devices or ARM64 (aarch64) based laptops. An ARM64 AppImage is possible to create for linux - e. g. FreeCAD developers created AppImage for ARM64 ( https://www.freecad.org/downloads.php ). I started more times to build QField on my Raspberry Pi, but it always stopped on some Qt dependencies - nor VCPKG solution cant handle these dependences (I quess if it could be set to deal with this?). I'm not a programmer, but who is more experienced can go further. ############################################################## Some notes from my last attempt to build it on fresh rasbperry pi os trixie on raspberry pi 5 ############################################################## ## Build on the master branch after c9f5523 commit VCPKG informs that 'arm64-linux' is community triplet, which is not built in the curated registry and is thus less likely to succeed. sudo apt install cmake # You need to have cmake installed. ## Dependencies for configuration (cmake -S QField -B build) sudo apt install bison flex autoconf # without it failed on 17th package 'libpq' sudo apt install autoconf-archive libtool # without it failed on 23rd package 'gperf' After that it failed on 84th package 'qtbase' this solution helped: sudo apt install qt6-base-dev and by https://www.interelectronix.com/cross-compile-qt-610-raspios-trixie.html this 2 rows sudo apt-get install libboost-all-dev libudev-dev libinput-dev libts-dev libmtdev-dev libjpeg-dev libfontconfig1-dev libssl-dev libdbus-1-dev libglib2.0-dev libxkbcommon-dev libegl1-mesa-dev libgbm-dev libgles2-mesa-dev mesa-common-dev libasound2-dev libpulse-dev libgstreamer1.0-dev libgstreamer-plugins-base1.0-dev gstreamer1.0-alsa libvpx-dev libsrtp2-dev libsnappy-dev libnss3-dev "^libxcb.*" flex bison libxslt-dev ruby gperf libbz2-dev libcups2-dev libatkmm-1.6-dev libxi6 libxcomposite1 libfreetype6-dev libicu-dev libsqlite3-dev libxslt1-dev sudo apt-get install libavcodec-dev libavformat-dev libswscale-dev libx11-dev freetds-dev libsqlite3-dev libpq-dev libiodbc2-dev firebird-dev libxext-dev libxcb1 libxcb1-dev libx11-xcb1 libx11-xcb-dev libxcb-keysyms1 libxcb-keysyms1-dev libxcb-image0 libxcb-image0-dev libxcb-shm0 libxcb-shm0-dev libxcb-icccm4 libxcb-icccm4-dev libxcb-sync1 libxcb-sync-dev libxcb-render-util0 libxcb-render-util0-dev libxcb-xfixes0-dev libxrender-dev libxcb-shape0-dev libxcb-randr0-dev libxcb-glx0-dev libxi-dev libdrm-dev libxcb-xinerama0 libxcb-xinerama0-dev libatspi2.0-dev libxcursor-dev libxcomposite-dev libxdamage-dev libxss-dev libxtst-dev libpci-dev libcap-dev libxrandr-dev libaudio-dev libxkbcommon-x11-dev gdbserver but maybe only this is enough?: sudo apt-get install '^libxcb.*-dev'libx11-xcb-dev libglu1-mesa-dev libxrender-dev libxi-dev libxkbcommon-dev libxkbcommon-x11-dev libegl1-mesa-dev after that it failed on 86th package 'qtshadertools' - Reported erros are in the log files are: "Package 'xkbcommon-x11' not found" "The link interface of target "Qt6::QXcbEglIntegrationPlugin" contains: Qt6::XcbQpaPrivate but the target was not found", etc. - nothing of the next rows helped sudo apt install qt6 dev* sudo apt install libxcb*dev sudo apt install libghc-xcb-types-dev sudo apt install libxcb sudo apt install lib qt6* sudo apt install xkb sudo apt install qtcreator sudo apt install -qt6 sudo apt install qt6* sudo apt install libx11* After some googling it looks, that problems with finding xcb and xkb packages are not rare during qt compiling some of solutions needs editing cmake files, which I'm not experienced with.
0
Add Distance Input Tool for Precise Line/Polygon Creation (Similar to QGIS "Advanced Digitizing")
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!
10
·
in progress
Load More