From a704ec0df1c70d8e79e0b327504d90d42b1b4316 Mon Sep 17 00:00:00 2001 From: nobohan Date: Tue, 28 Feb 2023 22:43:53 +0100 Subject: [PATCH] upd README and CHANGELOG for qgis --- CHANGELOG.md | 6 ++++++ README.md | 6 +++++- qgis/README.md | 22 +++++++++++----------- 3 files changed, 22 insertions(+), 12 deletions(-) diff --git a/CHANGELOG.md b/CHANGELOG.md index 535d40b..d3a7580 100644 --- a/CHANGELOG.md +++ b/CHANGELOG.md @@ -1,3 +1,9 @@ +## v0.9.0 winter-2022-2023 + +### Description + +The OpenArdenneMap style was made available for QGIS, besides the Mapnik/cartoCSS implementation. A new "qgis" folder was created, with simply a qgis project that uses the same PostGIS layers than the Mapnik style. + ## v0.8.0 summer-2022 ### Description diff --git a/README.md b/README.md index 6562e39..e76fd31 100644 --- a/README.md +++ b/README.md @@ -10,7 +10,7 @@ OpenArdenneMap Un exemple peut être téléchargé [ici](http://www.nobohan.be/docs/OpenArdenneMap_Rulles_1_20000e.pdf). -Some blog posts about the OpenArdenneMap semestrial releases [here](https://www.nobohan.be/tag/openardennemap/). +Some blog posts about the OpenArdenneMap semestrial releases [here](https://www.nobohan.be/tag/openardennemap/).   @@ -45,6 +45,8 @@ Lancer le script `create-db.sh`. Il faut l'éditer auparavant selon le chemin de # Usage OpenArdenneMap fonctionne avec les importateurs `imposm` et `osm2pgsql`. Les styles et le fichier de projet propres à chaque importateur se trouvent dans leurs dossiers respectifs. À noter que, grâce à sa meilleure façon de gérer les multipolygones, les développement les plus récents se font avec `osm2pgsql`, le fichier de projet avec `imposm` n'est plus mis à jour. +OpenArdenneMap a été originellement développé pour le logiciel de cartographie Mapnik. Depuis 2023, il est aussi disponible avec le logiciel QGIS. Avec QGIS, le style est simplement disponible au travers d'un fichier de projet QGIS (qgis/oam.qgs), fonctionnant avec la même base de données que Mapnik. + ## Pour changer les données OSM (import dans une db) Avec osm2pgsql, éditer le fichier `osm2pgsql/OpenArdenneMap.style`. @@ -276,6 +278,8 @@ Run the script `create-db.sh`. Edit it before according to the path of your virt # Usage OpenArdenneMap works with `imposm` or `osm2pgsql`. Map styles and project file for each importer are within their own folder (osm2pgsql or imposm). Note that, due to is better handling of complex multipolygons, recent map developments are done with `osm2pgsql` and the project file with `imposm` is not longer updated. +OpenArdenneMap was originally developed for the Mapnik mapping software. Since 2023, it is also available with QGIS software. With QGIS, the style is simply available through a QGIS project file (qgis/oam.qgs), running on the same database as Mapnik. + ## To change the way the OSM data are imported For imposm, edit the `imposm/imposm-mapping.py` file. diff --git a/qgis/README.md b/qgis/README.md index 2392041..aedcd79 100644 --- a/qgis/README.md +++ b/qgis/README.md @@ -8,14 +8,21 @@ Open the oam.qgs project file and use the map composer for producing some maps. ## About QGIS for OpenArdenneMap -OpenArdenneMap was originally developed as a cartographic style with the `imposm` importer and a `cartoCSS` style derived from OSMBright. Later the `osm2pgsql`importer was used instead of the `imposm`. From 2023, the OpenArdenneMap is also available in QGIS, using the same `osm2pgsql`importer. +OpenArdenneMap was originally developed as a cartographic style with the `imposm` importer and a `cartoCSS` style derived from OSMBright. Later the `osm2pgsql`importer was used instead of the `imposm`. From 2023, the OpenArdenneMap is also available in QGIS, using the same `osm2pgsql`importer for building the map layers. -The tools used for making maps have (unfortunately) some influence on the cartographic style itself. The aim of this QGIS support is to reproduce the same feeling than the maps produced with the Mapnik/cartoCSS style, even though the 2 solutions are not 100% equivalent. +The tools used for making maps have some influence on the cartographic style itself. The aim of this QGIS support is to reproduce the same feeling than the maps produced with the Mapnik/cartoCSS style, even though the 2 solutions are not 100% equivalent. Although it still requires a postGIS database, the QGIS style is much simpler to use for composing maps at various scales than the Mapnik/cartoCSS one. It was also much simpler to set up. Here are some key findings when moving this style from Mapnik/cartoCSS to QGIS. +### Much more simple rules for scaling in QGIS + +QGIS supports the use of geographic units for defining the sizes of symbols (meters at scale, map units), whereas Mapnik/cartoCSS, as far as I know, only deals with pixels units. It means that, in QGIS, you can define a size which will be depending on the map scale. This is really useful for very high map scale (i.e., > 1:10000), where some elements such as road widths can take their "real" size on the map. For the same effect in Mapnik, we have to define different widths for every zoom level. + +### Use of QGIS variables + +A key advantage of using Mapnik and cartoCSS is that we can define variables that are used throughout the project, typically for some dimensioning variables and colors. Hopefully, we can also define variables in a QGIS project (Go to Project > Properties > Variables) and use them in the style definitions. ### Use filtered full Postgis table filtered vs SQL layers @@ -38,19 +45,12 @@ which combines linear ways from `planet_osm_line` with lines created from `plane These PostGIS queries were just defined as layers in the QGIS DB manager and then added to the map. -However, for some performances issues, it seems easier to filter from a PostGIS layer from the DB rather than defining a new SQL layer with the DB manager. Whenever possible, layers are full PostGIS tables that are just filtered for the required elements. +However, for some performances issues, it seems easier to filter directly from a PostGIS layer from the DB rather than defining a new SQL layer with the DB manager. Whenever possible, layers are full PostGIS tables that are just filtered for the required elements. -### Much more simple rules for scaling in QGIS - -QGIS supports the use of geographic units for defining the sizes of symbols (meters at scale, map units), whereas Mapnik/cartoCSS, as far as I know, only deals with pixels units. It means that, in QGIS, you can define a size which will be depending on the map scale. This is really useful for very high map scale (i.e., > 1:10000), where some elements such as road widths can take their "real" size on the map. For the same effect in Mapnik, we have to define different widths for every zoom level. - -### Use of QGIS variables - -A key advantage of using Mapnik and cartoCSS is that we can define variables that are used throughout the project, typically for some dimensioning variables and colors. Hopefully, we can also define variables in a QGIS project (Go to Project > Properties > Variables) and use them in the style definitions. ### How to prevent overlapping symbols/labels -This is a core functionality of Mapnik, and a so common but also so hard issue in cartography: how do you prevent symbols that overlaps each other, either from the same layer or from different layers? The same applies to labels. Unfortunately, preventing overlapping symbols was not found in QGIS. +This is a core functionality of Mapnik, and a so common but also so hard issue in cartography: how do you prevent symbols that overlaps each other, either from the same layer or from different layers? The same applies to labels. Unfortunately, until now preventing overlapping symbols was not found in QGIS.