Details Ticket 1201


Comment | Reply | Take | Open


Serial Number 1201
Subject can't remove base map from reclassed map
Area bug
Queue grass
Requestors otto.dassau@gmx.de
Owner none
Status resolved
Last User Contact Thu Jul 25 00:21:21 2002 (6 yr ago)
Current Priority 30
Final Priority 70
Due No date assigned
Last Action Tue Jun 19 08:53:58 2007 (1 yr ago)
Created Tue Jul 23 10:18:20 2002 (6 yr ago)

Transaction History Ticket 1201


Tue, Jul 23 2002 10:18:20    Request created by guest  
Subject: can't remove base map from reclassed map  

Platform: GNU/Linux/i386
grass obtained from: Trento Italy site
grass binary for platform: Compiled from Sources

GRASS Version: grass50_exp_2002_07_12 CVS Snapshot [HEAD]

Hi,

I reclassified a vector map and cannot delete its base map. The message is:
g.remove vect=buek3314.id.botyp5
  [buek3314.id.botyp5@dassau] is a base map. Remove reclassed map first:
  tmp.recl@dassau

There is no tmp.recl map anywhere on my pc and I never created such a map, so
I guess it was some temporary file built somewhere during reclassification.
The same happened with the converted raster map:

g.remove rast=buek3314.id.botyp5
 [buek3314.id.botyp5@dassau] is a base map. Remove reclassed map first:
 tmp.recl@dassau

I imported the map buek3314.id.botyp with v.in.shape, converted it into raster
format and reclassified each format. Later I could delete all maps except these
2. Did I miss something ? 


thanks

 Otto Dassau
Wed, Jul 24 2002 14:29:17    Mail sent by mneteler  
Hi,

I also consider this to be a bug which sometimes appears.
On my machine 4-5 times, see also:

http://intevation.de/rt/webrt?serial_num=837&display=History
http://intevation.de/rt/webrt?serial_num=863&display=History

I don't think that it is a user error because it is pretty
hard to use g.remove in a wrong way.

 Markus
Thu, Jul 25 2002 00:21:21    Mail sent by glynn.clements@virgin.net  
Return-Path <glynn.clements@virgin.net>
Delivered-To grass-bugs@lists.intevation.de
From Glynn Clements <glynn.clements@virgin.net>
MIME-Version 1.0
Content-Type text/plain; charset=us-ascii
Content-Transfer-Encoding 7bit
Message-ID <15679.8720.403701.163208@cerise.nosuchdomain.co.uk>
Date Wed, 24 Jul 2002 22:54:24 +0100
To Markus Neteler via RT <grass-bugs@intevation.de>
Cc otto.dassau@gmx.de, grass5@grass.itc.it
Subject Re: [GRASS5] [bug #1201] (grass) can't remove base map from reclassed map
In-Reply-To <20020724122917.C1AE81397F@lists.intevation.de>
References <20020724122917.C1AE81397F@lists.intevation.de>
X-Mailer VM 6.94 under 21.4 (patch 4) "Artificial Intelligence (candidate #1)" XEmacs Lucid
X-Spam-Status No, hits=-4.4 required=5.0 tests=IN_REP_TO version=2.20
X-Spam-Level
Markus Neteler via RT wrote:

> I also consider this to be a bug which sometimes appears.
> On my machine 4-5 times, see also:
> 
> http://intevation.de/rt/webrt?serial_num=837&display=History
> http://intevation.de/rt/webrt?serial_num=863&display=History
> 
> I don't think that it is a user error because it is pretty
> hard to use g.remove in a wrong way.

Note that this particular bug report refers to vector maps. Also, the
fact that the map is called "tmp.recl" suggests that the reclass is
being (mis)managed automatically.

The most likely reason is that some program is creating the reclass
map automatically, then deleting the files for the resulting reclass
map without removing the entry from the reclassed_to file. Presumably
this is because the program in question predates the existence of the
reclassed_to file.

Viable solutions include:

1. Finding and fixing any programs which delete reclass maps. However,
we should also add a "force" switch to g.remove to override the "is
base map" check, to allow for:

a) the possibility that we miss a case, and

b) the situation where a user modifies the database by hand (e.g. with
"rm", "mv" etc).

2. Removing the reclassed_to file altogether. The concept itself is
inherently flawed, and was clearly implemented without sufficient
consideration of the implications.

-- 
Glynn Clements <glynn.clements@virgin.net>


Tue, Jun 19 2007 08:53:58    Status changed to resolved by hbowman  
Tue, Jun 19 2007 08:53:58    Comments added by hbowman  
"g.remove -f" force flag will solve this now.


closing bug.


Hamish
Comment | Reply | Take | Open

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