Highway area labels #642
Comments
Author: tom[at]compton.nu No, no, no. Tags describe what the object is, not how you'd like it rendered. That is up to the renderers. |
Author: andre-r[at]online.de But one developer in the chat had said, that the blue labels are bugs of the renderer and he'll fix it so i only should post this ticket as reminder. |
Author: bob[at]cakebox.net I think the best fix for this will be to only render names for highway=* area=yes if it's different from any connected way, I believe it should be possible to implement this in osmarender. |
Author: grand.edgemaster[at]gmail.com Possibly requiring osmarender:renderName=yes should be required for names for areas as a forced fallback? |
Author: bobkare (In [9574]) Fairly big osmarender change doing some refactoring on the rule parsing and falling back to simple BBOX center for areas with more than 150 nodes. Adds size-dependent rendering of names for large natural features (fixes #716) and suppresses labels for highway areas with same name as connected features (fixes #642). r8442@pastry: bob | 2008-06-24 21:48:19 +0200 |
Reporter: andre-r[at]online.de
[Submitted to the original trac issue database at 10.59pm, Wednesday, 16th January 2008]
You know the new feature of highway areas? Ok! But there is a little problem: The small blue label. I think, this should be activateable via a special tag because the labels are not needed in common causes. So default should be off. Example: labeled="no|yes"
The text was updated successfully, but these errors were encountered: