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

Electric poles are rendered but telephone poles are not #3215

Closed
jidanni opened this issue May 5, 2018 · 14 comments
Closed

Electric poles are rendered but telephone poles are not #3215

jidanni opened this issue May 5, 2018 · 14 comments

Comments

@jidanni
Copy link

jidanni commented May 5, 2018

Electric poles are rendered but telephone poles are not.
It is not fair.
https://wiki.openstreetmap.org/wiki/Talk:WikiProject_Telecoms#Telephone_poles_rendered.3F

@kocio-pl
Copy link
Collaborator

kocio-pl commented May 5, 2018

Currently there are only 64 of them:

https://taginfo.openstreetmap.org/tags/telecom=pole

I don't think they should be rendered until we're pretty sure that it's the way the community accepts as standard for tagging them.

@kocio-pl kocio-pl added this to the New features milestone May 5, 2018
@jidanni
Copy link
Author

jidanni commented May 5, 2018

I did not ask you to render telecom=pole.
I think you should render the recommended tag(s).

@kocio-pl
Copy link
Collaborator

kocio-pl commented May 5, 2018

While communication=pole is much better in that respect (2 587 uses), it lacks a wiki page, so please start with completing it.

@jidanni
Copy link
Author

jidanni commented May 5, 2018

OK I mentioned your comment there.

@sommerluk
Copy link
Collaborator

Rendering telephone pole without rendering the telephone line is cartographically ugly. communication=line is below 2000 usages. Furthermore, rendering communication=line would require a stable way to distinguish overland communication lines (on poles) from underground or underwater communication lines, because the latter we won’t render in a general map.

Electric poles are rendered but telephone poles are not.
It is not fair.

I do not follow this argument. Electric poles are usually bigger than communication poles, which makes them better landmarks, which might be a reason to treat them differently.

Even if usage numbers would be higher for this feature and tagging style would be stable, we would have to discuss if we want this in a general map at all (and how to render it differently from power lines). Maybe only at the highest zoom level…

We will see if the situation improves in the future. In the mean time I tent to close this issue.

@jidanni
Copy link
Author

jidanni commented May 5, 2018

In rural areas being able to locate and distinguish one is at electric pole #123 would be just as important a lifesaver as distinguishing one is at telephone pole #123. Also if one rams ones car into one, the effect is the same, electric pole or telephone pole...

@jidanni
Copy link
Author

jidanni commented May 5, 2018

A city person wouldn't understand. But in rural areas regular spaced numbered utility poles beat infrequent addresses and mileposts, simply a pure gold landmark reference, be it for reporting emergencies or other uses.

@flacombe
Copy link

flacombe commented May 5, 2018

I second the need of rendering poles.
Nevertheless, there is work to be done on telecom=* key first
See proposals like https://wiki.openstreetmap.org/wiki/Proposed_features/Telecom_local_loop intended to make telecom=* more useful and meaningful than communication=*

@dieterdreist
Copy link

dieterdreist commented May 5, 2018 via email

@matkoniecz
Copy link
Contributor

Is there any widely used, stable tagging scheme for that feature? Without that it is not viable to even consider rendering.

@matkoniecz
Copy link
Contributor

Closing for now without prejudice to a a new issue once clear tagging scheme is established and widely used.

@jidanni
Copy link
Author

jidanni commented Oct 8, 2019

Rendering telephone pole without rendering the telephone line is cartographically ugly.

Well currently electric poles are rendered without one needing to "clutter the map even more" and figure out where their wires go to map them. Especially as one's automobile needs to worry about banging into the poles, not the wires... Don't get me wrong: I would love to have their wires on the map too. (And I even wrote a program once to automatically add wires from a pole #1 to a pole #2... Worked great until one day I discovered that one can't just assume the wires actually always go that way...)

@jidanni
Copy link
Author

jidanni commented Oct 9, 2019

in rural areas regular spaced numbered utility poles beat infrequent addresses and mileposts, simply a pure gold landmark reference, be it for reporting emergencies or other uses.

Real life example: Often in the middle of the night I have to tell the
police "the (hunters') gunfire is coming from the (anonymous) road at electric pole 61.
Just turn off your rotating lights and wait in ambush at that junction and eventually they will have to come
out because it is a dead end road."

I am able to tell them electric pole 61 because I can see the electric
pole rendered on the map, and then I can use Query Feature on the OSM
website right panel to get the name of the pole.

However, for

even though they also have labels on them very useful for coordinating
emergency responses over the telephone or two-way radio, alas as they are hidden on the map. The user cannot see where to Query Feature. So even though looking across the valley he
can see where the criminals / chemical spill / etc. is, if he wishes to
be able to tell the police what pole number that is at, he has no other
choice to go over there in person to have a look. Putting himself in the
line of fire / danger.

Sure, for city slickers, bars and snack shops are all the craze, not to be cluttered by ho-hum utility poles. But when you are talking about rural areas, these boring items are the only "game in the book" (only things on the ground), and (being able to refer to them) could be lifesavers.

@matkoniecz
Copy link
Contributor

matkoniecz commented Oct 9, 2019

Closing for now without prejudice to a a new issue once clear tagging scheme is established and widely used.

And this is not a place to define a new tagging scheme or discuss why it is necessary.

Once a clear tagging scheme is established and widely used it may be discussed whatever this data should be rendered.

Repository owner locked and limited conversation to collaborators Oct 9, 2019
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

6 participants