OpenStreetMap

kocio's diary

Recent diary entries

OpenStreetMap Carto release v4.16.0

Posted by kocio on 19 October 2018 in English (English)

Dear all,

Today, v4.16.0 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 show the new rendering.

Changes include

  • Changing societal amenities color to less intensive
  • Adding rendering for natural=strait
  • Adding rendering for leisure=track on lines
  • Adding icon for amenity=vehicle_inspection
  • Adding icon for leisure=sports_centre + sport=swimming and leisure=swimming_area
  • Adding icon for tourism=gallery
  • Changing color for aeroway=apron in aerodromes
  • Moving amenity=post_box to z19+
  • Moving amenity=atm to z19+
  • Replacing icon for information=tactile_model
  • Ordering amenity_lines by layer
  • Small documentation and code fixes

Thanks to all the contributors for this release including dryo, a new contributor.

For a full list of commits, see https://github.com/gravitystorm/openstreetmap-carto/compare/v4.15.0...v4.16.0

As always, we welcome any bug reports at https://github.com/gravitystorm/openstreetmap-carto/issues

OpenStreetMap Carto release v4.15.0

Posted by kocio on 21 September 2018 in English (English)

Dear all,

Today, v4.15.0 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 show the new rendering.

Changes include

  • Changing gastronomy objects color to orange (affects restaurant, fast_food, ice_cream, food_court, bar, cafe, nightclub, pub and biergarten)
  • Changing farmland and societal amenities (like school, hospital etc.) colors to fit better into the overall color systematic
  • Adding rendering for man_made=wastewater_plant and man_made=water_works
  • Adding icon for man_made=storage_tank and man_made=silo
  • Adding icon for amenity=bicycle_repair_station
  • Adding icon for leisure=amusement_arcade
  • Adding icon for shop=bookmaker
  • Adding icon for shop=trade and shop=wholesale
  • Adding rendering for attraction=water_slide
  • Rendering most of the road links thinner (affects trunk_link, primary_link, secondary_link)
  • Moving manors to z16+
  • Fixing missing country labels on z4 (affects Canada, Russia and Greenland)
  • Small code and icon fixes

Thanks to all the contributors for this release.

For a full list of commits, see https://github.com/gravitystorm/openstreetmap-carto/compare/v4.14.0...v4.15.0

As always, we welcome any bug reports at https://github.com/gravitystorm/openstreetmap-carto/issues

OpenStreetMap Carto - my thoughts on development (part 2)

Posted by kocio on 28 August 2018 in English (English)

First part was about why dense (well mapped) areas should be treated better than outdoor/rural areas. Today I will discuss rendering objects according to their size.

There are many types of maps and one of the most important property is their preferred use. OSM Carto has no special goals of this kind, it is meant to be general style. Unfortunately, it's harder to develop because of this.

Putting all the things on the map according to their "importance" is misleading, because without clear goal it's hard to tell what system should we apply to show some items more prominently than the others. In practice it seems that people tend to think mostly like "I want to find x" or "it was always like this". But finding is better done by apps and we show many object types, so sticking to the old solutions will just highlight lack of clear rules eventually.

So - what could be the universal property of objects that we could use on the map? I think this is their size.

In a matter of fact, it is used a lot already. We use initial zoom levels to not show benches at the world level, because then the map would look more or less like this:

screenshot_2018-08-28 amenity bench tagi openstreetmap taginfo

https://taginfo.openstreetmap.org/tags/amenity=bench#map

Of course, it is not always clear what size are we talking about. For example building can be as small as a shed or as big as a factory. But at least we know that there are no buildings of the size of a country.

What helps in a lot of cases is typical size and typical usage.

Sometimes we have a special hint, like with monuments and memorials, supermarkets and convenience shops or rivers and streams. They are just defined as big/small objects, so it's easier to render them properly, because it's the mapper who takes the bigger part of responsibility. But most of the time we have to check that for example beach resort is typically quite big area and act accordingly.

There is also second type of hints: typical usage. That means that if object A can be a part of some other object (B), we should render A later then B, even if that's not clear looking at their size alone. That's the case of towers and castles for example - in general height is useful direct hint how early towers should be rendered. We could do the same with defensive towers, but they (and city gates) are frequently a part of the castle. So it makes sense to always show them later, because when we see the castle, we can initially skip all the details. They will be visible when we zoom in - that means when we're interested in more details. The castle is a generalization for all these elements and showing defensive towers from the same zoom level would break this generalization and make visual noise.

Look at this example on z15-z17. You could also notice that the castle has no name label initially (z15) - it's typically smaller than town and because of that it shouldn't be too loud:

screenshot_2018-08-28 openstreetmap screenshot_2018-08-28 openstreetmap 1 screenshot_2018-08-28 openstreetmap 2

https://www.openstreetmap.org/#map=16/51.9571/21.2338

Of course there are single, standalone defensive towers and city gates around the world. But it's safer to show them at least one step later than castles, because they can be a part of such castle and we don't know it just by looking at tags.

There are also some other hints - for example hierarchy of objects. This is the case of rendering quarters: we can just observe that they are higher level objects than neighborhood and lower than suburbs, and we're basically done with the subject, even if don't know their typical size or typical usage.

So please, mind the size...

OpenStreetMap Carto - my thoughts on development (part 1)

Posted by kocio on 23 August 2018 in English (English)

This entry is a copy of my comment in a discussion on some of the OSM Carto rendering ideas. It's so general, that I think it makes sense to show it for more people. I have some more thoughts on this subject and I hope I will write them down too.


I believe the main obstacle for better coexistence of big cities and outdoor rendering is #1957 "equalizing" ticket being unresolved.

I think about "WMAs" (well-mapped areas), which are located in the big cities where mappers were active, that they make the biggest difference. They start to be very rich, because this is the reality, which was not well covered by mappers just a few years ago. We could rely on this incompleteness up to some point and render whatever was available without critically rethinking the whole system for years. But this is no longer true and the WMAs begin to be drastically more dense than outdoor areas. This is nobody's fault, it's just the unexpected consequence of the success of OSM in gathering all kind of data. Of course, we might stay with what we were showing before, but it's just closing eyes to avoid noticing the constant change of OSM data. Something like taking the snapshot of some past moment and refusing to take more current ones, just because it's more familiar for cartographers than trying to face these new challenges.

I like the outdoor rendering and when it doesn't hurt, I'm happy to make it also rich. There are places where we outperform typical (if not all) outdoor maps with details, like for example here:

screenshot_2018-08-23 openstreetmap

https://www.openstreetmap.org/#map=17/47.35137/8.49157

But without some kind of equalizer (making rendering aware of a place context), it's absolutely not possible to find a visual balance between rural/urban environments. And when this inevitable moment of clash comes, I tend to care more about proper depicting WMAs than the outdoor.

Why?

  1. There are already many outdoor maps in the wild, including some based on OSM data (Hike&Bike, OpenTopoMap, cycling maps etc.), which are better suited for such tasks as hiking, precisely because they are very limited by design. General, rich map is just not a competitor for them. And I don't even mention primary solution for such activities, which are Garmin-like devices packed with vector maps and geolocalization included.

  2. Choosing the outdoor advantage is not just trying to play the wrong game, it also means clutter for WMAs with no hope for being readable. And these are the places where a lot of people might be interested in looking at the map. Rendering problem in the middle of Andes is still a problem, but for example visual mess in London is just much worse.

  3. The last argument is that there are no special maps of WMAs. There might be hand-crafted maps of specific places, but no other general map style to reflect data richness. I believe they deserve to be shown as good as it's possible.

OpenStreetMap Carto release v4.14.0

Posted by kocio on 17 August 2018 in English (English)

Dear all,

Yesterday, v4.14.0 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.

Changes include

  • Added text-repeat-distance for waterways
  • Added text-repeat-distance for railways
  • Added icon for leisure=bowling_alley
  • Added icon for leisure=outdoor_seating
  • Added icon for leisure=bird_hide
  • Added icon for shop=video
  • Added icon for shop=paint
  • Added icon for shop=massage
  • Increased casing width of tertiary road on z12
  • Standard text halo for fitness_centre and fitness_station
  • Updated Docker images definitions
  • Small documentation updates

Thanks to all the contributors for this release.

For a full list of commits, see https://github.com/gravitystorm/openstreetmap-carto/compare/v4.13.0...v4.14.0

As always, we welcome any bug reports at https://github.com/gravitystorm/openstreetmap-carto/issues

Developer wanted for CartoCSS

Posted by kocio on 15 August 2018 in English (English)

I recently got worried about CartoCSS project, which we use as a Mapnik configuration parser in OSM Carto. There's only one person available for a long time and I feel this is dangerous, because he has officially stepped down recently and if he looses any interest in it, there would be not even basic support, like merging code or making the release.

If there's somebody ready to look at the code (JavaScript) and join the project even to just keep it alive in standby mode, I would be very glad. Here is nebulon42 story and what he expects to "share the keys" (or even pass the baton) in the project:

https://github.com/mapbox/carto/issues/495#issuecomment-412987738

OpenStreetMap Carto release v4.13.0

Posted by kocio on 23 July 2018 in English (English)

Dear all,

Today, v4.13.0 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 show the new rendering.

Changes include:

  • Increased shield distances on roads
  • Added icon for shop=ticket
  • Added icon for shop=houseware
  • 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
  • Small documentation and code fixes

Thanks to all the contributors for this release.

For a full list of commits, see https://github.com/gravitystorm/openstreetmap-carto/compare/v4.12.0...v4.13.0

As always, we welcome any bug reports at https://github.com/gravitystorm/openstreetmap-carto/issues

OpenStreetMap Carto release v4.12.0

Posted by kocio on 22 June 2018 in English (English)

Dear all,

Today, v4.12.0 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 show the new rendering.

Changes include:

Major changes

  • Dropped subpixel accuracy for areas, which includes tuning some database indexes. When deployed, it might speed up reading data.

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)
  • 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
  • Added rendering of lock_name
  • Ditch and drain name labels are rendered with some offset
  • Pixel aligned ford icon
  • Made amenity=shelter icon brown
  • Finer man_made=pier width rendering
  • Rendering living street tunnels different from residential
  • Added rendering of overground power=cable like power=line
  • Small documentation and code fixes

Thanks to all the contributors for this release including Adamant36 and M1dgard, new contributors. I also like to thank nebulon42 who left our team due to a change of his priorities for all the work on this style and the tools we're using!

For a full list of commits, see https://github.com/gravitystorm/openstreetmap-carto/compare/v4.11.0...v4.12.0

As always, we welcome any bug reports at https://github.com/gravitystorm/openstreetmap-carto/issues

OpenStreetMap Carto release v4.11.0

Posted by kocio on 11 May 2018 in English (English)

Dear all,

Today, v4.11.0 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 show the new rendering.

Changes include

  • Fixed office/amenity conflict
  • Brightened built-up areas on z12
  • Refurbished natural=spring icon
  • Added rendering for amenity=police and amenity=fire_station areas
  • Added rendering of amenity=nursing_home
  • Added rendering of amenity=childcare
  • Added rendering of amenity=driving_school
  • Added area rendering for amenity=bus_station
  • Added area rendering of amenity=taxi
  • Made highway=traffic_signals icon less obtrusive
  • Moved barriers to higher zoom level
  • Hiding railway=platform with location=underground, tunnels and covered=yes
  • Small documentation and code fixes

Thanks to all the contributors for this release.

For a full list of commits, see https://github.com/gravitystorm/openstreetmap-carto/compare/v4.10.0...v4.11.0

As always, we welcome any bug reports at https://github.com/gravitystorm/openstreetmap-carto/issues

OpenStreetMap Carto release v4.10.0

Posted by kocio on 20 April 2018 in English (English)

Dear all,

Today, v4.10.0 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 show the new rendering.

Changes include

  • Adding rendering for historic=castle and historic=manor
  • Adding rendering office=* as dots + names
  • Adding rendering for waterway=waterfall
  • Adding place=square name rendering for nodes
  • Adding rendering for big natural=bay
  • Adding rendering for leisure=beach_resort
  • Adding rendering for amenity=parking_space
  • Adding rendering of aerialway=zip_line
  • Adding rendering for shop=bed
  • Adding rendering for shop=video_games
  • Adding halo to roads on z6 and z7
  • Extending intermittent waterbody rendering to landuse=basin
  • Moving highway=mini_roundabout rendering to higher zoom level
  • Dropping waterway=derelict_canal rendering
  • Small documentation and code fixes

Thanks to all the contributors for this release, including d3d9, doktorpixel14 and hikemaniac, new contributors.

For a full list of commits, see https://github.com/gravitystorm/openstreetmap-carto/compare/v4.9.0...v4.10.0

As always, we welcome any bug reports at https://github.com/gravitystorm/openstreetmap-carto/issues

OpenStreetMap Carto release v4.9.0

Posted by kocio on 23 March 2018 in English (English)

Dear all,

Today, v4.9.0 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 show the new rendering.

Changes include

Major changes

  • A bug where closed ways with natural=cliff or natural=tree_row were not rendering has been fixed. This required fixing a transform bug. The fix will apply to all objects when they are created in OSM, but there is no migration for existing databases. Deployments will have to decide if the effects are serious enough to require them to reload the database.

Changes

  • Adding place=square name rendering
  • Adding rendering for different types of towers and masts
  • Making gardens to use grass color with plant nursery pattern
  • Adding rendering for intermittent water bodies
  • Give oceans outline and simplify shapefiles on z0-7
  • Simplify (generalize) admin borders
  • Move natural=grassland and landuse=meadow earlier
  • Start rendering aerialway name
  • Adding icons for amenity=bbq, amenity=shower, leisure=sauna and advertising=column
  • Adding special icons for shop=dairy, shop=medical_supply and shop=music
  • Move amenity=toilets to higher zoom levels
  • Fixing some SVG icons artifacts
  • Make military=danger_area font dark pink and slanted
  • Changing rendering for construction=steps to distinguish it from roads
  • Changing label colour of private parking
  • Small documentation and code fixes

Thanks to all the contributors for this release, including james2432, Penegal and jragusa, new contributors.

For a full list of commits, see https://github.com/gravitystorm/openstreetmap-carto/compare/v4.8.0...v4.9.0

As always, we welcome any bug reports at https://github.com/gravitystorm/openstreetmap-carto/issues

OpenStreetMap Carto release v4.8.0

Posted by kocio on 23 February 2018 in English (English)

Dear all,

Today, v4.8.0 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 show the new rendering.

Changes include

  • Made military area rendering less prominent
  • Adding rendering for historic=wayside_shrine
  • Adding rendering for historic=fort
  • Adding rendering for amenity=public_bath
  • Adding rendering for shop=chocolate
  • Adding rendering for barrier=toll_booth (nodes)
  • Adding rendering barrier=log
  • Adding rendering for amenity=waste_disposal
  • Moving tourism-boundary under barrier layer
  • Docker: run osm2pgsql in slim mode
  • Fix operator precedence for hstore queries
  • Small documentation fixes

Thanks to all the contributors for this release, including jbelien, MKuranowski, andrzej-r and Zverik, new contributors.

For a full list of commits, see https://github.com/gravitystorm/openstreetmap-carto/compare/v4.7.0...v4.8.0

As always, we welcome any bug reports at https://github.com/gravitystorm/openstreetmap-carto/issues

OpenStreetMap Carto release v4.7.1

Posted by kocio on 31 January 2018 in English (English)

Dear all,

Today, v4.7.1 of the openstreetmap-carto stylesheet (the defaultstylesheet 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.

This is a bugfix release, the only change is a code fixing this rendering problem: https://github.com/gravitystorm/openstreetmap-carto/issues/3043

Thanks to all the contributors for this release.

For a full list of commits, see https://github.com/gravitystorm/openstreetmap-carto/compare/v4.7.0...v4.7.1

As always, we welcome any bug reports at https://github.com/gravitystorm/openstreetmap-carto/issues

OpenStreetMap Carto release v4.7.0

Posted by kocio on 26 January 2018 in English (English)

Dear all,

Today, v4.7.0 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 show the new rendering.

Changes include

  • Adding icon for tourism=apartment
  • Adding icon for leisure=firepit
  • Yellow background for amenity=arts_centre
  • Start rendering natural=heath earlier
  • Start rendering entrances
  • Changing tourism=picnic_site icon colour to green
  • Move emergency=phone to higher zoom level
  • Rendering seasonal waterways as intermittent
  • Update Noto fonts to Phase III
  • Fine-tuning of bridge labels
  • Documentation changes and updates

Thanks to all the contributors for this release.

For a full list of commits, see https://github.com/gravitystorm/openstreetmap-carto/compare/v4.6.0...v4.7.0

As always, we welcome any bug reports at https://github.com/gravitystorm/openstreetmap-carto/issues

Planned rendering changes of protected areas

Posted by kocio on 3 December 2017 in English (English)

I'd like to change the rendering of protected areas on osm-carto (the style which is used as a default map layer on the main OSM.org website). That proved to be a complex problem, however thanks to the comments from the community on the issue tracker and Talk list I see the general plan what to do. This entry is just a slightly edited message I sent to the list.

screenshot-2017-12-3 openstreetmap Exhibit A: Adirondack Park disaster...

TL;DR summary: I think that for now we should render all the existing tags, but make some of them appear earlier to encourage smooth migration to a more precise scheme.

General findings

  1. As I currently understand it, nature reserve is always a type of protected area, to begin with.

    We were talking on osm-carto ticket with some people about private reserves and even when someone told me "it's not about protection!" this term was used immediately in the same sentence (or in the next one). =} I guess they meant "it's voluntary and not formal", but still it's intended as a protection of nature, so it's just a special, weak type of protection.

  2. The problem seems to be for a mapper to be more precise, since a typical survey can reveal a sign with a name "XYZ nature reserve". However this is not about just a name.

    Boundaries are not visible on the ground easily, so a mapper who draw them has to use some other sources and I believe there are more informations available. Otherwise the area shape is probably not verifiable, which would be bad anyway. And I think all of them are areas, not the points (node would mean probably "here is the protection area, but exact shape is not shown at the moment"), so boundary is also a sure thing.

  3. The name tag leisure=nature_reserve states that it's about leisure (which of course might be for a given object), but it's always about protection. So even if the value has merits, this key assumption is wrong in general and misses more important property (boundary=nature_reserve has only 35 uses).

  4. Another problem is lack of coherent definition of protection (other than numbers) and lack of high-level classes.

    The numbers seem to be derived from IUCN scheme, but wider: only categories 1-6 are IUCN-based and I don't know about the rest.

    Especially class 7 is interesting for us: "nature-feature area: similar to 4. but without IUCN-level.", so i guess it's for all the non-IUCN classified nature reserves. Probably most of the time this should be clear from the boundary shape source.

    It would be good to have more standardized subtags for common features:

    • "nature" - protection_object=* is the same mess as numbers, when talking about hierarchy levels, so maybe some subtag like "nature_reserve=yes" would be useful
    • "private" owner type (not the access type) - governance_type=private_landowner would be great (if really used...)
    • "voluntary" - but that might be clear from the lack of government or international authorities influence

Tagging solutions

In summary, we have 3 popular but overlapping types now:

  1. leisure=nature_reserve (77 264)
  2. boundary=national_park (16 583)
  3. boundary=protected_area (62 016)

Their general properties and relations:

  1. has a wrong key, but nice value name, and is a subtype of 3.
  2. has a nice value name and a proper key, it's also subtype of 3.
  3. is very broad with precise, but not so common name, it also has subtypes, which are useful for official classification, but are not clear for all the other types of conservation

Therefore I would advice to:

  1. Discourage leisure=nature_reserve and make it a subtag of boundary=protected_area (if needed, otherwise just use a protect_class=7 or other class if known), like:

    • nature_reserve=yes - 2 uses
    • protected_area=nature_reserve - 22 uses
    • protected_area=nature - 61 uses
  2. Drop boundary=national_park, since it's easy to identify them all and they are equivalent for boundary=protected_area + protect_class=2 anyway.

Rendering proposition

For rendering I would show all of them as currently, just using different zoom levels, starting from z8 currently (this might change in the future, of course):

  • z8+: national parks and wilderness areas (both are big by definition)
  • z9+: important natural protected areas (class 1-6, with hatched 1a probably)
  • z10+: other natural protected areas (class 7, maybe also 12, 14 and 97-99)
  • z11+: protected areas without class (if we know they're nature related) and leisure=nature_reserve

This is just a rough sketch, however it has some nice properties:

  • all the existing schemes are visible (boundary=national_park can be dropped later)
  • more important objects are rendered first
  • less precise tagging is rendered later

Another important factor might be their size (so for example small national parks wouldn't be shown on z8) and a name (when the name is not tagged, push them later), but it needs a lot of worldwide testing.

Usage stats

taghistory 6 taghistory 7 (class 4 is the most popular) taghistory 8

OpenStreetMap Carto release v4.5.0

Posted by kocio on 17 November 2017 in English (English)

Dear all,

Today, v4.5.0 of the openstreetmap-carto stylesheet (the default stylesheet on openstreetmap.org) has been released.

Changes include:

Major changes

  • Cleaning up low zoom levels (z5-z7):
    • Rendering roads from z6 instead of z5
    • Rendering national parks from z8 instead of z7
    • Rendering railways from z8 instead of z7
  • Changing parking color from yellow to gray

Changes

  • Unified rendering of leisure=fitness_station and leisure=fitness_centre
  • Rendering of military=bunker
  • 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

Thanks to all the contributors for this release.

For a full list of commits, see https://github.com/gravitystorm/openstreetmap-carto/compare/v4.4.0...v4.5.0

As always, we welcome any bug reports at https://github.com/gravitystorm/openstreetmap-carto/issues

OpenStreetMap Carto release v4.4.0

Posted by kocio on 20 October 2017 in English (English)

Dear all,

Today, v4.4.0 of the openstreetmap-carto stylesheet (the default stylesheet on openstreetmap.org) has been released.

Changes include:

Major changes

  • Rendering inland water areas and labels from z0
  • Rendering island and islet labels earlier

Changes

  • Rendering of amenity=marketplace
  • 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
  • Rendering icon for slipway ways
  • Better minimal distance between housenumbers
  • Moving aeroways to their own layer
  • Creating amenity POI categories
  • Some other documentation and code cleaning

Thanks to all the contributors for this release, including tpikonen, a new contributor.

For a full list of commits, see https://github.com/gravitystorm/openstreetmap-carto/compare/v4.3.0...v4.4.0

As always, we welcome any bug reports at https://github.com/gravitystorm/openstreetmap-carto/issues

OpenStreetMap Carto release v4.2.0

Posted by kocio on 25 August 2017 in English (English)

Dear all,

Today, v4.2.0 of the openstreetmap-carto stylesheet (the default stylesheet on openstreetmap.org) has been released.

Changes include:

Major changes

  • Water color and default water text color are changed to be more visible
  • Medium zoom level (z8-z12) rework:
    • Landuses colors are faded and some of them are visible earlier
    • Most of the man related landuses are combined into one color and more visible
    • More important roads are better legible

Changes

  • Leaf type rendering in woods and forests
  • Cemetery symbols are not so dense now and Muslim cemetery has its own symbol
  • Rendering of amenity=ferry_terminal
  • Plaque rendering is now different and moved to z19
  • Rendering railway labels
  • Smaller line spaces in labels
  • Junction names on areas
  • Area color for railway=station is the same as for railways
  • Database performance tuning available for Docker
  • Different patterns and all remaining icons moved to SVG
  • Some documentation and code cleaning

Thanks to all the contributors for this release, including littlebtc and giggls, new contributors. Special thanks for rrzefox for testing major changes on his server.

For a full list of commits, see https://github.com/gravitystorm/openstreetmap-carto/compare/v4.1.0...v4.2.0

As always, we welcome any bug reports at https://github.com/gravitystorm/openstreetmap-carto/issues.

OpenStreetMap Carto release v4.1.0

Posted by kocio on 30 July 2017 in English (English)

Dear all,

Today, v4.1.0 of the openstreetmap-carto stylesheet (the default stylesheet on openstreetmap.org) 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

  • Malls are no longer rendered as dots (bug fix)
  • Special icon for shop=tyres
  • Airports rendering changes: removing clutter on z10 and moving name labels under the icon
  • Switching forest, scrub and quarry patterns to SVG

In this release we're also introducing Docker-based development environment, which makes it much easier to preview rendering changes before they are deployed on the servers.

Be warned that there's a change in our release plans: compatibility with v3.x series is no longer maintained from now on, so database reload is needed to keep up with current style changes. Some of them can be however backported, especially if you're using hstore-enabled database already.

Thanks to all the contributors for this release. Special thanks go to MaestroGlanz and daganzdaanda for a new icon.

For a full list of commits, see https://github.com/gravitystorm/openstreetmap-carto/compare/v4.0.0...v4.1.0

As always, we welcome any bug reports at https://github.com/gravitystorm/openstreetmap-carto/issues.

OpenStreetMap Carto release v2.45.1

Posted by kocio on 3 December 2016 in English (English)

Dear all,

Today, v2.45.1 of the openstreetmap-carto stylesheet (the default stylesheet on openstreetmap.org) 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.

This is a bugfix release restoring two icons:

  • memorial
  • tobacco shop

Thanks to all the contributors for this release.

For a full list of commits, see https://github.com/gravitystorm/openstreetmap-carto/compare/v2.45.0...v2.45.1

As always, we welcome any bug reports at https://github.com/gravitystorm/openstreetmap-carto/issues.