search

landam / grass-gis-git-migration-test

0 stars 0 forks source link

Vector map shifted in the map display #124

Open landam opened 5 years ago

landam commented 5 years ago

Reported by hcho on 14 Jun 2014 08:13 UTC 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)?

GRASS GIS version and provenance

svn-trunk

Migrated-From: https://trac.osgeo.org/grass/ticket/2336

landam commented 5 years ago

Attachment from hcho on 14 Jun 2014 08:14 UTC Vector lines don't match with cell boundaries. https://trac.osgeo.org/grass/attachment/ticket/2336/display_resolution.png

landam commented 5 years ago

Comment by hcho on 14 Jun 2014 08:23 UTC 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.

landam commented 5 years ago

Comment by hcho on 14 Jun 2014 08:36 UTC IMO, aligning vector lines and cell boundaries is still a valid point.

landam commented 5 years ago

Comment by neteler on 5 May 2016 14:08 UTC Milestone renamed

landam commented 5 years ago

Comment by neteler on 28 Dec 2016 15:04 UTC Ticket retargeted after milestone closed

landam commented 5 years ago

Modified by @landam on 5 May 2017 20:41 UTC

landam commented 5 years ago

Comment by @landam on 1 Sep 2017 20:28 UTC All enhancement tickets should be assigned to 7.4 milestone.

landam commented 5 years ago

Comment by neteler on 26 Jan 2018 11:40 UTC Ticket retargeted after milestone closed

landam commented 5 years ago

Modified by neteler on 12 Jun 2018 20:48 UTC

landam commented 5 years ago

Comment by @landam on 25 Sep 2018 16:51 UTC All enhancement tickets should be assigned to 7.6 milestone.

landam commented 5 years ago

Comment by @landam on 25 Jan 2019 21:08 UTC Ticket retargeted after milestone closed