Bug report #13151: Zonal statistics error: 0-d arrays can't be indexed - QGIS Application - QGIS Issue Tracking

Bug report #13151

Zonal statistics error: 0-d arrays can't be indexed

Added by Sergio Antonio over 9 years ago. Updated almost 8 years ago.

Status:	Closed
Priority:	Normal
Assignee:	-
Category:	Analysis library
Affected QGIS version:	2.10.0	Regression?:	No
Operating System:		Easy fix?:	No
Pull Request or Patch supplied:	No	Resolution:	not reproducable
Crashes QGIS or corrupts data:	No	Copied to github as #:	21214

Description

The error "0-d arrays can't be indexed" appeared in 2.8.1 version and persists in version 2.10.1.

ZonalStat.zip (435 KB) Sergio Antonio, 2015-08-01 03:28 PM

History

#1 Updated by Giovanni Manghi over 9 years ago

Category changed from Rasters to 115
Status changed from Open to Feedback
Target version deleted (~~Version 2.10~~)

Do you refer to the "zonal statistics" core plugin (c++) or its counterpart in the QGIS Processing toolbox?

I cannot replicate the issue with any of my data, can you please attach sample data that cause the issue? thanks.

#2 Updated by Sergio Antonio over 9 years ago

File ZonalStat.zip added
Target version set to Version 2.10

This zip file contains a clip of srtm_27_17.tif, two polygon grids (shp) created by vector grid tool (10000 x 10000 m and 1000 x 1000m), and the zonalstatistics.qgs.
All of them in EPSG 31983 - SIRGAS 2000 / UTM zone 23S.
I refer to the "zonal statistics" in the QGIS Processing toolbox.

#3 Updated by Giovanni Manghi over 9 years ago

no error here with your project and dataset. What version of Processing are you using (check the version in the plugin manager)?

#4 Updated by Sergio Antonio over 9 years ago

Category: Analysis
Author: Victor Olaya
Installed version: 2.10.1
Available version: 2.10.1 (in Official repository of add-ons QGIS)

Complementary information:
Running Catchment Area (Processing toolbox) occurs
ERROR 1: Can't load requested DLL: .....apps\\saga\\dll\\ gdal_MrSID.dll

but gdal_MrSID.dll is there.

#5 Updated by Giovanni Manghi over 9 years ago

Sergio Antonio wrote:

Category: Analysis
Author: Victor Olaya
Installed version: 2.10.1
Available version: 2.10.1 (in Official repository of add-ons QGIS)

still no error here. Tested on Linux and Windows. Seems likely a local issue, would you mind testing on a different system?

Complementary information:
Running Catchment Area (Processing toolbox) occurs
ERROR 1: Can't load requested DLL: .....apps\\saga\\dll\\ gdal_MrSID.dll

but gdal_MrSID.dll is there.

that is a message that is thrown by SAGA, not QGIS (is anyway not important apparently).

#6 Updated by Sergio Antonio over 9 years ago

The error happens in three machines (Windows) that had version 2.6 and were upgraded to 2.8 and, then, to 2.10.
Ok, it seems that really isn't a bug. I have discussed it with others users that, like you, didn't find the error.

#7 Updated by Giovanni Manghi over 9 years ago

Sergio Antonio wrote:

The error happens in three machines (Windows) that had version 2.6 and were upgraded to 2.8 and, then, to 2.10.
Ok, it seems that really isn't a bug. I have discussed it with others users that, like you, didn't find the error.

I would suggest try (backup and) delete the .qgis2 folder and try again.

#8 Updated by Sergio Antonio over 9 years ago

I deleted the .qgis2 folder, then I removed qgis 2.8 and I restarted the machine: sorry, the problem remains.
I verified that this machine had the versions: Brighton, Chugiak, Wien and Lisboa.

#9 Updated by Giovanni Manghi over 9 years ago

Sergio Antonio wrote:

I deleted the .qgis2 folder, then I removed qgis 2.8 and I restarted the machine: sorry, the problem remains.
I verified that this machine had the versions: Brighton, Chugiak, Wien and Lisboa.

so you have machines where this error always surface but you know that does not happen on other users machines (like mine)... what the machines where the bug occur have in common? XP?

#10 Updated by Sergio Antonio over 9 years ago

Yes, XP.
Just now I prepared, for testing, a fourth computer that was out of use (Windows XP) and the error occurred again.
Those machines do not accept others versions of Windows. I believe that they are gone finally...