-
Notifications
You must be signed in to change notification settings - Fork 823
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Render tower:type=communication (always) #339
Comments
@math1985
Is there any result? Or is the tagging situation still at state that makes data unusable? |
No result yet, I made a new call to the Dutch community. |
so, any results jet? what makes the rendering of tower:type=communication (or man_made=tower if you don't want to render the other one) impossible? |
Still no change? There is a Less important masts get rendered without problems. |
@math1985 Are you still trying to discuss or is it time to decide? The PR should be rather easy to make. |
This really needs to be sorted out. I'm amazed that a tag with 35,000 uses gets rendered (even though they might not be used for communication), but the tower:type=communication tag with almost 100,000 uses is ignored. If there's a problem with incorrect tagging in one country that's a data problem and no reason not to render the tag elsewhere. |
One problem is deciding, the other is purely technical - does There's also very similar tag, which should be rendered the same way, probably on z16+, since it's for large structure - |
I think this issue shoud be closed and further discussion should move to #2556. |
This relates (at least in part) to Issue #181. In fact, my comment to it explains to whole thing - just wanted to open a separate issue for this in case as rendering of man_made=tower could mean different things, too:
"if there's a tower:type=communication in conjunction with man_made=mast then that icon is shown in OSM Mapnik (example: http://www.openstreetmap.org/node/2666366790).
I think this same rendering should happen when using man_made=tower (with tower:type=communication), which currently doesn't (http://www.openstreetmap.org/node/2489765793)."
The text was updated successfully, but these errors were encountered: