Hi Stefan, I just read your All-In-One Project Plugin documentation here (are you about to develop it? or already developed it?). I think more or less the goal would be the same with current GSoC project if we extend the definition of 'collection' to also contain data itself. So one colleciton is a self-sufficient QGIS resources (including its data) to create a coherent map design.
Cheers On Sun, Jun 19, 2016 at 10:55 PM, Akbar Gumbira <[email protected]> wrote: > HI Stefan, > > I am the one doing that GSoC project. You remind me that I need to update > the project description in osgeo wiki. The concept has changed a lot since > then. We decided that we would go with sharing collections to a directory > based repository (For now I will implement it for Github and Bitbucket). If > you have some time, I would suggest you to read the current plan here (it > would be long to explain in this email) > https://docs.google.com/document/d/13ETuLBTx5IjVejB8TQPjjsMWBcUQO6pIKrNSrAZUApo/edit?usp=sharing > > > Cheers > > On Sun, Jun 19, 2016 at 10:00 PM, Stefan Keller <[email protected]> > wrote: > >> Hi, >> >> These are thoughts on sharing 1. a whole QGIS symbology and 2. a whole >> QGIS project including symbology and data. >> >> There's a promising current GSoC project, where users ("designers, >> cartographers") can << share QGIS style files >> incl. styles (.qml), >> symbols (.xml) and SVG markers. End users can download and add styles, >> symbols or SVG markers (set of?). See >> https://wiki.osgeo.org/wiki/QGIS_Sharing_Repository . >> >> Use case A: What about sharing a symbology with dozens of layers still >> without the data? So, this is about users ("style producers") who want >> to << share a complete set QGIS styles >> which involves references to >> several data layers. End users should be able to open a dataset (like >> a vector/raster data from GeoPackage or a QGIS project), and then load >> or exchange a "symbology set". This is often the case when data is >> split into several regions or when end users capture data of same >> schema. >> >> I have no ideas yet to resolve this use case, except taking use case B >> as a (rather unmaintainable, intermediate) solution. >> >> Use case B: Users ("producers") want to easily << share a complete >> QGIS project >> including data and symbology. Currently for producers, >> it is necessary to: 1. Manually collect all required files into a >> "project directory" including project file .qgs, data, svg markers, >> color ramps (others?), 2. Edit QGIS project to adapt file paths, and >> finally 3. zip the directory and send or publish it. End users would >> unpack it and double click on the QGIS project file. >> >> Possible approaches are the relocator and QConsolidate plugins >> (possibly not maintained any more) and my "All-in-one Project" >> (unfinished). And there's Pirmin's idea to put everything into a >> GeoPackage file instead of a zip file. >> >> => Any comments or ideas? >> >> :Stefan >> >> P.S. For more issues on this like locally installed symbol fonts, >> temporary/in-memory data layers, databases, secured web services, and >> layer provider plugins) see my "All-in-one Project" >> (http://giswiki.hsr.ch/All-in-one_Project_QGIS_Plugin). >> _______________________________________________ >> Qgis-developer mailing list >> [email protected] >> List info: http://lists.osgeo.org/mailman/listinfo/qgis-developer >> Unsubscribe: http://lists.osgeo.org/mailman/listinfo/qgis-developer > > > > > -- > > *-------------------* > *Akbar Gumbira * > *www.akbargumbira.com <http://www.akbargumbira.com>* > -- *-------------------* *Akbar Gumbira * *www.akbargumbira.com <http://www.akbargumbira.com>*
_______________________________________________ Qgis-developer mailing list [email protected] List info: http://lists.osgeo.org/mailman/listinfo/qgis-developer Unsubscribe: http://lists.osgeo.org/mailman/listinfo/qgis-developer
