OpenStreetMap Carto (default map on OSM.org)

I still plan to start rendering them. It just took some time to make research which proved that there’s no clear mapping between them and natural reserves, so they can’t be be unified, and after that there were a lot of other, more clear issues.

If you could do something with coding or testing, it would help a lot.

Tomasz-W (active OSM Carto contributor) diary entry “Make OSM-Carto brighter”:

https://www.openstreetmap.org/user/Tomasz_W/diary/45047

New release v4.16.0 is out:

https://www.openstreetmap.org/user/kocio/diary/45180

New release v4.17.0 is out with more changes than usually. Some of them are quite visible, like rendering natural areas from z5, dots for gastronomy objects on z17 or new icons for memorial subtags:

https://www.openstreetmap.org/user/kocio/diary/46993

New release v4.18.0 is out (it will probably start to roll out on OSMF servers this night):

https://www.openstreetmap.org/user/kocio/diary/47284

Highlights include rendering healthcare tag scheme, changing natural=scrub color, changing landuse=allotments color and pattern, adding rendering for natural=cape and something special for the winter - rendering leisure=ice_rink. :slight_smile:

If anyone needs current set of low zoom OSM Carto tiles, Paul Norman offers them for download (from level 0 to 6, 8, 9 or 10):

http://legolas.paulnorman.ca/prerender/

https://lists.openstreetmap.org/pipermail/dev/2019-January/030488.html

New release v4.19.0 is out and as always I suspect it will start to roll out on OSMF servers tonight:

https://www.openstreetmap.org/user/kocio/diary/47491

It adds rendering for boundary=protected_area, makes boundaries of all the protected areas less aggressive, renders few icons for amenity=vending_machine, adds more barrier icons and (once again in a short time) changes allotments color and pattern - it’s fixing few more problems than previous pattern and I hope it will stay for a long time. It includes also many more additional tweaks and fixes than usually.

Thanks!

Well done team. The boundary=protected_area looks great and one I have been keen to see.

@nevw: We are discussing currently what features are missing on the map outside the Europe and in rural places, what would you propose?

@kocio: for me, about the only problem is that the State Forestry boundaries need to be rendered.
The boundary becomes indistinguishable when the wooded areas, which normally extend beyond the SF boundary, are also mapped and this commonly occurs.
I thought this was fixed with the latest change to render boundary=protected_area, because I have been tagging them as relations, type=boundary, boundary=protected_area, landuse=forest, protection_title=State Forest as I feel that state managed forestry areas are resources-protected-areas mostly class 14 I guess and rarely a nature-protected-area class 6
https://wiki.openstreetmap.org/wiki/Tag:boundary%3Dprotected_area
But looking at how others map the state forests I see most don’t map them as boundary=protected_area as I do so I am a bit uncertain in my thoughts for the moment.

I would like to see the landcover scheme rendered in due course https://wiki.openstreetmap.org/wiki/Landcover

I have mentioned this topic on the Talk.au (Australian talk group) to see if others have more to add regarding rendering deficiencies.

Great! Please let us know here or in the proper ticket (if possible):

https://github.com/gravitystorm/openstreetmap-carto/issues/3635

New release (v4.20.0) is out, the most important things are progressive lightening major buildings, rendering aboriginal areas, dropping rendering of leisure=common and restoring missing oneway arrows for tracks and paths - here is a full announcement:

https://www.openstreetmap.org/user/kocio/diary/47716

Look at , the Carto renderer’s font used an incorrect glyph for the character “men” in the (Simplified) Chinese name of the city of Xiamen (the character above the mouse pointer in the screenshot)

Please report it there:

https://github.com/gravitystorm/openstreetmap-carto/issues

As I try to file a ticket, I realized that it was already reported by issue #2862 and turns out to be a subset of the problem of issue#2208 https://github.com/gravitystorm/openstreetmap-carto/issues/2208

There is a new PR on the Openstreetmap-carto Github page which would switch this style to water polygons instead of land polygons.

However, some users reported problems with the simplified water polygon shapefiles when this change was attempted in 2016. We believe the problem is no longer present, because the German map style is using these shapefiles without problems, but it needs testing. If you were one of the affected users, please try out the change on your server.

The branch is available at:
https://github.com/jeisenbe/openstreetmap-carto/tree/ocean-polygons

New PR:
https://github.com/gravitystorm/openstreetmap-carto/pull/3694

Old issue:
https://github.com/gravitystorm/openstreetmap-carto/issues/2101

New release (v4.21.0) is out and waits for deployment, read about the changes here:

https://www.openstreetmap.org/user/pnorman/diary/155756

New release is on hold, since it contains regressions, wait for v4.21.1:

https://github.com/gravitystorm/openstreetmap-carto/issues/3736

OpenStreetMap Carto release v4.22.0 is available for more than a week already:

https://www.openstreetmap.org/user/pnorman/diary/390578