Skip to content
This repository has been archived by the owner on Jul 24, 2021. It is now read-only.

Add rendering for areas tagged waterway=dam #3985

Closed
openstreetmap-trac opened this issue Jul 23, 2021 · 3 comments
Closed

Add rendering for areas tagged waterway=dam #3985

openstreetmap-trac opened this issue Jul 23, 2021 · 3 comments

Comments

@openstreetmap-trac
Copy link

Reporter: drnoble
[Submitted to the original trac issue database at 10.17pm, Friday, 26th August 2011]

Mapnik does not appear to render areas tagged as waterway=dam, although it does render on ways. This means smaller dams show up, but larger more detailed mapping does not. The Wiki page http://wiki.openstreetmap.org/wiki/Dam suggests a rendering of black outline with grey hatching, suggesting this might be a regression from a previous implementation

Similar to ticket #1985 but not a duplicate

Osmarender shows waterway=dam on an area as a thick black line e.g. http://www.openstreetmap.org/?lat=55.90788&lon=-4.72763&zoom=17&layers=O

@openstreetmap-trac
Copy link
Author

Author: katpatuka
[Added to the original trac issue at 5.36am, Sunday, 21st October 2012]

this ticket is open now for 14 months...!

@openstreetmap-trac
Copy link
Author

Author: RicoZ
[Added to the original trac issue at 11.28pm, Saturday, 9th November 2013]

Replying to [comment:1 katpatuka]:

this ticket is open now for 14 months...!

... and another 13 months now...

Would be really nice if it would work.

@openstreetmap-trac
Copy link
Author

Author: pnorman
[Added to the original trac issue at 6.02am, Monday, 11th November 2013]

The "mapnik" component in trac is for the old XML-based openstreetmap.xml stylesheets which are not deployed on OpenStreetMap.org. Since June the default style on OpenStreetMap.org has been openstreetmap-carto, which has its own issue tracker at https://github.com/gravitystorm/openstreetmap-carto/issues.

I'm going to go ahead and close this issue as wontfix to avoid people being confused by it and commenting on it instead of somewhere where it will effect the rendering on osm.org. Closing it doesn't mean the issue won't be fixed in openstreetmap-carto, just that this ticket is against old unmaintained software that has been replaced and this ticket has zero chance of being resolved.

There is an openstreetmap-carto ticket requesting a distinction between unpaved and paved surfaces at gravitystorm/openstreetmap-carto#227, but please read the roadmap at https://github.com/gravitystorm/openstreetmap-carto#roadmap to understand what issues are an immediate priority.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

1 participant