Support Website Contact Support Blog

Error e9022 / w0920 Invalid Images

I have a dataset from one mission consisting of 2 battery swaps. A large portion of the images (all jpegs-no different from any other mission I’ve flown with our P4P) came back with an error of “invalid images have been detected. Please remove them to process. Error e9022”. I click on learn more and there is nothing and I look on the pix webpage and there is nothing for this error. Any suggestions? There is also a separate error in the log that says 

Warning w9020: GDAL Error <4>

these errors come right after adding images, not during one of the processing steps…

Hi Kevin,

Could you please share the following so we can have a further look at the project:

▸ The project log file (text file): …\project_name\project_name.log
▸ The project file (.p4d): …\project_name.p4d

Hello,

 

I have today the same problem also…

 

warning w9020 GDAL error… the image not recognized as a supported file format

Hi Jacquelin,

Could you please share the files above (log and .p4d)?
What is the format of the images that were imported into the project and which camera was used?

i’ve been getting this same message for quite a few projects recently. We are using a Phantom 4 Pro and are flying the mission at 3-4 different heights. 

Any solutions to this?

1 Like

Hi,

 

Was this ever solved? Images below.

 

Need a solution quick.

Error from log file is as follows (confindential information replaced with “XXXXXXXXXXXXXX”):

quote

"

[2018.10.09 15:55:57][21%RAM][2%CPU][Warning]: Warning w9020: GDAL Warning <1> XXXXXXXXXXXXXX/FINAL Images Collected/test set/1217866617000000_300.tiff:JPEG compression support is not configured
[2018.10.09 15:55:57][21%RAM][2%CPU][Warning]: Warning w9020: GDAL Error <1> Cannot open TIFF file due to missing codec.
[2018.10.09 15:55:57][21%RAM][2%CPU][Warning]: Unable to open image XXXXXXXXXXXXXX/FINAL Images Collected/test set/1217866617000000_300.tiff
[2018.10.09 15:55:57][21%RAM][2%CPU][Error]: Error e9022: Invalid images have been detected. Please remove them to proceed.
[2018.10.09 15:56:24][21%RAM][9%CPU][UI]: Closing Project.

"

End Quote

Hi all,

The error you are getting is due to the compression of the images (and it was a bug). 

This was not an issue in the previous version but in 4.2.26/.27 some changes were made in the library that is used to read and write TIFF files. Our developers have fixed the issue in the latest version (4.3.27) was released on the 6th of September.
Here you can download the Pix4dmapper 4.3.27.

Cheers!

I downloaded and install the Pix4dmapper 4.3.27.  I am still receiving the error when trying to run a set of images.  I have even removed the files from the folder. The software just fines a new file it doesn’t like.  Can you please help? I have wasted the entire day on this one set of images.

[UI]: Open Project clicked.

[UI]: New Project clicked.

[Warning]: Warning w9020: GDAL Error \<1\> TIFFFetchDirectory:Y:/xxxxxx/Polygon 1 flight 1-20181005T145944Z-005/Polygon 1 flight 1/0004SET/002/IMG\_0160\_1.tif: Can not read TIFF directory count

[Warning]: Warning w9020: GDAL Error \<1\> TIFFReadDirectory:Failed to read directory at offset 2463522

[Warning]: Unable to open image Y:/xxxxxx/Polygon 1 flight 1-20181005T145944Z-005/Polygon 1 flight 1/0004SET/002/IMG\_0160\_1.tif

[Warning]: Warning w9020: GDAL Error \<1\> TIFFFetchDirectory:Y:/xxxxxx/Polygon 1 flight 2-20181005T152053Z-001/Polygon 1 flight 2/0000SET/000/IMG\_0159\_1.tif: Can not read TIFF directory count

[Warning]: Warning w9020: GDAL Error \<1\> TIFFReadDirectory:Failed to read directory at offset 2463516

[Warning]: Unable to open image Y:/xxxxxx/Polygon 1 flight 2-20181005T152053Z-001/Polygon 1 flight 2/0000SET/000/IMG\_0159\_1.tif

[Warning]: Warning w9020: GDAL Error \<1\> TIFFFetchDirectory:Y:/xxxxxx/Polygon 1 flight 2-20181005T152053Z-001/Polygon 1 flight 2/0000SET/001/IMG\_0169\_2.tif: Can not read TIFF directory count

[Warning]: Warning w9020: GDAL Error \<1\> TIFFReadDirectory:Failed to read directory at offset 2463524

[Warning]: Unable to open image Y:/xxxxxx/Polygon 1 flight 2-20181005T152053Z-001/Polygon 1 flight 2/0000SET/001/IMG\_0169\_2.tif

[Warning]: Warning w9020: GDAL Error \<1\> TIFFFetchDirectory:Y:/xxxxxx/Polygon 1 flight 2-20181005T152053Z-004/Polygon 1 flight 2/0000SET/002/IMG\_0085\_5.tif: Can not read TIFF directory count

[Warning]: Warning w9020: GDAL Error \<1\> TIFFReadDirectory:Failed to read directory at offset 2463522

[Warning]: Unable to open image Y:/xxxxxx/Polygon 1 flight 2-20181005T152053Z-004/Polygon 1 flight 2/0000SET/002/IMG\_0085\_5.tif

[Warning]: Warning w9020: GDAL Error \<1\> TIFFFetchDirectory:Y:/xxxxxx/Polygon 1 flight 2-20181005T152053Z-005/Polygon 1 flight 2/0000SET/002/IMG\_0013\_1.tif: Can not read TIFF directory count

[Warning]: Warning w9020: GDAL Error \<1\> TIFFReadDirectory:Failed to read directory at offset 2463522

[Warning]: Unable to open image Y:/xxxxxx/Polygon 1 flight 2-20181005T152053Z-005/Polygon 1 flight 2/0000SET/002/IMG\_0013\_1.tif

[Warning]: Warning w9020: GDAL Error \<1\> TIFFFetchDirectory:Y:/xxxxxx/Polygon 1 flight 2-20181005T152053Z-005/Polygon 1 flight 2/0000SET/004/IMG\_0006\_3.tif: Can not read TIFF directory count

[Warning]: Warning w9020: GDAL Error \<1\> TIFFReadDirectory:Failed to read directory at offset 2463522

[Warning]: Unable to open image Y:/xxxxxx/Polygon 1 flight 2-20181005T152053Z-005/Polygon 1 flight 2/0000SET/004/IMG\_0006\_3.tif

[Warning]: Warning w9020: GDAL Error \<1\> TIFFFetchDirectory:Y:/xxxxxx/Polygon 1 flight 3-20181005T142459Z-001/Polygon 1 flight 3/0000SET/001/IMG\_0064\_2.tif: Can not read TIFF directory count

[Warning]: Warning w9020: GDAL Error \<1\> TIFFReadDirectory:Failed to read directory at offset 2463526

[Warning]: Unable to open image Y:/xxxxxx/Polygon 1 flight 3-20181005T142459Z-001/Polygon 1 flight 3/0000SET/001/IMG\_0064\_2.tif

[Error]: Error e9022: Invalid images have been detected. Please remove them to proceed.
1 Like

Hi Billie,

Can you please submit a request to Support and send us a log file and screenshots of the popping up errors that you are receiving (if any)? We will investigate your issue separately and once we will have all the details and solutions to this particular example we will share it here.

Best!