Modify

Opened 7 years ago

Closed 7 years ago

Last modified 7 years ago

#14487 closed enhancement (wontfix)

Discourage using wires=* on power relations and frequency on passive power elements

Reported by: francois.lacombe Owned by: team
Priority: normal Milestone:
Component: Core validator Version:
Keywords: power, wires, frequency Cc:

Description

Dear all,

As recently discovered, using wires=* key on power relations and frequency on power lines or cables can introduce redundancy and mistaking of osm data.

As suggested on wiki (https://wiki.openstreetmap.org/wiki/Key:wires), wires refers to a physical characteristic of power lines and a validation warn should rise when used in combination with route=power on a (logical) relation.

Secondly, frequency=* refers to operation of active components of networks (radio, telecoms, power...). On power networks, it shouldn't be used on power=line, power=cable ways or power=terminal, power=insulator, power=tower, power=pole nodes.
The given reason is they are all passive elements and aren't designed for a dedicated frequency

Thank you in advance to add this to validation rules :)

Attachments (0)

Change History (6)

comment:1 by Klumbumbus, 7 years ago

frequency is marked as additional optional key for cable and line at their wiki pages

Last edited 7 years ago by Klumbumbus (previous) (diff)

comment:2 by francois.lacombe, 7 years ago

Hi Kumbumbus,

You're right, this topic is currently discussed on tagging ML.
I wasn't aware this would engage a debate but it may be interesting to wait until a conclusion.

Anyway, wires=* point sounds consistent with wiki doesn't it ?

in reply to:  2 comment:3 by Klumbumbus, 7 years ago

Milestone: 17.03

Replying to francois.lacombe:

to wait until a conclusion.

Yes, should be clarified first.

Anyway, wires=* point sounds consistent with wiki doesn't it ?

Yes, semms so, I'll consider the other topics in this milestone.

comment:4 by francois.lacombe, 7 years ago

Hi,

It seems this proposal doesn't get a direct concensus on tagging ML
I think this ticket should be closed until we vote a more complex proposal on wiki

Sorry for disturbance :)

comment:5 by Klumbumbus, 7 years ago

Keywords: validation removed
Milestone: 17.03
Resolution: wontfix
Status: newclosed

The hint in the wiki about relations was just added this week. And there are 8316 relations with wires=*. So, wontfix for now until the tagging schema is clarified by the community.

comment:6 by Klumbumbus, 7 years ago

(link to tagging malinglist for reference)

Modify Ticket

Change Properties
Set your email in Preferences
Action
as closed The owner will remain team.
as The resolution will be set.
The resolution will be deleted. Next status will be 'reopened'.

Add Comment


E-mail address and name can be saved in the Preferences .
 
Note: See TracTickets for help on using tickets.