Modifying layers / in-memory layers

[Didrik Pinte]

On Mon, 2008-06-30 at 13:21 -0300, Anthony Lenton wrote:
> So,
>  - What do you think of the whole
> allow-the-user-to-modify-shapes-and-info idea?  Is it bound to fail?
> Is somebody working on this already?

I am really interested in this.  Thuban is actually only a viewer but
with such functionnalities, it could be much more than that. 

I never heard about someone working on that king of new feature for
Thuban. I was planning to try to link Thuban with a mysql database to be
able to edit some of it's data attributes, so this could be a really
interesting thing.

>  - What do you think of the in-memory stores idea?  Is there an
> implementation I haven't seen?  Is there a reason not to do this all
> together?  Is a postgis store a better idea?

You can think about a "generic" in-memory store that you can feed with
any type of data. Specialized stores like postgis and shapefile are
there to increase performance or make use of specific feature of the
backend.

>  - How much work does shptree do, is it a in-memory store that only
> needs a shapefile to initialize from, or is it more of just a proxy to
> the shapefile?

I don't know. Isn't it related to the qix file ?

>  - Has anybody tried SpatiaLite? http://www.gaia-gis.it/spatialite/ I
> haven't, but it might come in handy as a middle point between keeping
> layers in memory and needing to set up a postgis database.

It could be a way to persist the dataset on the filesystem. We could
imagine an Extension that would allow a user to store/retrieve an
in-memory layer from spatialite.

Didrik
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 197 bytes
Desc: This is a digitally signed message part
Url : http://www.intevation.de/pipermail/thuban-devel/attachments/20080701/88ec17c5/attachment.bin