[GRASS-dev] [GRASS GIS] #232: raster and vector mismatch in monitors

GRASS GRASS developer
1

#232: raster and vector mismatch in monitors
------------------------------+---------------------------------------------
Reporter: hcho | Owner: grass-dev@lists.osgeo.org
     Type: defect | Status: new
Priority: major | Milestone: 7.0.0
Component: default | Version: svn-trunk
Keywords: display, monitor | Platform: Linux
      Cpu: x86-32 |
------------------------------+---------------------------------------------
I used r.to.vect to convert a raster map to vector and displayed both of
them on a monitor. When the monitor is in the default size, I can see
slight mismatch along the boundaries of the two maps. For example,

d.mon[[BR]]
g.region rast=tmp[[BR]]
d.erase[[BR]]
r.to.vect input=tmp output=tmp feature=area[[BR]]
d.rast tmp[[BR]]
d.vect tmp type=boundary

If I zoom in a lot or make the monitor larger, I don't see this effect. My
guess is that conversion between raster and vector was OK, but scaling
coordinates (R_scaled_raster or something?) before actually displaying
them might cause this problem. In effect, PNG maps exported from the
monitor looks so ugly.

I'm attaching two figures (small and large monitors).

Any idea?

--
Ticket URL: <http://trac.osgeo.org/grass/ticket/232&gt;
GRASS GIS <http://grass.osgeo.org>

2

#232: raster and vector mismatch in monitors
----------------------+-----------------------------------------------------
  Reporter: hcho | Owner: grass-dev@lists.osgeo.org
      Type: defect | Status: new
  Priority: major | Milestone: 7.0.0
Component: default | Version: svn-trunk
Resolution: | Keywords: display, monitor
  Platform: Linux | Cpu: x86-32
----------------------+-----------------------------------------------------
Comment (by hamish):

see also trac #72.

Hamish

--
Ticket URL: <https://trac.osgeo.org/grass/ticket/232#comment:1&gt;
GRASS GIS <http://grass.osgeo.org>

3

#232: raster and vector mismatch in monitors
-------------------------+--------------------------------------------------
  Reporter: hcho | Owner: grass-dev@…
      Type: defect | Status: closed
  Priority: major | Milestone: 7.0.0
Component: Default | Version: svn-trunk
Resolution: worksforme | Keywords: display, monitor
  Platform: Linux | Cpu: x86-32
-------------------------+--------------------------------------------------
Changes (by mlennert):

  * status: new => closed
  * resolution: => worksforme

Comment:

This is 5 years old and I cannot reproduce the problem with the wxgui, so
closing.

--
Ticket URL: <https://trac.osgeo.org/grass/ticket/232#comment:2&gt;
GRASS GIS <http://grass.osgeo.org>

4

#232: raster and vector mismatch in monitors
----------------------+-----------------------------------------------------
  Reporter: hcho | Owner: grass-dev@…
      Type: defect | Status: reopened
  Priority: major | Milestone: 7.0.0
Component: Default | Version: svn-trunk
Resolution: | Keywords: display, monitor
  Platform: Linux | Cpu: x86-32
----------------------+-----------------------------------------------------
Changes (by hamish):

  * status: closed => reopened
  * resolution: worksforme =>

Comment:

The bug still exists, at least in GRASS 6. Play with "xmag".

Also a similar issue is visible in symbols, but that's different, this one
is to do with d.vect.

Hamish

--
Ticket URL: <https://trac.osgeo.org/grass/ticket/232#comment:3&gt;
GRASS GIS <http://grass.osgeo.org>

5

#232: raster and vector mismatch in monitors
----------------------+-----------------------------------------------------
  Reporter: hcho | Owner: grass-dev@…
      Type: defect | Status: reopened
  Priority: major | Milestone: 6.4.4
Component: Default | Version: svn-releasebranch64
Resolution: | Keywords: display, monitor
  Platform: Linux | Cpu: x86-32
----------------------+-----------------------------------------------------
Changes (by mlennert):

  * version: svn-trunk => svn-releasebranch64
  * milestone: 7.0.0 => 6.4.4

Comment:

Replying to [comment:3 hamish]:
> The bug still exists, at least in GRASS 6. Play with "xmag".

Ok, I can see it in GRASS 6 release, but not in 7. Can you reproduce it in
7 ?

I'm changing the milestone and version of this bug to better reflect where
the issue is.

--
Ticket URL: <https://trac.osgeo.org/grass/ticket/232#comment:4&gt;
GRASS GIS <http://grass.osgeo.org>