Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Qfield pictures going into Files folder #4800

Closed
connorjfns opened this issue Nov 23, 2023 · 9 comments
Closed

Qfield pictures going into Files folder #4800

connorjfns opened this issue Nov 23, 2023 · 9 comments

Comments

@connorjfns
Copy link

connorjfns commented Nov 23, 2023

Describe the issue

Qfield pictures now going into a folder called "Files". It's also losing the .jpg or .png extension.

Reproduction steps

Steps to reproduce the behavior:

  1. Take a picture on Qfield
  2. Connect mobile device to a laptop/PC and use File explorer to go to Tablet folder location. For us, it's This PC\TB85Plus\Internal shared storage\Android\data\ch.opengis.qfield\files\Imported Projects\
  3. Open project, then go to Files folder.

Expected behavior

The pictures used to go into the folder "DCIM" and they had the .jpg extension

Observed behavior

Not sure what to put as already mentioned

Screenshots and GIFs

Picture1
image (1)

[Please also attach additional files if a specific project/dataset is useful to investigate the problem.]

Desktop (please complete the following information)

  • OS: Windows 10/11

Mobile (please complete the following information)

  • Device: Unitech TB85
  • OS: Android 8
  • QField version: 3.0.7

Additional information

  • Problem started happening recently, didn't happen in an older version of QField: Yes
  • Problem can be reliably reproduced, doesn't happen randomly: Yes
  • Problem happens with all files and projects, not only some files or projects: Yes

Can I make a request that these pictures go back into the DCIM folder and retain the .jpg extension please?

@nirvn
Copy link
Member

nirvn commented Nov 25, 2023

@connorjfns , that sounds like a project setting issue to me, can you share the expression you've set for the photo attachment's path in the vector layer properties dialog, i.e. this:

image

@nirvn nirvn added the feedback label Nov 25, 2023
@connorjfns
Copy link
Author

@nirvn So, by default I use the expression below (the part after DCIM varies based on layer)
'DCIM/chambers-and-notes_' || format_date(now(),'yyyyMMddhhmmsszzz') || '_{filename}' || '.jpg'

But sometimes the QGIS changes the formula above to the default one (PSB). This happenes when the project is opened with the older QGIS version and sometimes it happens like randomly for reason I can`t detect.
'files/objects_' || format_date(now(),'yyyyMMddhhmmsszzz') || '_{filename}'

My observation though is that this seems to change with the qfield version without any changes on our end to the project settings. For example, if we did a project in Qfield version 2.6.2, the pictures would go into DCIM. If we worked on the same project from any version from 2.8.0 onwards, the pictures would go into Files.

@m-kuhn
Copy link
Member

m-kuhn commented Dec 3, 2023

Which QGIS versions are you using?
Can you share an affected file with a description of what's affected?

@connorjfns
Copy link
Author

connorjfns commented Dec 4, 2023

Hi, we are using QGIS version 3.22.11
On our Tablets, we are using latest version of Qfield 3.0.7

I have uploaded 2 files. The folder named "Correct-work" is when we worked on a project using qfield version 2.6.2. the other folder named "Faulty-work" is the same project, but on qfield version 3.0.7

In the correct work folder, the pictures are stored in the folder DCIM with the .jpg extension. In the faulty folder, the pictures are stored in the Files folder with no extension.

Correct-work.zip
Faulty-work.zip

@gioman
Copy link

gioman commented Dec 12, 2023

Seen also here on several different devices.

Copy link
Contributor

The QField project highly values your report and would love to see it addressed. However, this issue has been left in feedback mode for the last 14 days and is being automatically marked as "stale". If you would like to continue with this issue, please provide any missing information or answer any open questions. If you could resolve the issue yourself meanwhile, please leave a note for future readers with the same problem and close the issue.
In case you should have any uncertainty, please leave a comment and we will be happy to help you proceed with this issue.
If there is no further activity on this issue, it will be closed in a week.

@github-actions github-actions bot added the stale label Dec 27, 2023
@github-actions github-actions bot closed this as not planned Won't fix, can't repro, duplicate, stale Jan 3, 2024
@m-kuhn m-kuhn removed the feedback label Jan 3, 2024
@m-kuhn m-kuhn reopened this Jan 3, 2024
@nirvn
Copy link
Member

nirvn commented Jan 3, 2024

@connorjfns , looking at the faulty-work.zip project, I can see one configuration issue. You should set your attachment viewer type to image, that provides the hint for QField to through images in DCIM by default:

image

In your case, you'll also need to tweaked the preexisting attachment expressions here:

image

@github-actions github-actions bot removed the stale label Jan 3, 2024
@nirvn nirvn added the feedback label Aug 11, 2024
@nirvn
Copy link
Member

nirvn commented Aug 11, 2024

@connorjfns , is this still an issue?

Copy link
Contributor

The QField project highly values your report and would love to see it addressed. However, this issue has been left in feedback mode for the last 14 days and is being automatically marked as "stale". If you would like to continue with this issue, please provide any missing information or answer any open questions. If you could resolve the issue yourself meanwhile, please leave a note for future readers with the same problem and close the issue.
In case you should have any uncertainty, please leave a comment and we will be happy to help you proceed with this issue.
If there is no further activity on this issue, it will be closed in a week.

@github-actions github-actions bot added the stale label Aug 26, 2024
@github-actions github-actions bot closed this as not planned Won't fix, can't repro, duplicate, stale Sep 2, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

4 participants