Opened 14 years ago

Last modified 6 years ago

#232 reopened defect

raster and vector mismatch in monitors

Reported by: hcho Owned by: grass-dev@…
Priority: major Milestone: 6.4.6
Component: Default Version: svn-releasebranch64
Keywords: display, monitor Cc:
CPU: x86-32 Platform: Linux

Description

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
g.region rast=tmp
d.erase
r.to.vect input=tmp output=tmp feature=area
d.rast tmp
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?

Attachments (2)

1.png (11.2 KB ) - added by hcho 14 years ago.
default monitor
2.png (22.7 KB ) - added by hcho 14 years ago.
maximized monitor

Download all attachments as: .zip

Change History (7)

by hcho, 14 years ago

Attachment: 1.png added

default monitor

by hcho, 14 years ago

Attachment: 2.png added

maximized monitor

comment:1 by hamish, 14 years ago

see also trac #72.

Hamish

comment:2 by mlennert, 9 years ago

Resolution: worksforme
Status: newclosed

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

comment:3 by hamish, 9 years ago

Resolution: worksforme
Status: closedreopened

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

in reply to:  3 comment:4 by mlennert, 9 years ago

Milestone: 7.0.06.4.4
Version: svn-trunksvn-releasebranch64

Replying to 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.

comment:5 by neteler, 6 years ago

Milestone: 6.4.46.4.6
Note: See TracTickets for help on using tickets.