I’ve been trying QField off and on as an exploratory thing for my organization and I’ve been having trouble nailing down the underlying problems behind some issues I’ve had. The test has been pretty rudimentary; just adding points and syncing, online and offline, with a WMS basemap.

Some stuff I’ve noted (these are all AFAIK, someone please correct me if I’m wrong, because I really want this to work):

• the iOS app requires you to use iTunes for file management unless you use QField Cloud, and it’s been a while since I’ve tried it but it’s kind of a manual process to sync rather than a push button solution within QGIS.

• I was able to set up a postgis layer with offline sync, but it created a gpkg copy of it that never seemed to write back to the original table. Direct access to the postgis layer worked well, but seemed to require an outward facing server (QField Cloud had a “secrets” tab for this, I think). I managed to get it working, but then our test server got pulled out from under us and I’ve not gotten our internal servers to connect over VPN to my phone.

It seems very close to being what we want, but just barely not making it, and with no clear idea of what’s failing and where.

Esri have few different options.

Field Maps is their general purpose app and Survey 123 is designed around field collection based on defined questionnaires.

I’ve not used Quick Capture, but I think it’s designed to be a lightweight field collection app.

Then I’m pretty sure you can create mobile apps on Experience Builder, if you want to make something a bit more tailored.

Needless to say, everything E$ri makes will cost you.

If you don’t have the infrastructure of an enterprise behind you, you may need to explore open source options, which I’m not familiar with. But you might be able to use ArcGIS Online to get everything you need at a smaller price than a full enterprise stack.

Qield is one good option, there is a new cloud for synching. Mergin has a similar cloud sync for field work. More general surveys can be created with kobotoolbox, based on odk and with some point/poly input (not a GIS, tabular).

My company uses pretty much exclusively Esri products (unfortunately) as we’re a partner organization. Here’s a basic run-down off the top of my head:

ArcGIS Field Maps

• Allows feature collection (Points, Lines, Polygons)
• Smart Forms allow for calculated values, i.e. calculating volume of a trench based on standard measurements
• Works with GPS recievers and collects GPS metadata (we recently began using the TDC-650 by Trimble, and get sub-inch accuracy in good conditions.)
• Includes markup layers by default
• Uploads directly to a feature service in ArcGIS Online
• Offline collection supported
• Editing and deleting supported My use cases: Inlet location, survey point location collection

ArcGIS QuickCapture

• Designed for rapid location data collection
• Typical usage is click button, take picture, upload, repeat
• Meant for point collection
• Less focus on accuracy and attributes My use cases: Quickly capturing potholes on roads while riding passenger in a vehicle, accuracy is typically 1-2’.

ArcGIS Survey123

• Incredibly powerful XLSS form based platform
• Extendable via JavaScript functions (
• Allows Point and Polygon collection
• Highly customizable
• Supports regex for input validation, conditional visibility, conditional required fields
• Desktop browser compatible My use cases: long-form inspections, desktop permit entry, data validation via JavaScript extensions.

I’m unfamiliar with open source alternatives - I’d prefer to use FOSS options but not up to me unfortunately.

I’m sure there’s more I’m missing though. First Lemmy post so apologies if formatting is awful.