[OSM-dev] OpenStreetMap Carto release v4.6.0

[Matthijs Melissen]

Dear all,

Today, v4.6.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
- 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 very small water areas on low zoom
- Do not render small national parks and nature reserves
- Do not render ferries on z7
- Improve rendering for bus guideways
- For built-up areas, replace the external data on z8 and z9 by OSM data
- Do not render bicycle/motorbike parking icons to z17
- Render community_centre and social_facility areas in light yellow

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

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

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

Kind regards,
Matthijs Melissen

___
dev mailing list
dev@openstreetmap.org
https://lists.openstreetmap.org/listinfo/dev

Re: [OSM-dev] Andy Allan joining web site maintainers

[Matthijs Melissen]

On 10 July 2017 at 11:14, Andy Allan  wrote:
> Thanks Tom. My intentions for the next few months are to continue to
> do whatever I can to encourage new contributors. I've done a lot of
> refactoring recently which will help whoever tries to make code
> changes, but there's other things I think I can do too.

Currently, the openstreetmap-website is both responsible for the
openstreetmap.org web application, and for the API.

How hard would it be to separate these two functions, perhaps even
into two projects?

Would there be any advantages in doing so? Intuitively both functions
seem to be separate projects. I could imagine having two smaller
applications might make maintenance easier. It would also mean we
could, for example phase Ruby out for the app but not for the api or
vice versa. Lastly, making the website make only use of well-defined
api endpoints instead of interface with the database directly might
also makes things clearer.

Have there been any thoughts in this direction?

-- Matthijs

___
dev mailing list
dev@openstreetmap.org
https://lists.openstreetmap.org/listinfo/dev

[OSM-dev] OpenStreetMap Carto release v3.3.1

[Matthijs Melissen]

Dear all,

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

This version includes a single change:
* Fix a regression in intermittent waterways

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

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

___
dev mailing list
dev@openstreetmap.org
https://lists.openstreetmap.org/listinfo/dev

Re: [OSM-dev] PHP vs. Ruby in OSM projects

[Matthijs Melissen]

On 20 March 2017 at 17:22, Hakuch  wrote:
> What do you think, are there more php or more ruby developers in OSM ?
> Normally within open source projects people tend to use ruby, but many
> times I saw small projects coded in php. Iam currently unsure if I
> should start a new project with php/symfony or ruby/rails.

Many people are moving towards Django. For new projects, I think it's
the way to go.

-- Matthijs

___
dev mailing list
dev@openstreetmap.org
https://lists.openstreetmap.org/listinfo/dev

Re: [OSM-dev] Tile usage without proper identification

[Matthijs Melissen]

On 12 August 2016 at 19:11, Andy Allan  wrote:
> We've always allowed other people to use our spare capacity on the
> tileservers, but recently it's got completely out of hand. Most of the
> use of our tileservers has become developers looking for free maps,
> nothing to do with the rest of the project. Often these are commercial
> companies who are using our tileservers and selling their apps.
> Subsidising commercial companies isn't the best use of community
> donations and volunteer sysadmin time, when there are many alternative
> services (such as those run by CartoDB, Stamen, etc) that provide
> zero-cost map layers based on OSM data anyway.

I would tend to disagree.

Our Articles of Association state:

| 3. The Foundation is established for the purposes listed below:
|
| (1) encouraging the growth, development and distribution of free geospatial
| data; and
| (2) providing geospatial data for anybody to use and share.

To me this would include the distribution of geospational data in
compiled form, i.e. as a map.

I think it would be great if we had the resources to provide free maps
to anybody, including commercial companies. I realize there are
practical considerations that make this infeasible at the moment, but
I think it would be a nice target to aim for. The easier and cheaper
to use Openstreetmap-data, the more people will use it, which will
hopefully in turn lead to more contributors and better data.

I would also like to point out that there might be a conflict of
interest here between commercial operators of OpenStreetMap services,
and the rest of the community.

-- Matthijs

___
dev mailing list
dev@openstreetmap.org
https://lists.openstreetmap.org/listinfo/dev

[OSM-dev] OpenStreetMap Carto release v2.42.0

[Matthijs Melissen]

Dear all,

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

Changes include:
* Add rendering of amenity=charging_station and tourism=artwork
* Change icon of shop=department_store
* Increase font size for various labels
* Change playground color
* Various bug fixes

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

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

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

Kind regards,
Matthijs Melissen

___
dev mailing list
dev@openstreetmap.org
https://lists.openstreetmap.org/listinfo/dev

[OSM-dev] Release openstreetmap-carto v2.40.0

[Matthijs Melissen]

Dear all,

Today, v2.40.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:

* More consistent size of icon labels (bigger labels in most cases).
* Changed rendering of power lines on low zoom levels.
* Changed rendering of turning circles.
* Changed icon for libraries and book shops.
* Larger labels for place names.
* Various bug fixes.

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

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

-- Matthijs

___
dev mailing list
dev@openstreetmap.org
https://lists.openstreetmap.org/listinfo/dev

[OSM-dev] Release openstreetmap-carto v2.38.0

[Matthijs Melissen]

Dear all,

Yesterday, v2.38.0 of the openstreetmap-carto stylesheet has been
released and rolled out to the openstreetmap.org servers. It might
still take a couple of days before all tiles show the new rendering.

Changes include:

* Add rendering for natural=shoal, and natural=reef.
* Change of rendering of linear barriers: keep rendering of barrier
types chain, city_wall, embankment, ditch, fence, guard_rail,
handrail, hedge, kerb, retaining_wall, and wall, and drop rendering of
all other barrier types.
* Add rendering for social facilities.
* New icon for sports shops.
* Changed rendering of cutlines.
* Changed rendering for beach surfaces: add rendering for
surface=fine_gravel, surface=pebbles, and surface=pebblestone; drop
rendering for surface=peeples
* Various other bug fixes and minor improvements.

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

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

-- Matthijs

___
dev mailing list
dev@openstreetmap.org
https://lists.openstreetmap.org/listinfo/dev

[OSM-dev] Script for analyzing shop tagging

[Matthijs Melissen]

Hi all,

I have created a small script that shows how chain shops are tagged in
a given set of
OpenStreetMap-data.

This script creates wiki-output like this:
https://wiki.openstreetmap.org/wiki/Shop_tagging_in_The_Netherlands

The UK page is also based on this script:
https://wiki.openstreetmap.org/wiki/UK_Retail_Chains

As this might also useful for other countries/communities, I have now made this
script available online:

https://github.com/math1985/openstreetmap-statistics-tools/

The wiki-output on the pages above is generated by the shops-wiki.php
file. The scripts maxspeed-completeness.py and shops-completeness.py
in the repository might also be useful, they are used to get an idea
of the completeness of shop tagging and maxspeed tagging in a given
area, respectively.

-- Matthijs

___
dev mailing list
dev@openstreetmap.org
https://lists.openstreetmap.org/listinfo/dev

[OSM-dev] Release openstreetmap-carto v2.36.0

[Matthijs Melissen]

Dear all,

Today, v2.36.0 of the openstreetmap-carto stylesheet has been
released and rolled out to the openstreetmap.org servers. It might
still take a couple of days before all tiles show the new rendering.

Changes include:

* Major rewrite of road and railway rendering, as part of Mateusz
Konieczny's Google Summer of Code project. See
https://blog.openstreetmap.org/2015/10/30/openstreetmap-org-map-changing/
for more information.
* Added rendering of the following tags:
  - amenity=fountain
  - amenity=car_wash
  - historic=wayside_cross and man_made=cross
  - shop=bag
  - shop=outdoor
  - power=plant (labels)
* Changed rendering of the following objects:
  - Placenames (new algorithm for deciding what placenames to render
on low zoomlevels)
  - Road shields
  - Oneway arrows
  - Glaciers
  - Marina labels
  - Station labels
* Dropped rendering of the following tags:
  - amenity=car_sharing (not relevant for the general public)
  - shop=antique (use shop=antiques)
  - shop=betting (use shop=lottery or shop=bookmaker)
  - shop=delicatessen (use shop=deli)
  - shop=dive (use shop=scuba_diving)
  - shop=fish (use shop=seafood, shop=pet, shop=angling or amenity=fast_food)
  - shop=gambling (use shop=lottery, shop=bookmaker, or
leisure=adult_gaming_centre)
  - shop=insurance (use office=insurance)
  - shop=pharmacy (use office=pharmacy)
  - shop=bags (use shop=bag)
* Various other bug fixes and minor improvements.

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

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

-- Matthijs

___
dev mailing list
dev@openstreetmap.org
https://lists.openstreetmap.org/listinfo/dev

Re: [OSM-dev] Release openstreetmap-carto v2.36.0

[Matthijs Melissen]

On 30 October 2015 at 22:01, Matthijs Melissen <i...@matthijsmelissen.nl> wrote:
>   - shop=pharmacy (use office=pharmacy)

This should be amenity=pharmacy instead of office=pharmacy, of course.

-- Matthijs

___
dev mailing list
dev@openstreetmap.org
https://lists.openstreetmap.org/listinfo/dev

Re: [OSM-dev] Simplified osm2pgsql database dump available

[Matthijs Melissen]

On 12 July 2015 at 06:02, Paul Norman penor...@mac.com wrote:
 To help with some OpenStreetMap carto development work, I've created a dump
 of the rendering tables with certain features removed, for testing at low
 zoom.

Very useful, thanks a lot!

-- Matthijs

___
dev mailing list
dev@openstreetmap.org
https://lists.openstreetmap.org/listinfo/dev

[OSM-dev] Release openstreetmap-carto v2.30.0

[Matthijs Melissen]

Dear all,

Today, v2.30.0 of the openstreetmap-carto stylesheet has been rolled
out to the openstreetmap.org servers.

This version includes the following changes:
* New wetland rendering, including differentiation based on the wetland key.
* Added rendering for amenity=bicycle_parking.
* Added icons for historic=monument, amenity=court_house,
amenity=bench, amenity=waste_basket, man_made=hunting_stand,
shop=alcohol, shop=electronics, shop=furniture, shop=gift,
shop=jewelry/jewellery, shop=mobile_phone, shop=optician, shop=shoes,
shop=diy, shop=hardware, and shop=bicycle.
* Changed icon for shop=clothes, historic=archaeological_site,
highway=bus_stop, tourism=caravan_site, tourism=motel, power=generator
with generator:source=wind, and man_made=lighthouse.
* Added rendering for landuse=greenhouse_horticulture (rendered as
landuse=farmland).
* Changed rendering for man_made=cutline
* Added name labels to tourism=viewpoint, amenity=post_office,
natural=tree, amenity=bicycle_rental,  man_made=mast,
amenity=recycling, amenity=drinking_water, man_made=water_tower,
tourism=picnic_site, leisure=picnic_table, and leisure=slipway,
amenity=car_sharing (operator label) and amenity=atm (operator label).
* Added name labels to natural=cliff and man_made=embankment.
* Better water halos.
* Various bug fixes.

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

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

-- Matthijs

___
dev mailing list
dev@openstreetmap.org
https://lists.openstreetmap.org/listinfo/dev

Re: [OSM-dev] Kosmtik rendering issues

[Matthijs Melissen]

On 5 April 2015 at 13:21, nebulon42 nebulo...@yandex.com wrote:
 I started playing around with Kosmtik instead of TileMill. So far it works
 well, but I'm having two issues with the rendering:

 * Labels and symbols are cut off at metatile borders. As far as I understand
 there needs to be a metatile buffer. How can I set this in the config
 options?

I can confirm this issue, and I don't currently have a solution.

 * Compared to openstreetmap.org my local tiles are more blurry. What can
 cause this? Or did I miss osm.org switching to high-res tiles?

This I cannot reproduce. Is everything more blurry, or certain elements only?

-- Matthijs

___
dev mailing list
dev@openstreetmap.org
https://lists.openstreetmap.org/listinfo/dev

[OSM-dev] Release openstreetmap-carto v2.28.0

[Matthijs Melissen]

Dear all,

Yesterday, v2.28.0 of the openstreetmap-carto stylesheet has been released
and rolled out to the openstreetmap.org servers.

This version includes the following changes:
* The tags amenity=dentist and amenity=townhall are now rendered.
* The tag natural=lake, which has fallen in disuse, is no longer rendered.
* New icons for amenity=fast_food, amenity=police,
amenity=fire_station, amenity=bier_garden, amenity=theatre,
amenity=drinking_water.
* Slightly improved icons for amenity=restaurant, amenity=bar,
amenity=cafe, amenity=embassy, tourism=picnic_site,
tourism=picnic_table, amenity=prison, historic=memorial.
* Waterways with intermittent=yes are now rendered dashed.
* The tag highway=proposed is rendered less prominently.
* Slightly change building colour and outline.
* Labels for natural=glacier,sand,scree,shingle,bare_rock are now
rendered from lower zoomlevels.

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

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

-- Matthijs

___
dev mailing list
dev@openstreetmap.org
https://lists.openstreetmap.org/listinfo/dev

Re: [OSM-dev] Release openstreetmap-carto v2.28.0

[Matthijs Melissen]

On 8 February 2015 at 18:26, Antje 2...@minoa.li wrote:
 Something doesn’t sound quite right about the roads at lower zoom levels 
 (8-11) because some villages are only reached by tertiary or minor roads: the 
 update seems to give an impression that the villages are not connected to the 
 broader road network.

You are right that this does not look right, it is indeed a bug. We
will try to solve this problem as soon as possible.

-- Matthijs

___
dev mailing list
dev@openstreetmap.org
https://lists.openstreetmap.org/listinfo/dev

[OSM-dev] Release openstreetmap-carto v2.27.0

[Matthijs Melissen]

Dear all,

Today, v2.27.0 of the openstreetmap-carto stylesheet has been
released and rolled out to the openstreetmap.org servers.

Changes include:

* The following tags are now rendered: amenity=food_court,
amenity=doctors, natural=scree, natural=shingle, natural=bare_rock,
leisure=water_park, leisure=miniature_golf.
* The tags leisure=golf_course is now rendered with an icon.
* The following tags are no longer rendered: natural=desert,
military=barracks, and landuse=field are no longer rendered. The tags
natural=sand, landuse=military, and landuse=farmland might in some
cases be replacements.
* New icons for amenity=pharmacy, amenity=atm, amenity=bank,
shop=bakery, and amenity=cinema.
* Slightly improved icon for amenity=hospital, tourism=museum,
amenity=recycling, tourism=camping, leisure=playground, places of
worship.
* Private leisure=playground and amenity=recycling are now rendered transparent
* Prison areas are now rendered.
* Various bug fixes.

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

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

-- Matthijs

___
dev mailing list
dev@openstreetmap.org
https://lists.openstreetmap.org/listinfo/dev

Re: [OSM-dev] Release openstreetmap-carto v2.26.1

[Matthijs Melissen]

Dear all,

Today, v2.26.1 of the openstreetmap-carto stylesheet has been released
and rolled out to the openstreetmap.org servers.

This version only includes one change:
* Areas tagged with amenity=place_of_worship and no building tag are
rendered again.

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

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

-- Matthijs

___
dev mailing list
dev@openstreetmap.org
https://lists.openstreetmap.org/listinfo/dev

[OSM-dev] Release openstreetmap-carto v2.26.0

[Matthijs Melissen]

Dear all,

Today, v2.26.0 of the openstreetmap-carto stylesheet has been
released. It will be rolled out to the openstreetmap.org servers soon.

Changes include:

* Buildings are now rendered in a much lighter colour
* Airport labels are rendered in a different colour
* The tag natural=mud is rendered from z10 instead of z13
* City names no longer hide country and state names on low zoom levels
* The tag natural=saddle is now rendered
* Areas tagged as tourism=attraction are no longer rendered in a special way
* Various bug fixes

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

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

-- Matthijs

___
dev mailing list
dev@openstreetmap.org
https://lists.openstreetmap.org/listinfo/dev

Re: [OSM-dev] [meta] Problem with reply to messages from mailing list on Gmail

[Matthijs Melissen]

On 11 December 2014 at 17:32, Mateusz Konieczny matkoni...@gmail.com wrote:
 Is there some known fix for this issue (so reply to e-mail for dev ml will
 work like
 replying to tagging mailing list) beyond stop using gmail, start using X?

In Gmail, under Settings-General, you can change 'Default reply
behaviour' to 'Reply all'. Of course, that will also lead to undesried
behaviour in some circumstances, but I tend to use 'Reply all' more
often than 'Reply'.

-- Matthijs

___
dev mailing list
dev@openstreetmap.org
https://lists.openstreetmap.org/listinfo/dev

Re: [OSM-dev] Release openstreetmap-carto v2.25.0

[Matthijs Melissen]

On 11 December 2014 at 15:16, Andy Allan gravityst...@gmail.com wrote:
 If anyone has any advice, I'm all ears.

I'm happy Christoph started this discussion. I agree with most things
that have already been said.

I think the main problem is that the time from design to deployment of
changes is currently too long, especially for changes that correct
bugs introduced earlier.

Andy mentions that he thinks that the pull requests he has merged are
not the most important ones. Of course, everyone considers different
things important. Some of the things we did I think were quite
important, such as shop rendering, mid-zoom path rendering, and the
landcover labels. But I think the main result so far is that the code
is much more consistent (although not perhaps not always easier to
understand), in particular related to roads and labels. Also, the
issues Andy referred to as important are mainly graphical design
issues, which I'm not very good at. It might be an idea to attract
some people who are good at design.

Furthermore, we cannot expect large changes from new developers, so I
think it is entirely reasonable for new developers to make pull
requests that seem trivial and might not be the most important. Still
I think merging them quickly is important - new developers now often
wait months before their trivial changes get merged, which likely
discourages them from contributing more.

I think it's important to have someone to guide development effort,
and keeps the larger picture in mind. I don't think Andy has even
indicated before which issues are the most important to him. I think
it'd be more useful for Andy to give high-level comments, and take
parts in discussions like this one, than to worry about individual
colors or zoom levels or syntax errors in pull requests. Perhaps he
also could document some of his vision in the CONTRIBUTING.md file

I do think it's good that commits are being reviewed. We quite often
catch issues in pull requests, so allowing everyone to commit might
not be the best idea. Also, we have people with different areas of
expertise: cartography, software development, database design, etc. So
the discussions are in my opinion usually a good thing - not only do
they improve the map, but I also have learned a lot from them.

My suggestion would be to allow collaborators to merge PRs of others
(but not their own). Perhaps we could also require a week for feedback
before they are being merged. Many PRs have received useful feedback.
I also don't mind extending the list of 'collaboratos' (currently Paul
Norman, Mateusz, Andy and me) if others are interested. Perhaps we
could try this policy for two months, and then evaluate whether we
need a stricter or even more lenient policy?

Of course, Andy can still do a quick high-level review when deploying
a new version. I don't think deploying automatically, as in the
Osmarender case, is a good idea. Deploying quickly is in my opinion
not as important as merging quickly. Deploying once per month, or even
less frequently provided we have a worldwide testing server, would be
fine with me.

If we let more people commit, we can also consider creating an
acceptance branch, or use one-week feature stops (like JOSM does)
before deploying, so that we don't introduce too much bugs into the
main website.

Finally, I also agree that we do need a testing server with worldwide
data. Testing worldwide is impossible on a consumer grade pc, so we
cannot expect contributors to arrange this themselves. Especially for
the low zoom levels, being able to test worldwide is important. I'm
not sure who we should contact to discuss this?

Kind regards,
Matthijs

___
dev mailing list
dev@openstreetmap.org
https://lists.openstreetmap.org/listinfo/dev

[OSM-dev] Release openstreetmap-carto v2.25.0

[Matthijs Melissen]

Dear all,

Today, v2.25.0 of the openstreetmap-carto stylesheet has been
released and rolled out to the openstreetmap.org servers. It might
take up to 48 hours before all tiles show the new rendering.

Changes include:

* New style for marsh/wetland rendering.
* Added rendering for marsh/wetland and mud labels.
* Changed rendering of national parks boundaries.
* Changed rendering of theme park boundaries.
* Country and state labels are now only rendered for areas of a minimum size.
* Airport icons are now also rendered on zoom 11, 12 and 13.
* Various bug fixes.

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

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

-- Matthijs

___
dev mailing list
dev@openstreetmap.org
https://lists.openstreetmap.org/listinfo/dev

Re: [OSM-dev] Mapnik-Glitch Schwarzwald

[Matthijs Melissen]

On 17 November 2014 16:13, Tom Hughes t...@compton.nu wrote:
 and plotted it on a map:


 http://maps.compton.nu/view?http://download.compton.nu/tmp/schwarzwald.json

 and it all looks perfectly sane.


Note that the label is also missing from the place where it should be,
i.e., within this multipolygon. Could this be a label placement bug in
Mapnik?

-- Matthijs

___
dev mailing list
dev@openstreetmap.org
https://lists.openstreetmap.org/listinfo/dev

Re: [OSM-dev] Mapnik-Glitch Schwarzwald

[Matthijs Melissen]

On 16 November 2014 15:28, Roland Olbricht roland.olbri...@gmx.de wrote:
 http://yevaud.openstreetmap.org/11/1076/704.png
 contains the string Schwarzwald (which doesn't belong there)
 but there is no element with a tag of any key with value Schwarzwald
 anywhere near, c.f.
 http://overpass-turbo.eu/s/64L


Strangely enough, on orm, the string is Schworzwald:
http://orm.openstreetmap.org/11/1076/704.png

-- Matthijs

___
dev mailing list
dev@openstreetmap.org
https://lists.openstreetmap.org/listinfo/dev

[OSM-dev] Release openstreetmap-carto v2.24.0

[Matthijs Melissen]

Dear all,

Today, v2.24.0 of the openstreetmap-carto stylesheet has been
released and rolled out to the openstreetmap.org servers. It might
take up to 48 hours before all tiles show the new rendering.

Changes include:

* Improve legibility of shop names.
* Better rendering of admin borders.
* Behind-the-scenes changes of (some) PNG icons to SVG.
* Labels for building names, addr:housename and addr:housenumber are
now prioritized by building size.
* Various bug fixes.

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

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

-- Matthijs

___
dev mailing list
dev@openstreetmap.org
https://lists.openstreetmap.org/listinfo/dev

[OSM-dev] Release openstreetmap-carto v2.23.0

[Matthijs Melissen]

Dear all,

Today, v2.23.0 of the openstreetmap-carto stylesheet has been
released and rolled out to the openstreetmap.org servers. It might
take up to 48 hours before all tiles show the new rendering.

Changes include:

* Various small rendering changes to icon labels.
* New icons for place of worship, windmill, hostel, and camping; minor
icon changes for cinema, recycling, and hairdresser.
* The tag tourism=bed_and_breakfast is no longer rendered - please use
tourism=guest_house instead.
* Tertiary roads are now rendered yellow from z12 instead of z13.
* The tag shop=mall is now rendered like landuse=retail.
* Barriers, level crossings, and mini roundabouts no longer block text
from appearing.
* The places of worship of Jehova's witnesses are no longer rendered as a cross.
* The rendering of highway=track areas has been changed.
* Large national parks and nature reserves now have their name
rendered along the outline.
* There is no longer a gap rendered between adjoining polygons of the same type.
* Various other bug fixes.

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

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

-- Matthijs

___
dev mailing list
dev@openstreetmap.org
https://lists.openstreetmap.org/listinfo/dev

[OSM-dev] Release openstreetmap-carto v2.22.0

[Matthijs Melissen]

Dear all,

Today, v2.22.0 of the openstreetmap-carto stylesheet has been
released and rolled out to the openstreetmap.org servers. It might
take up to 48 hours before all tiles show the new rendering.

Changes include:

* Major changes in landcover labelling. Landcover labels are now
rendered oblique, and in the colour of the landuse they belong to. The
minimum zoom level on which the labels appear, as well as their font
size, now depends on the size of the landcover object. All rendered
landcover labels now have their name rendered. The new rendering might
highlight tagging errors, so all mappers are invited to inspect their
local area for possible problems. Note that adding the name tag to the
landuse area rather than to a node generally yields better results.
* Changes in island and islet labelling. Islets (place=islet) now have
their name rendered. The minimum zoom level on which islands and
islets appear now depends on the island/islet size. The area size can
only be used when the island/islet is tagged as area, not as point, so
tagging islands/islets as area is recommended. Note that smaller
place=island objects can now be retagged as place=islet without losing
their label in the main renderer.
* Bus stops now have their name rendered.
* Apart from bridge=yes, we now also render the bridge keys boardwalk,
cantilever, covered, low_water_crossing, movable, trestle, and
viaduct. When applicable, bridges can now be retagged using the
correct key.
* Ferries now have their name rendered (when applicable), and
overlapping ferry lines now look better.
* Gates are no longer rendered on zoom level 15.
* Streams, ditches and drains are now rendered slightly wider.
* Long place names are now wrapped.
* Aerodrome names are now wrapped.
* Various bug fixes.

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

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

-- Matthijs

___
dev mailing list
dev@openstreetmap.org
https://lists.openstreetmap.org/listinfo/dev

Re: [OSM-dev] Release openstreetmap-carto v2.19.0

[Matthijs Melissen]

On 27 August 2014 19:02, Tom Hughes t...@compton.nu wrote:
 On 27/08/14 18:49, Matthijs Melissen wrote:

 Today, v2.19.0 of the openstreetmap-carto stylesheet has been
 released. It will be rolled out to the openstreetmap.org servers in
 one of the next days.

 Actually it probably won't be rolled out just yet as we have a degraded disk
 array in one of the tile servers that I want to get fixed before we put any
 more load on it.

I deliberately tried being as vague as possible on the schedule :).

In any case thank you for your work! Server maintenance is mainly
invisible, but as http://git.openstreetmap.org/chef.git/ shows, a lot
of work is going on behind the scenes.

-- Matthijs

___
dev mailing list
dev@openstreetmap.org
https://lists.openstreetmap.org/listinfo/dev

[OSM-dev] Release openstreetmap-carto v2.18.0

[Matthijs Melissen]

Dear all,

Today, v2.18.0 of the openstreetmap-carto stylesheet has been released.

Changes include:

* Remove transparency from certain landuse tags
(https://github.com/gravitystorm/openstreetmap-carto/pull/792)
* Render lake names on lower zoom levels
(https://github.com/gravitystorm/openstreetmap-carto/pull/816)
* Rewrite code for road ordering, resolving various road layering bugs
(https://github.com/gravitystorm/openstreetmap-carto/pull/626)
* Various bug fixes

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

We welcome any bug reports at
https://github.com/gravitystorm/openstreetmap-carto/issues.

-- Matthijs

___
dev mailing list
dev@openstreetmap.org
https://lists.openstreetmap.org/listinfo/dev

Re: [OSM-dev] [OSM-talk] Upcoming openstreetmap-carto changes (nature_reserve highway=services)

[Matthijs Melissen]

On 25 July 2014 15:30, Dave F. dave...@madasafish.com wrote:
 highway=services (ie service stations where you can get a drink/meal etc) as
 an area are rendering as a high level layer hiding detail such as car parks.
 Can this be put at a lower level?

I created an issue for that here:
https://github.com/gravitystorm/openstreetmap-carto/issues/764

 leisure=nature_reserve
 Used to have an infill of text 'NR'. that's been removed but not replaced by
 anything, it's now just a faint border, at all levels, which makes it
 extremely difficult to distinguish. According to this
 https://github.com/gravitystorm/openstreetmap-carto/commit/c505f51a930fe00977af8ae7fc2d58a36a659ff1
 it was meant to render the same as national parks but doesn't appear to
 work: http://www.openstreetmap.org/#map=16/51.4624/-2.4755

I think it does render the same as national parks, but apparently that
is not enough. A issue for this exists already:
https://github.com/gravitystorm/openstreetmap-carto/issues/563

-- Matthijs

___
dev mailing list
dev@openstreetmap.org
https://lists.openstreetmap.org/listinfo/dev

[OSM-dev] How to use render_list

[Matthijs Melissen]

Dear all,

Can anyone explain me how to use render_list?

I run the program as follows:

render_list -f -n 4 -s /var/run/renderd/renderd.sock -m benchmk_test.txt

This gives me the following output:

debug: init_storage_backend: initialising file storage backend at:
/var/lib/mod_tile
Rendering client
Starting 4 rendering threads


renderd itself gives the following output:

renderd[6415]: DEBUG: Got incoming connection, fd 9, number 1
renderd[6415]: DEBUG: Got incoming connection, fd 10, number 2
renderd[6415]: DEBUG: Got incoming connection, fd 11, number 3
renderd[6415]: DEBUG: Got incoming connection, fd 12, number 4

However, render_list does not terminate. Isn't it supposed to? I am
also not sure where I can find the rendered tiles.

Thanks in advance.

-- Matthijs

___
dev mailing list
dev@openstreetmap.org
https://lists.openstreetmap.org/listinfo/dev

Re: [OSM-dev] How to use render_list

[Matthijs Melissen]

Thank you, that does the job.

-- Matthijs

On 19 February 2014 13:14, Frederik Ramm frede...@remote.org wrote:
 Hi,

 On 02/19/2014 12:49 PM, Matthijs Melissen wrote:
 render_list -f -n 4 -s /var/run/renderd/renderd.sock -m benchmk_test.txt

 You misunderstood -m. This flag is for specifying which one, of
 potentially several configured, styles to use when rendering.

 Assuming your text file contains space-separated x/y/z values, what you
 want is  benchmk_test.txt (since render_list reads from stdin).

 Bye
 Frederik

 --
 Frederik Ramm  ##  eMail frede...@remote.org  ##  N49°00'09 E008°23'33

 ___
 dev mailing list
 dev@openstreetmap.org
 https://lists.openstreetmap.org/listinfo/dev

___
dev mailing list
dev@openstreetmap.org
https://lists.openstreetmap.org/listinfo/dev

[OSM-dev] Mechanically setting name tag of Naptan data

[Matthijs Melissen]

Dear all,

In Birmingham UK, all bus stops have been imported from a governmental
source called Naptan, but during the import, the name tag has not been
set. I am considering adding the name tag, by setting it to something
like:

camelcase(naptan:Street) + ' / ' + naptan:CommonName

That way, the name tag in OSM will match the name on the bus stop.

I am currently discussing whether this change is desirable on the
local mailing list [1]. Apart from whether this change is desirable,
what would be the easiest way to achieve it?

I suppose it's best to download the data with xapi, use a scripting
language to create a change set based on this data, and then upload
the change set? Is there someone who has already done something
similar, and can perhaps give me some demo code on to how walk through
the xapi output and how to to create the changeset? Or would there be
an easier way to achieve this?

Thanks in advance.

-- Matthijs

[1] 
https://lists.openstreetmap.org/pipermail/talk-gb-westmidlands/2013-November/001462.html

___
dev mailing list
dev@openstreetmap.org
https://lists.openstreetmap.org/listinfo/dev