[GRASS-dev] [GRASS GIS] #3210: r.texture: bug when non continuous series of values

GRASS GIS trac at osgeo.org
Wed Nov 16 13:09:08 PST 2016


#3210: r.texture: bug when non continuous series of values
--------------------------+-------------------------
  Reporter:  mlennert     |      Owner:  grass-dev@…
      Type:  defect       |     Status:  closed
  Priority:  normal       |  Milestone:  7.2.0
 Component:  Raster       |    Version:  svn-trunk
Resolution:  fixed        |   Keywords:  r.texture
       CPU:  Unspecified  |   Platform:  Unspecified
--------------------------+-------------------------

Comment (by mmetz):

 Replying to [comment:11 mmetz]:
 > In [changeset:"69838" 69838]:
 > {{{
 > #!CommitTicketReference repository="" revision="69838"
 > r.texture: fix #3210, #2315, clean up code
 > }}}

 r.texture is a big mess. Five years ago I spent a lot of time fixing bugs
 and optimizing code, submitted with r47112, r47113, r47160, r47698,
 r47700. Apparently, many bugs were not resolved. I made a new attempt with
 https://trac.osgeo.org/grass/changeset/69838/grass/trunk/raster/r.texture.

 The cause of this mess is that the texture calculations have been taken
 from netpbm, that code in itself is full of bugs. For GRASS, a wrapper has
 been created in 2003, using the netpbm code for an analysis based on
 moving windows. IMHO, that made things worse, not better.

 According to the original authors of texture features (Haralick et al.),
 texture features can be used for image classification which is probably of
 wider interest. Therefore it might be worth to spend more effort on
 r.texture. The features are interesting, the code is still dubious.

--
Ticket URL: <https://trac.osgeo.org/grass/ticket/3210#comment:14>
GRASS GIS <https://grass.osgeo.org>



More information about the grass-dev mailing list