[WIP] Borders and country name rework

CARTOGRAPHY.md

@@ -1,14 +1,14 @@
 
 # Design goals and guidelines for this style
 
-This is an attempt to outline the goals of this style and the principles under 
-which the maintainers make decisions.  These rules are not set in stone, they 
-can change and they may not be followed in all cases but contributors should 
+This is an attempt to outline the goals of this style and the principles under
+which the maintainers make decisions.  These rules are not set in stone, they
+can change and they may not be followed in all cases but contributors should
 be able to expect that they are generally the guiding principles design wise.
 
-It does not make much sense to try following these principles blindly as a 
-contributor without understanding them, they are meant to guide you to develop 
-an intuition and understanding how to make design decisions to fit into the 
+It does not make much sense to try following these principles blindly as a
+contributor without understanding them, they are meant to guide you to develop
+an intuition and understanding how to make design decisions to fit into the
 overall concept of this style.
 
 ## General purpose
@@ -20,15 +20,15 @@ This style has multiple purposes:
 * It's used in many map applications as a general purpose map.
 * It's an exemplar stylesheet for rendering OSM data.
 
-There is no ranking of these purposes.  To allow serving all of them and to 
-avoid satisfying only some at the cost of the others the following main goals 
+There is no ranking of these purposes.  To allow serving all of them and to
+avoid satisfying only some at the cost of the others the following main goals
 have been identified.
 
 ## Main goals
 
-The following goals need to be balanced against each other to serve the purposes 
-above.  There is no fixed order of priorities.  Apart from these goals there are 
-of course also technical constraints and requirements that need to be taken into 
+The following goals need to be balanced against each other to serve the purposes
+above.  There is no fixed order of priorities.  Apart from these goals there are
+of course also technical constraints and requirements that need to be taken into
 account.
 
 * **Legibility and clarity** - The map should be intuitively readable by users with some general experience using maps without a map key, preferrably with relatively little effort.  A map key or more extensive experience using this map style can be required for clearly identifying minor differences or the exact meaning of certain features but in broad strokes orientation and identification of map elements should be possible on an intuitive level.  We also aim for the map appearance to be esthetically pleasing.

CHANGELOG.md

@@ -1,4 +1,33 @@
-## [Unreleased](https://github.com/gravitystorm/openstreetmap-carto/compare/v4.18.0...master)
+## [Unreleased](https://github.com/gravitystorm/openstreetmap-carto/compare/v4.19.0...master)
+
+## [v4.19.0](https://github.com/gravitystorm/openstreetmap-carto/compare/v4.18.0...v4.19.0) - 2019-01-18
+## Changes
+- Adding rendering for boundary=protected_area (#3509)
+- Nature reserve boundaries revision (#3574) 
+- Adding support of amenity=vending_machine (#3601)
+- Adding more barrier icons (#3602)
+- Changing allotments color and adding outline (#3625)
+- Reducing priority of tourism=attraction and rendering from z17 (#3603)
+- Changing tourism outline color (#3582)
+- Making country borders thicker at z8 and z9 (#3563)
+- Rendering parking from z14 (#3612)
+- Starting to render most patterns at z13 instead of z14 (#3610) 
+- Changing zoom level and text size for place=hamlet (#3626)
+- Rendering airport gate refs black instead of purple (#3620)
+- Updating zoom levels by height for masts, towers and telescopes (#3536)
+- Hiding underground parking (#3600)
+- Rendering ref of minor roads more than once (#3627)
+- Adjusting width of highway=construction (#3580)
+- Selecting only motorway_link to tertiary_link as link (#3567)
+- Reducing tertiary-link width (#3570)
+- Changing certain amenity icons to grey (#3586)
+- Converting springs to use ST_PointOnSurface and reformatting SQL (#3233)
+- Adding "religious-icon" as color variable for #000000 (#3642)
+- Adding "barrier-icon" color variable in #3f3f3f for barriers (#3643)
+- Fixing inconsistency of leisure=ice_rink (#3598)
+- Fixing label opacity for tourism features (#3616)
+- Reverting lowzoom nobuilding test change (#3622)
+- Removing trailing whitespace (#3637)
 
 ## [v4.18.0](https://github.com/gravitystorm/openstreetmap-carto/compare/v4.17.0...v4.18.0) - 2018-12-21
 ## Changes
@@ -9,7 +38,7 @@
 - Changing landuse=allotments color and pattern
 - Adding rendering for natural=cape
 - Rendering leisure=ice_rink
-- Adding rendering for man_made=crane 
+- Adding rendering for man_made=crane
 - Adding icons for shop=fabric and shop=carpet
 - Updating icons for amenity=arts_centre, leisure=slipway, amenity=restaurant/amenity=food_court and man_made=storage_tank/man_made=silo
 - Using dedicated icon for artwork_type=bust
@@ -100,13 +129,13 @@
 - Increased shield distances on roads
 - Added icon for shop=ticket
 - Added icon for shop=houseware
-- Added icon for shop=charity 
+- Added icon for shop=charity
 - Added icon for shop=second_hand
 - Added icon for shop=interior_decoration
 - Added icon for amenity=bureau_de_change
 - Added icon for amenity=casino
 - Added icon for amenity=boat_rental
-- Updated shop=department_store icon 
+- Updated shop=department_store icon
 - Small documentation and code fixes
 
 ## [v4.12.1](https://github.com/gravitystorm/openstreetmap-carto/compare/v4.12.0...v4.12.1) - 2018-06-29
@@ -119,7 +148,7 @@
 
 ### Changes
 - Added rendering “surface” tag on roads with a pattern
-- More vertical objects rendering and tuning (man_made=tower types, man_made=chimney, man_made=communications_tower) 
+- More vertical objects rendering and tuning (man_made=tower types, man_made=chimney, man_made=communications_tower)
 - tourism=information types rendering and tuning (information=audioguide, board, guidepost, map, office, tactile_map, tactile_model and terminal)
 - Added rendering for place=quarter
 - Added rendering of historic=city_gate
@@ -225,7 +254,7 @@
 ### Changes
 - Change sports_centre and stadium color to light green
 - Change shades of green for landuse/leisure=recreation_ground and garden
-- Do not render glaciers and icesheets on z6 and z7 
+- Do not render glaciers and icesheets on z6 and z7
 - Do not render very small water areas on low zoom
 - Do not render small national parks and nature reserves
 - Do not render ferries on z7
@@ -243,9 +272,9 @@
 - Changing parking color from yellow to gray
 
 ### Changes
-- Unified rendering of leisure=fitness_station and leisure=fitness_centre 
+- Unified rendering of leisure=fitness_station and leisure=fitness_centre
 - Rendering of military=bunker
-- Rendering all station buildings as major buildings 
+- Rendering all station buildings as major buildings
 - Text wrapping for station labels
 - Changing windmill color from amenity brown to man_made gray
 - Some other documentation and code changes
@@ -257,12 +286,12 @@
 
 ### Changes
 - Rendering of amenity=marketplace
-- Rendering of landuse=religious 
+- Rendering of landuse=religious
 - Rendering shop=pastry like shop=confectionery
 - Rendering of addr:unit
 - Rendering natural=bare_rock earlier
 - Rendering elevation also on polygon alpine_hut and shelter
-- Introducing Noto Sans Arabic 
+- Introducing Noto Sans Arabic
 - Rendering icon for slipway ways
 - Better minimal distance between housenumbers
 - Moving aeroways to their own layer
@@ -298,7 +327,7 @@
 - Plaque rendering is now different and moved to z19
 - Rendering railway labels
 - Smaller line spaces in labels
-- Junction names on areas 
+- Junction names on areas
 - Area color for railway=station is the same as for railways
 - Database perfomance tuning available for Docker
 - Different patterns and all remaining icons moved to SVG

DOCKER.md

@@ -40,7 +40,7 @@ Once you have that file put it into the openstreetmap-carto directory and run `d
 This starts the PostgreSQL container (downloads it if it not exists) and starts a container that runs [osm2pgsql](https://github.com/openstreetmap/osm2pgsql) to import the data. The container is built the first time you run that command if it not exists.
 At startup of the container the script `scripts/docker-startup.sh` is invoked which prepares the database and itself starts osm2pgsql for importing the data.
 
-osm2pgsql has a few [command line options](https://manpages.debian.org/testing/osm2pgsql/osm2pgsql.1.en.html) and the import by default uses a RAM cache of 512 MB, 1 worker and expects the import file to be named `data.osm.pbf`. If you want to customize any of these parameters you have to set the environment variables `OSM2PGSQL_CACHE` (e.g. `export OSM2PGSQL_CACHE=1024` on Linux to set the cache to 1 GB) for the RAM cache (the value depends on the amount of RAM you have available, the more you can use here the faster the import may be), `OSM2PGSQL_NUMPROC` for the number of workers (this depends on the number of processors you have and whether your harddisk is fast enough e.g. is a SSD), or `OSM2PGSQL_DATAFILE` if your file has a different name. 
+osm2pgsql has a few [command line options](https://manpages.debian.org/testing/osm2pgsql/osm2pgsql.1.en.html) and the import by default uses a RAM cache of 512 MB, 1 worker and expects the import file to be named `data.osm.pbf`. If you want to customize any of these parameters you have to set the environment variables `OSM2PGSQL_CACHE` (e.g. `export OSM2PGSQL_CACHE=1024` on Linux to set the cache to 1 GB) for the RAM cache (the value depends on the amount of RAM you have available, the more you can use here the faster the import may be), `OSM2PGSQL_NUMPROC` for the number of workers (this depends on the number of processors you have and whether your harddisk is fast enough e.g. is a SSD), or `OSM2PGSQL_DATAFILE` if your file has a different name.
 
 You can also [tune the PostgreSQL](https://wiki.postgresql.org/wiki/Tuning_Your_PostgreSQL_Server) during the import phases, with `PG_WORK_MEM` (default to 16MB) and `PG_MAINTENANCE_WORK_MEM` (default to 256MB), which will eventually write `work_mem` and `maintenance_work_mem` to the `postgresql.auto.conf` once, making them applied each time the database started. Note that unlike osm2pgsql variables, once thay are set, you can only change them by running `ALTER SYSTEM` on your own, changing `postgresql.auto.conf` or remove the database volume by `docker-compose down -v && docker-compose rm -v` and import again.
 
@@ -50,7 +50,7 @@ If you want to customize and remember the values, supply it during your first im
 PG_WORK_MEM=128MB PG_MAINTENANCE_WORK_MEM=2GB \
 OSM2PGSQL_CACHE=2048 OSM2PGSQL_NUMPROC=4 \
 OSM2PGSQL_DATAFILE=taiwan.osm.pbf \
-docker-compose up import 
+docker-compose up import
 ```
 
 Variables will be remembered in `.env` if you don't have that file, and values in the file will be applied unless you manually assign them.
@@ -71,8 +71,8 @@ After startup is complete you can browse to [http://localhost:6789](http://local
 
 Importing the data needs a substantial amount of RAM in the virtual machine. If you find the import process (Reading in file: data.osm.pbf, Processing) being _killed_ by the Docker demon, exiting with error code 137, increase the Memory assigned to Docker (e.g. macOS: Docker Preferences / Windows: Docker Settings > Advanced > Adjust the computing resources).
 
-Docker copies log files from the virtual machine into the host system, their [location depends on the host OS](https://stackoverflow.com/questions/30969435/where-is-the-docker-daemon-log). E.g. the 'console-ring' appears to be a ringbuffer of the console log, which can help to find reasons for killings. 
+Docker copies log files from the virtual machine into the host system, their [location depends on the host OS](https://stackoverflow.com/questions/30969435/where-is-the-docker-daemon-log). E.g. the 'console-ring' appears to be a ringbuffer of the console log, which can help to find reasons for killings.
 
 While installing software in the containers and populating the database, the disk image of the virtual machine grows in size, by Docker allocating more clusters. When the disk on the host system is full (only a few MB remaining), Docker can appear stuck. Watch the system log files of your host system for failed allocations.
 
-Docker stores its disk image by default in the home directories of the user. If you don't have enough space here, you can move it elsewhere. (E.g. macOS: Docker > Preferences > Disk). 
+Docker stores its disk image by default in the home directories of the user. If you don't have enough space here, you can move it elsewhere. (E.g. macOS: Docker > Preferences > Disk).

Dockerfile

@@ -10,12 +10,12 @@ RUN apt-get update && apt-get install --no-install-recommends -y \
 # npm prefix to /usr/local, which breaks the install
 RUN npm set prefix /usr && npm install -g kosmtik
 
-WORKDIR /usr/lib/node_modules/kosmtik/ 
+WORKDIR /usr/lib/node_modules/kosmtik/
 RUN kosmtik plugins --install kosmtik-overpass-layer \
                     --install kosmtik-fetch-remote \
                     --install kosmtik-overlay \
                     --install kosmtik-open-in-josm \
-                    --install kosmtik-map-compare \ 
+                    --install kosmtik-map-compare \
                     --install kosmtik-osm-data-overlay \
                     --install kosmtik-mapnik-reference \
                     --install kosmtik-geojson-overlay \

README.md

@@ -13,7 +13,7 @@ are updated from each point release. They supersede the previous [XML-based styl
 
 # Installation
 
-You need a PostGIS database populated with OpenStreetMap data along with auxillary shapefiles. 
+You need a PostGIS database populated with OpenStreetMap data along with auxillary shapefiles.
 See [INSTALL.md](INSTALL.md).
 
 # Contributing
@@ -66,7 +66,7 @@ these often make it easier to customise, experience has shown that over-cleverne
 ## Database schema change (v4.x)
 
 The v4.x series includes [osm2pgsql lua transforms](https://github.com/openstreetmap/osm2pgsql/blob/master/docs/lua.md)
-and a hstore column with all other tags, allowing use of more OpenStreetMap data. Users need 
+and a hstore column with all other tags, allowing use of more OpenStreetMap data. Users need
 to reload their databases, v3.x compatibility is not maintained.
 
 There are over [300 open requests][issues], some that have been open for years.

RELEASES.md

@@ -28,16 +28,16 @@ Decide among the maintainers if a new release is due.
 Dear all,
 
 Today, $NEW_VERSION of the OpenStreetMap Carto stylesheet (the default
-stylesheet on the OSM website) has been released. Once changes are deployed 
-on the openstreetmap.org it will take couple of days before all tiles 
+stylesheet on the OSM website) has been released. Once changes are deployed
+on the openstreetmap.org it will take couple of days before all tiles
 show the new rendering.
 
 If the tile server admins have rolled out the new version, change it to:
 
   Today, $NEW_VERSION of the OpenStreetMap Carto stylesheet (the default
-  stylesheet on the OSM website) has been released and rolled out 
-  to the openstreetmap.org servers. It might take a couple of days 
-  before all tiles show the new rendering. 
+  stylesheet on the OSM website) has been released and rolled out
+  to the openstreetmap.org servers. It might take a couple of days
+  before all tiles show the new rendering.
 
 Changes include
 *A list of changes*