I don't know much about the memory layer handling - but here are some thoughts:
I think Jürgen's idea makes a lot of sense: keep in-memory spatialite
database, and save/restore when the project is saved/opened. And the
user can export the layer to a preferred format if he/she wishes.
Perhaps
We are designing the raster save as in a way that could be re-used
elsewhere, perhaps vector saving could follow the same route -
although not much (nothing) can be shared between the vector and
raster dialogs.
Etienne
On Thu, Jul 26, 2012 at 2:29 AM, Paolo Cavallini cavall...@faunalia.it wrote:
-
From: Even Rouault [mailto:even.roua...@mines-paris.org]
Sent: Thursday, 26 July 2012 6:47 a.m.
To: qgis-developer@lists.osgeo.org
Cc: Chris Crook; haubourg
Subject: Re: [Qgis-developer] Memory data provider persistence
Le mercredi 25 juillet 2012 20:03:16, Chris Crook a écrit :
Hi .. yes I
Le jeudi 26 juillet 2012 21:41:57, Chris Crook a écrit :
Hi Even
Thanks for the suggestion and code examples - very helpful. I haven't
followed up on this yet partly because this has prompted me to look at
other storage formats for the data (something I'd been putting off).
If I
]
Sent: Thursday, 26 July 2012 7:55 p.m.
To: qgis-developer@lists.osgeo.org
Subject: Re: [Qgis-developer] Memory data provider persistence
Having a specific memory storage have pros and cons that you explained very
well Chris.
From a user point of view, one drawback is that if something goes wrong
Le jeudi 26 juillet 2012 22:52:47, Chris Crook a écrit :
Hi Even
Sorry .. lost wasn't quite correct. The point is that my code for saving
some users data and then reloading needs to take account of whether they
have a field called fid or not if I want the list of fields unchanged
after
contributions, suggestions,
code, etc :-)
Cheers
Chris
From: haubourg [regis.haubo...@eau-adour-garonne.fr]
Sent: 23 July 2012 20:58
To: qgis-developer@lists.osgeo.org
Subject: Re: [Qgis-developer] Memory data provider persistence
Hi Chris, thanks for your feedback
-Original Message-
From: Chris Crook
Sent: Thursday, 26 July 2012 6:03 a.m.
To: haubourg; qgis-developer@lists.osgeo.org
Subject: RE: [Qgis-developer] Memory data provider persistence
Hi .. yes I don't like masking the FID field and I'm not thinking this is a
long term solution, even before
Hi,
On Thu, 26. Jul 2012 at 16:31:46 +1200, Chris Crook wrote:
Thoughts?
I didn't really follow this thread. But the subject made me wonder if anybody
ever mentioned/explored sqlite/spatialite in-memory databases[1] and their
backup facility[2]? Would that be an option? Maybe even as
Il 26/07/2012 06:31, Chris Crook ha scritto:
So what I'm considering is rebuilding the plugin to read and write the memory
layer data into a single file, say project.qgis.mldata, instead of the
current multiple gml files.
Thoughts?
Hi Chris,
please consider that much the same problem
Hi Chris, thanks for your feedback. I start thinking using a spatialite is a
great idea. I prefer this than having rules to mask FID field. This can
generate very hard-to-find bugs..
Having a complex Qgs zipfile containing either a spatialite DB or xml + data
would be great but is a big
: haubourg [mailto:regis.haubo...@eau-adour-garonne.fr]
Sent: Saturday, 21 July 2012 1:55 a.m.
To: qgis-developer@lists.osgeo.org
Subject: Re: [Qgis-developer] Memory data provider persistence
Hi all,
one up for this topic. Since QGIS 1.8, memory layer saver is not working the
same way as in 1.7.4.
I
Hi all,
one up for this topic. Since QGIS 1.8, memory layer saver is not working the
same way as in 1.7.4.
I raised a tickets here http://hub.qgis.org/issues/6075
http://hub.qgis.org/issues/6075 , but I think something changed in memory
layer provider or OGR GML provider, and it maybe isn't a
On Mon, Dec 6, 2010 at 10:45 AM, Barry Rowlingson
b.rowling...@lancaster.ac.uk wrote:
On Mon, Dec 6, 2010 at 2:04 AM, Chris Crook ccr...@linz.govt.nz wrote:
So, for my requirement for memory provider persistance, the only real
question is what is the right way to do it. Although Martin had
On Mon, Dec 6, 2010 at 2:04 AM, Chris Crook ccr...@linz.govt.nz wrote:
So, for my requirement for memory provider persistance, the only real
question is what is the right way to do it. Although Martin had suggested a
spatialite database, my leaning is towards a simple QDataStream. A simple
From: Martin Dobias [wonder...@gmail.com]
Sent: 06 December 2010 22:57
To: Barry Rowlingson
Cc: Chris Crook; qgis-developer@lists.osgeo.org
Subject: Re: [Qgis-developer] Memory data provider persistence
On Mon, Dec 6, 2010 at 10:45 AM, Barry Rowlingson
b.rowling
; qgis-developer@lists.osgeo.org
Subject: Re: [Qgis-developer] Memory data provider persistence
On Mon, Dec 6, 2010 at 6:05 PM, Chris Crook ccr...@linz.govt.nz wrote:
Hi All
Fair comment I guess. In fact Barry's suggestion is pretty much back at my
original ticket on this issue. This had two
On Mon, Dec 6, 2010 at 7:12 PM, Chris Crook ccr...@linz.govt.nz wrote:
Hi Barry et al
Good point about a plugin implementation .. I hadn't thought of that obvious
option - definitely one to follow up on. It might still need a few tweaks in
terms of Qgis. The QgisInterface has a
; qgis-developer@lists.osgeo.org
Subject: Re: [Qgis-developer] Memory data provider persistence
On Mon, Dec 6, 2010 at 7:12 PM, Chris Crook ccr...@linz.govt.nz wrote:
Hi Barry et al
Good point about a plugin implementation .. I hadn't thought of that obvious
option - definitely one to follow up
, then
they can save the layer to that.
How does this sound to people?
Cheers
Chris
-Original Message-
From: Martin Dobias [mailto:wonder...@gmail.com]
Sent: Sunday, 5 December 2010 6:08 a.m.
To: Chris Crook
Cc: qgis-developer@lists.osgeo.org
Subject: Re: [Qgis-developer] Memory data
Hi Chris
On Sat, Dec 4, 2010 at 3:35 AM, Chris Crook ccr...@linz.govt.nz wrote:
Another way to achieve a similar result could be to embed the project file in
the spatialite database? That would make the memory provider data easier to
use - basically it just becomes a spatialite provided
the
reinstated project would be a more accurate copy of the one originally saved.
Cheers
Chris
From: Martin Dobias [wonder...@gmail.com]
Sent: 05 December 2010 06:07
To: Chris Crook
Cc: qgis-developer@lists.osgeo.org
Subject: Re: [Qgis-developer] Memory data provider
From: Martin Dobias [wonder...@gmail.com]
Sent: 03 December 2010 11:01
To: Chris Crook
Cc: qgis-developer@lists.osgeo.org
Subject: Re: [Qgis-developer] Memory data provider persistence
Hi Chris
On Mon, Nov 29, 2010 at 8:54 PM, Chris Crook ccr...@linz.govt.nz wrote
Hi Chris
On Mon, Nov 29, 2010 at 8:54 PM, Chris Crook ccr...@linz.govt.nz wrote:
Hi All
I'm looking for ideas/suggestions/comments on the memory data provider.
A while ago I raised a ticket http://trac.osgeo.org/qgis/ticket/2487, the
essence of which is that if you save and reload a
Hi All
I'm looking for ideas/suggestions/comments on the memory data provider.
A while ago I raised a ticket http://trac.osgeo.org/qgis/ticket/2487, the
essence of which is that if you save and reload a project nothing should have
changed, but if you have a layer supported by a memory data
25 matches
Mail list logo
