Details Ticket 2885


Comment | Reply | Take | Resolve


Serial Number 2885
Subject g3d region problem
Area grass5.7
Queue grass
Requestors peter.loewe@gmx.de
Owner none
Status open
Last User Contact Wed Jan 5 17:03:31 2005 (4 yr ago)
Current Priority 30
Final Priority 70
Due No date assigned
Last Action Thu Jan 13 15:11:15 2005 (4 yr ago)
Created Tue Jan 4 11:56:08 2005 (4 yr ago)

Transaction History Ticket 2885


Tue, Jan 4 2005 11:56:08    Request created by guest  
Subject: g3d region problem

Platform: GNU/Linux/i386
grass obtained from: Trento Italy site
grass binary for platform: Compiled from Sources
GRASS Version: 5.7 weekly snapshot: 12-25-04

g3d-files appear to be immune to changes to the current region made by 
d.zoom 
 
example: A g3d-file is created from several rasters in a location (including
setting the r3-parameters for g.region). Then the current region is modified
by zooming in using d.zoom. 
When NVIZ is now called up, the 2d-region settings are as to be expected, 
yet the 3d-volume settings are way up in limbo: strange volumes (from outer 
space?) roam the skies. 
 
a workaround is to recreate the g3d-file after each zooming-step.  
 
Cheers, 
Peter Loewe 
Wed, Jan 5 2005 17:03:31    Mail sent by blazek@itc.it  
Return-Path <blazek@itc.it>
Delivered-To grass-bugs@lists.intevation.de
Message-ID <41DC0FC8.8040501@itc.it>
Date Wed, 05 Jan 2005 17:03:20 +0100
From Radim Blazek <blazek@itc.it>
User-Agent Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.6) Gecko/20040113
X-Accept-Language en-us, en
MIME-Version 1.0
To Request Tracker <grass-bugs@intevation.de>
Cc grass5@grass.itc.it
Subject Re: [GRASS5] [bug #2885] (grass) g3d region problem
References <20050104105608.B9D9910016B@lists.intevation.de>
In-Reply-To <20050104105608.B9D9910016B@lists.intevation.de>
Content-Type text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding 7bit
X-Spam-Status No, hits=-4.9 tagged_above=-999.0 required=3.0 tests=BAYES_00
X-Spam-Level
Request Tracker wrote:
> this bug's URL: http://intevation.de/rt/webrt?serial_num=2885
> -------------------------------------------------------------------------
> 
> Subject: g3d region problem
> 
> Platform: GNU/Linux/i386
> grass obtained from: Trento Italy site
> grass binary for platform: Compiled from Sources
> GRASS Version: 5.7 weekly snapshot: 12-25-04
> 
> g3d-files appear to be immune to changes to the current region made by 
> d.zoom 
>  
> example: A g3d-file is created from several rasters in a location (including
> setting the r3-parameters for g.region). Then the current region is modified
> by zooming in using d.zoom. 
> When NVIZ is now called up, the 2d-region settings are as to be expected, 
> yet the 3d-volume settings are way up in limbo: strange volumes (from outer
> space?) roam the skies. 
>  
> a workaround is to recreate the g3d-file after each zooming-step.  
>  
> Cheers, 
> Peter Loewe 

The problem is in NVIZ or in the module creating the raster 3D?

Can you post the output from?:
g.region -p3
r3.mapcalc "test=1"
r3.info test1

Radim


Thu, Jan 13 2005 15:11:15    Mail sent by peter.loewe@gmx.de  
Return-Path <peter.loewe@gmx.de>
Delivered-To grass-bugs@lists.intevation.de
Date Thu, 13 Jan 2005 15:11:11 +0100 (MET)
From =?ISO-8859-1?Q?=22Peter_L=F6we=22?= <peter.loewe@gmx.de>
To Radim Blazek via RT <grass-bugs@intevation.de>
MIME-Version 1.0
Content-Type multipart/mixed; boundary="========GMXBoundary263341105625471"
Subject Re: [bug #2885] (grass) g3d region problem
X-Priority 3 (Normal)
X-Authenticated #494617
Message-ID <26334.1105625471@www66.gmx.net>
X-Mailer WWW-Mail 1.6 (Global Message Exchange)
X-Flags 0001
X-Spam-Status No, hits=-4.9 tagged_above=-999.0 required=3.0 tests=BAYES_00
X-Spam-Level
This is a MIME encapsulated multipart message -
please use a MIME-compliant e-mail program to open it.

Dies ist eine mehrteilige Nachricht im MIME-Format -
bitte verwenden Sie zum Lesen ein MIME-konformes Mailprogramm.

--========GMXBoundary263341105625471
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: 8bit

Hey Radim,  
  
the output you requested is in the attachments.  
  
I was further able to track the problem down:  
  
Imagine a 400x400 XY-location  
  
A zoom into the _northeastern_ quadrant displays the correct rasters, yet
the volumes from the  
_southeastern quadrant_. I would guess that somethings funny regaring the
Y-coordinate for volumes.  
  
  
Cheers,  
Peter  

-- 
Dr. Peter Löwe

Diplom-Geograph

<loewe@geomancers.net>
<peter.loewe@gmx.de>

+++ Sparen Sie mit GMX DSL +++ http://www.gmx.net/de/go/dsl
AKTION für Wechsler: DSL-Tarife ab 3,99 EUR/Monat + Startguthaben
--========GMXBoundary263341105625471
Content-Type: text/plain; name="gregion-2p.txt"
Content-Transfer-Encoding: base64
Content-Disposition: attachment; filename="gregion-2p.txt"

cHJvamVjdGlvbjogMCAoeCx5KQp6b25lOiAgICAgICAwCm5vcnRoOiAgICAgIDQwMApzb3V0aDog
ICAgICAwCndlc3Q6ICAgICAgIDAKZWFzdDogICAgICAgNDAwCnRvcDogICAgICAgIDE4LjAwMDAw
MDAwCmJvdHRvbTogICAgIDAuMDAwMDAwMDAKbnNyZXM6ICAgICAgMQpuc3JlczM6ICAgICAxCmV3
cmVzOiAgICAgIDEKZXdyZXMzOiAgICAgMQp0YnJlczogICAgICAxCnJvd3M6ICAgICAgIDQwMApy
b3dzMzogICAgICA0MDAKY29sczogICAgICAgNDAwCmNvbHMzOiAgICAgIDQwMApkZXB0aHM6ICAg
ICAxOAo=

--========GMXBoundary263341105625471
Content-Type: text/plain; name="r3infotest.txt"
Content-Transfer-Encoding: base64
Content-Disposition: attachment; filename="r3infotest.txt"

ICstLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0t
LS0tLS0tLS0tLS0tLS0tLS0tLS0tKwogfCBMYXllcjogICAgdGVzdCAgICAgICAgICAgICAgICAg
ICAgICAgICAgIERhdGU6ID8/ICAgICAgICAgICAgICAgICAgICAgICAgICB8CiB8IE1hcHNldDog
ICBtcmwtMzAxMjIwMDEgICAgICAgICAgICAgICAgICAgTG9naW4gb2YgQ3JlYXRvcjogPz8gICAg
ICAgICAgICAgIHwKIHwgTG9jYXRpb246IHBvc3Rkb2MtcmFkYXIgICAgICAgICAgICAgICAgICAg
ICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgfAogfCBEYXRhQmFzZTogL21udC9oZGQx
L2xvY2F0aW9ucyAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICB8
CiB8IFRpdGxlOiAgICAgKCA/PyApICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAg
ICAgICAgICAgICAgICAgICAgICAgIHwKIHwtLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0t
LS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tfAogfCAgICAgICAg
ICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAg
ICAgICAgICAgICB8CiB8ICAgVHlwZSBvZiBNYXA6ICAzZCBjZWxsICAgICAgICAgICAgIE51bWJl
ciBvZiBDYXRlZ29yaWVzOiAwICAgICAgICAgICAgICAgIHwKIHwgICBSb3dzOiAgICAgICAgIDQw
MCAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAg
fAogfCAgIENvbHVtbnM6ICAgICAgNDAwICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAg
ICAgICAgICAgICAgICAgICAgICAgICB8CiB8ICAgRGVwdGhzOiAgICAgICAxOCAgICAgICAgICAg
ICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgIHwKIHwgICBUb3Rh
bCBDZWxsczogIDI4ODAwMDAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAg
ICAgICAgICAgICAgfAogfCAgICAgICAgUHJvamVjdGlvbjogeCx5ICh6b25lIDApICAgICAgICAg
ICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICB8CiB8ICAgICAgICAgICAgTjogICAg
ICAgIDQwMCAgICBTOiAgICAgICAgICAwICAgUmVzOiAgICAgMSAgICAgICAgICAgICAgICAgICAg
IHwKIHwgICAgICAgICAgICBFOiAgICAgICAgNDAwICAgIFc6ICAgICAgICAgIDAgICBSZXM6ICAg
ICAxICAgICAgICAgICAgICAgICAgICAgfAogfCAgICAgICAgICAgIFQ6ICAgICAgICAgMTggICAg
QjogICAgICAgICAgMCAgIFJlczogICAgIDEgICAgICAgICAgICAgICAgICAgICB8CiB8ICAgICAg
ICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAg
ICAgICAgICAgICAgIHwKICstLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0t
LS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tKwoK

--========GMXBoundary263341105625471--


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