Skip to content
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

Masts are not always for communication #1225

Closed
sanderd17 opened this issue Jan 14, 2015 · 2 comments
Closed

Masts are not always for communication #1225

sanderd17 opened this issue Jan 14, 2015 · 2 comments

Comments

@sanderd17
Copy link

The tag man_made=mast only says something about the physical look of the structure, not it's function. See http://wiki.openstreetmap.org/wiki/Tag:man_made%3Dmast

Next to communications, it can also be used for lightening (of football stadions f.e.), or for sports like popinjay archery.

Currently, the icon communications.p.20.png is used for all man_made=mast objects, that icon has a visualisation of "broadcasting" next to the mast view.

According to the wiki, it's advised to add tower:type=communication if the mast is used for communication purposes.

So I propose to use a version without broadcasting for a simple man_made=mast, and a version with broadcasting when tower:type=communication is added.

I made a simple icon of a mast, based on the communications icon, but where I just coloured the broadcasting stuff away. I hope it's good enough.
mast

@HolgerJeromin
Copy link
Contributor

related to #339

@matkoniecz matkoniecz added this to the Bugs and improvements milestone Jan 14, 2015
@pnorman pnorman modified the milestones: 3.x - Needs upgrade to mapnik or openstreetmap-carto.style, Bugs and improvements Jan 16, 2015
@nebulon42
Copy link
Contributor

I thought too that this needs upgrade, but it seems that tower:type is in the rendering database already (openstreetmap-carto.style#L137).

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

Successfully merging a pull request may close this issue.

6 participants