[GRASS-dev] [GRASS GIS] #1424: Profile tool always casts to integers (incl. csv output)

GRASS GIS trac at osgeo.org
Mon Nov 23 04:31:51 PST 2015


#1424: Profile tool always casts to integers (incl. csv output)
---------------------+-------------------------------------
  Reporter:  hamish  |      Owner:  grass-dev@…
      Type:  defect  |     Status:  new
  Priority:  major   |  Milestone:  6.4.6
 Component:  wxGUI   |    Version:  svn-releasebranch64
Resolution:          |   Keywords:  profile tool, precision
       CPU:  All     |   Platform:  All
---------------------+-------------------------------------

Comment (by mlennert):

 Sorry, was a bit quick with my answer here: there was still the issue of
 getting the region in a resolution in meters to be able to use it in
 relation with the m.measure output.

 I see two options:

 * Declare the profiling tool unusable in lat-long and output an error
 message in that case.
 * Use g.region -m to get region resolution in meters. This would mean
 something like this on line 239:

 {{{
 region = grass.parse_command('g.region', flags='m')
 }}}

 I'm not so sure about the meaning of this -m flag in g.region as a
 constant resolution in degrees does not mean a constant resolution in
 meters. So this does not seem correct. But then again, in this case it is
 only used to get an idea of the step size for the profile, so this is not
 much of a problem.

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



More information about the grass-dev mailing list