The wait is over; QFieldCloud (Beta) is here and will revolutionise the way you think about getting data from your field team to the office and let you focus on what's important, making sure you efficiently get the best field data possible.
What can you expect from QFieldCloud?
In short, open-source seamless synchronisation of your field data with your spatial infrastructure with change tracking, granular team permissions management and online-offline work capabilities in QField thanks to its native QFieldCloud integration.
For more details, you can directly check out https://qfield.cloud or look at our intro talk slides, our example workflow or even watch our CEO giving the complete talk online.
When will I get it?
As you probably know, when we announced QFieldCloud some time ago, we also opened a pre-registration for early adopters.
In the last months, we have been heavily testing and polishing QFieldCloud; the time has now come. On May 10th, we will open the first batch of public places on QFieldCloud Beta.
If you registered already, check your inbox regularly and be on the lookout for your invitation mail by our Mascotte Nyuki the bee. As soon as you are activated, you’ll be able to invite three friends or colleagues to use QFieldCloud immediately. No pre-registration involved for them, so choose wisely ;-)
As the interest for QFieldCloud is immense, the waiting list is pretty long, but do not despair; we hope to have worked the whole list by early June. After all pre-registered accounts are activated, we’ll open registrations to the public.
During the Beta phase, each user will get a free Team account with all functionalities enabled so you can test all QFieldCloud has to offer.
One month before the end of the Beta Phase, we’ll inform you to decide what plan you would like to subscribe to.
We mainly focused on two workflows during the development, one based on PostGIS and one on Geopackage. While both workflows are working, the Geopackage one is initially considered experimental since we focused our efforts on the enterprise-ready PostGIS-based workflow.
Throughout the beta, we will stabilise the Geopackage workflow so that by the time QFieldCloud goes into general availability, both workflows are rock-solid.
Furthermore, since QFieldCloud can internally use QGIS to manage synchronisation, we’ll be able to offer support for further providers like WFS-T, MSSQL, Oracle or Hana spatial as remote backends. As usual, you’ll be able to use those providers directly from QField for live connections, as you can do for web services like WMS, WFS and WMTS.