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

Update pictures.en.md #501

Closed
wants to merge 1 commit into from
Closed

Update pictures.en.md #501

wants to merge 1 commit into from

Conversation

cemno
Copy link

@cemno cemno commented Sep 24, 2024

The current explanation is somewhat confusing, as the native camera of most smartphones is capable of geotagging, while the actual problem lies in not providing this information to QField (For example iOS devices). Most non technical users would think there native camera app can geotag images, so it should qualify. This clarification should help understanding that the transfer of this information is the crucial part.

See #5532

The current explanation is somewhat confusing, as the native camera of most smartphones is capable of geotagging. The problem is if this information can not or will not be provided to qfield.
@m-kuhn
Copy link
Member

m-kuhn commented Sep 25, 2024

Thank you !
IIRC @nirvn was considering to switch the default cam to the internal one, as most systems nowadays block this access and the internal camera got quite powerful.

@nirvn
Copy link
Member

nirvn commented Sep 30, 2024

@m-kuhn , that is correct. As of QField 3.4, the internal QField camera is the default one.

@m-kuhn
Copy link
Member

m-kuhn commented Oct 6, 2024

@cemno thanks a lot for proposing this update, I have opened a pull request with a slightly adjusted version. #504
What do you think about it?

@cemno
Copy link
Author

cemno commented Oct 7, 2024

Thanks, a complete rewrite due to the changed default behaviour is indeed the best. I would suggest mentioning the on/off button for geotagging (with the camera ux update this would be a camera setting within the camera itself). This would make it clear what to look for when deciding whether or not to use this feature.
Should I make a suggestion at #504? Or where would be the right place?

@m-kuhn
Copy link
Member

m-kuhn commented Oct 7, 2024

Thanks for your feedback, such an addition would be great.
I have just merged #504, so you can suggest anything on top of the current master version

@suricactus
Copy link
Collaborator

I am closing this due to the conflict and agreement to open a follow-up PR.

@suricactus suricactus closed this Oct 10, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants