OpenStreetMap
Dear all,
Today, v4.25.0 of the OpenStreetMap Carto stylesheet (the default stylesheet on the Openstreetmap website) has been released. Once changes are deployed on openstreetmap.org it will take couple of days before all tiles show the new rendering.
Changes include:
-
Remove rendering of barrier=embankment (#4010)
Embankments are now commonly tagged with man_made=embankment or man_made=dyke
-
Remove rendering of barrier=kerb (#3969)
This feature is not similar to common barriers (fences and walls)
-
Remove boundary=protected_area fill color at low zoom levels (#3887)
Also changes protected area line and text to new @protected-area
-
Remove polygon fill rendering for barrier=hedge areas (#3844)
This makes the rendering consistent between walls and hedges as areas
-
Remove operator text label for most amenity=vending_machine (#3965)
Operator= label is still rendered for vending=public_transport_tickets
-
Add svg icon for parking=multi-storey + amenity=parking_entrance (#3599)
-
Fix syntax of font list and enable Armenian font (#3989)
- Use text-dy for wind generators only, not for other power=generator features (#3964)
- Use ST_PointOnSurface for bridge names (#3902)
- Use ST_PointOnSurface for text-poly-low-zoom (#3921)
- Use ST_PointOnSurface for roads-area-text-name (#3932)
-
Use ST_PointOnSurface for junctions (#3933)
These PRs complete the switch to ST_PointOnSurface for labeling all polygon features with text labels, which was began a year ago.
Minor code clean-ups:
- Remove way_pixels selection from bridge layer (#3950)
- Remove name from SQL select when unused (#3947)
- Combine line-barriers and area-barriers layers into one
Thanks to all the contributors for this release, including @Sjord (Sjoerd Langkemper), a new contributor.
For a full list of commits, see https://github.com/gravitystorm/openstreetmap-carto/compare/$v4.24.1…v4.25.0
As always, we welcome any bug reports at https://github.com/gravitystorm/openstreetmap-carto/issues and new contributions
Discussion
Comment from geowas on 5 February 2020 at 12:23
Thank you!
Comment from keithonearth on 16 February 2020 at 06:05
Thank you for all the hard work. I am sure it’s hard to please everyone, and I think it’s good that
barrier=kerbis not rendering the same as walls and fences, but I do think it’s useful to have it render. At some point I think we are going to need to map roads as areas, like we do withriverbankfor rivers. I think mappingbarrier=kerbis a good transition. At present it can give an idea of the with of roads, the existence of traffic islands, ease transition frommanmade=bridgeto the road mapped as a way, and probably more. In the future the traces could play a dual role of making the curb, and the extent of the roadway as an area.It seems like having it render as a lighter grey line would keep it distinct from fences and walls, but keep this useful feature on the visual representation of our data.