Wrong geopackage BLOB image rotation

[stuskier]

At 3.18.3, QGIS does not take EXIF orientation metadata into account when viewing images in a Geopackage table form view, as shown in the example below.

In comparison, Windows File Explorer, Paint, and IrfanView all correctly display the same image non-rotated, by default:

There is a very clumsy, time-consuming work-around, using external software such as IrfanView, to reset the EXIF Orientation, as discussed in this StackExchange post: https://gis.stackexchange.com/questions/401836/qgis-randomly-rotates-images-stored-as-geopackage-blob

However, QGIS would really rock if it acted - by default - just like Windows File Explorer, etc., and took the EXIF orientation metadata into account when viewing images.

[roya0045]

Unsure if this QGIS specific or provider specific.

[nicogodet]

Is this related to #38611 ?
In QGis in general, EXIF orientation is not supported ?

[stuskier]

Yes, perhaps so, in which case this might be a bug, rather than a feature request. Stu ‐‐‐‐‐‐‐ Original Message ‐‐‐‐‐‐‐

…

On Saturday, June 19th, 2021 at 2:06 PM, nicogodet ***@***.***> wrote: Is this related to [#38611](#38611) ? In QGis in general, EXIF orientation is not supported ? — You are receiving this because you are subscribed to this thread. Reply to this email directly, [view it on GitHub](#43789 (comment)), or [unsubscribe](https://github.com/notifications/unsubscribe-auth/ADBWODA3OPKVGXZDLFFWRYTTTUBG7ANCNFSM466HG4OQ).

[SrNetoChan]

If it never worked before, despite of what users would expect, it's a feature request, not a bug. See Andreas comment on the linked issue. If this is a big limitation for you, consider sponsoring the implementation or organize a crowdfunding to do it.

[nicogodet]

Tested with importPhoto processing tool (output to shapefile and gpkg), EXIF orientation is supported in table view.

How did you create your view form ?

[stuskier]

importPhoto requires that the source photo contains EXIF lat/long information, and will fail if the source photo lacks that EXIF geotagging. My project does not require EXIF geotagging. However, it does require that the photos be oriented correctly! Therefore, ImportPhoto is not a solution to my orientation problem. ‐‐‐‐‐‐‐ Original Message ‐‐‐‐‐‐‐

…

On Sunday, June 20th, 2021 at 1:24 AM, nicogodet ***@***.***> wrote: Tested with importPhoto tool (output to shapefile and gpkg), EXIF orientation is supported in table view. — You are receiving this because you are subscribed to this thread. Reply to this email directly, [view it on GitHub](#43789 (comment)), or [unsubscribe](https://github.com/notifications/unsubscribe-auth/ADBWODGLPW3HCFK3JTMPYHTTTWQVXANCNFSM466HG4OQ).

[nicogodet]

I used import photo tool juste to create the correct view form.

But how did you create your form ?
It looks like an html view.

When I display the image with "Attachment", orientation is OK.

[Houska1]

Could this be a Qt/QML autoTransform issue? I ran up against it a year or so back, and did my own workaround. It seemed Qt did not treat EXIF orientation consistently, there were some changes made around Qt version 5.5 or so, and when writing QML (in a form) one could get around it by including autoTransform: true. If so, it might be a reasonably easy fix.

BTW while borderline, I think this is a bug not a new feature request. If we display JPG images, georeferenced or not, we should display them correctly, which includes incorporating EXIF orientation tags which are quite commonplace.

[gioman]

When I display the image with "Attachment", orientation is OK.

@nicogodet the title seems to suggest that the photo preview comes from a binary/blob field, while normally previews are from a file system path, maybe this is an important difference?

[nicogodet]

@gioman After digging, yeah it seems to be an important difference.

You have to retrieve the binary data, convert to base64, then html img...
And based on @Houska1 script on GIS stack (here), not sure this is a QGIS issue.

A feature request would be to add ability to display the blob directly (like attachment does).

[gioman]

A feature request would be to add ability to display the blob directly

@nicogodet (I haven't tried) but this is not what @stuskier is describing?

[nicogodet]

@gioman Need te be confirmed but yes.

Currently it seems that the only way to display a picture stored as BLOB is to use a QML or HTML widget.
The feature would be to use attachement (which support EXIF orientation) to display the picture.
It's not exactly describe like this in first comment.

[gioman]

The feature would be to use attachement (which support EXIF orientation)

@nicogodet ok got it.

[github-actions]

The QGIS 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.

[stuskier]

I'm the person that originally submitted this issue. I received a github notice that it had gone stale because there was no action in the last 14 days. I'd really like to see this solved, but don't know how to get action on it. Suggestions?

[gioman]

I'm the person that originally submitted this issue. I received a github notice that it had gone stale because there was no action in the last 14 days. I'd really like to see this solved, but don't know how to get action on it. Suggestions?

@stuskier see #43789 (comment) attaching a sample project+sample dataset would also help.

[github-actions]

The QGIS 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]

While we hate to see this happen, this issue has been automatically closed because it has not had any activity in the last 42 days despite being marked as feedback. If this issue should be reconsidered, please follow the guidelines in the previous comment and reopen this issue.
Or, if you have any further questions, there are also further support channels that can help you.