Details Ticket 2962


Comment | Reply | Take | Resolve


Serial Number 2962
Subject v.digit - zooming changes resolution
Area grass6
Queue grass
Requestors filter@correo.ugr.es,michael.barton@asu.edu,tutey@o2.pl
Owner none
Status open
Last User Contact Thu Jan 18 17:41:33 2007 (2 yr ago)
Current Priority 30
Final Priority 70
Due No date assigned
Last Action Thu Jan 18 17:41:33 2007 (2 yr ago)
Created Fri Dec 17 23:47:14 2004 (4 yr ago)

Transaction History Ticket 2962


Fri, Dec 17 2004 23:47:14    Request created by guest (as #2857)  
Subject: v.digit doesn't display properly

Platform: GNU/Linux/i386
grass obtained from: Mirror of Trento site
grass binary for platform: Compiled from Sources
GRASS Version: grass57_exp_2004_11_13

In v.digit when I display a raster of res=10 together with vector lines, which
should perfectly overlay it, then after a few zoom in/out these two layers start
to disynchronize to an extent of half the res. Also it happens that one or two
cells of the raster layer fail to display at all. Moreover, if any of this faults
happen and I close the v.digit, then any d.rast or d.vect still give the same
faulty display until changing region settings with g.region. If that's not clear
what I mean I can post 2 example screendumps, please let me know.

Maciek Sieczka
Mon, Dec 20 2004 05:30:35    Mail sent by hamish_nospam@yahoo.com (as #2857)  
Return-Path <hamish_nospam@yahoo.com>
Delivered-To grass-bugs@lists.intevation.de
Date Mon, 20 Dec 2004 17:30:25 +1300
From Hamish <hamish_nospam@yahoo.com>
To Request Tracker <grass-bugs@intevation.de>
Subject Re: [GRASS5] [bug #2857] (grass) v.digit doesn't display properly
Message-Id <20041220173025.5971f52d.hamish_nospam@yahoo.com>
In-Reply-To <20041217224714.B6CCA102BE2@lists.intevation.de>
References <20041217224714.B6CCA102BE2@lists.intevation.de>
X-Mailer Sylpheed version 1.0.0beta3 (GTK+ 1.2.10; i386-pc-linux-gnu)
X-Face M<EoB)"*Z~u!,vFhXmw}R_KbdBta*P_=T|rbBL'e1/CQ9;/1g\BU3&!=y8ria$2Uk!HT&BB 8i?|X_+7~1jsy}F~g$2va%3fV`*=L(*cem[@3\yg,G,@rg6/QMJ
Mime-Version 1.0
Content-Type text/plain; charset=US-ASCII
Content-Transfer-Encoding 7bit
X-Spam-Status No, hits=-4.0 tagged_above=-999.0 required=3.0 tests=BAYES_00, FORGED_YAHOO_RCVD
X-Spam-Level
> this bug's URL: http://intevation.de/rt/webrt?serial_num=2857
> ---------------------------------------------------------------------
> ----
> 
> Subject: v.digit doesn't display properly
> 
> Platform: GNU/Linux/i386
> grass obtained from: Mirror of Trento site
> grass binary for platform: Compiled from Sources
> GRASS Version: grass57_exp_2004_11_13
> 
> In v.digit when I display a raster of res=10 together with vector
> lines, which should perfectly overlay it, then after a few zoom in/out
> these two layers start to disynchronize to an extent of half the res.
> Also it happens that one or two cells of the raster layer fail to
> display at all. Moreover, if any of this faults happen and I close the
> v.digit, then any d.rast or d.vect still give the same faulty display
> until changing region settings with g.region. If that's not clear what
> I mean I can post 2 example screendumps, please let me know.



how about starting and ending region settings?

g.region -p



thanks,
Hamish


Mon, Dec 20 2004 23:10:16    Mail sent by werchowyna@pf.pl (as #2857)  
Return-Path <werchowyna@pf.pl>
Delivered-To grass-bugs@lists.intevation.de
Message-ID <001201c4e6e0$b7c8a7e0$44c61d3e@eustahiush>
From "Maciek Sieczka" <werchowyna@pf.pl>
To "Hamish via RT" <grass-bugs@intevation.de>
Cc "grass devel" <grass5@grass.itc.it>
References <20041220043036.10E8F102C06@lists.intevation.de>
Subject Re: [bug #2857] (grass) v.digit doesn't display properly
Date Mon, 20 Dec 2004 23:08:07 +0100
MIME-Version 1.0
Content-Type text/plain; format=flowed; charset="iso-8859-2"; reply-type=original
Content-Transfer-Encoding 7bit
X-Priority 3
X-MSMail-Priority Normal
X-Mailer Microsoft Outlook Express 6.00.2900.2180
X-MimeOLE Produced By Microsoft MimeOLE V6.00.2900.2180
X-Spam-Status No, hits=-4.9 tagged_above=-999.0 required=3.0 tests=BAYES_00
X-Spam-Level
Maciek Sieczka <werhowyna@pf.pl> wrote:

>> In v.digit when I display a raster of res=10 together with vector
>> lines, which should perfectly overlay it, then after a few zoom in/out
>> these two layers start to disynchronize to an extent of half the res.

Hamish via RT <grass-bugs@intevation.de> wrote:

> how about starting and ending region settings?

Right, now I see the error is simply because zooming in v.digit changes my 
resolution. But I doubt it should. d.zoom doesn't.

starting region, layers on their places:

projection: 0 (x,y)
zone:       0
north:      2860
south:      2210
west:       1890
east:       2660
nsres:      10
ewres:      10
rows:       65
cols:       77

ending region, layers shifted:

projection: 0 (x,y)
zone:       0
north:      2726.29002635
south:      2289.05994619
west:       2027.70065918
east:       2696.75877635
nsres:      9.93704728
ewres:      9.98594205
rows:       44
cols:       67

Maciek


Thu, Feb 3 2005 22:30:49    Request created by guest  
Subject: v.digit - zooming changes resolution

Platform: GNU/Linux/i386
grass obtained from: Trento Italy site
grass binary for platform: Compiled from Sources
GRASS Version: grass-6.0.cvs_src_snapshot_2005_01_22

Zooming in v.digit changes resolution of the current region to the extent of
half the initial region resolution. Massive diplacements - imagine digitizing
on a 30m Landsat with positioning error +-15m.

Maciek

P.S
I have reported this once http://intevation.de/rt/webrt?serial_num=2857 but long
and messy thus here I go again.
Tue, Mar 1 2005 16:57:27    Request created by guest (as #3047)  
Subject: v.digit resolution bug continued - G_realloc: out of memory

Platform: GNU/Linux/i386
grass obtained from: Mirror of Trento site
grass binary for platform: Compiled from Sources
GRASS Version: grass-6.0.cvs_src_snapshot_2005_02_12

When zoooming out quickly (something about 15 quick key presses on the "ZOOM
OUT" button) v.digit crashes and says:

ERROR: G_realloc: out of memory

The region afterwards is rubbish like:

GRASS 6.0.cvs:~ > g.region -p
projection: 99 (Transverse Mercator)
zone:       0
datum:      etrs89
ellipsoid:  grs80
north:      347303.98453767
south:      346244.32828767
west:       330067.31292828
east:       331464.12542828
nsres:      0.00000395
ewres:      0.0000052
rows:       268435456
cols:       268435456

The res before I entered v.digit was 14.25.

Maciek
Tue, Apr 19 2005 23:51:03    Request created by guest (as #3164)  
Subject: Zoom in v.digit

Platform: GNU/Linux/i386
grass obtained from: Mirror of Trento site
grass binary for platform: Downloaded precompiled Binaries
GRASS Version: 6.0.0

Using Zoom in the v.digit utility is pretty unreliable. 
After using the zoom in and zoom out option in v.digit, the program usually 
stops working. 
Wed, Apr 20 2005 02:28:48    Mail sent by hamish_nospam@yahoo.com (as #3164)  
Return-Path <hamish_nospam@yahoo.com>
Delivered-To grass-bugs@lists.intevation.de
Date Wed, 20 Apr 2005 12:28:35 +1200
From Hamish <hamish_nospam@yahoo.com>
To Request Tracker <grass-bugs@intevation.de>
Cc grass5@grass.itc.it
Subject Re: [GRASS5] [bug #3164] (grass) Zoom in v.digit
Message-Id <20050420122835.40e05b6c.hamish_nospam@yahoo.com>
In-Reply-To <20050419215103.5986F1006D2@lists.intevation.de>
References <20050419215103.5986F1006D2@lists.intevation.de>
X-Mailer Sylpheed version 1.0.4 (GTK+ 1.2.10; i386-pc-linux-gnu)
X-Face M<EoB)"*Z~u!,vFhXmw}R_KbdBta*P_=T|rbBL'e1/CQ9;/1g\BU3&!=y8ria$2Uk!HT&BB 8i?|X_+7~1jsy}F~g$2va%3fV`*=L(*cem[@3\yg,G,@rg6/QMJ
Mime-Version 1.0
Content-Type text/plain; charset=US-ASCII
Content-Transfer-Encoding 7bit
X-Spam-Status No, hits=-4.0 tagged_above=-999.0 required=3.0 tests=BAYES_00, FORGED_YAHOO_RCVD
X-Spam-Level
> this bug's URL: http://intevation.de/rt/webrt?serial_num=3164
> ---------------------------------------------------------------------
.. 
> Using Zoom in the v.digit utility is pretty unreliable. 

There is room for improvement, yes.
(starting with reset to original region on exit)


> After using the zoom in and zoom out option in v.digit, the program
> usually stops working. 

can you provide more details on what "stops working" means? How far
in/out did you zoom? What projection? when? error messages? lockup?



Hamish


Wed, Apr 20 2005 21:38:50    Mail sent by werchowyna@epf.pl (as #3164)  
Return-Path <werchowyna@epf.pl>
Delivered-To grass-bugs@lists.intevation.de
Message-ID <013d01c545e0$b15efb70$5bd21d3e@eustahiush>
From "Maciek Sieczka" <werchowyna@epf.pl>
To "Hamish" <hamish_nospam@yahoo.com>, "Request Tracker" <grass-bugs@intevation.de>
Cc <grass5@grass.itc.it>
References <20050419215103.5986F1006D2@lists.intevation.de> <20050420122835.40e05b6c.hamish_nospam@yahoo.com>
Subject Re: [GRASS5] [bug #3164] (grass) Zoom in v.digit
Date Wed, 20 Apr 2005 21:38:06 +0200
MIME-Version 1.0
Content-Type text/plain; format=flowed; charset="iso-8859-1"; reply-type=original
Content-Transfer-Encoding 7bit
X-Priority 3
X-MSMail-Priority Normal
X-Mailer Microsoft Outlook Express 6.00.2900.2180
X-MIMEOLE Produced By Microsoft MimeOLE V6.00.2900.2180
X-Antivirus avast! (VPS 0516-0, 2005-04-18), Outbound message
X-Antivirus-Status Clean
X-Spam-Status No, hits=-4.9 tagged_above=-999.0 required=3.0 tests=BAYES_00
X-Spam-Level
I have reported on a similar (I think) issue. 
http://intevation.de/rt/webrt?serial_num=3047&display=History

Also please see related 
http://intevation.de/rt/webrt?serial_num=2962&display=History

Hope I helped. Did I?

Maciek

----- Original Message ----- 
From: "Hamish" <hamish_nospam@yahoo.com>
To: "Request Tracker" <grass-bugs@intevation.de>
Cc: <grass5@grass.itc.it>
Sent: Wednesday, April 20, 2005 2:28 AM
Subject: Re: [GRASS5] [bug #3164] (grass) Zoom in v.digit


>> this bug's URL: http://intevation.de/rt/webrt?serial_num=3164
>> ---------------------------------------------------------------------
> ..
>> Using Zoom in the v.digit utility is pretty unreliable.
>
> There is room for improvement, yes.
> (starting with reset to original region on exit)
>
>
>> After using the zoom in and zoom out option in v.digit, the program
>> usually stops working.
>
> can you provide more details on what "stops working" means? How far
> in/out did you zoom? What projection? when? error messages? lockup?
>
>
>
> Hamish
>
> _______________________________________________
> grass5 mailing list
> grass5@grass.itc.it
> http://grass.itc.it/mailman/listinfo/grass5
> 


Sat, Jul 23 2005 14:34:21    Mail sent by msieczka (as #3047)  
Still present, changing area to 6.1.

Maciek
Sat, Jul 23 2005 14:34:29    Area changed to grass6.1 by msieczka (as #3047)  
Wed, Aug 31 2005 20:49:16    Area changed to grass6 by mneteler (as #3047)  
Fri, Sep 2 2005 18:21:49    Area changed to grass6 by msieczka (as #2857)  
Fri, Sep 2 2005 18:21:54    User changed to werchowyna@epf.pl by msieczka (as #2857)  
Fri, Sep 2 2005 18:33:57    User changed to werchowyna@epf.pl by msieczka  
Fri, Sep 2 2005 18:34:03    Area changed to grass6 by msieczka  
Fri, Sep 2 2005 18:36:32    Mail sent by msieczka  
This one is ugly, and still applies.

Maciek
Fri, Sep 2 2005 18:40:00    User changed to werchowyna@epf.pl by msieczka (as #3047)  
Mon, Nov 7 2005 06:53:48    Request created by guest (as #3806)  
Subject: stop v.digit from changing region settings

Platform: Mac OSX
grass binary for platform: Downloaded precompiled Binaries
GRASS Version: GRASS 6.1 cvs 22-10-2005

Following up on a recent discussion on the developer's list, I'd like to make
a wish to update v.digit so that it does NOT change the region settings. Zooming
and panning for convenience and accuracy in digitizing should not affect the
region that is set for display and analysis.

Michael
Fri, Mar 24 2006 21:25:40    Mail sent by msieczka (as #3806)  
Michael,

What should we do with this report? Would you still prefer v.digit not to
change region extents?

I'm sure it shouldn't change resolution, though (which it still does).

Maciek
Fri, Mar 24 2006 21:40:30    Request 2857 merged into 2962 by msieczka (as #2857)  
Sat, Mar 25 2006 00:58:38    Mail sent by michael.barton@asu.edu (as #3806)  
Return-Path <Michael.Barton@asu.edu>
Delivered-To grass-bugs@lists.intevation.de
Date Fri, 24 Mar 2006 16:57:59 -0700
From Michael Barton <michael.barton@asu.edu>
Subject Re: [bug #3806] (grass) stop v.digit from changing region settings
In-reply-to <20060324202541.035611006C3@lists.intevation.de>
To Paolo Cavallini via RT <grass-bugs@intevation.de>, Maciek Sieczka <werchowyna@epf.pl>
Message-id <C049D597.1F924%michael.barton@asu.edu>
MIME-version 1.0
Content-type text/plain; charset=US-ASCII
Content-transfer-encoding 7bit
User-Agent Microsoft-Entourage/11.2.3.060209
Thread-Topic [bug #3806] (grass) stop v.digit from changing region settings
Thread-Index AcZPnscTBcEj27uSEdqPKQAUUSYxwg==
X-Spam-Status No, hits=-4.9 tagged_above=-999.0 required=3.0 tests=BAYES_00
X-Spam-Level
With the new gis manager, v.digit no longer affects the region extents or
resolution of any particular map display--unless you intentionally cause it
to by pressing the zoom to current region button.

Michael
______________________________
Michael Barton, Professor of Anthropology
School of Human Evolution and Social Change
Arizona State University
Tempe, AZ  85287-2402
USA

voice: 480-965-6262; fax: 480-965-7671
www: http://www.public.asu.edu/~cmbarton


> From: Maciek Sieczka via RT <grass-bugs@intevation.de>
> Reply-To: Maciek Sieczka via RT <grass-bugs@intevation.de>
> Date: Fri, 24 Mar 2006 21:25:41 +0100 (CET)
> To: <michael.barton@asu.edu>
> Subject: [bug #3806] (grass) stop v.digit from changing region settings
> 
> Michael,
> 
> 
> 
> What should we do with this report? Would you still prefer v.digit not to
> 
> change region extents?
> 
> 
> 
> I'm sure it shouldn't change resolution, though (which it still does).
> 
> 
> 
> Maciek
> 
> 
> 
> -------------------------------------------- Managed by Request Tracker


Wed, Jun 21 2006 05:24:44    Request 3047 merged into 2962 by hbowman (as #3047)  
Wed, Jun 21 2006 05:26:20    Request 3164 merged into 2962 by hbowman (as #3164)  
Wed, Jun 21 2006 05:39:34    Mail sent by hamish_nospam@yahoo.com  
Return-Path <hamish_nospam@yahoo.com>
Delivered-To grass-bugs@lists.intevation.de
Date Wed, 21 Jun 2006 15:39:23 +1200
From Hamish <hamish_nospam@yahoo.com>
To Maciek Sieczka <werchowyna@epf.pl>
Cc grass-dev@grass.itc.it, grass-bugs@intevation.de
Subject [bug #2962] Re: v.digit and region
Message-Id <20060621153923.25c29059.hamish_nospam@yahoo.com>
In-Reply-To <20060620221844.c76932e8.werchowyna@epf.pl>
References <20060620221844.c76932e8.werchowyna@epf.pl>
X-Mailer Sylpheed version 1.0.4 (GTK+ 1.2.10; i386-pc-linux-gnu)
X-Face M<EoB)"*Z~u!,vFhXmw}R_KbdBta*P_=T|rbBL'e1/CQ9;/1g\BU3&!=y8ria$2Uk!HT&BB 8i?|X_+7~1jsy}F~g$2va%3fV`*=L(*cem[@3\yg,G,@rg6/QMJ
Mime-Version 1.0
Content-Type text/plain; charset=US-ASCII
Content-Transfer-Encoding 7bit
X-Spam-Status No, hits=-3.9 tagged_above=-999.0 required=3.0 tests=BAYES_00, FORGED_YAHOO_RCVD, HTML_MESSAGE
X-Spam-Level
Maciek wrote:

> Regarding your recent fix for v.digit:
> 
> > Log Message:
> > restore original region and clear screen on exit.
> 
> I think the real problem about v.digit is that it changes resolution
> during the digitizing session, not that it changes the region extent.
> The latter one, I even like - you can stop digitizing, do some data
> viewing in the given location and restart digitizing from the same
> place.

I agree this is a bad problem. The resolution gets changed because the
zoomed rows and columns are not adjusted to it -- the resolution is
changed to meet the new number of rows,columns so it ends up slightly
off.

"g.region -a" fixes it from the command line:
general/g.region/cmd/main.c

/* res= */
       if (!G_scan_resolution (value, &x, window.proj))
            die(parm.res);
       window.ns_res = x;
       window.ew_res = x;

       if (flag.res_set->answer) {
          window.north =  ceil(window.north/x) * x ;
          window.south = floor(window.south/x) * x ;
          window.east = ceil(window.east/x) * x ;
          window.west = floor(window.west/x) * x ;
       }
[...]
/* nsres= [same for ewres=, tbres=] */
  if (!G_scan_resolution (value, &x, window.proj))
           die(parm.nsres);
  window.ns_res = x;

  if (flag.res_set->answer) {
      window.north = 2 * x * ( (int)(window.north/2/x));
      window.south = 2 * x * ( (int)(window.south/2/x));
  }


I am not sure which is the best approach.

I've never been very happy with int = (int)(float + 0.5); for rounding
either -- i.e. it goes wrong if your float is negative?

guidance?


G_adjust_Cell_head3() is constrained by the fact that rows,cols must end
up as an integer but resolution may be float. If they don't agree, guess
who gets changed? [software generally follows the path of least work]

 
> Do you think it would be hard to prevent v.digit from changing the 
> resolution instead of just reverting original region at quit?

I think it should do both.


> For me, it is huge disadvantage that the background map resolution
> changes as I zoom in and out in v.digit (not mentioning that it might
> lead to crashes in some cases - somehow when the resolution goes too
> fine v.digit can't cope with that). And I'd revert to letting the
> region extents to change as I pan in v.digit, that's cool.
> 
> https://intevation.de/rt/webrt?serial_num=3047
> https://intevation.de/rt/webrt?serial_num=2962
>
> Maybe related:
> https://intevation.de/rt/webrt?serial_num=3164

these are both symptoms of the same bug; reports merged.


> What do you think?


I think that only g.region and d.zoom should be allowed to change the
mapset's region permanently. All other modules should leave the system
in the same state as they found it.

G_put_window()'s help comments support this:
 * <b>Warning.</b> Since this routine actually changes the database region, it
* should only be called by modules which the user knows will change the region.
* It is probably fair to say that under GRASS 3.0 only the <i>g.region</i>,
 * and <i>d.zoom</i> modules should call this routine.


Usually a module would use G_set_window() to change the region -- the
difference being that this only persists within the module and the WIND
file is not touched. Apparently (but I am not sure about this) this
doesn't survive the C->Tcl back and forth so v.digit has to use
G_put_window()? It runs both, I'm not sure what happens if you comment
out the G_put_window()s.


in lib/gis/ have a read though the header comments in:
 align_window.c  get_window.c  put_window.c  set_window.c  adj_cellhd.c



Hamish


Wed, Jun 21 2006 19:34:41    Mail sent by glynn@gclements.plus.com  
Return-Path <glynn@gclements.plus.com>
Delivered-To grass-bugs@lists.intevation.de
From Glynn Clements <glynn@gclements.plus.com>
MIME-Version 1.0
Content-Type text/plain; charset=us-ascii
Content-Transfer-Encoding 7bit
Message-ID <17561.33572.722503.363276@cerise.gclements.plus.com>
Date Wed, 21 Jun 2006 18:34:28 +0100
To Hamish <hamish_nospam@yahoo.com>
Cc Maciek Sieczka <werchowyna@epf.pl>, grass-bugs@intevation.de, grass-dev@grass.itc.it
Subject Re: [GRASS-dev] [bug #2962] Re: v.digit and region
In-Reply-To <20060621153923.25c29059.hamish_nospam@yahoo.com>
References <20060620221844.c76932e8.werchowyna@epf.pl> <20060621153923.25c29059.hamish_nospam@yahoo.com>
X-Mailer VM 7.07 under 21.4 (patch 15) "Security Through Obscurity" XEmacs Lucid
X-Spam-Status No, hits=-4.8 tagged_above=-999.0 required=3.0 tests=BAYES_00, HTML_MESSAGE
X-Spam-Level
Hamish wrote:

> I've never been very happy with int = (int)(float + 0.5); for rounding
> either -- i.e. it goes wrong if your float is negative?
> 
> guidance?

	int = (int) floor(float + 0.5);

> G_adjust_Cell_head3() is constrained by the fact that rows,cols must end
> up as an integer but resolution may be float. If they don't agree, guess
> who gets changed? [software generally follows the path of least work]
>  
> > Do you think it would be hard to prevent v.digit from changing the 
> > resolution instead of just reverting original region at quit?
> 
> I think it should do both.

A program which needs to run other modules with a different region
should use either GRASS_REGION or WIND_OVERRIDE.

> I think that only g.region and d.zoom should be allowed to change the
> mapset's region permanently. All other modules should leave the system
> in the same state as they found it.

Definitely.

> G_put_window()'s help comments support this:
>  * <b>Warning.</b> Since this routine actually changes the database region,
it
>  * should only be called by modules which the user knows will change the region.
>  * It is probably fair to say that under GRASS 3.0 only the <i>g.region</i>,
>  * and <i>d.zoom</i> modules should call this routine.
> 
> 
> Usually a module would use G_set_window() to change the region -- the
> difference being that this only persists within the module and the WIND
> file is not touched. Apparently (but I am not sure about this) this
> doesn't survive the C->Tcl back and forth so v.digit has to use
> G_put_window()? It runs both, I'm not sure what happens if you comment
> out the G_put_window()s.

If WIND_OVERRIDE is set, G_put_window() will modify the named region
specified by that variable rather than the WIND file.

For v.digit, using GRASS_REGION is probably more appropriate, although
slightly more work (AFAIK, you have to construct the string yourself).

-- 
Glynn Clements <glynn@gclements.plus.com>


Fri, Jul 7 2006 16:44:57    Mail sent by mneteler  
Hi,

is this still an issue?
Hamish was working on that.

Markus
Fri, Jul 7 2006 22:19:36    Mail sent by msieczka  
On Fri,  7 Jul 2006 16:44:57 +0200 (CEST)
Markus Neteler via RT <grass-bugs@intevation.de> wrote:

> is this still an issue?
> Hamish was working on that.

Still a problem. See:

$ g.region -p
projection: 0 (x,y)
zone:       0
north:      10000
south:      10
west:       50
east:       5000
nsres:      10
ewres:      10
rows:       999
cols:       495

$ v.digit map1&

  (a single "Zoom out" click)

$ g.region -p
projection: 0 (x,y)
zone:       0
north:      12068.929
south:      -2058.929
west:       -975.145
east:       6025.145
            ^^^
            those should be alligned to multiple 10

nsres:      9.99848408
ewres:      10.00041429
            ^^^
            those should be equal 10

rows:       1413
cols:       700

Maciek
Mon, Jul 10 2006 08:55:54    Mail sent by hamish_nospam@yahoo.com  
Return-Path <hamish_nospam@yahoo.com>
Delivered-To grass-bugs@lists.intevation.de
Date Mon, 10 Jul 2006 18:55:48 +1200
From Hamish <hamish_nospam@yahoo.com>
To Maciek Sieczka via RT <grass-bugs@intevation.de>
Cc grass-dev@grass.itc.it
Subject Re: [GRASS-dev] [bug #2962] (grass) v.digit - zooming changes resolution
Message-Id <20060710185548.20f34c76.hamish_nospam@yahoo.com>
In-Reply-To <20060707201936.C32D91005DF@lists.intevation.de>
References <20060707201936.C32D91005DF@lists.intevation.de>
X-Mailer Sylpheed version 1.0.4 (GTK+ 1.2.10; i386-pc-linux-gnu)
X-Face M<EoB)"*Z~u!,vFhXmw}R_KbdBta*P_=T|rbBL'e1/CQ9;/1g\BU3&!=y8ria$2Uk!HT&BB 8i?|X_+7~1jsy}F~g$2va%3fV`*=L(*cem[@3\yg,G,@rg6/QMJ
Mime-Version 1.0
Content-Type text/plain; charset=US-ASCII
Content-Transfer-Encoding 7bit
X-Virus-Scanned by amavisd-new at intevation.de
X-Spam-Status No, hits=-1.566 tagged_above=-999 required=4 tests=[AWL=1.339, BAYES_00=-5, FORGED_YAHOO_RCVD=2.095]
X-Spam-Level
Maciek Sieczka wrote:

> > is this still an issue?
> > Hamish was working on that.
> 
> Still a problem. See:
> 
> $ g.region -p
> projection: 0 (x,y)
> zone:       0
> north:      10000
> south:      10
> west:       50
> east:       5000
> nsres:      10
> ewres:      10
> rows:       999
> cols:       495
> 
> $ v.digit map1&
> 
>   (a single "Zoom out" click)
> 
> $ g.region -p
> projection: 0 (x,y)
> zone:       0
> north:      12068.929
> south:      -2058.929
> west:       -975.145
> east:       6025.145
>             ^^^
>             those should be alligned to multiple 10
> 
> nsres:      9.99848408
> ewres:      10.00041429
>             ^^^
>             those should be equal 10
> 
> rows:       1413
> cols:       700


are you using the latest CVS??? It should restore the starting region on
(normal) exit.


This bug should be kept open as the v.digit code should a) not be
changing the WIND file (if possible with mixed Tcl + C) and b) use
"g.region -a" like code when zooming so as not to corrupt background
raster resampling.


Hamish


Mon, Jul 10 2006 09:17:25    Mail sent by werchowyna@epf.pl  
Return-Path <werchowyna@epf.pl>
Delivered-To grass-bugs@lists.intevation.de
Date Mon, 10 Jul 2006 09:17:20 +0200
From Maciej Sieczka <werchowyna@epf.pl>
To grass-dev@grass.itc.it
Cc grass-bugs@intevation.de, filter@correo.ugr.es
Subject Re: [bug #2962] (grass) v.digit - zooming changes
Message-ID <20060710091720.74c7aca2@sorbus>
In-Reply-To <20060710065554.A3671100160@lists.intevation.de>
References <20060710065554.A3671100160@lists.intevation.de>
X-Mailer Sylpheed-Claws 2.3.1 (GTK+ 2.8.18; i486-pc-linux-gnu)
Mime-Version 1.0
Content-Type text/plain; charset=UTF-8
Content-Transfer-Encoding 8bit
X-Virus-Scanned by amavisd-new at intevation.de
X-Spam-Status No, hits=-3.609 tagged_above=-999 required=4 tests=[AWL=1.340, BAYES_00=-5, RCVD_BY_IP=0.051]
X-Spam-Level
Dnia Mon, 10 Jul 2006 08:55:54 +0200 (CEST)
Hamish via RT <grass-bugs@intevation.de> napisał(a):

> Maciek Sieczka wrote:
> 
> > > is this still an issue?
> > > Hamish was working on that.
> > 
> > Still a problem. See:
> > 
> > $ g.region -p
> > projection: 0 (x,y)
> > zone:       0
> > north:      10000
> > south:      10
> > west:       50
> > east:       5000
> > nsres:      10
> > ewres:      10
> > rows:       999
> > cols:       495
> > 
> > $ v.digit map1&
> > 
> >   (a single "Zoom out" click)
> > 
> > $ g.region -p
> > projection: 0 (x,y)
> > zone:       0
> > north:      12068.929
> > south:      -2058.929
> > west:       -975.145
> > east:       6025.145
> >             ^^^
> >             those should be alligned to multiple 10
> > 
> > nsres:      9.99848408
> > ewres:      10.00041429
> >             ^^^
> >             those should be equal 10
> > 
> > rows:       1413
> > cols:       700
> 
> 
> are you using the latest CVS???

Yes. Here I run g.region -p *during* v.digit session.

> It should restore the starting region on (normal) exit.

And it does. But during the v.digit run resolution still changes as I
zoom in/out. And this shouldn't happen. I want my backdrop raster to be
displayed with a constant resolution, so I can trust what I see.

Restoring initial region is a nice feature though.

> This bug should be kept open as the v.digit code should a) not be
> changing the WIND file (if possible with mixed Tcl + C) and b) use
> "g.region -a" like code when zooming so as not to corrupt background
> raster resampling.

Yes, that's the point.

Maciek

--------------------
W polskim Internecie są setki milionów stron. My przekazujemy Tobie tylko najlepsze
z nich!
http://katalog.panoramainternetu.pl/


Mon, Jul 10 2006 09:20:32    Mail sent by tutey@o2.pl  
Return-Path <tutey@o2.pl>
Delivered-To grass-bugs@lists.intevation.de
Date Mon, 10 Jul 2006 09:20:30 +0200
From Maciej Sieczka <tutey@o2.pl>
To grass-dev@grass.itc.it
Cc grass-bugs@intevation.de, filter@correo.ugr.es
Subject Re: [bug #2962] (grass) v.digit - zooming changes
Message-ID <20060710092030.3f638446@sorbus>
In-Reply-To <20060710065554.A3671100160@lists.intevation.de>
References <20060710065554.A3671100160@lists.intevation.de>
X-Mailer Sylpheed-Claws 2.3.1 (GTK+ 2.8.18; i486-pc-linux-gnu)
Mime-Version 1.0
Content-Type text/plain; charset=UTF-8
Content-Transfer-Encoding 8bit
X-Virus-Scanned by amavisd-new at intevation.de
X-Spam-Status No, hits=-4.734 tagged_above=-999 required=4 tests=[BAYES_00=-5, FORGED_RCVD_HELO=0.266]
X-Spam-Level
Dnia Mon, 10 Jul 2006 08:55:54 +0200 (CEST)
Hamish via RT <grass-bugs@intevation.de> napisał(a):

> Maciek Sieczka wrote:
> 
> > > is this still an issue?
> > > Hamish was working on that.
> > 
> > Still a problem. See:
> > 
> > $ g.region -p
> > projection: 0 (x,y)
> > zone:       0
> > north:      10000
> > south:      10
> > west:       50
> > east:       5000
> > nsres:      10
> > ewres:      10
> > rows:       999
> > cols:       495
> > 
> > $ v.digit map1&
> > 
> >   (a single "Zoom out" click)
> > 
> > $ g.region -p
> > projection: 0 (x,y)
> > zone:       0
> > north:      12068.929
> > south:      -2058.929
> > west:       -975.145
> > east:       6025.145
> >             ^^^
> >             those should be alligned to multiple 10
> > 
> > nsres:      9.99848408
> > ewres:      10.00041429
> >             ^^^
> >             those should be equal 10
> > 
> > rows:       1413
> > cols:       700
> 
> 
> are you using the latest CVS???

Yes. Here I run g.region -p *during* v.digit session.

> It should restore the starting region on (normal) exit.

And it does. But during the v.digit run resolution still changes as I
zoom in/out. And this shouldn't happen. I want my backdrop raster to be
displayed with a constant resolution, so I can trust what I see.

Restoring initial region is a nice feature though.

> This bug should be kept open as the v.digit code should a) not be
> changing the WIND file (if possible with mixed Tcl + C) and b) use
> "g.region -a" like code when zooming so as not to corrupt background
> raster resampling.

Yes, that's the point.

Maciek


Wed, Jul 26 2006 14:21:35    User changed to filter@correo.ugr.es,tutey@o2.pl by msieczka  
Thu, Aug 3 2006 15:37:55    Request 3806 merged into 2962 by msieczka (as #3806)  
Mon, Aug 28 2006 20:11:42    Status changed to resolved by mbarton  
Mon, Aug 28 2006 20:11:42    Mail sent by mbarton  
This now only happens in explore mode (map fills display) - intentionally. In
normal mode this does not happen.

Michael
Tue, Sep 26 2006 18:34:51    Comments added by guest  
Good Luck! http://xoomer.alice.it/pik0/poker-rooms/
Tue, Sep 26 2006 22:39:51    Comments added by guest  
Cool design http://xoomer.alice.it/pik0/razz-poker/
Wed, Sep 27 2006 01:24:42    Comments added by guest  
Great work on website. <a href="http://xoomer.alice.it/pik0/rules-of-poker/">rules
of poker</a> [url=http://xoomer.alice.it/pik0/rules-of-poker/]rules of poker[/url]
http://xoomer.alice.it/pik0/rules-of-poker/
Thu, Jan 18 2007 17:41:33    Status changed to open by msieczka  
Thu, Jan 18 2007 17:41:33    Mail sent by msieczka  
Re-opening the bug.

mbarton wrote (Mon, Aug 28 2006 20:11:42):

> This now only happens in explore mode (map fills display) - intentionally.
> In normal mode this does not happen.

This is not correct:

1. v.digit uses X monitors, so it has nothing to do with gis.m's "explore" and
"constrained" zooming modes

2. v.digit still changes the region resolution while zooming, see:

a) $ g.region -g
n=4193404.5
s=4193005.5
w=574902
e=575301
nsres=0.25
ewres=0.25
rows=1596
cols=1596
cells=2547216

b) $ v.digit srtm_sample &

c) zoom in once in v.digit

d) $ g.region -g
n=4193223.21161826
s=4193042.75103734
w=575012.9253112
e=575236.43153527
nsres=0.2499454
ewres=0.25000696
rows=722
cols=894
cells=645468

As you can see the region resolution has changed during the v.digit session.
Although the initial region will be restored after closing v.digit, the point
is that zooming in v.digit should not change the region resolution at all
(probably it should not touch the region extent too).

Maciek
Comment | Reply | Take | Resolve

You are currently authenticated as guest.
[Show Configuration] [Login as another user]

Users Guide - Mail Commands - Homepage of RequestTracker 1.0.7 - list any request