fpl / gdal-calculations Goto Github PK

What steps will reproduce the problem?
1. Say I have two input data sets:

 1  0  0  0
 0  1  1  0
 0  0  1  1
 0  0  0  1

11 12 15 15
11 11 12 95
15 15 15 15
11 15 95 15

I need a elements 11 and 95 in the second to be 1s in the first.

Typically I would have done something like

first[second == 11] = 1
first[second == 95] = 1

How would I do this within the gdal_calculations framework.

What version of the product are you using? On what operating system?
0.8, CentOS 6.4, Python 2.6.6

What steps will reproduce the problem?
1. gdalinfo shows the shape of my tif file as (647, 553)
2. But using gdal_calculations...

g = gdal_calculations.Dataset (in_data_filename)
print g[0].shape

will show a shape of (12, 647).

What is the expected output? What do you see instead?
Expect the shape of each band to be (647, 553).

Am I thinking about this wrong?

What version of the product are you using? On what operating system?
0.8 on CentOS 6.4, Python 2.6.6

Please provide any additional information below.

numpy.log(gdal_calculations.Dataset)

Output bands out of order when calculations run on multiband raster

Please load up to pypi

I'm having some trouble getting gdal_calculations to work reliably with some 
inputs that I think should be working properly. It works great on occasion, but 
usually I get an error like:

RuntimeError: Invalid dataset dimensions : 498 x -435

Using those same two inputs in the raster calculator in QGIS with the same 
formula, it produces the expected output.

Command I'm running:
/usr/bin/python -m gdal_calculations --A /tmp/rastercalc7LCtaE.tif --B 
/tmp/rastercalc9lrqbS.tif --extent MAXOF --reproject --outfile 
/tmp/rastercalcZRb4Dh.tif --calc='(A[0] * B[0])'

I've attached the two files. They overlap nicely in QGIS, where the calculation 
works as expected. If it matters, I'm using GDAL 1.11.0 with Python 2.7.3.

Can you provide any guidance? Am I using it incorrectly, or is this a bug of 
some kind?

I'd like to use this as part of an automated process (hence the weird 
filenames), so having it highly reliable would be important to me. If it helps, 
I could provide a limited amount of funding for the support/consulting on this 
issue. Probably not a ton, but enough for a nice dinner or two at least!

You can reach me directly at chris (at) strategiccode.com if needed.

Thank you!
Chris Michaelis

PS. More output, if useful:


Python 2.7.3 (default, Feb 27 2014, 20:00:17)
[GCC 4.6.3] on linux2
Type "help", "copyright", "credits" or "license" for more information.
>>> import osgeo.gdal
>>> print osgeo.gdal.__version__
1.11.0
>>>


/usr/bin/python -m gdal_calculations --A /tmp/rastercalc7LCtaE.tif --B 
/tmp/rastercalc9lrqbS.tif --extent MAXOF --reproject --outfile 
/tmp/rastercalcZRb4Dh.tif --calc='(A[0] * B[0])' 2>&1
Running calculation
0Traceback (most recent call last):
  File "/usr/lib/python2.7/runpy.py", line 162, in _run_module_as_main
    "__main__", fname, loader, pkg_name)
  File "/usr/lib/python2.7/runpy.py", line 72, in _run_code
    exec code in run_globals
  File "/usr/local/lib/python2.7/dist-packages/gdal_calculations/__main__.py", line 25, in <module>
    gdal_calculations.gdal_calculate.main()
  File "/usr/local/lib/python2.7/dist-packages/gdal_calculations/gdal_calculate.py", line 235, in main
    outfile = eval(args.calc)
  File "<string>", line 1, in <module>
  File "/usr/local/lib/python2.7/dist-packages/gdal_calculations/gdal_dataset.py", line 397, in __mul__
    return self.__operation__(operator.__mul__,other)
  File "/usr/local/lib/python2.7/dist-packages/gdal_calculations/gdal_dataset.py", line 338, in __operation__
    dataset1,dataset2=self.check_extent(other)
  File "/usr/local/lib/python2.7/dist-packages/gdal_calculations/gdal_dataset.py", line 80, in apply_environment
    dataset1,dataset2=self.__check_extent__(dataset1,dataset2)
  File "/usr/local/lib/python2.7/dist-packages/gdal_calculations/gdal_dataset.py", line 184, in __check_extent__
    if dataset1.extent!=ext: dataset1=ClippedDataset(dataset1,ext)
  File "/usr/local/lib/python2.7/dist-packages/gdal_calculations/gdal_dataset.py", line 713, in __init__
    self._dataset=gdal.Open(self._filename)
RuntimeError: Invalid dataset dimensions : 498 x -435

$ gdal_calculate --co "compress=lzw" --calc "Int16(x+0.5)" -x 
autotest/pyscripts/data/tgc_geo.tif --outfile tgc_geo.tif
0...10...20...30...40...50...60..Traceback (most recent call last):
  File "/usr/lib/python2.7/runpy.py", line 162, in _run_module_as_main
    "__main__", fname, loader, pkg_name)
  File "/usr/lib/python2.7/runpy.py", line 72, in _run_code
    exec code in run_globals
  File "/usr/local/lib/python2.7/dist-packages/gdal_calculations/__main__.py", line 25, in <module>
    gdal_calculations.gdal_calculate.main()
  File "/usr/local/lib/python2.7/dist-packages/gdal_calculations/gdal_calculate.py", line 218, in main
    outfile.save(args.outfile,args.outformat,args.creation_options)
  File "/usr/local/lib/python2.7/dist-packages/gdal_calculations/gdal_dataset.py", line 608, in __getattr__
    else:raise AttributeError("'Dataset' object has no attribute '%s'"%attr)
AttributeError: 'Dataset' object has no attribute 'save'

[deleted issue]