All-in-one Project QGIS Plugin - Versionsgeschichte

Stefan am 19. Juni 2016 um 19:20 Uhr

2016-06-19T19:20:42Z

← Nächstältere Version		Version vom 19. Juni 2016, 19:20 Uhr
Zeile 2:		Zeile 2:

	Often users ("producers") want to share a QGIS project file including possibly many layers (data sources), a related symbology (style/styling) and some common project settings. On the other hand, users ("consumers") want to get a single data source containing the same data and map layer styling.		Often users ("producers") want to share a QGIS project file including possibly many layers (data sources), a related symbology (style/styling) and some common project settings. On the other hand, users ("consumers") want to get a single data source containing the same data and map layer styling.


	== About ==		== About ==
Zeile 69:		Zeile 70:
	** A styling default changed after in a new QGIS version.		** A styling default changed after in a new QGIS version.

	== ~~Solution~~ ==		== Proposals ==

	An obvious approach for a QGIS project and data publisher is to put everything - including data, styles and project settings - into one zip file as described above.		An obvious approach for a QGIS project and data publisher is to put everything - including data, styles and project settings - into one zip file as described above.

	~~There is another proposal~~ to put all data ~~and related styling info~~ into ~~a single [[GeoPackage]] file instead of zipping it~~.		This project proposes to generate a temporary file space and directory and put's all data into ot. See also [http://hub.qgis.org/wiki/quantum-gis/Google_Summer_of_Code_2012#All-in-one-Projects Martin Dobias' GSoC 2012-Proposal]. It's related to the proprietary [[ArcGIS#Layer_Package_and_Map_Package \| ArcGIS Layer and ArcGIS Map Packages]] and the standardized [[GeoPackage]].

	See also [http://hub.qgis.org/wiki/quantum-gis/Google_Summer_of_Code_2012#All-in-one-Projects Martin Dobias' GSoC 2012-Proposal]. It's related to the proprietary [[ArcGIS#Layer_Package_and_Map_Package \| ArcGIS Layer and ArcGIS Map Packages]] and the standardized [[GeoPackage]].		Then there are following plugins - all most probably not maintained any more:
			* "relocator" QGIS Plugin - Relocates all your project data to a specific local directory. Version 0.9 2015-05-08 with minimal QGIS v2.0.0. Autor Riccardo Klinger, Geolicious. [http://plugins.qgis.org/plugins/relocator/ plugins.qgis.org], [https://github.com/Geolicious/relocator github]
			* "QConsolidate" QGIS Plugin - Consolidate QGIS project into one directory. Version 0.2.1 2014-01-29 with minimal QGIS v2.0.0. Autor Alexander Bruy. [http://plugins.qgis.org/plugins/qconsolidate/ plugins.qgis.org] [https://github.com/alexbruy/qconsolidate github]
			* There is another proposal to put all data and related styling info into a single [[GeoPackage]] file instead of zipping it.

	== Discussion ==		== Discussion ==

Stefan: /* Problem Statement */

2016-06-19T19:13:00Z

Problem Statement

← Nächstältere Version		Version vom 19. Juni 2016, 19:13 Uhr
Zeile 51:		Zeile 51:

	Related use cases:		Related use cases:
	* Users (designers, cartographers) want to '''share a single QGIS style (.qml), QGIS symbols (.xml) and SVG markers'''. For sharing and downloading these, there's a GSoC project'' (see [https://wiki.osgeo.org/wiki/QGIS_Sharing_Repository wiki.osgeo.org] and [https://github.com/akbargumbira/qgis_symbology_sharing @akbargumbira github]) which implements a web application to allow users use them in QGIS.		* Users (designers, cartographers) want to '''share a single QGIS style (.qml), QGIS symbols (.xml) and SVG markers'''. For sharing and downloading these, there's a GSoC project (see [https://wiki.osgeo.org/wiki/QGIS_Sharing_Repository wiki.osgeo.org] and [https://github.com/akbargumbira/qgis_symbology_sharing @akbargumbira github]) which implements a web application to allow users use them in QGIS. End users
	* Users ("style producers") want to '''share a complete QGIS symbology''' which is common to several data sources of same schema. Other users ("consumers") get a new dataset (corresponding to this schema) and want to attach a common QGIS symbology to it.		* Users ("style producers") want to '''share a complete QGIS symbology''' which is common to several data sources of same schema. Other users ("consumers") get a new dataset (corresponding to this schema) and want to attach a common QGIS symbology to it.

Stefan: /* Problem Statement */

2016-06-19T18:47:48Z

Problem Statement

← Nächstältere Version		Version vom 19. Juni 2016, 18:47 Uhr
Zeile 51:		Zeile 51:

	Related use cases:		Related use cases:
	* Users ("producers") want to '''share a complete QGIS symbology''' which is common to several data sources of same schema. Other users ("consumers") get a new dataset (corresponding to this schema) and want to attach a common QGIS symbology to it.		* Users (designers, cartographers) want to '''share a single QGIS style (.qml), QGIS symbols (.xml) and SVG markers'''. For sharing and downloading these, there's a GSoC project'' (see [https://wiki.osgeo.org/wiki/QGIS_Sharing_Repository wiki.osgeo.org] and [https://github.com/akbargumbira/qgis_symbology_sharing @akbargumbira github]) which implements a web application to allow users use them in QGIS.
	* Users ("designers") want to '''share a single QGIS style (.qml), QGIS symbols (.xml) and SVG markers'''. For sharing and downloading these, there's a GSoC project'' (see [https://wiki.osgeo.org/wiki/QGIS_Sharing_Repository wiki.osgeo.org] and [https://github.com/akbargumbira/qgis_symbology_sharing @akbargumbira github]) which implements a web application to allow users use them in QGIS.		* Users ("style producers") want to '''share a complete QGIS symbology''' which is common to several data sources of same schema. Other users ("consumers") get a new dataset (corresponding to this schema) and want to attach a common QGIS symbology to it.

	Issues:		Issues:

Stefan: /* Problem Statement */

2016-06-19T18:46:56Z

Problem Statement

← Nächstältere Version		Version vom 19. Juni 2016, 18:46 Uhr
Zeile 52:		Zeile 52:
	Related use cases:		Related use cases:
	* Users ("producers") want to '''share a complete QGIS symbology''' which is common to several data sources of same schema. Other users ("consumers") get a new dataset (corresponding to this schema) and want to attach a common QGIS symbology to it.		* Users ("producers") want to '''share a complete QGIS symbology''' which is common to several data sources of same schema. Other users ("consumers") get a new dataset (corresponding to this schema) and want to attach a common QGIS symbology to it.
	* Users ("designers") want to '''share single QGIS style (.qml), QGIS symbols (.xml) and SVG markers. For sharing and downloading these, there's a GSoC project'' (see [https://wiki.osgeo.org/wiki/QGIS_Sharing_Repository wiki.osgeo.org] and [https://github.com/akbargumbira/qgis_symbology_sharing @akbargumbira github]) which implements a web application to allow users use them in QGIS.		* Users ("designers") want to '''share a single QGIS style (.qml), QGIS symbols (.xml) and SVG markers'''. For sharing and downloading these, there's a GSoC project'' (see [https://wiki.osgeo.org/wiki/QGIS_Sharing_Repository wiki.osgeo.org] and [https://github.com/akbargumbira/qgis_symbology_sharing @akbargumbira github]) which implements a web application to allow users use them in QGIS.

	Issues:		Issues:

Stefan: /* Problem Statement */

2016-06-19T18:44:56Z

Problem Statement

← Nächstältere Version		Version vom 19. Juni 2016, 18:44 Uhr
Zeile 46:		Zeile 46:
	Main use cases are:		Main use cases are:
	* Producers want to '''share a complete QGIS project''' including possibly many layers (data sources), a related symbology (style/styling) and some common settings.		* Producers want to '''share a complete QGIS project''' including possibly many layers (data sources), a related symbology (style/styling) and some common settings.
	* Consumers (end users)want to get a single data source which contains the same data and map layer styling.		* Consumers (end users) want to get a single data source which contains the same data and map layer styling.

	In addition to the main use case, data and symbology currently is handled in QGIS as if there was a one-to-one relationship, meaning one dataset attached to one QGIS instance: A dataset is styled with one symbology using a user-specific project file where symbology files can be anywhere. But in fact, one dataset can be styled with different symbologies - and one symbology can style different datasets of same schema.		In addition to the main use case, data and symbology currently is handled in QGIS as if there was a one-to-one relationship, meaning one dataset attached to one QGIS instance: A dataset is styled with one symbology using a user-specific project file where symbology files can be anywhere. But in fact, one dataset can be styled with different symbologies - and one symbology can style different datasets of same schema.

Stefan: /* Solution */

2016-06-19T18:33:11Z

Solution

← Nächstältere Version		Version vom 19. Juni 2016, 18:33 Uhr
Zeile 71:		Zeile 71:
	== Solution ==		== Solution ==

	An obvious approach for a QGIS project and data publisher is to put everything - including data, styles and project settings - into one file.		An obvious approach for a QGIS project and data publisher is to put everything - including data, styles and project settings - into one zip file as described above.

	When copying/moving project files to other people, it is necessary to manually collect all required files and update the project file. This is complicated. and it getos even more complicated when working with databases and secured webservices and with style files on different places

			There is another proposal to put all data and related styling info into a single [[GeoPackage]] file instead of zipping it.

	See also [http://hub.qgis.org/wiki/quantum-gis/Google_Summer_of_Code_2012#All-in-one-Projects Martin Dobias' GSoC 2012-Proposal]. It's related to the proprietary [[ArcGIS#Layer_Package_and_Map_Package \| ArcGIS Layer and ArcGIS Map Packages]] and the standardized [[GeoPackage]].		See also [http://hub.qgis.org/wiki/quantum-gis/Google_Summer_of_Code_2012#All-in-one-Projects Martin Dobias' GSoC 2012-Proposal]. It's related to the proprietary [[ArcGIS#Layer_Package_and_Map_Package \| ArcGIS Layer and ArcGIS Map Packages]] and the standardized [[GeoPackage]].

Stefan: /* Problem Statement */

2016-06-19T18:31:32Z

Problem Statement

← Nächstältere Version		Version vom 19. Juni 2016, 18:31 Uhr
Zeile 52:		Zeile 52:
	Related use cases:		Related use cases:
	* Users ("producers") want to '''share a complete QGIS symbology''' which is common to several data sources of same schema. Other users ("consumers") get a new dataset (corresponding to this schema) and want to attach a common QGIS symbology to it.		* Users ("producers") want to '''share a complete QGIS symbology''' which is common to several data sources of same schema. Other users ("consumers") get a new dataset (corresponding to this schema) and want to attach a common QGIS symbology to it.
	* There is a proposal to put all data and related styling info into a single specific [[GeoPackage]] file.
	* Users ("designers") want to '''share single QGIS style (.qml), QGIS symbols (.xml) and SVG markers. For sharing and downloading these, there's a GSoC project'' (see [https://wiki.osgeo.org/wiki/QGIS_Sharing_Repository wiki.osgeo.org] and [https://github.com/akbargumbira/qgis_symbology_sharing @akbargumbira github]) which implements a web application to allow users use them in QGIS.		* Users ("designers") want to '''share single QGIS style (.qml), QGIS symbols (.xml) and SVG markers. For sharing and downloading these, there's a GSoC project'' (see [https://wiki.osgeo.org/wiki/QGIS_Sharing_Repository wiki.osgeo.org] and [https://github.com/akbargumbira/qgis_symbology_sharing @akbargumbira github]) which implements a web application to allow users use them in QGIS.

Stefan: /* Problem Statement */

2016-06-19T18:30:26Z

Problem Statement

← Nächstältere Version		Version vom 19. Juni 2016, 18:30 Uhr
Zeile 45:		Zeile 45:

	Main use cases are:		Main use cases are:
	* Producers ~~users~~ want to '''share a QGIS project''' including possibly many layers (data sources), a related symbology (style/styling) and some common settings.		* Producers want to '''share a complete QGIS project''' including possibly many layers (data sources), a related symbology (style/styling) and some common settings.
	* ~~Consumer~~ users want to get a single data source which contains the same data and map layer styling.		* Consumers (end users)want to get a single data source which contains the same data and map layer styling.

	In addition to the main use case, data and symbology currently is handled in QGIS as if there was a one-to-one relationship, meaning one dataset attached to one QGIS instance: A dataset is styled with one symbology using a user-specific project file where symbology files can be anywhere. But in fact, one dataset can be styled with different symbologies - and one symbology can style different datasets of same schema.		In addition to the main use case, data and symbology currently is handled in QGIS as if there was a one-to-one relationship, meaning one dataset attached to one QGIS instance: A dataset is styled with one symbology using a user-specific project file where symbology files can be anywhere. But in fact, one dataset can be styled with different symbologies - and one symbology can style different datasets of same schema.

	Related use cases:		Related use cases:
	* Users ("producers") want to '''share a QGIS symbology''' which is common to several data sources of same schema. Other users ("consumers") get a new dataset (corresponding to this schema) and want to attach a common QGIS symbology to it.		* Users ("producers") want to '''share a complete QGIS symbology''' which is common to several data sources of same schema. Other users ("consumers") get a new dataset (corresponding to this schema) and want to attach a common QGIS symbology to it.
	* There is a proposal to put all data and related styling info into a single specific [[GeoPackage]] file.		* There is a proposal to put all data and related styling info into a single specific [[GeoPackage]] file.
	* ~~For sharing and downloading~~ QGIS ~~styles~~ (.qml), QGIS symbols ~~definitions~~ (.xml) and SVG markers there's a GSoC project'' (see [https://wiki.osgeo.org/wiki/QGIS_Sharing_Repository wiki.osgeo.org] and [https://github.com/akbargumbira/qgis_symbology_sharing @akbargumbira github]) which implements a web application to allow users use them in QGIS.		* Users ("designers") want to '''share single QGIS style (.qml), QGIS symbols (.xml) and SVG markers. For sharing and downloading these, there's a GSoC project'' (see [https://wiki.osgeo.org/wiki/QGIS_Sharing_Repository wiki.osgeo.org] and [https://github.com/akbargumbira/qgis_symbology_sharing @akbargumbira github]) which implements a web application to allow users use them in QGIS.

	Issues:		Issues:

Stefan: /* Problem Statement */

2016-06-19T18:26:55Z

Problem Statement

← Nächstältere Version		Version vom 19. Juni 2016, 18:26 Uhr
Zeile 51:		Zeile 51:

	Related use cases:		Related use cases:
	* Users ("producers") want to '''share a QGIS symbology''' which is common to several ~~datasources~~ of same schema. Other users ("consumers") get a new dataset (corresponding to this schema) and want to attach a common QGIS symbology to it.		* Users ("producers") want to '''share a QGIS symbology''' which is common to several data sources of same schema. Other users ("consumers") get a new dataset (corresponding to this schema) and want to attach a common QGIS symbology to it.
	* There is a proposal to put all data and related styling info into a single specific [[GeoPackage]] file.		* There is a proposal to put all data and related styling info into a single specific [[GeoPackage]] file.
	* For sharing and downloading QGIS styles (.qml), QGIS symbols definitions (.xml) and SVG markers there's a GSoC project'' (see [https://wiki.osgeo.org/wiki/QGIS_Sharing_Repository wiki.osgeo.org] and [https://github.com/akbargumbira/qgis_symbology_sharing @akbargumbira github]) which implements a web application to allow users use them in QGIS.		* For sharing and downloading QGIS styles (.qml), QGIS symbols definitions (.xml) and SVG markers there's a GSoC project'' (see [https://wiki.osgeo.org/wiki/QGIS_Sharing_Repository wiki.osgeo.org] and [https://github.com/akbargumbira/qgis_symbology_sharing @akbargumbira github]) which implements a web application to allow users use them in QGIS.

Stefan: /* Current state and recommendation */

2016-06-19T18:25:15Z

Current state and recommendation

← Nächstältere Version		Version vom 19. Juni 2016, 18:25 Uhr
Zeile 30:		Zeile 30:
	** no layer which requires a plugin, like e.g. [http://plugins.qgis.org/plugins/quick_map_services/ QuickMapServices Plugin], [[Editable_GeoCSV_QGIS_Plugin GeoCSV]].		** no layer which requires a plugin, like e.g. [http://plugins.qgis.org/plugins/quick_map_services/ QuickMapServices Plugin], [[Editable_GeoCSV_QGIS_Plugin GeoCSV]].

	Goal is to have everything in a '''"project directory"''' including QGIS project file (.qgs), all datasets and symbology:		Goal is to have everything in a '''"project directory"''' including QGIS project file (.qgs), all datasets and symbology - and then to zip and share it:
	* In OS (file manager): Make sure and eventually create there is a single "project directory" which will contain everything to be shared.		* In OS (file manager): Make sure and eventually create there is a single "project directory" which will contain everything to be shared.
	* In OS (file manager): Make sure (eventually copy or move), data, SVG files and color ramps are in the "project directory" (probably you want to have a subdirectories for data/, symbology/ etc.).		* In OS (file manager): Make sure (eventually copy or move), data, SVG files and color ramps are in the "project directory" (probably you want to have a subdirectories for data/, symbology/ etc.).