Nyall, I don't think there's a compatibility issue with memory layers.
Those are by their nature QGIS-dependant data, the same way ArcGIS can't
simply open a .qgs project file, a .qml layer properties file, etc.

One of the nice "feature" of memory layers (and its sister plugin memory
layer saver) is the fact that they are embedded within .qgs project files.
It should stay that way (which using GeoJSON within the XML structure of an
.qgs file would do). Transforming the .qgs project file into a zip
container would probably be a huge project driven by greater needs than
memory layers :)

Re Temporary Layers, I find it slightly better than Scratch Layer for non
native English speakers (i.e. more to the point in "simple" English :) ).

M



On Thu, Sep 25, 2014 at 1:38 PM, Nyall Dawson <nyall.daw...@gmail.com>
wrote:

>
> On 25/09/2014 4:27 pm, "Mathieu Pellerin" <nirvn.a...@gmail.com> wrote:
> >
> > Possibly although that'd clutter that space.
>
> Not really- it could be handled in the same way as the editing icon is at
> the moment. That doesn't take up any extra room as it replaces the style
> swatch.
>
> >
> > That said, I must say I quite enjoy using the memory layer saver, I'd be
> sad to see this function not making it into core.
> >
> > Martin raised an important issue re format. What about saving memory
> layer data as GeoJSON within the qgis project file? That's a solution that
> is compatible with the project file's xml format.
>
> I think the issue is more with compatibility with other programs. That's
> why a zip/archive style project file which stores memory layers in an
> existing standard format (eg geojson) was suggested.
>
> Nyall
>
_______________________________________________
Qgis-developer mailing list
Qgis-developer@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/qgis-developer

Reply via email to