Opened 13 years ago

Closed 13 years ago

#1542 closed defect (fixed)

NG gdalnumeric - wrong array order

Reported by: warmerdam Owned by: warmerdam
Priority: normal Milestone: 1.4.1
Component: PythonBindings Version: 1.4.0
Severity: normal Keywords:
Cc: hobu

Description

In the old generation bindings ReadBandAsArray?() returned a 2d array, and ReadDatasetAsArray?() returned a 2d array for 1 band files, and 3d for multi band files.

The NG bindings return 3d arrays from both in all circumstances.

I would like to correct the NG bindings to do the same thing as the old gen bindings.

The is an effort to maintain compatibility (as well as to provide the behavior I think is natural). But it will mean that folks who have written scripts to the NG bindings for 1.4.0 may find them breaking.

Change History (3)

comment:2 Changed 13 years ago by warmerdam

Status: newassigned

comment:3 Changed 13 years ago by warmerdam

This has been fixed in trunk (r11113).

This is also now tested for in gcore/numpy_rw.py

Still need to backport into 1.4 branch.

comment:4 Changed 13 years ago by warmerdam

Resolution: fixed
Status: assignedclosed

Merged fix into 1.4 branch (r11118).

Note: See TracTickets for help on using tickets.