#1161: g.region and r.info decimel issue when using grass python libs
-------------------------+--------------------------------------------------
Reporter: isaacullah | Owner: grass-...@…
Type: defect | Status: closed
Priority: normal | Milestone: 6.4.1
Component: Python | Version: 6.4.0
Resolution: invalid | Keywords:
Platform: All | Cpu: All
-------------------------+--------------------------------------------------
Comment(by cmbarton):
Thanks again. We can follow this to ensure the matches within Java. I just
wondered if this would be better accomplished within grass.region(). This
returns a dictionary (seen in our original post). I can't say exactly
where the lossy conversion is happening--going into the dictionary, coming
out of the dictionary, or at some other point. It's clear from your
explanation that the representation of these values can change at various
places. This all makes sense. But still most users would expect
grass.run_command('g.region', flags='gp') and grass.region() to give the
same results.
--
Ticket URL: <http://trac.osgeo.org/grass/ticket/1161#comment:7>
GRASS GIS <http://grass.osgeo.org>
_______________________________________________
grass-dev mailing list
grass-dev@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/grass-dev
