[bug report] I uploaded this normal pic - but it is showed as an 360

Why is it showed as a 360 pic?

HUAWEI P20 PRO > CLT-L29

the original file/exif would help - something is messed up there I’d reckon, probably on Huawei’s camera software part

1 Like

It does look kinda cool! :sweat_smile:

Hi

I hope someone can see that the problem is.

ExifTool Version Number : 11.44
File Name : IMG_20190517_114230.jpg
Directory : .
File Size : 3.6 MB
File Modification Date/Time : 2019:05:21 20:12:26+02:00
File Access Date/Time : 2019:05:24 17:14:12+02:00
File Creation Date/Time : 2019:05:24 17:14:12+02:00
File Permissions : rw-rw-rw-
File Type : JPEG
File Type Extension : jpg
MIME Type : image/jpeg
Exif Byte Order : Big-endian (Motorola, MM)
Image Description : cof
Make : HUAWEI
Camera Model Name : CLT-L29
Orientation : Unknown (0)
X Resolution : 72
Y Resolution : 72
Resolution Unit : inches
Software : CLT-L29 9.0.0.270(C432E5R1P9)
Modify Date : 2019:05:17 11:42:30
Y Cb Cr Positioning : Centered
Document Name :
Exposure Time : 1/368
F Number : 1.8
Exposure Program : Program AE
ISO : 50
Exif Version : 0210
Date/Time Original : 2019:05:17 11:42:30
Create Date : 2019:05:17 11:42:30
Components Configuration : Y, Cb, Cr, -
Compressed Bits Per Pixel : 0.95
Shutter Speed Value : 1/999963365
Aperture Value : 1.8
Brightness Value : 0
Exposure Compensation : 0
Max Aperture Value : 1.8
Metering Mode : Multi-segment
Light Source : Daylight
Flash : Auto, Did not fire
Focal Length : 4.0 mm
Warning : [minor] Unrecognized MakerNotes
Maker Note Unknown Text : Auto
Sub Sec Time : 771435
Sub Sec Time Original : 771435
Sub Sec Time Digitized : 771435
Flashpix Version : 0100
Color Space : sRGB
Exif Image Width : 3648
Exif Image Height : 1824
Interoperability Index : R98 - DCF basic file (sRGB)
Interoperability Version : 0100
Sensing Method : One-chip color area
File Source : Digital Camera
Scene Type : Directly photographed
Custom Rendered : Custom
Exposure Mode : Auto
White Balance : Auto
Digital Zoom Ratio : 1
Focal Length In 35mm Format : 27 mm
Scene Capture Type : Standard
Gain Control : None
Contrast : Normal
Saturation : Normal
Sharpness : Normal
Subject Distance Range : Unknown
GPS Version ID : 2.2.0.0
GPS Latitude Ref : North
GPS Longitude Ref : East
GPS Altitude Ref : Above Sea Level
GPS Time Stamp : 09:42:30
GPS Processing Method : GPS
GPS Date Stamp : 2019:05:17
Device Setting Description : (Binary data 4 bytes, use -b option to extract)
Compression : JPEG (old-style)
Thumbnail Offset : 8852
Thumbnail Length : 33928
JFIF Version : 1.01
Image Width : 3648
Image Height : 1824
Encoding Process : Baseline DCT, Huffman coding
Bits Per Sample : 8
Color Components : 3
Y Cb Cr Sub Sampling : YCbCr4:2:0 (2 2)
Aperture : 1.8
GPS Altitude : 57.5 m Above Sea Level
GPS Date/Time : 2019:05:17 09:42:30Z
GPS Latitude : 55 deg 51’ 44.08" N
GPS Longitude : 8 deg 18’ 37.23" E
GPS Position : 55 deg 51’ 44.08" N, 8 deg 18’ 37.23" E
Image Size : 3648x1824
Megapixels : 6.7
Scale Factor To 35 mm Equivalent: 6.8
Shutter Speed : 1/368
Create Date : 2019:05:17 11:42:30.771435
Date/Time Original : 2019:05:17 11:42:30.771435
Modify Date : 2019:05:17 11:42:30.771435
Thumbnail Image : (Binary data 33928 bytes, use -b option to extract)
Circle Of Confusion : 0.004 mm
Field Of View : 67.4 deg
Focal Length : 4.0 mm (35 mm equivalent: 27.0 mm)
Hyperfocal Distance : 1.97 m
Light Value : 11.2

I know it is art :rofl:

weird, nothing seems terribly off in exif.
maybe someone more pro can help

I recently uploaded 360 images where I later descovered they missed the proper EXIF tags to be “official 360” images. But Mapillary did detect them as 360 images.

I can’t speak for Mapillary naturally, but I think this part of your EXIF/image data may clarify things:

The width is exactly double of the height. That is a tell tale property of a 360 image. And I think there are rarely “normal” images with that aspect ratio (2:1). So maybe Mapillary assumes a 360 image solely on that aspect ratio?

3 Likes

Yep, looks like this is indeed the reason.