QField-docs Update pictures.en.md

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

Sep 24 '24 20:09 cemno

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.

Sep 25 '24 06:09 m-kuhn

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

Sep 30 '24 08:09 nirvn

@cemno thanks a lot for proposing this update, I have opened a pull request with a slightly adjusted version. https://github.com/opengisch/QField-docs/pull/504 What do you think about it?

Oct 06 '24 13:10 m-kuhn

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?

Oct 07 '24 11:10 cemno

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

Oct 07 '24 11:10 m-kuhn

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

Oct 10 '24 11:10 suricactus