Hi,
I was just wondering. I have small test project with a layer that is part of geopackage with many other layers somewhere else on my pc. This layer is set to Copy in Cable Packaging - Packaging actions.
When I click Package for QField I get the warning Layer … is outside the project’s home directory. QFieldSync may not transfer your layer. Please move the file to …
Clicking next just continues and packages the project. Upon inspection of the QField project folder the layer is transferred, together with all other layers of the geopackage. Actually, the entire geopackage has been copied to the QField project folder. The result being a 150Mb+ geopackage file where I would just need a single layer. And worse, the entire geopackage is now available within the QField project folder and thus being shared…
Is this intended and if so why? Or is this a bug?
Dear Jeroen,
It is a file based copy that happens. Hence, this is not a bug and indeed the whole Gpkg will be transferred.
In this case, I would recommend that you save this layer as a separate Gpkg and overwrite the Gpkg that is currently stored in the project.
Thank you. Is there a reason it is a file based copy? Could this functionality be adjusted to create a new geopackage with the layers added to it.
I was simply following the steps mentioned here: Get Started - QField Ecosystem Documentation and it doesn’t mention anywhere that the result will be a file copy, for each layer.
Interestingly, the steps mentioned here: Storage - QField Ecosystem Documentation show a different workflow, manually creating a geopackage. This workflow also ompletely bypasses the use of the QField Sync Plugin (it is not mentioned at all in this How-to).
I am creating training material so I start here, seeing what is in the Get Started and the How-to guides. That’s why I noticed the differences between the two. Once the training material is finished I will give feedback on the Get Started and How-to sections.