Hello,
I am trying to create various projects for QField using QFieldCloud. In these projects, I wanted to use WFS layers available via the Geoplateforme server (https://data.geopf.fr/wfs/ows?VERSION=2.0.0)—specifically the cadastral parcels layer (CADASTRALPARCELS.PARCELLAIRE_EXPRESS:parcelle) and environmental data such as biotope protection order boundaries (patrinat_apb:apb).
When using one of these layers, I have no trouble exporting the project to QFieldCloud, but when downloading the project to my mobile device, I get the error message: “The project owner’s subscription plan is insufficient.” I am using a free QFieldCloud account.
What is very strange is that I managed to get it working twice, but subsequently, whenever I try to modify the project, the error message reappears during synchronization. Does anyone have any other ideas for displaying these WFS layers, particularly the cadastral parcels one?
Thanks for any ideas or suggestions you can offer.
Fabien
NB: As I write this post, I am running a test by adding the WFS layer “CADASTRALPARCELS.PARCELLAIRE_EXPRESS:parcelle” to my project without changing anything (neither the layer name nor the symbology). Surprisingly, when synchronizing the project to the mobile device, the layer appears. I then make a simple change to the symbology (setting the polygon fill to transparent). I re-sync, and that’s when I get the same error message as before. I repeat the test by reloading the same layer into the project without modifying the symbology, but now it no longer works; I get the subscription-related error message again.
@Exebecce , is it possible that your WFS layer is set to offline editing (in the project properties dialog’s QField panel?)
Yes it was set to offline editing. My error.
But issue is still there. Because last time I work on it (when I posted my first message), I finished to succeed to download the project on my device.
After your comment, I set the WMS layer to “Directly acess data source” and uploaded the project. Back on my mobile device, I can’t download it, still the subscription plan error.
If I set the WMS layer back to offline editing, I still have the subscription plan issue.
hello @Exebecce , a wild guess since I haven’t tried it, but maybe you need to delete the old copy on your phone (assuming you don’t have any local changes that you still need to upload) and re-download the project with the correct layer configuration?
I’m guessing that maybe the wrong configuration may leave the layer stuck on that error, for example by trying to “download” an offline copy of the WMS layer; or maybe is traying to read it from the data.gpkg that’s generated when converting the project to a QField one.
You can delete a local copy from your mobile device by going to the Imported/QFieldCloud projects folder from the main menu, tapping on the 3-dots/kebab icon on the right of the folder name and choosing delete.
Hello,
Thank you for the answer.
It doesn’t seem to resolve the issue.
Here’s what I did to test:
- I created a new project with a single Geopackage layer containing a single polygon (the territory of a municipality)
- On my mobile phone (so the project didn’t exist), I loaded the project, I can see the polygon of the municipality
- In my project, I loaded the WFS layer indicated earlier
- In the project settings, I have indicated for this layer “Directly access data source” Back on my mobile,
- I tried to synchronize
- The error message “Project owner’s subscription plan is insufficient” is back and I can’t synchronize the project
OK I got an answer right there : Connection to PostgreSQL(PostGIS) DB through QField/QFieldCloud is possible with community plan?
I can’t use WFS layers with community plan.
It doesn’t explain why it worked a few times when testing 
Thanks for help
aa, I see! maybe it’s the same strategy as the drug dealers 
Maybe you’ve tried with a cable transfer instead of QFieldCloud? Or set the WMS as a basemap for example (in which case, maybe you see an offline copy of the online layer made at the time of creation of the mobile/packaged version for QField)? In other words, the limitation seems to apply only to QFieldCloud, not QField itself.
I believe this is a limitation for the official QFieldCloud instance, but I’m not sure. Maybe you can try with a Self-Hosted version of QFieldCloud.