[GRASS-dev] [GRASS GIS] #2654: r.thin crashes

[GRASS GIS]

#2654: r.thin crashes
----------------------+-----------------------------------------------------
 Reporter:  pairmand  |       Owner:  grass-dev@…              
     Type:  defect    |      Status:  new                      
 Priority:  normal    |   Milestone:  7.0.1                    
Component:  Raster    |     Version:  7.0.0                    
 Keywords:  r.thin    |    Platform:  MSWindows 7              
      Cpu:  x86-64    |  
----------------------+-----------------------------------------------------

Comment(by mlennert):

 Replying to [comment:3 pairmand]:
 > Thank you both for your help - I think it was actually multiple
 unrelated problems.
 > If I create a new location/mapset then g.region -p produces;
 >
 > {{{
 > g.region -p
 > projection: 99 (Transverse Mercator)
 > zone:       0
 > datum:      nzgd2k
 > ellipsoid:  grs80
 > north:      1
 > south:      0
 > west:       0
 > east:       1
 > nsres:      1
 > ewres:      1
 > rows:       1
 > cols:       1
 > cells:      1
 > (Mon Apr 20 11:50:24 2015) Command finished (0 sec)
 > }}}
 >
 > If I then import the Imagine file with extend region and repeat I get;
 >
 > {{{
 > r.in.gdal input=D:\temp_work\temukaSub_rasterEdges.img
 output=temukaSub_rasterEdges -e
 > WARNING: Datum <NZGD2000_NTv2> not recognised by GRASS and no parameters
 found
 > Raster map <temukaSub_rasterEdges> created.
 > Region for the current mapset updated
 > r.in.gdal complete.
 > (Mon Apr 20 11:53:07 2015) Command finished (0 sec)
 > (Mon Apr 20 11:53:20 2015)
 > g.region -p
 > projection: 99 (Transverse Mercator)
 > zone:       0
 > datum:      nzgd2k
 > ellipsoid:  grs80
 > north:      5117010
 > south:      0
 > west:       0
 > east:       1474010
 > nsres:      1
 > ewres:      1
 > rows:       5117010
 > cols:       1474010
 > cells:      7542523910100
 > (Mon Apr 20 11:53:20 2015) Command finished (0 sec)
 > }}}
 >
 >
 > That is, the map coordinates seem to be set to the north east corner but
 south, west, cols and rows are all incorrect. This appears to be a bug
 importing from the Imagine file using the gdal importer.

 The man page of r.in.gdal says about the '-e' flag: "Extend region extents
 based on new dataset". It does not say: Set the computational region to
 the extents of the imported map. So, the behaviour is conform to what it
 announces: your region is '''extended''' so that it also englobes the
 imported map.

 I think that r.thin should not crash if there are no null values, so this
 is a bug, but AFAICS there is no bug in r.in.gdal.

 Moritz

-- 
Ticket URL: <http://trac.osgeo.org/grass/ticket/2654#comment:4>
GRASS GIS <http://grass.osgeo.org>