Opened 10 years ago

Closed 10 years ago

#3587 closed defect (fixed)

VrtRasterBand misses some Set and Get methods in Python bindings.

Reported by: fasano Owned by: hobu
Priority: normal Milestone: 1.8.0
Component: PythonBindings Version: unspecified
Severity: normal Keywords:
Cc: antonio

Description

Python bindings miss some VRTRasterBand Set and Get methods, present in C++ code, for example:

  • Set and Get of UniType
  • Set and Get of Offset
  • Set and Get of Scale

Change History (5)

comment:1 Changed 10 years ago by fasano

Summary: {{{VrtRasterBand}}} misses some {{{Set}}} and {{{Get}}} methods in Python bindings.VrtRasterBand misses some Set and Get methods in Python bindings.

comment:2 Changed 10 years ago by antonio

Cc: antonio added

comment:3 Changed 10 years ago by fasano

GetScale, GetOffset and even GetUnitType methods are already present in current Gdal stable version.

With [19412] SetScale and SetOffset methods are added.

When SetUnitType method will be added too, this ticket could be considered as solved.

comment:4 in reply to:  3 Changed 10 years ago by antonio

Replying to fasano:

GetScale, GetOffset and even GetUnitType methods are already present in current Gdal stable version.

With [19412] SetScale and SetOffset methods are added.

The [19412] changeset seems to be in current trunk and new features should be available with GDAL 1.8, isn't it?

Maybe it could be a good idea to backport them to 1.7 branch.

comment:5 Changed 10 years ago by Even Rouault

Milestone: 1.8.0
Resolution: fixed
Status: newclosed

r19815 /trunk/gdal/ (6 files in 5 dirs): Add C wrapper GDALSetRasterUnitType() for GDALRasterBand::SetUnitType?() and map it to SWIG (#3587)

Note: See TracTickets for help on using tickets.