Mein System: QGIS 3.34 auf Windows 11 PC, Android Version 16 auf Samsung Galaxy A56 Smartphone.
Hallo zusammen,
In meinem QGIS-Projekt (Kartierung von Pflanzen und Pflanzenpilzen in einem Naturschutzgebiet) benutze ich Fotos, die ich mit QField erzeuge.
Relevant sind bei meinem Problem drei Punktlayer: Baum_Strauch, Blütenpflanzen, Pflanzenpilze.
Die Vorgabe ist, dass QField die Fotos für alle drei Layer in einunddemselben, von mir definierten Ordner \files\ speichert.
Beim Layer Baum_Strauch wird das auch gemäß meiner Parametrierung in QField realisiert, während die Fotos für die beiden anderen Layer fälschlicherweise in einem von mir nicht definierten Ordner \dcim\ abgespeichert werden.
Ich bitte dringend um Hilfe!
Das Projekt:
Leider kann ich als New User nur ein Foto anhängen. Ich bitte um Verzeihung.
Viele Grüße - Bernd
Nachfolgend (1 Screenshot pro Post) die Parametrierung des Layers Blütenpflanzen, bei dem QField die Fotos fälschlicherweide in \dcim\ abspeichert:
Please compare the Attributes Form setting for foto_1 (and the other foto fields) for all three layers.
Do you see any differences between the three layers? Especially in the section Widget Type?
Since Baum_Strauch is working as intended there might be a very small thing that is different?
I cannot see any difference betrween Baum_Strauch and Blütenpflanzen. Please have a look at the screenshots.
The problem ist, I cannot see any difference between the parameters of baum_strauch and blütenpflanzen. Please see the following screenshots.
I will repeat the problem: In my QGIS project (mapping of plants and plant-associated fungi in a nature reserve), I use photos that I generate using QField.
Three point layers are relevant to my problem: Baum_Strauch, Blütenpflanzen, and Pflanzenpilze.
The requirement is that QField saves the photos for all three layers into a single, specific folder—\files\—which I have defined.
For the Baum_Strauch layer, this works ex
actly as configured in my QField settings; however, the photos for the other two layers are incorrectly saved in a different folder—\dcim\—which I did not define.
Hello!
At least by seeing the screenshots you gave, you define the /files path in the Default path variable/parameter. If I’m not mistaken, this value is used as a sort of preffix onto which append the content of the whole field/attribute (foto_umfeld, for example). But QField by default uses the /DCIM folder in its camera. To change this, you have to specify it for each field.
First, set up the Attribute Form as you want it, although maybe it would be better to leave the Default path empty, so it points to the “root” of your project (assuming you use the relative path option). Once you are finished, hit OK to close the Layer Properties window.
Then open the Layer Properties window again and scroll down to the bottom of the left-most menu, to the QField option. There you should see your attachment field populated in the Attachment Settings section. As you can see, there QField has set the path as DCIM/etc/etc. I think this is where you should change to files/etc/etc.
Let me know if this worked.
I have corrected the path as you suggested. Additionally, I had to replace ‘.{extension}’ with ‘.jpg’ at the very end of the path. Everything is now working perfectly. Thank you very much!
Custom paths for attachments is still something I am figuring out. I think the documentation on this is lacking some important explanations.
I think the reason for you to explicitly use .jpg is because you use the foldername files.
files is one of the four default foldernames QField uses to store attachments, next to DCIM, audio and video, see Project Properties > QField
Probably all four of these use a specific extension which is hardcoded somewhere?
And for DCIM it probably is .jpg
I have not tested what the default extension is for the other three attachment folders, but probably .jpg is not associated with the files folder.
Or I am completely mistaken and the Attachment directories and the Naming expression in Layer properties work differently. Insight into this is what I find missing in the documentation.
