When a panorama mission is processed in Site Scan for ArcGIS, the resulting 360° image (JPG) that is downloaded appears to be missing metadata, compared to panoramas generated directly from the drone (e.g. DJI Matrice 4E).
This issue may be related to the current behavior where the panorama opens in a new browser tab instead of being downloaded directly as a file
Hi @msmpokos
What metadata do you need and for what use?
Here is what is currently included:
File Modification Date/Time : 2026:03:18 09:25:26-07:00
File Access Date/Time : 2026:03:18 09:25:48-07:00
File Inode Change Date/Time : 2026:03:18 09:25:29-07:00
File Permissions : -rw-r--r--
File Type : JPEG
File Type Extension : jpg
MIME Type : image/jpeg
JFIF Version : 1.01
Exif Byte Order : Big-endian (Motorola, MM)
Make : DJI
Camera Model Name : FC6310S
X Resolution : 1
Y Resolution : 1
Resolution Unit : None
Software : Site Scan
Modify Date : 2022:08:25 12:52:55
Y Cb Cr Positioning : Centered
Exif Version : 0232
Date/Time Original : 2022:08:25 12:52:55
Create Date : 2022:08:25 12:52:55
Components Configuration : Y, Cb, Cr, -
User Comment : -.Projection: Equirectangular (2).FOV: 360 x 180
Flashpix Version : 0100
Color Space : Uncalibrated
Serial Number : 61e958bcb868f77f1517c30ca01778bf
GPS Version ID : 2.3.0.0
GPS Latitude Ref : North
GPS Longitude Ref : West
GPS Altitude Ref : Above Sea Level
XMP Toolkit : Image::ExifTool 12.39
Cropped Area Image Height Pixels: 8192
Cropped Area Image Width Pixels : 16384
Cropped Area Left Pixels : 0
Cropped Area Top Pixels : 0
Full Pano Height Pixels : 8192
Full Pano Width Pixels : 16384
Projection Type : equirectangular
Source Photos Count : 30
Stitching Software : Hugin
Use Panorama Viewer : True
Image Width : 16384
Image Height : 8192
Encoding Process : Baseline DCT, Huffman coding
Bits Per Sample : 8
Color Components : 3
Y Cb Cr Sub Sampling : YCbCr4:2:0 (2 2)
Image Size : 16384x8192
Megapixels : 134.2
GPS Altitude : 331.4 m Above Sea Level
GPS Latitude : 29 deg 44' 15.39" N
GPS Longitude : 98 deg 27' 6.62" W
GPS Position : 29 deg 44' 15.39" N, 98 deg 27' 6.62" W
Hello @NicoBonnafoux and thank you for your reply.
The issue is specifically related to missing camera orientation metadata required for Oriented Imagery in ArcGIS. While SiteScan panoramas include GPS and projection info, they do not contain a valid heading value.As a result, when these images are added to an Oriented Imagery dataset, the system reports "Camera Heading value is invalid for the selected image. All the oriented imagery viewer tools using CameraHeading value are disabled."
In contrast, DJI processed panoramas from the same mission work correctly because they include orientation metadata.
Copying some colleagues for awareness @dozer , @EmilyWindahl, @JarellPerez08.
@msmpokos , we'll look into this.
We also just added the ability to publish360º panos directly from Site Scan to ArcGIS Online, have you tried this?
Hello @NicoBonnafoux thank you and i am looking forward for your reply.
As for the ability to publish 360º panos directly from Site Scan to ArcGIS Online, we have tried ti but unfortunately would not work for our use case for several reasons:
1) We need a single oriented imagery dataset that contains all the panos, not separate datasets per flight.
2) This functionality is not yet available in ArcGIS Enterprise, which we use
3) In the generated oriented imagery, the footprints are incorrect:
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.