Opened 11 years ago

Last modified 6 years ago

#2336 reopened enhancement

Vector map shifted in the map display

Reported by: hcho Owned by: grass-dev@…
Priority: normal Milestone: 7.6.2
Component: Display Version: svn-trunk
Keywords: d.rast.arrow Cc:
CPU: All Platform: All

Description

I don't have this problem until I draw flow arrows (Add raster flow arrows). When I click this menu, I'm asked to change the display resolution. If I click No, the resolution looks very high (I think it's 1 arrow per pixel) and everything is just green (the default arrow color). If I click Yes as recommended, raster cells in the display become perfectly aligned with the display borders and arrows are drawn as expected. So far, so good.

Now, if I add a polygon vector map representing cell boundaries, the lines don't perfectly match with the raster cells (shown in the attached screenshot). IMO, if I choose to align raster cells with the display borders, vector coordinates have to be transformed such that they are also snapped to the nearest cell vertices... Hmm... in some case, we may not want this.

OR can we not change the display resolution at all and display arrows correctly (one arrow per cell, not one arrow per pixel)?

Attachments (1)

display_resolution.png (123.2 KB ) - added by hcho 11 years ago.
Vector lines don't match with cell boundaries.

Download all attachments as: .zip

Change History (12)

by hcho, 11 years ago

Attachment: display_resolution.png added

Vector lines don't match with cell boundaries.

comment:1 by hcho, 11 years ago

Resolution: invalid
Status: newclosed

Ah! Now, I remember I added the -a flag just for this purpose. IMHO, it's better to use -a by default without constraining the display resolution to computational settings.

comment:2 by hcho, 11 years ago

Resolution: invalid
Status: closedreopened

IMO, aligning vector lines and cell boundaries is still a valid point.

comment:3 by neteler, 9 years ago

Milestone: 7.1.07.2.0

Milestone renamed

comment:4 by neteler, 8 years ago

Milestone: 7.2.07.2.1

Ticket retargeted after milestone closed

comment:5 by martinl, 8 years ago

Milestone: 7.2.17.2.2

comment:6 by martinl, 7 years ago

Milestone: 7.2.27.4.0

All enhancement tickets should be assigned to 7.4 milestone.

comment:7 by neteler, 7 years ago

Milestone: 7.4.07.4.1

Ticket retargeted after milestone closed

comment:8 by neteler, 7 years ago

Milestone: 7.4.17.4.2

comment:9 by martinl, 6 years ago

Milestone: 7.4.27.6.0

All enhancement tickets should be assigned to 7.6 milestone.

comment:10 by martinl, 6 years ago

Milestone: 7.6.07.6.1

Ticket retargeted after milestone closed

comment:11 by martinl, 6 years ago

Milestone: 7.6.17.6.2

Ticket retargeted after milestone closed

Note: See TracTickets for help on using tickets.