Details Ticket 3193


Comment | Reply | Take | Resolve


Serial Number 3193
Subject Building spatial index only for vectors once
Area wish6
Queue grass
Requestors hamish_nospam@yahoo.com
Owner none
Status open
Last User Contact Fri May 6 18:57:50 2005 (3 yr ago)
Current Priority 30
Final Priority 70
Due No date assigned
Last Action Wed Aug 16 15:35:56 2006 (2 yr ago)
Created Mon May 2 06:25:48 2005 (3 yr ago)

Transaction History Ticket 3193


Mon, May 2 2005 06:25:48    Request created by hbowman  
Subject: Building spatial index only for vectors once

Hi,

now that the spatial index is no longer built automatically but generated at
run-time as needed, it would be nice if it would save the spatial index so
that subsequent calls didn't have to regenerate it everytime.

e.g. running d.what.vect on LIDAR data takes a long time to start up, when
running multiple queries you have to wait each time..

maybe this is just me missing the point of not generating the spatial index
upon vector creation: was the point to save time or disk space?


thanks,
Hamish
Mon, May 2 2005 10:33:48    Mail sent by blazek@itc.it  
Return-Path <blazek@itc.it>
Delivered-To grass-bugs@lists.intevation.de
Message-ID <4275E5E8.50106@itc.it>
Date Mon, 02 May 2005 10:33:44 +0200
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 #3193] (grass) Building spatial index only for vectors once
References <20050502042548.84AA91006B1@lists.intevation.de>
In-Reply-To <20050502042548.84AA91006B1@lists.intevation.de>
Content-Type text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding 7bit
X-OriginalArrivalTime 02 May 2005 08:33:45.0098 (UTC) FILETIME=[A74EEEA0:01C54EF1]
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=3193
> -------------------------------------------------------------------------
> 
> Subject: Building spatial index only for vectors once
> 
> Hi,
> 
> now that the spatial index is no longer built automatically but generated at
> run-time as needed, it would be nice if it would save the spatial index so
> that subsequent calls didn't have to regenerate it everytime.
> 
> e.g. running d.what.vect on LIDAR data takes a long time to start up, when
> running multiple queries you have to wait each time..
> 
> maybe this is just me missing the point of not generating the spatial index
> upon vector creation: was the point to save time or disk space?

The reason was to save both. I am not sure if d.what.vect should write a 
data, probably it should not.

Writing of the index to disk could be enabled by GRASS variable and/or 
v.build option. But that changes vector format which must be supported 
in all next version. Before we enable writing of spatial index, it 
should be revised if the format can be changed to save some space.

Radim


Tue, May 3 2005 10:09:32    Mail sent by hbowman  
what about writing the index into $MAPSET/.tmp/$HOST/ so it is cached for that
session at least?


Hamish
Fri, May 6 2005 18:57:50    Mail sent by neteler@itc.it  
Return-Path <neteler@itc.it>
Delivered-To grass-bugs@lists.intevation.de
Date Fri, 6 May 2005 18:57:47 +0200
From Markus Neteler <neteler@itc.it>
To Harmish Bowman via RT <grass-bugs@intevation.de>
Cc grass5@grass.itc.it
Subject Re: [GRASS5] [bug #3193] (grass) Building spatial index only for vectors once
Message-ID <20050506165747.GL2425@thuille.itc.it>
Mail-Followup-To Harmish Bowman via RT <grass-bugs@intevation.de>, grass5@grass.itc.it
References <20050503080932.7E691100161@lists.intevation.de>
Mime-Version 1.0
Content-Type text/plain; charset=us-ascii
Content-Disposition inline
In-Reply-To <20050503080932.7E691100161@lists.intevation.de>
User-Agent Mutt/1.4.1i
X-Spam-Status No, hits=-4.9 tagged_above=-999.0 required=3.0 tests=BAYES_00
X-Spam-Level
On Tue, May 03, 2005 at 10:09:32AM +0200, Harmish Bowman via RT wrote:
> what about writing the index into $MAPSET/.tmp/$HOST/ so it is cached for that
> session at least?

Sounds good to me... When closing the GRASS session, the file(s)
would be deleted by clean_temp then as desired.
Maybe there are problems with that?

Markus


Wed, Aug 16 2006 15:35:56    Comments added by guest  
Cc: grass-dev@grass.itc.it

I think that seen the fact that we are quickly moving to new releases and then
to further development, it might be the time to take this up again in order to
plan ahead. 

Reminder of the problem: 
Hamish:
"Now that the spatial index is no longer built automatically but generated at
run-time as needed, it would be nice if it would save the spatial index so
that subsequent calls didn't have to regenerate it everytime."

On Tue, May 03, 2005 at 10:09:32AM +0200, Harmish Bowman via RT wrote:
> what about writing the index into $MAPSET/.tmp/$HOST/ so it is cached for that
> session at least?

Markus:
"Sounds good to me... When closing the GRASS session, the file(s)
would be deleted by clean_temp then as desired.
Maybe there are problems with that?"

I don't know if space is such as problem, but for me even this seems
inefficient. Once the index is created it should stay there even when leaving
the session. Or at least there should be a configurable option (maybe a GRASS
environment variable) to leave the index files in place.

Moritz

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