[water] mapnik dosn't use width tag for waterway=canal #1721
Comments
Author: bmog Replying to [ticket:1721 bmog]:
Hi, this bug is still present and very annoying. Was this bug simply forgotten or is there a more fundamental problem ? |
Author: Ldp The width tag is visually hard to implement. What should render at the transition from sections with width tag and those without, or with different values? All that could conceivably be done now is to make a sudden change in the width of the rendered line, which is aesthetically displeasing. A major technical hurdle is the fact that the source data can be in different geographical projections, some in projected values, some in latlong values. Line widths are done in pixels. Somehow the geographical value would need to be translated to a pixel value. In short, I don't see support for width=* tags in the foreseeable future. |
Author: cmuelle8 Replying to [comment:3 Ldp]:
Why not just adjust the rendering in ranges, this way you don't have to translate width to an exact pixel value? E.g.
If this is not implemented people "tag for renderers", e.g. tag small man_made canals as waterway=stream, instead of doing it right. It's understandable since a small canal carrying wood in the medieval ages should not appear visually the same as a large canal built for barges or similar. Thanks a ton to whomever steps up and fixes this bug in the mapnik stylesheet. |
Author: math1985 This is difficult to accomplish. For example, what should we do where the width changes? Explicitly mapping the outline would be the best solution. I will close this as wontfix. |
Reporter: bmog
[Submitted to the original trac issue database at 1.20am, Sunday, 19th April 2009]
For example:
http://openstreetmap.org/?lat=50.6042&lon=9.46831&zoom=17&layers=B000FTF
The text was updated successfully, but these errors were encountered: